A little context before you begin.
Terminus products are under development. This guide explains their intended roles and the planned development workflow, rather than documenting a released installer or stable API. Installation steps, supported languages, commands, and integration details will depend on a published release.
Who this guide is for
- Developers exploring an integrated engineering environment
- Teams interested in repeatable build and test workflows
- Engineers evaluating the direction of foundational development tools
Set yourself up for a useful walkthrough.
- 01
Identify your project's language, operating system, toolchain, and existing build process.
- 02
Decide which problem matters first: editing, code understanding, workflow automation, or runtime integration.
- 03
Review each product's development status and discuss compatibility or early access with the team.
- 04
Use an isolated sample project for any future evaluation and confirm data access and execution permissions before enabling integrations.
One step at a time.
Choose a step to see its purpose, the expected outcome, and an example.
Start in the workspace
Terminus IDE is intended to be the place where a developer opens a project, edits source files, and works with diagnostics and integrated tools.
The workspace provides a consistent view of the project and the work being changed.
See how the pieces connect.
This diagram is a conceptual view of responsibilities, not a specification of released interfaces or a requirement that every task use every component.
- 01
Workspace
IDE: source code and project work
- 02
Context
Cortex: code understanding
- 03
Workflow
Conductor: ordered development tasks
- 04
Foundations
Core + Kernel: services and execution
Terminus IDE
The integrated workspace for editing, project navigation, and development tooling.
Terminus Cortex
The contextual intelligence layer for understanding code and assisting development decisions.
Terminus Conductor
The orchestration layer for coordinating build steps, tests, and other development tasks.
Terminus Core
The shared service and communication foundation intended to connect ecosystem tools.
Terminus Kernel
The lower-level runtime direction for process execution, memory isolation, and native subsystems.
A thoughtful process makes a difference.
Start with a small project
For a future evaluation, choose a non-production project with an existing build and test process so you can compare behavior clearly.
Keep engineering review in the loop
Review suggested code, inspect diagnostics, and run relevant checks. Assistance should support your judgment about correctness.
Confirm boundaries first
Ask about filesystem access, process permissions, model or network services, logs, and supported integrations for the release being evaluated.
A few useful answers.
Can I download or run Terminus today?+
The five Terminus products are marked as in development. This site does not publish a stable installer, release date, or setup commands. Ask the team about the current roadmap and any evaluation opportunities.
Are Core and Kernel the same product?+
Their planned responsibilities differ. Core focuses on shared platform services and communication. Kernel focuses on lower-level runtime and process execution. Specific interfaces may evolve during development.
Does Cortex automatically make every code change?+
Cortex is described as contextual intelligence and automated assistance. The exact permissions, review controls, and feature set need to be confirmed for a release. Review and verification remain part of the intended workflow.
Which languages, extensions, and operating systems are supported?+
A final compatibility matrix has not been published on this website. Share your language, operating system, and toolchain requirements with the team instead of assuming compatibility from a concept illustration.
Make it specific to your team.
Share your workflow, environment, and requirements with Apex Tech Labs.