seeds is an issue tracker for AI coding agents that stores each work item as
facts in a quipu knowledge graph instead of
rows in a versioned database. It is a CLI that answers the bd/br verbs
agents already type (create, show, ready, close, …) with --json in the
same shape, and it is the beads replacement for the quipu stack. The
name comes from the counting board: a quipucamayoc moved seeds across a
yupana to count, then knotted the result into the quipu.
This 20-second recording runs native sd 0.8.0 in a new, isolated local Quipu store. Every command names the public fixture graph and actor; the local fixture configuration sets the demo prefix. It creates one work item, reads the ready queue, then reports counts. No server, sync or production tracker is used. Reproduce the recording.
- Share a work queue: read ready work and claim it with conflict checks.
- Keep history with each fact: inspect earlier revisions of a work item.
- Choose where work lives: use a local file, a committed pendant or a shared server.
curl -fsSL https://raw.githubusercontent.com/scbrown/seeds/main/install.sh | shPython 3.9+, curl, and a Linux or macOS shell. Downloads the latest published archive, verifies SHA-256 and the executable
version before publishing command links in ~/.local/bin. Add it to PATH.
The complete versioned bundle stays in ~/.local/lib/seeds/TAG for rollback.
Published targets: Linux and macOS, x86_64 and arm64.
Set STACK_INSTALL_ROOT on the receiving shell for another prefix.
Pinned releases, alternatives, configuration and removal are in the
installation and usage reference.
No server and no configuration: the first write creates a local quipu store at
.seeds/seeds.db.
sd create "Write the parser" -p 1
sd ready --json
echo "exit $?"created â—‹ sd-k2x [P1] [task] Write the parser (tx 1)
[{"assignee":null, … ,"id":"sd-k2x","issue_type":"task", … ,"priority":1,"revision":1,"status":"open","title":"Write the parser", … }]
exit 0
| You want to | Run |
|---|---|
| Read ready work | sd ready --json |
| Open an item | sd create "Write the parser" -p 1 -t task |
| Claim an item | sd update <id> --claim |
| Inspect supported commands and output | sd capabilities --json |
Command reference covers flags, output and exit codes.
Give your agent the command reference
and run sd capabilities --json to inspect the installed command contract.
Choose the intended store and graph explicitly when working across projects.
An alias from another tracker is a separate Desire Path configuration; review
existing aliases before changing them.
The shell installer needs Python 3.9+, curl and Linux or macOS. A local store
needs no server; its first write creates .seeds/seeds.db. Run the example in
a disposable directory if you do not want a project ledger there. Shared stores
require endpoint and graph configuration; see storage modes.
- The Seeds book: concepts and usage.
- Installation reference: configuration and removal.
- Reproduce the terminal demo: local fixture and full output.
- Tambo: guided stack installation and verification.
- Camayoc: governed memory and vocabulary.
- Detailed examples and agent setup.
Load this repository’s graph: public repository-pendant assets have not yet been verified. When a release supplies the archive, checksum and provenance, follow the verified import workflow: extract the share directory and use quipu import SHARE_DIR --db repository.db. Import stages knowledge; ROOT stays unchanged.
The Quipu stack is built around a governed, bitemporal knowledge store: shared facts, decisions and work history your agents can query. Quipu can check writes against your rules, records where each fact came from, and answers what was true when.
| tool | what it gives your agents |
|---|---|
| tambo | 🧰 Agent Platform Toolkit - installs and configures the quipu stack |
| quipu | stores shared facts with provenance and history; can check writes against your rules |
| camayoc | prepares knowledge and vocabulary for Quipu, with checks before it is admitted |
| quechua | shared vocabulary and shapes for interoperable knowledge |
| chaski | reacts to graph changes and delivers governed notifications |
| bobbin | indexes your codebase and injects context from that index and Quipu knowledge |
| yupana | shows code impact and can read policies from Quipu to govern agent actions |
| desire-path | turns agent mistakes into feature requests; works on its own without Quipu |
| seeds | a work item tracker backed by the Quipu knowledge base |
| shantytown | runs crews of AI agents on work items, triggered by hand, on a schedule or by events; can share work and memory through Quipu |
| rikuy | live brief: status, graphs, watches and signed decisions over Quipu |
| shuttle | runs signed agent workflows and keeps their records in Quipu |
Run just check and just test before submitting a change.