Skip to main content
Most identifiers in the CLI accept more than one form. You rarely need to paste a UUID.

​
Agents and workspaces

Three forms work anywhere an agent or workspace id is expected.

​
When handles repeat

Team handles are unique within an organization, not across all of them. Two organizations can each have a platform workspace. jstm workspace resolve returns every match rather than guessing:
To find out which organization a workspace belongs to:

​
Runs

A run can be addressed by UUID, or by its per-agent sequence number:
The sequence form is <agent>/runs/N, where the agent part is itself a handle, UUID, or FQN, and N counts from 1 per agent. The second form is the one you can read out loud.

​
Catalog entries

MCP servers registered as endpoints get a qualified name derived by the server when you register them:
You pass that qualified name to mcp introspect, mcp connect-key, mcp disconnect-key, and mcp remove-endpoint. Each of these also accepts the server’s UUID. Repositories and skill sources are addressed by UUID, listed with jstm mcp repo list and jstm skills repo list.

​
Input requests

jstm input-requests submit accepts either an input-request UUID, or an agent handle, UUID, or FQN. Given an agent, it resolves to that agent’s single open request — and errors rather than guessing if there is none, or more than one.

​
Active workspace context

Commands that take an optional --workspace fall back to your active workspace. Check and change it with:
Some commands require --workspace explicitly rather than defaulting — the connection group is the main one, because credential resolution depends on which workspace is asking.