Troubleshooting & Support

Shared Memory Isn’t Available

By TermSquad · Last reviewed

If an agent cannot recall shared memory, first check whether it is using the correct computer, Linux user, and project. An empty search result is different from an unavailable memory service.

Check scope and access

  1. Open the intended repository as the agent user.
  2. Ask the agent to identify the current project.
  3. Ask it to read recent context, then search for a known topic.
  4. Check the project on any returned observation.
  5. If MCP tools are missing, check the supported CLI interface.

The MCP server name is squad_memory. Pi normally uses the CLI path, so it does not need to expose the same MCP interface.

Check the CLI

In the agent terminal:

termsquad memory help
termsquad memory version
termsquad memory stats

To search a known project:

termsquad memory search "Build command" --project my-project

Replace the topic and project. Do not share private search results as generic diagnostics.

If the store appears empty

Check whether you are on a new or reset computer, another Linux user, or a restored backup from before the observation was saved.

The default store is ~/.termsquad/memory; a configured directory override can point somewhere else. Do not delete that directory as a troubleshooting step.

If you have an export, follow the recovery guide before importing. Ask the agent to be explicit about failed recall rather than inventing a summary.

See memory storage and recovery and support.