Skip to main content
Corunner uses human approval by default. Any action that touches a production system, a customer, or a person appears in chat with Approve, Edit, and Reject controls attached to Corunner’s message. There is no separate approval queue to check.

​
Where approvals happen

Approvals happen where Corunner proposes the action: the same Slack thread, Teams channel, or DM. Anyone in the thread with the right permission can act on the request. You never need to switch to the web app to unblock work.

​
The three controls

  • Approve — Corunner runs the proposed action immediately.
  • Edit — Adjust the parameters before running (for example, change the recipient, the ticket title, or the message body).
  • Reject — Cancel the action. Corunner will not run it and records the reasoning for future context.

​
What triggers an approval

Corunner asks for approval based on your governance policies. These decide which categories of work always run automatically, which always require approval, and which fall in between based on Corunner’s confidence.

Governance policies

Set what runs automatically, what needs approval, and what to block.

Approvals history

A read-only log of every approval Corunner has requested.

​
Approvals history in the web app

The /approvals page in the web app is a read-only history of past approval requests. You cannot act on approvals from that page. Use it to audit past decisions or share links to specific requests. See Approvals History.