Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
docs: correct MCP alias notes
AkitaOnRailsc826b0fa9906
diff --git a/docs/ARCHITECTURE.md b/docs/ARCHITECTURE.mdindex 1395bcd0..28781217 100644--- a/docs/ARCHITECTURE.md+++ b/docs/ARCHITECTURE.md@@ -188,8 +188,9 @@ rules into a project's `CLAUDE.md` / `AGENTS.md`. The narrow-surfacediscipline still holds — every new tool has to earn its slot — but thev1 count is 11, not 10.-All MCP tools accept verbal-variance parameter aliases (`query|q|search`,-`workspace|ws`) so the calling agent can phrase arguments naturally.+MCP parameter aliases are intentionally sparse: `memory_query.query` accepts+`q|search`, and limit fields accept `n` / `top_k` where shipped. Project and+cwd parameters use their canonical names.## CLI subcommand surface (17 commands)diff --git a/docs/design-decisions.md b/docs/design-decisions.mdindex be0e9f06..4d77a42b 100644--- a/docs/design-decisions.md+++ b/docs/design-decisions.md@@ -170,7 +170,9 @@ basic-memory has ~25 tools, agentmemory has 53. Both have user confusion as a re| `memory_lint` | Rule-based + optional LLM contradiction findings → `wiki/_lint/<date>.md` | destructive || `memory_install_self_routing` | Returns the canonical CLAUDE.md / AGENTS.md routing block + per-agent filename hints | read-only |-Tool param aliases: accept `query|q|search`, `project|workspace`, `dir|directory` - basic-memory's `AliasChoices` pattern works for LLM resilience.+Tool param aliases stay narrow: shipped aliases cover `query|q|search` and+`limit|n|top_k`; project and cwd parameters use canonical names unless the+code adds a concrete alias.## 11. Identity & project scoping (3-tuple from day one)