The agent in a workspace
A workspace can run an agent UI of its own. T3 Code runs in the workspace as its agent
user,
spin-agent-t3, and drives Claude Code and Codex from a browser: threads, checkpoints, and
switching between them. It is built and tested, and it is also the part of Spinbox with the least
day-to-day use so far.
Open it
Section titled “Open it”spin agent <workspace>spin agent <workspace> <path> --startThe server listens on the workspace’s loopback alone. Your own SSH session forwards it to your
computer, and the command prints a link that pairs your browser with it. --port picks the
local port. Ctrl-C ends the forwarding, not the server. path defaults to the project’s
checkout, or to /workspace in a workspace with no project.
The workspace’s Agent tab in the dashboard opens the same server. It frames the client and carries it over your passkey’s session.
You do not start or stop the server yourself. The supervisor starts it when you ask, and stops
it once nobody uses it and no chat is at
work.
Every flag is in spin agent.
Sign in once
Section titled “Sign in once”You sign Claude Code and Codex in from the agent’s page. Each is the CLI’s own login, run by the supervisor as the agent’s user. The credentials stay in the agent’s home and never pass through the page.
One login signs in every workspace of yours, plain or a project’s. Each workspace hands back every refresh and logout. A workspace that names a guest holds none.
This is a known gap: whoever runs code in one of your workspaces holds the provider token of all of them, until you log out or revoke it at the provider. See Known gaps.
What it reaches
Section titled “What it reaches”The agent’s user has no capability and is given only path. Its traffic is marked, and it
reaches only brokered
names.
An administrator decides which names those are: see An agent without keys.
Chats and the agent’s home
Section titled “Chats and the agent’s home”spin workspace threads <workspace>The workspace lists the agent’s chats as its supervisor last reported them: a title, the directory, the model and a time. Never a message. You read a chat in T3 Code.
The agent’s home is a volume of its
own,
mounted at /home/spin-agent-t3. Erasing a workspace leaves its home yours, unmounted. A new
workspace mounts it when it is created and finds the chats there.
spin agent home listspin workspace create --agent-home <id> --waitspin agent home delete <id>delete erases a home no workspace mounts: its chats, its key and its bytes.
Driving other workspaces
Section titled “Driving other workspaces”spin in a workspace needs no login of its own. An agent there drives other workspaces on a
key it gets for the workspace’s
identity.
The key is a child of the key that made the workspace. It holds no more than that key, and goes
when the workspace goes to the trash.
spin -o json workspace listThe call goes through the workspace’s host, whatever the workspace’s network allows: an agent
in an offline workspace drives others too. For keys, scopes and review, see Agents and
automation.
Installations run Spinbox v20261027.01; the reference is generated from spin v20261114.01 (51f7e0dea). This page as Markdown, for a model or a terminal.

