Observed arrival · 2026-10-03
Canon keeps agent work in the repo
A local-first harness for planning, running, and checking coding-agent work across projects.
○Open
⊠Login
$Paid
†Ads
✦Pretty
●Pro
◎Niche
◉Human
⚑Risk
ƒJS
- 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