Relationship to aide.sh
amem and aide are complementary layers of the same system.
aide — orchestration
aide.sh dispatches work between agents. An Aidefile defines each agent’s persona, budget, triggers, and skills. aide dispatch <agent> <task> spawns an isolated Claude Code process and returns a bounded summary.
amem — knowledge
amem captures, compiles, and serves references. An agent running under aide can call amem_recall over MCP to ground its reasoning in real sources.
Integration point
In aide.toml:
[sync.memory]
method = "amem"
conflict = "causal"
When this is set, aide uses amem as its cross-agent memory substrate. Agents share a wiki; a fact learned by one agent is available to all.
Division of labor
| Concern | aide | amem |
|---|---|---|
| Which agent runs? | ✓ | — |
| How much budget? | ✓ | — |
| What does the agent read? | — | ✓ |
| Where are citations stored? | — | ✓ |
| How are secrets gated? | ✓ | — |
| What’s the SHA-256 of chunk 7? | — | ✓ |
Using one without the other
- amem alone: CLI + extension + MCP. Useful for human-led research and single-agent setups.
- aide alone: works fine, just without shared knowledge. Agents reason from their own seed context.
- Both together: the full stack.