Troubleshoot Remember

Start from a fresh session in the expected repository. The agent can continue coding if memory is unavailable, but the handoff may be missing context.

Check the daemon

From the Remember checkout, run:

uv run --no-dev --project embed remember-embed daemon status

Use daemon logs, daemon stop, or daemon start in place of daemon status for the other lifecycle actions. Run with the same Remember environment as your agent. Check the plugin log under ~/.remember/coding-agents/plugin.log (or your configured Remember home). Logs can contain prompt or response text.

If the daemon does not start, verify that the checkout still exists and that uv and your inference provider are available to the agent process. If another service occupies the port, choose an unused local apiPort and restart the agent.

When recall is empty

Check that the agent shows the Remember memory tools and that its hooks are enabled and trusted. Restart the agent after installation.
Confirm both sessions are in the same bank. Linked worktrees share a project bank by default; a second clone may not.
Use remember_sync_status to check for pending writes and remember_diagnose to learn why the integration is inactive. On first start, allow time for the database and models to load.
Check project opt-in, disabled, retainSessions, and autoInject. If a recent correction is missing, ask for a distinctly worded detail and allow time for indexing.

Back up or restore

Keep the settings file separately from the database backup. Use the administration command to produce a consistent backup while the database is running:

REMEMBER_API_DATABASE_URL=pg0://remember-embed-coding-agent \
  uv run --no-dev --project api remember-admin backup /path/to/remember-backup.zip

Restore replaces the target database's existing data. Take a separate backup first, stop the daemon, and follow the restore procedure before verifying recall again. Do not copy the files of a running PostgreSQL database as a backup.