Permissions and secrets
How approvals, operating-system grants, and provider credentials are handled.
Approval cards
Supported providers emit permission requests and questions through the local harness. Dash Bot displays these inline and records the outcome. Cancellation closes outstanding requests so stale approvals cannot be answered after a turn has ended.
“Always allow” is narrow: it is tied to a server-issued key and a pending request rather than granting arbitrary execution from a paired device.
Operating-system permissions
Screen Recording and Accessibility permissions are controlled by the operating system. The desktop process owns local CUA lifecycle so grants are attributed to Dash Bot.
Secret handling
- Do not paste API keys into chat.
- Packaged builds use write-only settings and operating-system-backed encryption where supported.
- Secret values are scrubbed from public configuration responses and mobile APIs.
- Per-provider environment injection prevents unrelated agent processes from inheriting credentials they do not use.
- OAuth provider tokens for connected apps stay with Composio.
Shared machines
Dash Bot assumes the logged-in operating-system user is the workspace owner. On a shared machine, other administrators may be able to read application data or inspect processes. Use a dedicated OS account for stronger separation.