loading…
Search for a command to run...
loading…
Project memory and scoping engine for AI coding agents. It gives any agent persistent project state, bounded work packages, and cross-session continuity.
Project memory and scoping engine for AI coding agents. It gives any agent persistent project state, bounded work packages, and cross-session continuity.
PyPI version Downloads Python 3.13+ Tests License: MIT
Project memory and scoping engine for AI coding agents.
AI coding agents are stateless — they forget between sessions, lose decisions, and have no way to scope complex work. agendum is an MCP server that gives any agent (Claude Code, Cursor, Windsurf, Cline, and others) persistent project state, bounded work packages, and cross-session continuity.
| Without agendum | With agendum |
|---|---|
| Agent forgets everything between sessions | Picks up exactly where it left off |
| No scope — agent modifies random files | Bounded work packages with file lists, acceptance criteria, constraints |
| Decisions lost — same mistakes repeated | Decisions and patterns persist in searchable memory |
| No task ordering — agent picks randomly | Dependency graph with auto-unblocking and priority scoring |
| Learning locked inside one project | Cross-project learnings carry patterns forward |
pip install agendum # or: uvx agendum
claude mcp add agendum -- uvx agendum --home serve # add to Claude Code
# Done. pm_* tools are now available in your agent.
Works with any MCP client — see setup for Cursor, Windsurf, VS Code, and others.
flowchart LR
A["PLAN\nwrite plan file"] --> B["pm_ingest\nboard items + deps"]
B --> C["pm_next\nwork package + context"]
C --> D["EXECUTE\nagent implements"]
D --> E["pm_done\ndecisions + patterns"]
E -->|next task| C
E -->|new session| F["pm_status\nresume context"]
F --> C
Each pm_done records decisions and patterns that enrich future pm_next calls — context compounds across sessions.
Example session:
You: I have a plan file for the API rewrite. Ingest it.
Agent:
→ pm_ingest(project="api-rewrite", plan_file="plan.md")
Ingested 4 board items from plan:
item-001: Schema design [high]
item-002: Resolver layer (depends on item-001)
item-003: Auth middleware (depends on item-001)
item-004: Integration tests (depends on item-002, item-003)
You: What should I work on?
Agent:
→ pm_next(project="api-rewrite")
Work package for item-001 "Schema design":
Context: project rules, memory from last session
Scope: Define GraphQL schema types
Acceptance criteria: Types for User, Product, Order
You: Done with the schema. Here's what I decided...
Agent:
→ pm_done(project="api-rewrite", item_id="item-001",
decisions="Using code-first with Strawberry",
patterns="N+1 queries need DataLoader",
verified=True)
Marked item-001 as done. Unblocked: item-002, item-003
> Next: pm_next("api-rewrite") to continue with newly unblocked tasks
| Tool | Purpose |
|---|---|
pm_init |
Initialize board directory (optional — auto-initializes on first use) |
pm_project |
Create, list, or get projects |
pm_status |
Dashboard — item counts, recent progress, memory health, suggested next task |
| Tool | Purpose |
|---|---|
pm_add |
Add an item with type, priority, tags, dependencies, acceptance criteria |
pm_board |
View and filter the project board |
pm_ingest |
Import a Markdown plan file into bounded board items with dependencies |
| Tool | Purpose |
|---|---|
pm_next |
Get the next scoped work package with complexity signal and enriched context |
pm_done |
Complete an item — record decisions, patterns, learnings; auto-extract from git; auto-unblock dependents |
pm_block |
Report a task as blocked with reason |
| Tool | Purpose |
|---|---|
pm_memory |
Read, write, append, or search project memory (decisions, patterns, project knowledge) |
pm_learn |
Record global or project-scoped learnings with tags and topic entities |
pm_search |
Hybrid search across all knowledge — memory, learnings, completed items |
pm_consolidate |
Clean memory corruption, deduplicate learnings, detect contradictions |
pm_supersede |
Soft-invalidate a learning — excluded from all future searches |
pm_search combines three signals to find relevant knowledge across memory, learnings, and completed board items:
auth matches authentication, config matches configuration. Always on, zero config.agendum[vectors] to add semantic similarity via fastembed + sqlite-vec. Activates automatically alongside FTS5.All three signals are fused via Reciprocal Rank Fusion (RRF), then reranked by recency and access frequency. The index rebuilds from Markdown files — no data loss if it gets corrupted.
pm_done(verified=True) distinguishes tested from untested completionspm_done reads git diff and git log automatically when no files are specifiedpm_status warns about corrupted entries; pm_consolidate strips XML fragments, deduplicates, and flags contradictions.agendum/, diffable and committableAll MCP clients except VS Code use the same config. Add to the appropriate file:
{
"mcpServers": {
"agendum": {
"command": "uvx",
"args": ["agendum", "--home", "serve"]
}
}
}
| Client | Config location |
|---|---|
| Claude Code | Run: claude mcp add agendum -- uvx agendum --home serve |
| Cursor | .cursor/mcp.json in project root |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
| Cline | Settings › MCP Servers › Edit |
| Roo Code | MCP settings file |
| Claude Desktop | claude_desktop_config.json |
VS Code (GitHub Copilot): Uses
"servers"instead of"mcpServers". Add to.vscode/mcp.json:{ "servers": { "agendum": { "command": "uvx", "args": ["agendum", "--home", "serve"] } } }
pip install agendum
agendum project create my-app # Create a project
agendum status # Dashboard overview
agendum next my-app # Suggest next task
All state lives in ~/.agendum/ (or .agendum/ in your project if you prefer local storage):
~/.agendum/
├── .cache/
│ └── search.db # FTS5 + vector search index (auto-rebuilt)
├── config.yaml
├── projects/
│ └── webapp/
│ ├── project.yaml # Project metadata
│ ├── board/
│ │ ├── item-001.md # Markdown + YAML frontmatter
│ │ └── item-002.md
│ └── learnings/ # Project-scoped learnings
│ └── learning-001.md
├── learnings/ # Cross-project learnings
│ └── learning-001.md
└── memory/
├── decisions.md # Key decisions + rationale
└── patterns.md # Discovered conventions
src/agendum/
├── server.py # MCP server wiring (FastMCP)
├── tools.py # 14 MCP tools
├── models.py # Pydantic models (BoardItem, WorkPackage, SearchResult)
├── task_graph.py # Dependency resolution + topological levels
├── config.py # Shared configuration
├── env_context.py # Git diff/log auto-extraction
├── cli.py # CLI interface
├── enrichment/
│ ├── pipeline.py # ContextEnricher, budget allocation
│ └── sources.py # ProjectRules, Memory, Dependency, Learnings sources
└── store/
├── board_store.py # BoardItem CRUD
├── board_format.py # Markdown <-> BoardItem serialization
├── project_store.py # Project metadata
├── memory_store.py # Scoped memory storage
├── learnings_store.py # Global and project-scoped learnings
├── search_index.py # FTS5 + vector + entity graph + RRF
├── embedding.py # Lazy fastembed wrapper (optional)
└── locking.py # get_lock() + atomic_write()
git clone https://github.com/sralli/agendum.git
cd agendum
uv sync
uv run pytest tests/ -v # all tests
uv run ruff check . # lint
uv run ruff format --check . # format check
MIT
Выполни в терминале:
claude mcp add agendum -- npx Web content fetching and conversion for efficient LLM usage.
Retrieval from AWS Knowledge Base using Bedrock Agent Runtime.
автор: modelcontextprotocolProvides auto-configuration for setting up an MCP server in Spring Boot applications.
A very streamlined mcp client that supports calling and monitoring stdio/sse/streamableHttp, and can also view request responses through the /logs page. It also
автор: xuzexin-hzНе уверен что выбрать?
Найди свой стек за 60 секунд
Автор?
Embed-бейдж для README
Похожее
Все в категории ai