Skip to content
TokenWork
↑↓Navigate ↵Open escClose

Troubleshooting

Hit a snag? Find the symptom below and try the fix.

TokenWork command exits or fails to start

  • confirm Node.js >=22
  • run openchamber --version
  • reinstall latest CLI if needed

Web UI is not reachable

  • check server logs with openchamber logs
  • verify active port (default 3000)
  • open http://localhost:3000 directly first before testing tunnel links
  • run openchamber tunnel status --all
  • restart tunnel from the same instance/port
  • regenerate connect link if previous token was already used

See Tunnels for the full setup, and Reverse Proxy if you run one.

VS Code extension does not connect

  • confirm TokenWork server is running
  • verify extension is updated
  • reload VS Code window and retry connection

A request to a shared agent is refused or stops

These limits apply to Agent Collaboration requests:

  • A request can run for up to 30 minutes on the other computer.
  • Agents can pass work along to other shared agents, up to 5 steps. A request that would loop back to an agent already in the chain is refused.
  • Each share link accepts up to 60 requests per minute.

A Draft merge stopped partway

If TokenWork restarts or a file can’t be written while a Draft is merging, some Main files may already be changed.

  • click Finish merge to write the rest
  • if you edited Main files after the restart, the merge stops and lists them; check those files yourself