Save, Find, and Update Project Knowledge

Save memory when you learn something that will matter in a future task. Use a clear title, the correct project, and a stable topic for knowledge that will change over time.

Save a useful observation

Ask your agent:

Save this project’s build decision in shared memory. Include what we chose, why, the affected files, and anything a future agent needs to know.

A useful structure is What, Why, Where, and Learned. Keep the observation focused on one topic.

You can also use the CLI. Replace my-project with your project name:

termsquad memory save "Build command" "Use npm run build for this project; it creates the production output." --project my-project --type discovery --topic project/build-command

Use this example only if that command is correct for your repository.

Find existing knowledge

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

Read the result’s project and context before relying on it. If a search result is shortened, ask the agent to retrieve the full observation through its memory tools.

Update a decision

Ask the agent to find the existing observation, verify the changed facts, and update the same topic. Reusing a stable topic key helps keep evolving knowledge together.

If the store reports a conflict, inspect the earlier observation and resolve the relationship instead of silently overwriting unrelated knowledge. The available MCP tools can support updates even when there is no corresponding termsquad memory update command.

Keep secrets out of all observations. See How Shared Memory Works and memory recovery.