Permissions

Any action classified as destructive is refused before it runs unless the request carries an explicit confirmed flag. This is checked by the execution engine, not left to individual features to remember to implement.

• Writing or deleting a file, running a command, installing software, changing PATH or an environment variable, committing to git, and deploying are all in this destructive set.
• A first-time browser navigation to a non-local, non-deployment URL is confirmed once per session; subsequent navigation in that same session doesn’t re-ask.

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.

Types of approval