Configure the standard closeout
The standard closeout is the ritual an agent runs when a task finishes: close the source issue, update the project documentation, update the product (user) documentation, add a wiki note, and propose a memory. Each step is turned on or off independently — there is no master switch — and the effective set is resolved per step across three tiers: a workspace default, an optional per-project override, and an optional per-run override at launch.
The five steps
Section titled “The five steps”| Step | What the agent does |
|---|---|
| Close the source issue | Comments on and closes (or transitions) the linked issue. This is the project’s existing completion action. |
| Update the project docs | Updates repo-internal docs (for example docs/**, CLAUDE.md, README.md) when the change affects them. |
| Update the user docs | Maintains the product documentation (the Starlight site under docs/user/**) in every configured language. |
| Write a wiki note | Adds a short note to the git provider’s wiki. |
| Propose a memory | Distils the run into a reusable fact and files it for review — see below. |
What “propose a memory” now files
Section titled “What “propose a memory” now files”This step used to hand you the task’s own summary, word for word. Approving that wrote narration into workspace memory, and a coordinator run filed one such row per worker sub-task, so the review inbox grew with the fleet rather than with what was learned. Three rules changed that:
- A proposal must carry a reusable fact — a trap, a decision, a mechanism: the thing a future run needs to know. A proposal that is essentially the summary again is not filed at all, because everything in it is already on the task.
- Claimed artefacts are checked. If the text names commits, branches or a pull request, the proposal is only filed as confirmed when the run really persisted them. Where it did not — for example a run with no push path configured, so nothing could be pushed — the proposal still appears, but carries a visible Artifacts not verified warning naming the unconfirmed claims. It is a warning, not a block: an agent may legitimately quote someone else’s commit, and refusing the proposal on a heuristic would turn a false positive into lost information.
- Sub-tasks no longer file one each. A delegating run produces one proposal on the parent, with the workers’ contributions attached to it.
Set the workspace default
Section titled “Set the workspace default”The workspace default applies to every project that does not override a step.
- Open Settings → Closeout.
- Turn each step on or off. For the doc steps, set the paths (globs) and the condition (only when touched or always); for user docs, set the languages to keep in sync.
- Save. Only a workspace owner or admin can change the default.
Override for one project
Section titled “Override for one project”A project can override individual steps; the steps it does not touch keep inheriting the workspace default.
- Open the project’s Edit modal and find the Closeout section.
- The banner shows whether the project is inherited or overridden. Change any step to override it — the others keep inheriting.
- To drop the override entirely and go back to the workspace default, use Reset to workspace default.
- Save. Changing a project’s closeout is a workspace-admin action, so a plain member editing an unrelated field never trips it.
Override for a single run
Section titled “Override for a single run”When you launch a task you can override the closeout for that run only — for example, run once without touching the docs. Open the Closeout for this run disclosure in the launch dialog and set any step to inherit, on, or off. Leaving every step on inherit uses the project (then workspace) resolution.