Persistent sessions for real work
Long-running agent jobs keep their session, workspace, event history, and outputs attached to the hosted project instead of disappearing with a terminal window.
use case
A hosted coding agent workspace for teams that need custody, replay, and browser access.
Use onesagent when local-only agent sessions are too hard to share, recover, observe, or isolate across projects and users.
Browser access for operators
Teams can inspect state, artifacts, runtime progress, and session history through a hosted browser surface without taking over the runtime loop.
Runtime custody without lock-in
The runtime remains OpenCode, Codex CLI, Claude Code, Hermes, or OpenClaw. onesagent adds the shared workspace and control plane around it.
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.
Internal coding agent workspace
Multi-user scoped projects
Job queues and worker concurrency
Artifact persistence
SSE recovery
Runtime-specific execution lanes
FAQ
Direct answers for searchers.
Can teams use it without replacing their CLI workflow?
Yes. The goal is to host existing agent runtimes with durable control-plane guarantees, not to force a new agent runtime.
What makes this different from a chat app?
The durable workspace, job, artifact, and runtime-adapter layers are the product center, not only a conversational UI.