TokST Durable context for people and AI agents

TokST Help Center

Resolve the next step quickly

Search an error, command, or workflow. Each guide provides the checks, recovery path, and proof that it worked.

Install & update

tokst: command not found

Install the standalone CLI and refresh the terminal PATH.

  1. Run the platform installer.
  2. Open a new terminal.
  3. Confirm the selected binary.
curl -fsSLo tokst-install.sh https://tokst.com/install.sh && sh tokst-install.sh

Read the full guide

Install & update

The version remains old after update

Refresh the standalone binary and identify the command selected by the shell.

  1. Run the built-in updater.
  2. Open a new terminal.
  3. Inspect the active binary path.
tokst update

Read the full guide

Sign in & connection

Browser authorization did not return

Restart browser authorization while the terminal process remains open.

  1. Keep the terminal flow open.
  2. Start setup again.
  3. Confirm cloud access after approval.
tokst login

Read the full guide

Sign in & connection

API key or permission request failed

Confirm the saved identity, target workspace, and key owner permissions.

  1. Check the active cloud connection.
  2. Review accessible workspaces in the Dashboard or Cloud MCP.
  3. Create or rotate the trusted API key in the dashboard.
tokst connection test

Read the full guide

Workspaces & Teams

Workspace or Atlas creation is unavailable

Creation follows the current personal or Team plan limits.

  1. Inspect your current plan and usage.
  2. Select the intended workspace in the Dashboard or Cloud MCP.
  3. Create the space within its available limit.
tokst status

Read the full guide

Workspaces & Teams

A Team invitation is missing

The recipient reviews and accepts invitations from their own account.

  1. Confirm the invitee email address.
  2. Review the recipient Dashboard inbox.
  3. Accept the active invitation before team access starts.
Open Dashboard → Workspaces

Read the full guide

MCP & Agents

MCP tools do not appear

Authorize the Cloud MCP connection, then restart the MCP client.

  1. Confirm the saved cloud connection.
  2. Refresh generated Agent integration files.
  3. Restart the MCP client.
tokst connection test
tokst start

Read the full guide

MCP & Agents

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

Use a dedicated API key in a Streamable HTTP MCP Authorization header.

  1. Create a dedicated API key named for the client.
  2. Set the client transport to Streamable HTTP.
  3. Paste the complete key after Bearer and restart the client.
{
  "mcpServers": {
    "tokst": {
      "type": "streamable-http",
      "url": "https://api.tokst.com/mcp",
      "headers": { "Authorization": "Bearer tk_live_your_api_key" }
    }
  }
}

Read the full guide

MCP & Agents

A device appears online but cannot execute

Separate heartbeat presence from the Runtime, executor, model, and Agent binding health.

  1. Open Dashboard → Agents and inspect the device and selected Agent binding.
  2. Confirm the binding has an executable adapter, valid model, and healthy Runtime route.
  3. Run status and doctor on the connected device, then inspect recent Runtime logs.
tokst status --json
tokst doctor
tokst logs

Read the full guide

MCP & Agents

A direct chat is delivered but has no reply

Trace WSS delivery, Agent binding, executor startup, model response, and result persistence.

  1. Open the contact details and confirm the device, adapter, primary model, and fallback model.
  2. Check that the Runtime remains connected and the local Agent client is authenticated.
  3. Review the failure stage, then retry the failed reply once after correcting the route.
tokst status --json
tokst doctor
tokst logs

Read the full guide

MCP & Agents

Only part of an Agent group replied

Each group member has an independent delivery and execution result.

  1. Open group details and inspect every member's current binding and status.
  2. Confirm the message recipients and review each member's delivery state.
  3. Retry only failed members so successful replies remain unchanged.
Open Dashboard → Communication → Group details

Read the full guide

MCP & Agents

Automatic Session did not appear

Automatic memory captures a connected Agent Session, compiles its result, and extracts durable Memories only when the work contains reusable information.

  1. Enable automatic memory for the intended supported Agent; it is off by default.
  2. Restart the Agent client once after installing or repairing its bridge.
  3. Check the connection and queue state.
  4. Open the linked Session to inspect its compilation, extracted Memories, and diagnostics.
tokst auto status --agent all --json
tokst auto verify --agent <name> --json

Read the full guide

MCP & Agents

A Session shows [REDACTED]

TokST removes credential-like content, private keys, tokens, passwords, cookies, and sensitive patterns before Session material is stored or displayed.

  1. Treat the original credential as exposed and rotate it through its provider.
  2. Open the Session diagnostics to review the redaction result without exposing source material.
  3. Keep the reusable conclusion and remove credentials from the source before retrying the work.
tokst status --json

Read the full guide

Files & quota

A file or its memory association is missing

Review the Files recycle bin and verify the target workspace and memory lifecycle.

  1. Open Files for the selected workspace.
  2. Review the recycle bin and orphan repair results.
  3. Restore the memory or file association when available.
tokst status

Read the full guide

Files & quota

Upload or request reached a quota

Usage belongs to the selected personal or Team workspace.

  1. Inspect plan and available usage.
  2. Confirm the selected workspace.
  3. Ask the Team Owner to adjust team capacity when needed.
tokst status --json

Read the full guide