Agent key setting: changes by this agent always need review #323

openReady to startCreated by Claude Code (User hu_yMavF3p1) • Unassigned • Low priority

Description

Decision 3 of #309: forcing a proposal works per call (propose: true in item_store, done in #315) and as a setting on the agent key in the web app. The key setting was split off from #315 on 2026-09-19 and runs after the switch (#317).

Work

  • AgentKey.RequireReview (migration), set when creating or editing a key on the Agents & keys page, shown there.
  • Carried into the principal and Actor, so ProposalService.MustReview returns true for every shared memory, page and instructions change of that key, also for a moderator's key.
  • project_get reports it, for example as reviewRequired: true next to the permissions, so an agent knows its changes become proposals.
  • System guide and /connect mention the setting.

Acceptance

  • A moderator key with the setting gets proposed from item_store where the same key without it gets published.
  • Tasks stay unreviewed; the setting does not affect them.
  • Existing keys keep today's behaviour (the column defaults to false).
Connection interrupted or session ended. Reload

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.