Organizations and workspaces

An organization is your team. A workspace is context for a use case—not an agent identity or a running process. Several authorized agents can use one workspace.

For Acme, start with a Customer support workspace. Add Research when its instructions, owners, or release cadence differ. You do not need a workspace per conversation or per model.

Choose before writing

1
agenttrunk workspaces
2
agenttrunk scopes --workspace WORKSPACE_ID

Select IDs deliberately. The API calls a workspace a trunk; trunkId and WORKSPACE_ID identify the same object. Use the General scope unless you need different permissions or independent releases.

To create a workspace when your task requires one:

1
agenttrunk workspace-create --name "Customer support"

It creates a General scope and staging/production environments. An empty list is not the same as an authorization error. Never create a replacement organization to get around denied access.

Continue with uploads or permissions.