A real coding workspace
OpenOrange Code is not a chat box bolted onto a repository. It manages projects, configurations, model selection, sessions, history, queues, forks, archives, and navigation as first-class team data.
// start.code_session
OpenOrange Code
OpenOrange Code is a shared coding-agent runtime for private teams, with projects, isolated sessions, model choice, durable queues, forks, handoffs, history, and per-user usage attribution.
OpenOrange Code brings collaborative coding agents into the private OpenOrange workspace. Teams share projects and history while every coding session runs in an isolated OCI container with a maintained development toolchain.
01
Projects, runtime configurations, models, sessions, and history are shared by the team.
02
One-writer leases, presence, handoff, and durable prompt queues make collaboration explicit.
03
Session forks preserve lineage without forcing people into one shared execution state.
04
Model requests and spend remain attributable by user, project, and session.
Isolated execution
Each session starts an isolated OCI sandbox with Git, GitHub CLI, Node.js, Python, Go, Rust, Java, shell tooling, search utilities, and browser support while the shared control surface stays in OpenOrange.
GitHub without loose tokens
The current authorization work uses scoped, short-lived GitHub grants so instances and coding sandboxes do not need a long-lived organization token.
// questions
Can multiple people work in the same project?
Yes. Presence, one-writer leases, explicit handoff, durable prompt queues, independent forks, and persisted lineage make collaboration visible and predictable.
Does a coding session share the host directly?
No. Each session runs in an isolated container with a maintained toolchain and explicit project and credential boundaries.