Tool execution problems

• Confirm you’re on Paw Pro or higher — taking actions requires Pro; Paw Go is read-only. See Billing → Plans.
• Check whether a confirmation is pending — a destructive action waits for your explicit yes before it runs.
• Check the request’s Work Record for the real, specific failure reason rather than assuming.

How it works

What you see

• What to check for common situations: sign-in, commands, installs, PATH, connections, usage limits, payments, previews and builds.
• What PawOS already checks for you, and what to gather before trying again.

What PawOS does

• PawOS reports problems in the task view, Work Records, connection status and check results.
• For commands, installs, builds and tests it shows the real output.

Permissions

• Never bypass permission questions or run unsafe commands to get past a problem.
• If a plan, connection permission, local permission or administrator approval is missing, retrying won’t help until that changes.

Records

• Useful details: the task, what it was doing, the command and its result, file paths, check results, and a screenshot if something looks wrong.

Good to know

• Some fixes happen outside PawOS — in a service’s dashboard, your system settings or your account.