Multiplayer AI for companies and teams
TerminalX turns every agent session into shared team work — one live terminal, real roles, clean handoff, and a record your company keeps. Contained in an isolated sandbox, so you can actually authorize it.
Take it through staging when the retry tests are green.
Retries and idempotency keys are in. 21 tests green. Staging deploy needs approval.
Paresh is offline. Taking control — I’ll approve staging.
The problem
Every AI coding tool assumes one engineer, one chat window, one laptop. That works for an individual. At company scale it produces four predictable failures.
Dozens of separate conversations, none of them visible to anyone else. The company accumulates isolated context instead of compounding knowledge.
A task that works for hours will pass the point where the person who started it is still watching. The run stalls at the first decision.
A colleague can’t pick up the thread without losing the reasoning, the goals and the history that got the work there.
No view of what agents are doing across teams, what they touched, or who authorized it — until something breaks.
The workspace
Not one shared terminal — as many concurrent sessions as your teams have work. Each one is its own durable Team Session with its own participants, roles and run. The workspace is where an engineering lead sees all of them at once, and where anything waiting on a human surfaces immediately.
People move between sessions; sessions don’t belong to people. The same engineer can be assignee on one, supervisor on another, and merely present on a third — with different steering authority in each.
Open any session and it’s the same durable object: live terminal, threaded conversation, who is present, artifacts, and the current run state — in one frame everyone authorized is looking at simultaneously.
Roles
Access is granted through the team, and steering authority is separate from presence. Being in the room does not mean being able to drive.
The organizational unit. Members belong to it, and access to sessions is granted through it.
Full access within the team, not restricted to individually invited sessions.
A contractor, agency or partner with access only through explicit, revocable session shares.
The single participant currently responsible for carrying a session forward.
Can oversee, take control, and delegate steering when the assignee is unavailable.
Authorized to send directives or terminal input under the current steering fence.
Revoking one relationship never silently preserves another. Remove a guest and their access to sessions, connections and standing authority goes with them — in one action, not six.
Handoff
End of shift. On-call rotation. A holiday. Someone leaving the company. The work continues under the same goals, and every control transfer is recorded.
The session is shared from the first second — not escalated into sharing after something goes wrong.
Migrations, retries, idempotency keys, 21 tests green. The team can watch or ignore it.
Destructive operation. The run pauses at the fence rather than proceeding on a blanket permission.
Arti steers directly, or assigns Atharva as an additional steerer. No credentials change hands, and nothing is re-explained.
Same session, same history, same evidence. The transfer itself is part of the record.
Work never depends on one person being awake.
The record
Session history, decisions, goals, blockers, approvals and evidence survive disconnects and restarts. Every control transfer and material effect is version-fenced and recorded — reviewable long after the run ends.
| Time | Actor | Event | Bound to |
|---|---|---|---|
| 17:38:04 | AGAgent | Requested approval — deploy staging | session 8f2a · policy p-14 · gen 7 |
| 17:39:12 | ARArti | Took control from assignee | supervisor fence · run 04 |
| 17:39:48 | ARArti | Granted approval — expires 09:41 | one-use · gen 7 |
| 17:40:02 | ARArti | Assigned Atharva as steerer | run 04 · revocable |
| 17:41:30 | AGAgent | Deploy staging — receipt recorded | gen 7 · receipt r-2291 |
| 18:04:19 | DVDev (guest) | Access revoked at session close | share s-77 · all connections |
The reasoning behind a change stays attached to the change. Six months later, the session still explains why.
Real runs, real decisions, real fences — observable without handing anyone production access.
Containment
The reason a company can say yes. Autonomy here is scoped authority with a defined edge — not a blanket permission bypass on somebody’s laptop.
Execution is isolated. Runs happen in a hosted sandbox, not on a developer’s machine sitting next to everything else they can reach.
Authority expires and is bound. Approvals are tied to the exact user, policy, session and sandbox generation. Change the sandbox and prior authority is invalid.
Dangerous operations are explicit. A prominent, expiring, one-use confirmation — never a mode somebody leaves switched on.
Secrets stay behind a broker. Raw credentials are never visible to the agent, terminal, logs, artifacts or model output.
Recovery doesn’t need the operator. Emergency stop, quarantine and grant revocation work without the person who started the run.
Everywhere your team is
Cloud-hosted and reachable from the browser, phone, tablet and desktop — plus Telegram and Slack. Same history, same authority, no separate mobile compromise. The person who needs to approve something at 11pm is on their phone.
The full workspace — every session, plus terminal, thread, participants, artifacts and run state inside each one.
Watch a run, take control, approve or deny at the fence — from anywhere.
Brokered, revocable identities. Steer from chat without exposing raw tokens.
Book a demo
A live walkthrough against your own workflow — terminal, roles, handoff and the sandbox boundary, across several sessions at once. Not a slide deck.
TerminalX is early and works closely with the first teams that adopt it — which means direct access to the roadmap and real influence over what ships next.