Context Circuit
Workflows

Complete plans and update knowledge

Close the work and reconcile the durable concepts it changed.

Template 2.5.0CLI 2.5.0

Request completion after the work lands

Name the plan or plans to complete. The agent inspects actual changes, then records your completion request with record complete --id ID --text TEXT. The note preserves your words; completed_at records the instant.

Judge the knowledge candidates

The CLI returns local catalog entries claiming the affected repositories. The agent reads candidates whose meaning could have changed and compares them with the implemented result.

  • Update a changed note and its catalog entry together.
  • Move the reviewed date after confirming it against code.
  • Say explicitly when no durable concept changed.
  • Raise borrowed-knowledge corrections upstream, through that repository's own review, never in context/.

For a direct change without a plan, context find --repo ID supplies the same reconciliation candidates.

Answer the commit question

record complete returns commit_recommended when the plan's files, its intent's file, or the ID files are uncommitted. The agent asks one question: commit and push those files, or commit only. After "commit only", it says other clones cannot see them yet.

Archive, if you want to

While you have finished records not archived, completion also returns archive_offer, and the agent offers to archive them:

Yes, archive my finished records.

record archive moves your completed plans, and approved intents whose plans are all completed, under the _archive/ beside them. Every ID stays reserved and lookup by ID still finds them. It returns its own commit_recommended. Declining the offer changes nothing.

Keep the working copies

Completion is not cleanup. Worktrees and branches remain, including local files. Removing them requires a separate request. The reconciled knowledge is the starting point for the next intent.

On this page