Slash command reference
This reference is generated at build time from the owner command table in the backend, so it always matches the commands the product actually accepts.
Commands
Section titled “Commands”| Command | Usage | Description | Type |
|---|---|---|---|
/decisions |
/decisions: list pending decisions |
List pending decisions | Read-only |
/approve |
/approve <n> [action with @employee and #integration] |
Approve a pending decision, optionally routing an action first | Mutating |
/reject |
/reject <n> <reason> |
Reject a pending decision with a reason | Mutating |
/ask |
/ask <employee> <text> |
Ask an employee a question (owner task) | Mutating |
/do |
/do <action with @employee and #integration> |
Route an action through the Action Box | Mutating |
/communicate |
/communicate @employee [...] <text>: message employees, or a team announcement with no @mention |
Message mentioned employees or post a team announcement | Mutating |
/run |
/run <task id or title fragment> |
Execute the most recent matching orchestration task | Mutating |
/comms |
/comms: recent communications |
Show recent communications | Read-only |
/help |
/help: this list |
Show the command list | Read-only |
Where commands run
Section titled “Where commands run”Read-only commands (/decisions, /comms, /help) are safe on any surface.
Mutating commands only run on a surface that verifies the sender as the account
owner independently of the employee container: currently Slack and the
dashboard chat. On any other surface they are refused with an explanation, and
nothing is changed.
Generated 2026-10-24 from owner-command-router.service.ts (9 commands).