Companion Permissions
What the companion needs access to, and what it doesn’t.
- Microphone access — only if you use voice input; text input works without it.
- The companion overlay itself does not require elevated OS permissions beyond normal window display.
- Companion memory (goals, routines) is stored locally; resetting it is an irreversible, always-confirmed action — the same confirmation discipline as any other destructive action.
How it works
What you see
- A desktop companion you talk to by voice or text, with optional spoken replies, personality and appearance settings, and live task progress.
- You can customise personality, voice and appearance, including uploading your own compatible 3D model.
What PawOS does
- Requests you make to the companion go through the same task and permission flow as typed ones.
- Your speech is shown as text so you can review it before sending; spoken replies read summaries, not raw logs.
Permissions
- The companion follows the same permissions as everything else — it cannot skip an approval.
- Appearance and personality never change billing, connections, files, commands or security.
Records
- Tasks started through the companion leave the same Work Records as typed tasks.
Good to know
- Push-to-talk with review-before-send is the input model.
Related