Pending approval

create_page, update_page, delete_page, and move_item all respond with "Proposal submitted — awaiting approval" when the agent is not configured for auto-approve. This is the default — and it's the feature, not a bug. The action sits in the workspace's pending inbox until a human approves, edits, or rejects it.

What the response looks like

Proposal submitted — awaiting approval in Plainwork before the page is
created. Action ID: act_abc123. The user can approve, reject, or edit it
first.

The agent should not retry. The action is queued; retrying enqueues a duplicate.

Where to find the proposal

In Plainwork:

1. Click the pending-actions inbox (bell icon in the header).
2. Each card shows the proposing agent, a title, a diff summary, and a timestamp.
3. Approve, edit-then-approve, or reject with a reason.

On approval, the original action ID resolves; the agent can follow up with read_page if it needs the new ID.

When to flip auto-approve

Auto-approve is a per-agent setting in Plainwork → Settings → Agents. Flip it on when:

• The agent is well-scoped (one collection, narrow tasks).
• You've watched ~20 proposals from it and approved them all without edit.
• You've decided the write volume is too high for human review.

Flip it back off immediately if the agent's behaviour changes — new prompt, new model, new tool mix.

Auto-approve is on but things still queue

Auto-approve is evaluated at the API, based on the agent record attached to the token. If the MCP response still says "awaiting approval" after you flipped the toggle:

• Confirm you flipped it on the right agent (the one whose token the host is using, not a differently-named agent).
• Restart the MCP process. Stdio hosts spawn a fresh child per launch; HTTP transports hold the agent identity until process exit.