Skip to content
PawOS Docs

Quickstart

A five-minute walkthrough of your first session.

  1. 1

    Sign in

    Paw Go (free) requires only an account — no payment method.

  2. 2

    Say or type something low-risk

    "Open my downloads folder" is a good first request — it exercises the full plan → confirm → execute loop without touching anything sensitive.

  3. 3

    Watch it narrate

    PawOS describes what it’s about to do before doing it, and asks for confirmation before anything destructive.

  4. 4

    Check Working History

    Every completed request leaves a real Work Record — open it from the sidebar to see exactly what ran.

Tip

Push-to-talk and the companion toggle are the two most-used shortcuts — both are shown once in Settings on first launch, and are reconfigurable afterward.

How it works

What you see

  • The PawOS desktop app: your companion, the conversation panel, task progress, workspace selection, account and billing screens, and permission questions when an action needs them.
  • After signing in you choose a workspace folder, and PawOS asks before it does anything that changes your machine.

What PawOS does

  • PawOS turns each request into a task and keeps a record of what happens.
  • For files and code, the workspace folder you picked is the project boundary.
  • For coding work, PawOS can inspect your project, plan changes, apply them, run commands and tests, and report the results.

Permissions

  • Signing in does not give PawOS blanket permission: editing files, running commands, installing tools, connecting accounts or deploying each ask for approval.
  • Approving a plan and approving an action are separate — a plan can be approved while later actions still ask first.
  • Your plan determines which kinds of work PawOS can carry out.

Records

  • Every completed task leaves a Work Record: the actions that ran, their output, files changed, and test results.

Good to know

  • Project analysis is deepest for TypeScript and JavaScript projects; other languages are fully editable.
  • Local permissions, missing dependencies, organization policy or your plan can stop a request from running — PawOS tells you which.

Related