Cortex
A standalone coding agent for working directly with real projects, terminals and development workflows.
Open Cortex at my.crtx.dev.
No configured instances: my.crtx.dev immediately opens localhost:7331, so a normal single local installation needs no launcher setup.
One configured instance: it opens that named instance directly. Two or more: it shows the instance catalog, with each entry storing a name, domain/IP and optional port.
The configuration remains browser-local and can be opened directly even when normal launcher navigation redirects. The planned my.gantry.cv app drawer links into these per-project launchers rather than copying their instance registries.
An agent that works where the code actually lives.
Cortex is a self-hosted coding-agent application built around real workspaces rather than an isolated chat box. A session can point at a project, use a terminal, run tools and keep its own conversation state while you remain in control of what workspace the agent is allowed to see.
The interface is intentionally closer to a practical development tool than a generic assistant. Multiple sessions can stay open at once, running work remains visible, token use is surfaced, and conversations persist independently of a particular terminal window. The point is to shorten the path from deciding what needs to change to actually inspecting, testing and modifying the project.
Cortex remains useful on its own. Gantry integrations shorten hand-offs; they do not make Cortex depend on a monitoring server, IDE or backend platform.
Useful capability without mandatory complexity.
The project stays focused on its own job; the surrounding Gantry tools remain optional.
Point a session at a real directory or use the configured default root. Historical conversations retain their recorded workspace identity rather than silently switching to whatever directory is open later.
Agent tasks use the host tooling and shell environment available to Cortex, so builds, tests, git inspection and project-specific commands live in the same workflow.
Sessions are durable rather than disposable browser state, so a task can be resumed without reconstructing the entire context from scratch.
Run Cortex in the foreground for the smallest workflow or install it as a user service when it should stay available independently of a terminal.
Start with the shortest path.
Advanced deployment or integration features appear only when the workflow actually needs them.
- 01
Start Cortex locally and open
my.crtx.dev; with no launcher configuration it goes directly tolocalhost:7331. - 02
Choose a workspace or use the configured default root, then keep one session per independent task rather than mixing unrelated changes.
- 03
Let Cortex inspect, build and test through the host tools you already use; review the result in the same session.
- 04
When Watchpost or Warden knows the relevant machine, use that hand-off so Cortex opens on the right deployment instead of manually reconstructing the context.
Connections that remove real hand-off friction.
Each product already owns one side of these workflows. The integration exists to remove duplicate navigation, setup or context.
Warden
Warden is the broader self-hosted development workspace while Cortex is the focused agent experience. Use Warden when you want editor, terminals, users and agent work in one remote IDE; use Cortex when the agent itself is the primary surface. Shared session and terminal primitives can improve both without making either a wrapper around the other.
Explore Warden →Watchpost
Watchpost can turn an unhealthy machine into an actionable hand-off instead of a dead-end alert. The intended flow is “Open Cortex” in a new tab while Watchpost stays open as the incident view; later the hand-off can include symptoms and recent telemetry so the investigation starts with useful evidence already attached.
Explore Watchpost →Trestle
Cortex is a natural place to investigate a Trestle-backed application because it can work on the application code and run the same build, test and diagnostic commands a developer would use. There is no hidden dependency: Trestle simply becomes another concrete system Cortex can help you operate.
Explore Trestle →Where Cortex earns its place.
Use Cortex on a workstation or NUC as a fast agent surface over repositories you already work with.
Keep Cortex running on an always-on machine and reach it through a stable hostname or the my.* launcher.
Open Cortex from a Watchpost incident to investigate a service, configuration or code problem without replacing the monitoring context.
Explore Cortex.
Project-specific installation, commands and release details live on the project site.