Configurable, scoped memory for AI agents. Tiroir is French for drawer.
Give any AI agent a memory organised the way its user actually works. A developer thinks in repositories, an accountant in client files, a consultant in engagements. With tiroir, the organisation of memory is configuration: you declare your drawers, and tiroir handles storage, indexing, retrieval, context injection and sync.
Status: design phase. Nothing is usable yet. The requirements are being written; code follows once the design is approved.
- Plain files are the truth. Memory is readable Markdown in a Git repository. Every index is derived and rebuildable.
- Your drawers, your schema. Drawer types, layout, metadata, templates and injection rules are configuration, not code.
- Isolation over recall. When a drawer is active, retrieval stays inside it. Isolation between drawers is a tested guarantee.
- Abstain rather than mislead. Injecting nothing beats injecting a plausible but wrong memory.
- You choose where your memory lives. It syncs to a Git repository you pick, self-hosted or hosted. Nothing else leaves your machine: no telemetry, no third-party APIs, and embeddings are computed locally.
- Git without Git. tiroir syncs your memory across machines and team members through Git, and you never have to touch Git.
- Humans own the synthesis. Logs are append-only, and summaries change only after you confirm.
- An MCP server for Claude Desktop and Claude Code.
- A Claude Code adapter with automatic context injection.
- A guided setup skill that interviews you and designs your schema.
- A CLI for setup, indexing, search, validation, sync, migration and erasure.
- Presets for developers and accounting firms, with synthetic data.
- Product brief: vision, principles and constraints.
- Requirements: what v1 must do, checkably.
- Prior art review: what we learned from existing agent memory projects.