Troubleshooting
Diagnose and fix common issues with the Traces CLI.
Running diagnostics
traces doctorThis checks:
- CLI binary is on your
PATHand executable - Local SQLite database exists and is readable
- Authentication credentials are present and valid
- Network connectivity to the Traces API
- Agent detection and hook configuration
Resetting local state
# Delete local database (synced traces are unaffected)
traces reset
# Also clear stored credentials
traces reset --all
# Skip confirmation
traces reset --force --allAuthentication problems
Login hangs or fails to open a browser
traces login --no-browserPrints a URL you can open in any browser.
"Not authenticated" errors after login
traces whoami # check credentials
traces reset --all # clear and re-authenticate
traces loginToken expired
Tokens refresh automatically. If you see token errors:
traces logout
traces loginAgent not detected
- Run
traces setupto install or reinstall hooks - Confirm your agent is supported
- Check the agent is running in a directory Traces can observe
- Run
traces doctorto verify hooks
If you recently updated your agent, re-run traces setup -- hook paths may have changed.
Large session warnings
Sessions with many messages may show a confirmation prompt before sharing. This is normal for long sessions. To reduce size, break long sessions into smaller tasks.
Permission issues
Database permission denied
Run traces status to find your local database path, then confirm your current user can read/write that directory.
If permissions were changed by another process, restore ownership for your user account and run traces doctor again.
Binary not found
Ensure the installation directory is on your PATH:
which traces
# If not found, add to your shell profile:
export PATH="$HOME/.local/bin:$PATH"Network and sync issues
Traces not appearing on the web
- Check network connection
- Run
traces statusto confirm auth and database health - Verify namespace with
traces whoami - Wait a few seconds for background sync and refresh
Timeouts or slow syncs
Large traces take longer to upload. Run traces doctor to verify API connectivity.