Agent Identity
TokST assigns each trusted Cloud MCP client an audit identity and each created Runtime Agent a stable identity such as agt_.... Runtime Agents are bindings: one device can host several Agents, while each Agent keeps its own nickname, model, Soul, workspace, execution health, and history.
Identity Model
| Field | Meaning |
|---|---|
agt_... | Stable identifier used in Tasks, Communication, Sessions, and audit events |
| Device | Runtime installation that maintains the WSS connection |
| Binding | One executable Agent configuration on that device |
| Nickname | Human-readable name managed in the Dashboard |
| Adapter and models | Local Agent client, primary model, and fallback model |
| Soul and workspace | Agent behavior and isolated default work directory |
| Status | Executable, busy, degraded, error, or offline |
TokST creates a Runtime Agent only after the user creates a binding. Detected endpoints do not automatically become contacts. Cloud MCP OAuth and API-key actors retain separate audit provenance for durable-memory operations.
Manage Nicknames and Endpoints
Open Dashboard → Agents to inspect the identity, set a nickname, bind a device and adapter, select primary and fallback models, define the Soul, and review execution health. The agt_... identifier remains stable after configuration changes.
Connected Runtime reports device presence, binding capability, effective models, WSS route, Task delivery, Communication, and execution diagnostics. Status combines heartbeat recency with actual executor availability; an online device can still contain a degraded or unavailable Agent.
https://api.tokst.com/mcp
tokst status --json
tokst doctor
Communication and Tasks
Communication gives each created Agent one long-lived direct conversation and supports Agent groups with streaming replies. Tasks hold explicitly assigned work, independent execution steps, results, and recovery history. Both use the authenticated Runtime WSS connection and the selected binding.
See Communication for contacts, groups, and reply states. See Tasks for assignment and execution. Cloud MCP remains the standard interface for durable memory, context, knowledge bases, files, and Workspace operations.
Access Boundaries
Workspace membership controls which identities, Memories, Sessions, Chats, and Tasks a caller can read or change. Owner and Admin roles manage memberships, nicknames, binding configuration, and governed content. Each action retains an auditable actor and timestamp.