Turbo Quant Memory

Takes no parameters.

Takes no parameters.

Takes no parameters.

Takes no parameters.

Store a typed project note. kind must be exactly one of: lesson, decision, pattern, handoff. tags: 2-3 lowercase tags are strongly recommended — tags are the only way to FILTER notes; an untagged note is reachable by semantic_search alone. source_refs: the files / notes / issues this note is about. Pass them as entity URIs (note://<id>, file://<relative/path>, issue://KEY, https://...) and they are auto-linked into the knowledge graph as `references` relations, so get_related_entities can later surface them. provenance: who originated the note. Use "human-explicit" when the USER asked to remember something ("remember this", "save that"); "agent" for your own observations (the default); "external-tool" for API/tool data; "system" for automatic processes. tier: normally derived from `kind` (handoff -> episodic, every other kind -> durable). Override e.g. tier="durable" to keep a `handoff` in the default-searchable set, or tier="episodic" to keep a noisy lesson out of regular search. After storing, connect the note with link_entities(source_uri="note://<id>", ...) when it relates to a file, issue, or prior note — the response echoes the note's uri and hints this when the note still has no relations.

Compact memory retrieval (dense vector + BM25, fused via RRF). By default only the `durable` and `reference` tiers are searched, so session `handoff` notes (which live in the `episodic` tier) are NOT returned. To recover handoffs / session summaries pass ``tier_filter=["episodic"]`` (or list every tier to opt everything in). For a query-free "where did I leave off" bootstrap at session start, prefer the `recent_context` tool instead. source_filter narrows results by source type: ``"notes"`` returns only memory notes (decisions/lessons/patterns/handoffs), ``"markdown"`` only indexed doc blocks. In doc-heavy projects the reference blocks often crowd notes out of the top ranks on question-shaped queries — when you are asking "what did we decide/learn about X", pass ``source_filter="notes"``.

Register and index Markdown directories into project memory. Supports .tqmemoryignore files (placed in project root or any indexed directory) with glob patterns to exclude paths from indexing. One pattern per line, # for comments. Example patterns: ``workspace-*`` skips any directory matching the glob; ``data/reports/*.md`` skips files matching a path pattern; ``backups/`` (trailing slash, as in .gitignore) skips a directory. Agent worktrees under ``.claude/worktrees`` are skipped by default.

Create a Knowledge Graph link between two entities. Entities are specified using URIs: - Note: note://<note_id> - File: file://<relative_path> (relative to project root) - External: e.g. issue://BUG-404, task://TASK-101

Remove a Knowledge Graph link between two entities. source_uri / target_uri use the same URI forms as link_entities: note://<note_id>, file://<relative/path>, issue://KEY, https://...

Query relations involving a specific entity URI. uri: the entity to look up, as note://<note_id>, file://<relative/path>, issue://KEY, task://KEY, or https://... — the same URI forms link_entities accepts. Returns nothing for an entity that has no links yet.

Store an encrypted secret in the active project's vault. The value is encrypted with AES-256-GCM under a per-project master key resolved from TQMEMORY_SECRETS_PASSPHRASE or the OS keyring. Secrets are NEVER indexed, embedded, or returned via ``semantic_search`` / ``hydrate``. They live in ``~/.turbo-quant-memory/projects/<project_id>/secrets/vault.tqv`` and stay on this machine.

Fetch a project secret by exact name. Returns the value in a dedicated ``secret_value`` field (never in descriptive text). Status is ``"ok"`` on hit, ``"missing"`` when no such name exists, or ``"error"`` with ``setup_hint`` when no master key is configured yet.

List secret names in the active project. Never returns values.

Takes no parameters.

Delete a project secret by exact name.

Query-free session bootstrap: the most recently updated notes. Call this FIRST when starting a new session or resuming after a context compaction, when you do not yet know what to search for. Returns notes ordered by recency (newest first), NOT by relevance — including `handoff` notes (episodic tier), which a plain semantic_search hides by default. This is the reliable "where did I leave off" entry point. scope: 'project' (default), 'global', or 'hybrid'. Use 'hybrid' to also surface promoted cross-project knowledge. tier_filter: defaults to all tiers (so handoffs are included). Pass e.g. ["durable"] to exclude episodic session notes. format: 'json' (default); 'text' — compact plain text, one line per note with its hydrate handle (about 20% of the JSON size); 'hook' — the same text as Claude Code SessionStart hook output. Use 'hook' from a SessionStart mcp_tool hook: Claude Code shows the model only an mcp_tool hook's JSON additionalContext, never its plain text.

Tell the other agents in this working tree what you are changing. feature: short name of the work. areas: workspace-relative files or directories (globs allowed). Returns the peers whose announced areas overlap yours and recent changes inside them. Inferred writers are guesses from announced areas, never facts.

Clear the work this session announced with announce_work.

Takes no parameters.

Overview of the sessions sharing this working tree: peers, overlaps and recent file changes. Call it at session start. Inferred writers are guesses from announced areas, never facts. Peers that made no tqmemory call for a long time are listed under `idle_sessions`, not in `sessions`, and their announced areas are left out of `overlaps`.

Takes no parameters.

Journaled versions of one file in this working tree, newest first. Versions are snapshots taken while several sessions share the tree. Use restore_file with a version id to bring one back; the overwritten content is kept as a new version.

Write a journaled version of one file back into the working tree. version: a version id from file_history, or "HEAD" for the committed content. The content being overwritten is kept as a new version, so the restore can be undone.