Long-running coding tasks without terminal dependency
Use a hosted Codex CLI session when a repair, migration, or implementation needs to keep running even after the original browser tab or local terminal is gone.
use case
Use Codex CLI from a browser workspace when the work must outlive a terminal.
Host Codex CLI tasks for teams that need browser visibility, durable job state, generated artifacts, and a project-scoped history of coding work.
Project context that can be reopened
The session history, run activity, and generated outputs remain with the hosted project so a developer can inspect the work later instead of relying on an ephemeral shell transcript.
A browser surface for review and handoff
Teams can review the stored response, artifacts, and execution record in the browser before deciding the next Codex CLI follow-up.
why this page exists
What teams need to understand.
Each page focuses on the actual workflow question: browser access, persistent sessions, durable jobs, artifacts, replay, runtime support, and team-scoped workspace custody.
Hosted Codex CLI
Browser-accessible session
Durable task state
Run artifacts
Replay after reload
Project-scoped handoff
Related guides
From runtime choice to the workflow.
FAQ
Direct answers for searchers.
Why use Codex CLI in a browser workspace?
A browser workspace makes the session, job state, artifacts, and replay recoverable for the project instead of leaving them tied to one local terminal.
Does this change the Codex CLI runtime?
No. Codex CLI remains the runtime; onesagent provides the hosted workspace and control-plane custody around the execution.