TokST Durable context for people and AI agents

Help Center

Use this page to diagnose common TokST setup and daily-use issues. Each section includes the fastest recovery path and a command to verify the result.

Installation and updates

tokst: command not found

Install the standalone CLI, then open a new terminal so the updated PATH is loaded.

curl -fsSLo tokst-install.sh https://tokst.com/install.sh
sh tokst-install.sh
tokst version

Windows PowerShell uses:

Invoke-WebRequest https://tokst.com/install.ps1 -OutFile "$env:TEMP\\tokst-install.ps1"
& "$env:TEMP\\tokst-install.ps1"
tokst version

Windows Git Bash supports the Unix command and opens the PowerShell installer automatically.

The installed version looks older after an update

tokst update downloads and verifies the latest standalone CLI binary. Inspect the active binary when a terminal still resolves an older path.

tokst update
tokst version --verbose
tokst doctor
tokst doctor --fix-path

Open a new terminal after a standalone installation or PATH repair. The installer records its binary location and retains cloud authorization.

Sign in and cloud connection

Browser authorization does not return to the terminal

Keep the terminal process open while confirming the browser page. Start a fresh flow when the browser says the connection request is unavailable.

tokst login
tokst connection test

Use an API key for CI, servers, and other unattended environments:

tokst login --key tk_live_xxxx
tokst connection test

Select an Atlas for an Agent workflow

Cloud MCP provides Workspace and Atlas tools. Select the appropriate governed scope in the Dashboard or through the authenticated Agent before writing shared memory.

Retired Local mode

TokST Local is retired. Existing device files remain untouched, and the CLI no longer opens, exports, restores, synchronizes, or serves Local SQLite profiles. Connected Runtime devices retain an internal encrypted queue for sanitized delivery recovery. See TokST Local retirement.

Workspaces and Atlases

I cannot create a workspace or Atlas

Workspace and Atlas creation follow the current plan limits. Review account usage in the dashboard, switch to the intended workspace, and retry.

tokst status

Cloud Free includes one personal workspace and one Atlas. Team workspaces use their own Team subscription and shared quota. See Product Editions.

I cannot see a team invitation

The invitee can review every pending invitation and accept or decline it in the Dashboard. Authorized Agents use the corresponding Cloud MCP Workspace tools.

Team owners and admins manage invitations in Team Collaboration.

MCP and Agent setup

WorkBuddy, ZCode, Qoder, or Kimi cannot open browser authorization

Create a dedicated API key in Dashboard → API Keys. Configure the client as Streamable HTTP and send the key in every request through the Authorization header. Revoke the key when the client is no longer used.

{
  "mcpServers": {
    "tokst": {
      "type": "streamable-http",
      "url": "https://api.tokst.com/mcp",
      "headers": {
        "Authorization": "Bearer tk_live_your_api_key"
      }
    }
  }
}

MCP tools do not appear

Reconnect the MCP client to https://api.tokst.com/mcp and complete browser authorization. Restart the MCP client after approval and ask it to list accessible TokST Workspaces. See MCP Overview for OAuth and API-key setup.

A device appears online but cannot execute

Dashboard presence combines heartbeat and execution health. Open Agents, select the device and Agent binding, then inspect the effective adapter, primary model, fallback model, WSS route, and latest diagnostic.

tokst status --json
tokst doctor
tokst logs

The healthy state is executable. A recent heartbeat by itself only proves that the Runtime reported presence.

A direct chat is delivered but has no reply

Open the contact details and review the delivery stage. Confirm that the bound device is connected, the local Agent client is authenticated, and the selected model is available. Correct the reported route or executor failure, then retry only the failed reply.

See Communication for message states, WSS delivery, streaming replies, groups, and recovery.

Only part of an Agent group replied

Every group member has an independent delivery and execution record. Open group details, inspect each member, and retry only failed members. Successful replies stay in the shared conversation and become context for later group turns.

An automatic Session does not appear

Automatic Memory is off by default. Enable it for the intended supported client, restart that client once after bridge installation, and complete a request with a final reply.

tokst auto status --agent all --json
tokst auto verify --agent <name> --json

Open Dashboard -> Sessions to review compilation or diagnostic status. See Sessions.

Files, usage, and security

A file is visible but its memory is gone

Open Files in the dashboard and review the recycle bin. Restoring the memory restores the normal association; the repair tools identify orphaned attachments for review.

Upload, usage, or permission requests fail

Confirm the target workspace, available shared or personal quota, and your workspace role. Owners manage billing and audit access; admins manage team content; members manage their own memories.

tokst status

API keys inherit the permissions of their owner. Revoke unused keys from the dashboard and create keys only for trusted automation. See API Keys.

Still need help?

Gather the command, complete error message, installed version, operating system, and whether the flow used the device bridge, CLI, Cloud MCP, dashboard, or a REST compatibility endpoint. This makes support and issue triage reproducible.

Useful checks:

tokst version
tokst doctor
tokst connection test
tokst status --json