Cadence
Cadence is an agentic-first todo application: a task manager whose primary user is an AI agent, with a human surface good enough that a person prefers it to what they use now.
The plan is to publish Cadence as a public, installable, open-source project by 6 November 2026. That date is a delivery commitment, not an estimate.
Status
Early build. Not yet published to a package registry (see the finish-line
checklist below) but it builds, runs, and is tested from a fresh clone.
See docs/bakeoff.md for the five candidate concepts we
researched, the evidence behind each, and which one we chose and why, and
docs/human-surface.md for the CLI's binding
design spec.
Try it from a fresh clone
git clone https://github.com/dominicplouffe/Cadence.git
cd Cadence
pip install -e .
cadence add "Buy milk" --due 2026-09-01 --priority high
cadence list
cadence done 1
By default tasks live in ~/.cadence/cadence.db (a local SQLite file).
Set CADENCE_DB_PATH to point at a scratch file instead (used by the test
suite and useful for an agent that wants an isolated store).
Start the MCP server (agent surface) over stdio, exposing add_task,
list_tasks, complete_task, and schedule_task as tools with structured
JSON returns:
cadence mcp
Run the test suite:
pip install pytest
pytest -q
What "agentic-first" means here
- Primary interface is agent-legible by design. An agent that has never read the docs should be able to work out what each tool does, what it returns, and what it did wrong, from the interface itself.
- A human surface is not optional. A capability that exists only for agents is half-built, and so is one that exists only for humans.
- Local-first bias. We prefer something a person installs with a single command and owns the data of, over a hosted multi-tenant web app.
The finish line
Three things must be true and independently checkable by someone outside this company, on or before the committed date:
- Published on a public package registry, installable with one command.
- CI on a clean GitHub-hosted runner goes green on the full suite, including an end-to-end test that installs the published artifact and drives it.
- A committed transcript exists of an agent with no access to this repository completing a fixed ten-step script using only the published package.
Contributing
Not yet open for external contributions — the project is pre-publication. Once published, this section will describe how to build from a fresh clone, run the test suite, and submit changes.
License
MIT — see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for cadence-todo 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| cadence_todo-0.2.2.tar.gz | 34.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cadence_todo-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 62.2 kB
Release files / cadence_todo-0.2.2.tar.gz
| Download URL | cadence_todo-0.2.2.tar.gz |
|---|---|
| Size | 34.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d3d083fa2a5553ac01f3ac7efcdb4bb1b1bf6d9aa8726f5f407ca178eba72626
|
|
BLAKE2b-256 checksum How to use checksums |
c6af8d788a4bf709776fee7ec80e834e3507b0f8a26e8541956dc684e0dc43be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / cadence_todo-0.2.2-py3-none-any.whl
| Download URL | cadence_todo-0.2.2-py3-none-any.whl |
|---|---|
| Size | 27.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aff9a19fe2fddd40fd812c667989e26ee4b4da69e639ba711f181bf8a8c65f34
|
|
BLAKE2b-256 checksum How to use checksums |
75bc9ea1831d256a86a7fdd8dea87b1c01406c85dc403270716f70d6a4e6fef3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for cadence-todo 0.2.2
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
