Ticket setting: memorize then auto-close the console when a ticket is set to done

When orchestrating a backlog with one throwaway console per ticket, finished consoles pile up idle until an agent or the user closes them, and each close has to be preceded by a "memorize now" prompt so durable learnings reach project memory before the transcript is discarded.

Today this is dispatcher discipline (merge → done → send "memorize now" → wait → agents_close), and it gets skipped.

Proposal: a per-ticket (or per-project default) setting "on done: memorize, then close console" that sends the memorize prompt to the ticket's console, waits for its turn to end, then closes it — so every new ticket starts with fresh context without anyone remembering to tidy up.

AgentsRoom diagnostics

• App version: 1.161.0
• OS: darwin 25.6.0 (arm64)
• Agent CLI: claude
• MCP server: 1.18.0
• App language: system

Problem to solve

Finished ticket consoles stay open and idle; closing them is manual, and the memorize-before-close step is easy to skip, so learnings are lost with the discarded transcript.

Proposed behavior

Per-ticket or per-project setting: when a ticket is set to done, send the console the memorize-now prompt, wait for the turn to end, then close the console automatically.

Who benefits

Anyone running backlog_start_next unattended with useWorktree tickets and a fresh throwaway console per ticket.

Acceptance criteria

No idle finished consoles; project memory captured before every close; each new ticket starts with fresh context.

[Full-Stack Developer @ 2026-09-04T13:57:19.935Z]

Where to find the setting

Shipped as an opt-in backlog setting, so nothing changes until it is turned on. It exists in two scopes, and both lead to the same control:

• Account default — Settings > Backlog > "Memorize and close on done" (it sits right under "Review column"). This is the default every project inherits.
• Per project — Project settings > Backlog tab, same row. Three states: On / Off / inherit the account default (the row spells out what "inherit" currently resolves to).
• Both rows are reachable from the settings search box by typing memorize or close.
• From an agent, without opening the UI: settings_get({ key: "backlogMemorizeCloseOnDone" }) / settings_set({ key: "backlogMemorizeCloseOnDone", value: true }).

What happens once it is on

A ticket reaching done — from ANY path: the Done button, a kanban drag, backlog_update over MCP, the phone — makes the console that worked it:

1. finish whatever turn it is in (nothing is ever interrupted),
2. receive the memorize instruction and write the session's durable learnings to the Project Memory,
3. get closed as soon as that turn ends (a throwaway console is discarded, a saved agent of the project only loses its session and stays in the list).

The memorize step is skipped, and the console simply closed, when it would be pointless: Project Memory disabled for the project, an agent already set to "Always memorize", or a console that never ran a real turn. A console owned by a live Agent Team run is left alone — the run's own finalization tears it down.

Scope note

The setting is per project (with an account default) rather than per ticket: the need described here is a project-wide policy, and a per-ticket flag would mean a schema column plus the API, mobile and MCP surfaces for a knob every ticket of a board would carry the same value on. Say so if a per-ticket override still matters and it can be added on top.