Scaffolded memory-bank toolkit for AI coding agents
Structured project memory · Progressive context loading · Deterministic maintenance hooks
Claude Code · Codex CLI · Qwen Code · OpenCode
Memora helps teams turn long-lived project context into a structured, navigable, and reusable memory-bank for AI coding agents.
Instead of relying on one large prompt or an ever-growing context window, Memora gives your repository a clear memory architecture:
- a stable entry point for agents,
- a routing layer for minimal relevant context,
- canonical knowledge files for architecture, decisions, conventions, and testing,
- isolated session state for ongoing work,
- maintenance hooks that keep memory workflows visible and predictable.
Memora is especially useful when AI agents work on the same codebase across many sessions and need more than ad-hoc prompting.
Memora already provides a practical foundation for structured project memory:
- deterministic scaffold delivery through a shared
scaffold.manifest.jsonused by bothmemora initandpostinstall, - working CLI commands for project initialization and profile-driven validation:
memora initandmemora validate, - an operational health command:
memora doctor, - a ready-to-use memory-bank scaffold with core files such as
PROJECT.md,ARCHITECTURE.md,CONVENTIONS.md,TESTING.md,DECISIONS.md,OPEN_QUESTIONS.md,CHANGELOG.md, and.local/session state, - schema-driven validation for front matter, cross-file integrity, and operational hygiene, including strict mode, JSON output, watch mode, and profiles (
core,extended,governance), - pre-commit validation for
memory-bank/*.mdfiles, - GitHub Actions CI for core validation, extended validation, and markdown linting,
- deterministic advisory hooks for reflection, consolidation, and cleanup reminders,
- toolchain adapters for Claude Code, Codex CLI, Qwen Code, and OpenCode.
In short, Memora already gives you a strong base for project memory structure, validation, and repeatable agent workflows.
Memora gives repositories a predictable memory layout instead of unstructured notes:
AGENTS.mdas the entry point,memory-bank/INDEX.mdas the routing table,- stable knowledge files for project identity, architecture, decisions, policies, and patterns,
.local/for active session context and handoff.
Memora is designed around reading only what is needed. The routing layer in INDEX.md maps tasks to the right files and keeps agents away from unnecessary context.
The project includes deterministic advisory hooks, a shared scaffold manifest, and explicit lifecycle docs. This makes installation and memory maintenance more visible and less dependent on agent improvisation.
Memora supports local validation, strict mode, JSON reports, live watch mode, memora doctor, pre-commit checks, and CI validation. This is a major strength for teams that want memory files to stay clean and consistent.
The same memory-bank structure can be used with multiple AI toolchains through project-specific adapter files and hook integrations.
At a high level, Memora organizes memory like this:
Agent starts
↓
Reads: AGENTS.md
↓
Checks: memory-bank/INDEX.md
↓
Loads: Only relevant files
↓
Works on the task
↓
Updates: CURRENT.md and HANDOFF.md
↓
Uses hooks and maintenance workflows as needed
This structure gives you three practical benefits:
- less context noise,
- better continuity across sessions,
- cleaner separation between stable knowledge and ongoing work.
- Node.js
>=16 bash(macOS/Linux; Windows via Git Bash or WSL)
npm install -g ./memora-cli-X.X.X.tgz
# or for development
npm linkmemora init ./my-project
cd ./my-projectmemora validate
memora validate --strict
memora validate --profile extended
memora validate --profile governance
memora validate --format json
memora validate --watch
memora doctorStart with:
memory-bank/PROJECT.mdmemory-bank/ARCHITECTURE.mdmemory-bank/CONVENTIONS.mdmemory-bank/TESTING.md
Memora includes adapter files for Claude Code, Codex CLI, Qwen Code, and OpenCode.
memora init and postinstall copy the same scaffold entries from scaffold.manifest.json, including .githooks/, .github/workflows/, local bin//lib/, and adapter directories. Repository authoring docs in docs/ are not copied into your target project.
For a step-by-step guide, see docs/GETTING_STARTED.md.
- Documentation Index — complete map of the documentation set
- Getting Started — first successful setup
- CLI Reference — commands, flags, and examples
- Memory Model — layered memory architecture
- Workflows — session-start, update, audit, consolidate, reflect, cleanup
- Toolchains — Claude Code, Codex CLI, Qwen Code, OpenCode
- Hooks — deterministic advisory maintenance hooks
- Validation — front-matter validation, doctor checks, pre-commit, CI, schemas
- Patterns — reusable memory and workflow patterns
- Security — memory hygiene, privacy zones, safe operating practices
- Manifesto — protocol and design philosophy behind Memora
| Area | Claude Code | Codex CLI | Qwen Code | OpenCode |
|---|---|---|---|---|
| Adapter files present | ✅ | ✅ | ✅ | ✅ |
| Hook integration present | ✅ | ✅ | ✅ | ✅ |
| Workflow docs present | ✅ | ✅ | ✅ | ✅ |
| Shared memory-bank model | ✅ | ✅ | ✅ | ✅ |
Memora’s core advantage here is consistency: one memory-bank architecture, multiple integrations.
Memora already has a solid foundation in structure, validation, hooks, and adapters. The roadmap continues to build on these strengths:
- richer schema-driven validation,
- stronger scaffold parity and install diagnostics,
- stronger memory quality automation,
- more starter packs and templates,
- broader adapter polish,
- improved observability and maintenance tooling.
MIT — Use freely. See LICENSE for details.
Memora — Structured memory for long-lived AI coding work