Choose native depth for runtime-aware work
OpenCode is the strongest current native lane when the team needs the browser workspace to expose its runtime-specific session and event surfaces rather than only a generic CLI wrapper.
use case
Use OpenCode when your hosted workspace needs the deepest native runtime surface.
Choose the OpenCode lane for browser workspaces that benefit from the richest current native session and event integration, alongside durable jobs, artifacts, and replay.
Retain a durable project record around native behavior
onesagent keeps the project session, jobs, artifacts, and replay durable while OpenCode remains responsible for its own runtime behavior and tool loop.
Review live work without replacing the runtime
Operators can inspect hosted workspace state and the available native facts in the browser, then continue the same project-scoped work without inventing a parallel agent model.
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.
OpenCode native lane
Native session facts
Runtime event visibility
Hosted browser access
Durable artifacts
Project-scoped replay
Related guides
From runtime choice to the workflow.
FAQ
Direct answers for searchers.
Why choose OpenCode for a hosted workspace?
OpenCode currently has the deepest native session and event surface available in onesagent, making it the strongest choice when those runtime-specific facts matter.
Does a native lane remove the hosted workspace boundary?
No. onesagent still owns the browser workspace, durable jobs, artifacts, replay, and scoped project custody while OpenCode owns its runtime behavior.