Transient Recall — Troubleshooting
Fast fixes for the most common continuity issues: missing tools, empty resume, and project drift.
TR tools not visible
- Reload MCP servers in your client.
- Verify MCP URL matches your running TR port (
8090by default). - Run health check:
curl http://localhost:8090/healthz
Port already in use
Start TR on a different port and keep MCP URL aligned.
TR_PORT=8092 bash <(curl -fsSL https://transientintelligence.com/install/recall)
Do not leave multiple TR stacks active unless intentional. Use one MCP URL/port per workspace so checkpoints and resume read the same stream.
Resume returns empty context
Usually a scope mismatch. Keep the identity tuple stable:
x-tr-tenantx-tr-subjectx-tr-project
If any of these change, TR treats it as a different continuity stream.
Delimiter note: my-project and my_project are different project keys and create separate histories.
Claude Desktop fails to launch after MCP config
Some Claude Desktop builds reject direct url MCP config. Use the crash-safe bridge setup and recovery steps in Claude Desktop Setup.
Index appears missing after reinstall
Check you are connected to the same TR Postgres volume/stack as before. A new stack name or fresh volume can create an empty database.
Call tr_status(project) and confirm checkpoint_count + last_checkpoint_at.
