> ## Documentation Index
> Fetch the complete documentation index at: https://docs.joystream.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Addressing

> How to refer to agents, workspaces, runs, and catalog entries — handles, UUIDs, fully qualified names, and sequence addresses.

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.

| Form                 | Example                                | When to use                              |
| -------------------- | -------------------------------------- | ---------------------------------------- |
| Handle               | `month-end-close`                      | Inside your active workspace             |
| UUID                 | `4d90c7e2-6b18-4a55-9f31-c8ab27e05d10` | Scripting, or when a handle is ambiguous |
| Fully qualified name | `acme-corp/finance/month-end-close`    | Referring across workspaces              |

```bash theme={null}
jstm agent show month-end-close
jstm agent show acme-corp/finance/month-end-close
jstm workspace get acme-corp/finance
```

## 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:

```bash theme={null}
jstm workspace resolve platform
jstm workspace resolve platform --org acme-corp    # scope to one org
```

To find out which organization a workspace belongs to:

```bash theme={null}
jstm workspace org platform
```

## Runs

A run can be addressed by UUID, or by its per-agent sequence number:

```bash theme={null}
jstm agent run show 5f3a5c81-2d44-4e0b-9a17-0c9d3b7e9b21
jstm agent run show acme-corp/finance/month-end-close/runs/12
```

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:

```text theme={null}
endpoint/<workspace_id>/<slug-of-name>
```

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.

```bash theme={null}
jstm input-requests submit acme-corp/finance/month-end-close \
  --values '{"approver":"dana@acme.com"}'
```

## Active workspace context

Commands that take an optional `--workspace` fall back to your active workspace. Check and change it with:

```bash theme={null}
jstm workspace context
jstm workspace switch acme-corp/finance
```

Some commands require `--workspace` explicitly rather than defaulting — the `connection` group is the main one, because credential resolution depends on which workspace is asking.