One model, two profiles
Projects, versions, tasks and sessions. At home a version is a stage that ends in a tag; at work a task is a ticket across several projects and branches. The same binary serves both through a profile.
$ npm i -g @lacodda/rigger $ cargo install rigger # then, once: $ rigger init $ rigger project add .
rigger
One seat for all your projects and tasks. A local record of what is done, what is next and when it ships - read by you and your coding assistant.
The problem
Section titled “The problem”Run more than a handful of projects and the record scatters: a plan here, a changelog there, a session log the assistant writes for itself, a release calendar kept by hand. You stop reading it, because prose cannot be filtered or summed across projects. The assistant reads it every session at full price, and the biggest project no longer fits in a context window. The facts about what shipped live in git, where nobody looks.
rigger keeps the record as data in a local SQLite file and derives everything else from it.
What rigger does
Section titled “What rigger does”Facts from git
A pushed tag means the version shipped, on that date. Commits since the last tag are activity. The plan cannot claim more than git confirms; a mismatch is reported, never silently fixed.
A context packet, not a hub
rigger context prints what the assistant needs to start - state, current stage, open questions, last events, next step - inside a fixed token budget that is tested, not hoped for.
An MCP server as the only pen
Decisions, findings, pitfalls, changes and the next step are recorded through tools, as events with a date and a session. Nothing is written by editing markdown.
The owner's inbox
Every question waiting for your answer, across all projects, in one list. Answer it and the answer becomes a decision on record.
Hubs as an export
The markdown you keep in your notes is generated from the database: stable bytes for a stable database, so the history in git stays readable.
Status
Section titled “Status”v0.1.0 brings the database, projects and doctor. The road to 1.0 is twenty-two small releases in seven blocks; see the roadmap and the command reference for what arrives when.