System Requirements
What you need for PawOS Desktop on Windows, and for PawOS Web on a computer or phone.
PawOS Desktop is for Windows only, and is installed from the Microsoft Store. PawOS Web runs in a browser on any computer or phone, with nothing to install.
PawOS Desktop (Windows only)
| Requirement | |
|---|---|
| Operating system | Windows 10 (64-bit) or later |
| Memory | 4 GB RAM minimum (8 GB recommended) |
| Install from | The Microsoft Store |
Note
A graphics card with 3D acceleration is recommended for smooth companion animation — PawOS still runs without one, with reduced animation quality.
PawOS Desktop is not currently available for macOS or Linux. On a Mac or a Linux computer you can use PawOS Web in your browser, and the PawOS CLI in your terminal.
PawOS Web and Mobile (any browser)
| Requirement | |
|---|---|
| PawOS Web | A current web browser on Windows, macOS or Linux. Nothing to install. |
| PawOS on a phone | A current mobile browser on your phone. Nothing to install; you can add PawOS to your home screen. |
| A phone paired with PawOS Desktop | The phone’s browser, and PawOS Desktop running on a Windows computer signed in to the same account. |
PawOS CLI
The PawOS CLI needs Node.js 20 or newer and runs local project work from your current folder. It can use PawOS account services after sign-in; it does not require PawOS Desktop or the Web app to be installed. Sign-in may hand off to a browser.
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