Docs › Operate

Operating guide

Your day-to-day job as the supervisor.

Approvals

Anything at 🙋 Ask me first level, and every irreversible action at any level, waits in Approvals. The view shows all products in one list by default — or pick a single product from its selector. Rows are paged (5 by default; choose 5/10/20/50). Each row shows the product, the capability, the situation that motivated it, and the exact parameters. Click Approve to execute now, or Reject to discard.

If the kill switch is on or the system is degraded when you approve, execution is refused and the approval stays pending — nothing is silently lost.

Permissions (autonomy levels)

On the Permissions view you set, per product, how much freedom each capability has. Recommended path for any new capability:

  1. 👁 Watch only — watch it in the reports for several cycles. It touches nothing.
  2. 🙋 Ask me first — it proposes; you approve each action.
  3. 🤖 Act alone — it acts on its own, once you trust it.

PowerExecutor also promotes automatically after three consecutive clean outcomes, and demotes on any failure. Override either way with the level selector.

Irreversible capabilities (e.g. send_broadcast) always require an approval, even at Autonomous.

The Supervisor PIN

The PIN protects consequential actions. It is stored hashed in the server database and managed from the console: Settings → Security → Set / change PIN.

Requires it: approve/reject, change autonomy, save Configuration, kill switch, clear degraded. Reading (reports, approvals list, status) never requires it.

  1. Set it once under Settings → Security. First time: if the server was deployed with a POWEREXECUTOR_PIN env var, that value is the initial PIN — enter it as "Current PIN"; if none exists, leave "Current PIN" blank. (The placeholder CHANGE_ME is treated as no PIN.)
  2. Unlock each session: any protected action asks for the PIN and remembers it in memory for that session — never saved in the browser. Or pre-fill it under Settings → Supervisor PIN.

Forgot it? On the server: docker exec powerexecutor-api sqlite3 /data/powerexecutor.db "DELETE FROM config WHERE key='supervisor_pin_hash';" then set a new one.

The kill switch

On the Dashboard, Engage the kill switch to deny every action immediately — the loop, the approval endpoints, and the scheduler all stop acting (observation continues). Disengage to resume.

Degraded mode

PowerExecutor trips into degraded mode automatically when an irreversible action fails, pausing all acting. Investigate, then click Clear on the Dashboard to resume.

Recommended rollout

WeekPosture
1Everything at Watch only. Read every report. Confirm the reasoning is sound.
2Promote low-risk reversible capabilities to Ask-me-first. Approve deliberately.
3+Promote proven capabilities to Act-alone. Keep irreversible ones on approval.