Browser access for agent work
Open long-running coding agent sessions from a hosted workspace instead of tying every run to a local terminal.
Hosted coding agent workspace for modern developer teams
Run Claude Code, Codex CLI, and OpenCode in a persistent browser workspace
Keep sessions, jobs, files, artifacts, and replay attached to a hosted workspace instead of a terminal window.
Currently free to use. Enter an email only to separate your workspace.
5 runtimes
persistent sessions
durable jobs
artifacts and replay
browser workspace
session_9f31a2
live
prompt
Run a Codex CLI job, keep the workspace alive, replay events, and collect generated artifacts.
Persistent workspace
Durable job queued
Replay ready
Why not only use the CLI?
Persistent sessions
Keep session history, workspace files, job state, and event replay attached to the project and user scope.
Runtime-native lanes
Use OpenCode-native surfaces where available and host Codex CLI, Claude Code, Hermes, and OpenClaw through adapter lanes.
Durable jobs and artifacts
Queue work, recover from browser reloads, and keep generated files or outputs with the session that produced them.
Scoped team custody
Separate users, projects, sessions, and job workspaces so hosted execution remains observable and recoverable.
Runtime support
FAQ
Searchers usually ask
Is onesagent another AI agent?
No. onesagent is a hosted browser workspace around existing coding agent runtimes, focused on sessions, jobs, files, artifacts, and replay.
Can I run Codex CLI in a browser workspace?
onesagent can host Codex CLI through a worker-managed CLI lane while keeping browser access, durable jobs, and scoped workspace custody.
Is this a Manus alternative for developers?
It addresses a similar hosted workspace need, but is designed around runtime-native coding agents rather than a closed runtime abstraction.