corvee
A local, multi-agent-aware CLI issue tracker and fact store for AI coding agents, with humans as a secondary user.
Agents lose context between sessions and collide with each other mid-task. corvee tracks tasks, todos, decisions, and checked-true facts in a local SQLite database instead of chat history or a markdown file, so an agent (or a human) picks up exactly where the last session left off, and multiple agents work the same project without silently overwriting each other's edits.
See the documentation site for the full pitch, the Quickstart, the Commands reference, the Specification, and the MCP server for hosts that speak Model Context Protocol natively instead of shelling out to the CLI.
flowchart LR
subgraph sessions["Sessions, same project"]
A1["Agent session A"]
A2["Agent session B"]
H["Human"]
end
A1 -->|claim / update| CLI["corvee CLI"]
A2 -->|claim / update| MCP["corvee MCP server"]
H -->|claim / update| CLI
CLI <--> LDB[("Local SQLite\ntasks + facts")]
CLI <--> GDB[("Global SQLite\ntasks + facts")]
MCP <--> LDB
MCP <--> GDB
LDB -.->|"already claimed -> exit 4"| A2
Every task and fact lives in exactly one of these two independent databases,
picked with --global at creation time and encoded in the id from then on.
--scope all (the default for listing) reads both.
corvee itself is built with spec-driven development: docs/spec.md
is written and extended before any code, then implemented and refined
across many iterations.
Install
uv tool install corvee
Hosts that speak MCP natively instead of shelling out to the CLI need the
mcp extra and corvee mcp serve (see MCP server for
per-host setup):
uv tool install 'corvee[mcp]'
Quickstart
cd your-project
corvee init # once per project
corvee task add "Fix the flaky auth test" --description "..."
corvee task list --json
corvee task claim TASK-1
corvee task update TASK-1 --state done # claim clears automatically
corvee fact add "requests is Apache-2.0 licensed" --proof "pip show requests"
corvee fact search "license" --json
corvee explain prints a compact, agent-oriented cheat sheet from inside
any initialized project. See Quickstart for facts,
global scope, and the full core loop.
License
Contributing
See CONTRIBUTING.md for the development setup and the project's quality gate.
Release files for corvee 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| corvee-0.1.0.tar.gz | 226.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| corvee-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 349.2 kB
Release files / corvee-0.1.0.tar.gz
| Download URL | corvee-0.1.0.tar.gz |
|---|---|
| Size | 226.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
246871ac2ddf1285a0e108e42d9aa3f06774f7f55e9ada60336634a1b18d4829
|
|
BLAKE2b-256 checksum How to use checksums |
91bc4ea70d9ee0bf5c95867ca087393d7bd10a4866b13a597c437f2d0b4d7179
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / corvee-0.1.0-py3-none-any.whl
| Download URL | corvee-0.1.0-py3-none-any.whl |
|---|---|
| Size | 122.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ec1633d0de0c9baca2722276bedf18853999c3e5da605c3b9448e47e9904c89b
|
|
BLAKE2b-256 checksum How to use checksums |
5f2d7fc112c149031407a3677b6306028f2ef8d9e29bdc3f31fd8f4569da02e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency log