AGENT.md and key-value store. A team workspace
also has its own skills.
The model
Every organization gets General on its first request. Solo users without an
organization get a personal workspace only.
Team roles are
owner, who created it and can delete it, admin, who manages
members and renaming, and editor, who works in the workspace. The owner row
cannot be changed, and members can always remove themselves.
In the web client
The workspace menu in the navbar switches between Personal and the team workspaces, and creates new ones for whoevercreate= allows. On small screens it
sits in the avatar menu. Owners and admins of a workspace get a members button
beside it that opens Settings, Workspaces on that workspace. Members,
roles, the name, the icon and deletion are managed there.
Lists of people load everyone in the organization, not only the first 10, and
someone who has left it shows as Former member. A search box appears once a
list has more than 8 people, and the organization’s Members table in Settings
shows 20 at a time with Show more.
Each workspace keeps its open chat and canvas tabs while the page stays open, so
switching back finds them as they were.
Team chats
A team workspace has chats of its own beside each person’s chats with the agent. The chat list switches between the two, and every member of the workspace reads and writes the team’s chats.- Talking to the team or the agent. A message goes to the team alone, with no
run. Naming the agent with
@asks it to answer, and it reads the whole conversation, with each message signed by who wrote it. - Mentions.
@offers the agent,@alland the workspace’s members. A mention marks the chat for that person in their chat list, beside the unread mark. - Reactions, edits and typing. Members react with emoji, edit or delete their own messages, and see who is typing. Deleting a message moves its uploads to the trash.
- One run at a time. While the agent works on one person’s request, a message to the team is held and saved after the reply. Only the person who asked sees Stop.
- Favorites are each member’s own.
- Pictures and videos show in the conversation, and any file opens on the canvas.
- Long chats open on their newest messages and load older ones as you scroll up.
Files and the audit log
Each file shows the face of the person who last changed it, and a star on the face when an agent made the change for them. A file’s details list who made and changed it, and in which chat. Files a chat made, received or named are marked when that chat is open, and the From this chat filter shows them alone. Org admins get an Audit log tab in Settings. It covers the organization’s team workspaces and the organization itself, never personal workspaces. Each row says when, who, what, the target, the workspace and the agent when one acted. Rows are kept 180 days.GET /audit pages through it, and GET /audit.csv exports all of
it, which is itself recorded.
Selecting one
The client sends the active workspace in anX-Workspace header on every
request. No header means the personal workspace, so existing API clients keep
working unchanged.
Inside the agent
context.workspace resolves to the active workspace. The bash sandbox binds only
that workspace’s directory at /workspace, and uploads, the canvas and AGENT.md
all follow it. Skills come from the agent, the
organization, the team workspace and the person, whose own follow them into every
workspace.
Chats and the database tool stay per user within a workspace. Teammates share
files, not each other’s conversations.
HTTP API
Mounted only when workspaces are enabled. All routes require auth.
Adding a member takes their user id from the identity provider. The row alone
grants nothing: access also needs a valid token for the same organization, so a
stray id is inert.
Turning it on for an existing deployment
The SDK moves no data. On an organization’s first request it creates General’s registry row and nothing else. Existing content under the organization root stays where it is and is invisible in workspace mode until an operator migrates it. Solo accounts need no migration at all, because their personal workspace is the account root.Security notes
Sandbox isolation
Sandbox isolation
The bash sandbox binds only the active workspace at
/workspace. Sibling
workspaces are not mounted. Registry and ACL rows live outside every workspace
root, out of reach of both the sandbox and the path-validated file tools.Network-enabled bash
Network-enabled bash
A deliberately adversarial user with network-enabled bash can reach the
deployment’s own credentials.
.sandbox(network=False) closes that path.Next
Monetization
Plans, quotas, and in-app purchase entitlements.