Skip to the card

Card 321 of 9792026-10-03 issue

Observed arrival · 2026-10-03

Canon keeps agent work in the repo

getcanon.dev Visit website
Editorial interest 80/100 Selection signal · not a rating of the site

A local-first harness for planning, running, and checking coding-agent work across projects.

Landing page captured for the 2026-10-03 issue.
For
Developers coordinating coding agents across repositories
Worth noticing
A sprint’s candidate lessons enter a queue; a separate later session judges whether to promote them.

Field notes

The described loop starts with an agent drafting a ticket, followed by human approval before code changes. Canon says its board draws from tickets, HANDOFF.md, and git history, while agent sessions run under a local daemon and can be resumed after interruption. Its lesson process is deliberately staged: a sprint creates a candidate, and a later session decides whether it should be kept.

Observed signals

Read the marks

Editorial observations of this landing page, not a rating.

○OpenPublic substance visible
✦PrettyNotable craft visible
●ProPolished or operationally mature
◎NicheUnusually specific use

One card from the complete issue

The Checkerboard Turn

435,484 arrived 1,000 judged 979 catalogued Enter the complete issue
getcanon.dev

Landing page observed 2026-10-03. The live site may have changed.