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.

Note

The doc and wiki steps are performed by the agent during the run (through the same environment injection as the visual-verify capture), not by a person ticking boxes afterwards. The issue-close step is the project’s existing completion action — the closeout only shows it.

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	Summarises the outcome as a memory proposal for review.

Set the workspace default

The workspace default applies to every project that does not override a step.

1. Open Settings → Closeout.
2. 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.
3. Save. Only a workspace owner or admin can change the default.

Override for one project

A project can override individual steps; the steps it does not touch keep inheriting the workspace default.

1. Open the project’s Edit modal and find the Closeout section.
2. The banner shows whether the project is inherited or overridden. Change any step to override it — the others keep inheriting.
3. To drop the override entirely and go back to the workspace default, use Reset to workspace default.
4. Save. Changing a project’s closeout is a workspace-admin action, so a plain member editing an unrelated field never trips it.

Tip

Because a step you leave alone keeps inheriting, changing the workspace default later flows through to every project that had not overridden that step.

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.

See also

• Manage memories
• Configure visual-verify gates