Installation
How to install PawOS for Windows.
PawOS Desktop is a self-contained app for Windows only, installed from the Microsoft Store — nothing else needs to be installed first.
- 1
Get PawOS from the Microsoft Store
Open the PawOS listing in the Microsoft Store and choose Get or Install. On this site, Download for Windows asks you to request early access, and the email you receive links to the same Microsoft Store listing.
- 2
Let the Store install it
The Microsoft Store downloads and installs PawOS for you. There is no separate installer file to run.
- 3
Sign in
Open PawOS and sign in. Workspace and system permissions are requested only when a task needs them.
PawOS Desktop for Windows is installed from the Microsoft Store.
Get PawOS Desktop for WindowsWarning
Only install PawOS from its Microsoft Store listing.
Note
The repository’s existing Desktop 1.0.4 MSIX is unsigned, has no matching WACK report or verified source provenance, and has not passed disposable-environment installation/runtime testing. It is not certified or ready for Partner Center. This local artifact does not establish which version, if any, the separate Store listing currently serves.
First launch
On first launch you’ll be asked to sign in (Paw Go, the free tier, requires only an account) and grant OS-level permissions PawOS needs for its companion overlay and, if you use voice, microphone access.
- What if launch fails?
- Make sure you installed PawOS from the Microsoft Store, that Windows allowed the app to run, and see Troubleshooting → PawOS won’t start.
- Do I need anything else installed first?
- No — the PawOS installer includes everything the app needs.
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.