tracking-agent-changes-with-canary

name	tracking-agent-changes-with-canary
description	Tracks and presents the agent's file changes and durable review context for the user through Canary. Use in repositories with Canary when generated code introduces a non-obvious decision, question, risk, scope change, or file ownership update that should stay visible in diffs, threads, file briefs, and the todo queue, and when canaryctl should be used to keep that context current.

Canary

Canary has two surfaces:

• canary: the repo-local monitor and wrapped-agent launcher. canary serve watches repo changes and serves the local review UI. canary codex / canary claude start attributed agent sessions.
• canaryctl: the tool the agent uses to create and update that context.

The user can:

• inspect what files changed
• read the agent's threads and file briefs
• reply to threads in the UI

Canary's durable artifacts are:

• threads: focused review discussions for one issue, usually tied to a file and line range
• file briefs: durable notes about what a file owns and what future editors should know

Use Canary when the user should be able to review a non-obvious change after the chat, not just read about it in the transcript.

Authorship rules:

• If you are running inside a wrapped Canary agent session, canaryctl will resolve your actor identity automatically from the inherited Canary session token.
• Do not invent or pass your own display name for thread or file-brief authorship.
• If the repo is using Canary for attributed agent threads, prefer being launched via canary codex or canary claude so your threads and replies are tagged to the correct live actor.