openfolksApprovals and oversight
OpenFolks turns structured engine events into cards in the conversation. Questions, permission requests, tool activity and failures appear on the task that produced them.
Approval cards
When an engine supports approvals, the request appears in the thread. Read the action and its scope before you allow it. Denying hands control back so the folk can choose a safer path. “Always allow” is tied to a specific request and does not grant general execution.
Backstage
Backstage shows the live record of a turn: tool calls, requests, errors and the engine protocol recorded for the thread.
Failed runs
OpenFolks retries transient stream failures. If retries end in an authentication or configuration error, the fix is in the engine setup.
Limits
- Approvals depend on what the engine reports. Some engines run actions without asking.
Documentation
Next: Folks, tasks and rooms