Know where the project stands.
00 / THE OBSERVER
A window into
the work.
Inspect the selected project while Codex directs its work. Studio brings the Plan, jobs, evidence and runtime observations into one read-only window.
Scroll to follow the observer. Open a node or a window field for its own detail.
01 / PLAN AND JOBS
Know what is current.
See what comes next.
The current revision, task scope and job state remain visible. Selecting a view changes what you inspect; it does not start work or revise the Plan.
The scene stays connected as its view changes. Drag the open scene to explore its depth.
02 / THE EVIDENCE TRAIL
Open the result.
Follow what supports it.
Trace the output to its task, selected material and recorded checks. A historical receipt and a fresh source observation answer different questions.
The scene stays connected as its view changes. Drag the open scene to explore its depth.
03 / RUNTIME OBSERVATIONS
Declared support.
Measured readiness.
Tools, workers and compute have distinct observations. Studio shows what the connected engine reports; catalogue membership alone does not establish execution.
The scene stays connected as its view changes. Drag the open scene to explore its depth.
04 / CONNECTIONS AND RETURN
One persistent engine.
A view you can return to.
Studio stays visible and accessible on Windows. Open, minimise and restore the observer; use Codex for project changes and connection configuration.
The scene stays connected as its view changes. Drag the open scene to explore its depth.
THE OBSERVER STAYS AVAILABLE
Open. Minimise. Return.
Studio runs on persistent local Windows with Codex Desktop Stable or Beta. The engine can serve authorized clients in the background; humans use Studio to navigate and inspect.
Read the Studio guide ↗This website illustration is not connected to your engine or project.