Live sessions on every surface
Watch every prompt, tool call, and diff stream in real time — desktop, web portal, iOS and Android. The session runs on your machine; the view follows you.
Your agents. Your environment.
OpenAI Codex,steerable at fleet scale.
Glueprint spawns the same codex CLI you already run — your ChatGPT login, your AGENTS.md, your config — and adds what the terminal can't: live sessions on every device, mid-turn steering, approvals from your phone, parallel worktrees, and schedules.
Your provider account. Your code. A workspace to bring them together.
AG-401The integration01 / 05
Your chosen agent.A shared workspace.
Codex is a first-class native adapter in Glueprint — not a wrapper script, not a re-implementation, and not routed through the generic ACP harness. Four things make it feel native.
Everything below works with the Codex CLI you have today — no migration, no new account for the model, no lock-in. Uninstall Glueprint and your terminal workflow is exactly as it was.
Note
Your Codex environment stays authoritativeYour ChatGPT login or OpenAI API key, AGENTS.md, and Codex configuration continue to load from the official CLI. Glueprint adds the working surface around it.
AG-402Install & connect02 / 05
Make it part ofyour next project.
Set up the integration on each machine where the agent will run.
- 01
Install and authenticate Codex
Install the official package on every host where sessions should run, then complete Codex's own authentication flow.
- 02
Detect the CLI in Glueprint
Open Settings -> Agents -> Codex. Leave CLI Path on Auto-detect, choose Detect, and confirm the resolved path and version.
- 03
Start and steer a project session
Open a project or worktree, create a Codex session, and send a follow-up while a turn is active to steer it.
Terminal - install and verify
npm install -g @openai/codex
codex --versionThe process stays on its host. Remote access follows your Glueprint plan and the capabilities of the installed agent.
Help with agent setupAG-403How it works03 / 05
A direct connection.A shared view of the work.
Glueprint adds the workspace around the agent. Its provider account and configuration stay with the CLI.
- 01
It runs your Codex CLI, not a fork
Glueprint finds the codex binary you already installed, probes the version, and spawns it. Your ChatGPT login or API key, your config, your project's AGENTS.md: all of it comes along, because it's the same CLI you run in the terminal.
- 02
A persistent JSON-RPC connection
The adapter drives Codex through its app-server mode — a long-lived JSON-RPC 2.0 channel rather than one-shot invocations. Prompts, reasoning, tool calls, and diffs arrive as typed events and render as a live timeline on every surface.
- 03
Steer the agent mid-turn
Codex's turn-steering is wired through. Send a clarification while the agent is still working — the next tool call uses your new context instead of finishing the wrong plan first.
- 04
Approvals follow you
When Codex wants to write a file or run a command, the request lands as an inline approval card on the desktop, in the browser, or on your phone. Approve, deny, or auto-allow per tool.
AG-404Compatibility04 / 05
Know what’savailable.
Some features come from Glueprint. Others depend on what the installed agent supports or reports when it connects.
| Capability | Status | Behavior |
|---|---|---|
| Structured streaming | Supported | Persistent app-server events render as a typed timeline. |
| Mid-turn steering | Native | Follow-up context is acknowledged while the active turn continues. |
| Permission approvals | Supported | Command and file requests become Glueprint approval cards. |
| Project instructions | Agent | AGENTS.md and Codex configuration load from the working directory. |
| Reasoning effort | Native | Reasoning effort is selectable per session. |
| Explicit interrupt | Supported | Active turns can be interrupted from any connected surface. |
Check the connected agent for its available models, modes, and permissions. Learn about ACP
AG-405Ownership & limits05 / 05
Your tools.Clear boundaries.
Credentials and model access follow the provider. Glueprint brings the surrounding work into one place.
Glueprint surface
Approve from your phone
Permission prompts arrive as approval cards wherever you are. Kick off a refactor at your desk, approve the file writes from the couch.
Native adapter
Mid-turn steering
Don't wait for a wrong turn to finish. Glueprint wires Codex's steering through, so a follow-up message redirects the agent while it's still working.
Glueprint surface
Parallel sessions across worktrees
Run several Codex sessions side by side, each in its own git worktree. Built-in worktree management, diffs, and a three-pane conflict resolver keep them from stepping on each other.
Glueprint surface
One screen, many machines
Tile Codex sessions from your laptop, your desktop, and a homelab box into one Command Center mosaic — next to Claude Code and Gemini if you run those too.
Glueprint surface
Assistants on Codex
Promote Codex to a persistent assistant: persona, constitution, long-term memory, and a daily journal on disk, loaded into every wake from AGENTS.md.
Glueprint surface
Routines on a schedule
Wake Codex on cron: triage the inbox every 30 minutes, sweep PRs at 9am, run the nightly cleanup. Quiet hours and watermarks prevent re-fires.
Glueprint surface
Analytics per harness
Messages, sessions, and output tokens computed from session logs — compare Codex against Claude Code, Gemini, and your ACP agents.
AG-406A few useful answersNotes
Before youstart building.
Q.01Does Glueprint replace the Codex CLI?
No. Glueprint is an Agentic Development Environment that hosts Codex. It spawns the official CLI you already installed and adds the surfaces around it: live session streaming, mid-turn steering, inline approvals, parallel worktrees, scheduling, and remote control.
Q.02Do I need an API key or a separate ChatGPT subscription?
No. Glueprint doesn't resell model access. Sessions run through the codex CLI's own authentication — your existing ChatGPT plan or OpenAI API key is exactly what gets used.
Q.03Will it use my AGENTS.md and config?
Yes. Sessions launch from your project directory, so AGENTS.md and your Codex configuration load exactly as they do in the terminal.
Q.04Can I run Codex from my phone?
Sessions always run on your machines — a laptop, a desktop, or a server with the headless daemon. The iOS and Android app streams them live, lets you send follow-ups, and handles permission approvals from anywhere.
Q.05Can I run Codex next to Claude Code?
Yes — that's the point. Each harness is an adapter; sessions from all of them tile into the same Command Center, share the same task boards, and roll up in the same per-harness analytics. See how Glueprint runs Claude Code.
Q.06Is my session content private?
Yes. Remote viewing routes AES-256-GCM-encrypted envelopes through the relay, which stores a wrapped key it cannot open — decryption happens on your devices. On the free local tier, session content never leaves your machine at all. See security.
AG-407Go to the sourceOfficial resources
Officialresources.
Codex CLI · Hand-researched native descriptor; capabilities are validated on the execution host.
AG-408Keep exploringThe same workspace
More agents.The same workspace.
AG-409 The local tier is free
Your next project.A place to begin.
Download once, run on your hardware, scale up to teams when you're ready. No credit card.