Raw Terminal Feed
$ curl api.gcode.dev/run
› 200 OK · 812ms
$ node agent.js --once
› task complete (no retry logic)
As projects evolve, the command center shifts layouts, archives historical traces, and maintains transparent telemetry — so you can inspect not just outputs, but the full execution journey.
Adaptive Layouts
Raw Terminal Feed
$ curl api.gcode.dev/run
› 200 OK · 812ms
$ node agent.js --once
› task complete (no retry logic)
API Uplink
POST /run — single endpoint
auth: static key
retries: none
Raw terminal, direct API calls.
Historical Traces
Every key engineering moment is a node on the fiber. Select one to replay its historical trace — commit, latency impact, and the exact lines that changed.
gcode ▸ historical trace ▸ genesis
Execution Journey
Outputs are the surface. Toggle the X-ray and the workspace card splits into its isometric strata — client, orchestration, memory — with a single trace following one click from the button all the way to the database and back.
CLIENT · UI
API ORCHESTRATION
# embeddings · pgvector
id uuid pk
embedding vector(1536)
project_id fk → vaults.id
ivfflat · lists=128 · cosine
VECTOR MEMORY · SCHEMA