System Actions
Installing software and modifying PATH — the highest-privilege actions PawOS takes.
Installing software and modifying system PATH/environment variables are the most system-invasive actions PawOS can take — always confirmed, and PATH/environment writes can request real Windows administrator elevation.
Implemented
Currently these actions are gated only by that one-time confirmation, not by a subscription-tier check — see Coding → Software Installation for the full, verified detail.
How it works
What you see
- Permission questions, connection approval screens, blocked-action messages, workspace boundaries and system-change warnings.
- When something is blocked, you see why.
What PawOS does
- Security-sensitive actions are carried out by protected parts of the app that the interface cannot bypass.
- Commands follow strict rules that prevent injected or chained commands.
- Credentials stay in each connection’s secure storage — you never paste them into chat.
Permissions
- No plan approval, companion setting or urgency can skip a permission question.
- Changes to files, commands, git, installs, system settings, deployments and connected services always need approval.
Records
- Security-sensitive actions record the request, the approval, the result, and why anything was blocked.
Good to know
- Review plans, diffs, commands and deployments before approving them.
- Your operating system and connected services have their own permission prompts and policies.