Skip to content

Engineering work, carried through.

PawOS helps developers plan and carry out supported engineering tasks, with a clear view of the work and its results. Choose Desktop for your Windows environment, CLI for a local project folder, or Web for chat and GitHub-connected work.

Engineering work crosses tools. PawOS helps connect the steps.

A code change can involve understanding a project, editing files, running commands and reporting the result. PawOS supports that work in three distinct ways: Desktop on Windows, CLI in a local project folder, and Web for browser chat and GitHub-connected repository changes.

Start with what you need.

PawOS Desktop gives you a graphical place to start a task, continue a conversation, and work with projects. Use the desktop app when you want PawOS alongside your local environment.

From a request to reviewed changes

A terminal interface for local projects

PawOS CLI works from a local project folder. It can inspect the project, propose a plan, request approval for file changes or commands, and report the checks it ran.

PawOS Web

Select your repo and start coding from the web.

PawOS Web offers browser-based Chat and Code modes. In Code mode, connect GitHub, choose a repository and describe a change. Web works with the connected repository; it does not access your computer's files or terminal.

  1. 1Connect GitHubSign in with GitHub — from your computer or your phone.
  2. 2Pick a repositoryChoose the repo Paw should work in.
  3. 3Describe the changeReview the proposed change and its available checks.

Work from the folder you choose.

The CLI starts by identifying the current folder, Git branch, and repository. You can then describe a task in the terminal and review the proposed work before proceeding.

See the checks that ran.

The terminal asks before running the lint command and shows it in progress. A separate PawOS CLI capture records the lint and build results.

ShopFlow storefront live preview, showing the product cards and store navigation.
PawOS CLI proposing an edit to src/App.css in the local ShopFlow project.
PRODUCT RECORDING

PawOS in action.

The first recording shows the ShopFlow e-commerce live preview built with PawOS. The second shows PawOS CLI preparing an edit in the local ShopFlow project. Use each player's controls to review the recordings.

Work doesn't live in one place.

Your project may begin in a folder, continue in code, depend on a terminal command, pass through Git, and end with a ticket or message. PawOS is built to carry the context across those boundaries. Connected services expose different actions, depending on each integration.

REQUEST
Fix the authentication issue.
01Incoming task
WORKSPACE
Read the project. Inspect the relevant files.
02Files & Code
EXECUTION
Change the code. Run the environment.
03Terminal
VERIFICATION
Verify the result. Commit to Git.
04Version Control
REPORTING
Report the result through supported connections.
05Issue tracker

Where PawOS is today — and where we're taking it.

Desktop, CLI and Web each support different parts of an engineering workflow. Here is what is available today and what we are still working toward.

01

A companion that executes real work.

On Windows, PawOS Desktop can work with supported local projects and development tools. Depending on the task and permissions, it can inspect files, make changes, run commands, install software and help repair environment issues.

Understand an existing project
Change and refactor code
Install software and configure environments
Fix paths and development issues
Run commands and verify results
Work with Git and project files
02

Deepening the working environment.

We are improving how people review work in PawOS. The details shown depend on the experience and task; check the current product and documentation for what is available.

Review the task plan before work begins
See command output and reported results
Approve actions that require confirmation
Choose the experience that fits the project
03

Expanding across connections.

A task may involve a local project, terminal commands, Git and a connected issue tracker. PawOS can help with supported steps, but the actions available depend on the product experience and each connection.

04

Autonomous execution.

PawOS includes ticket-based workflows for supported plans and connected services. They can stop when a step needs approval or a required capability is unavailable; they do not guarantee a fix or pull request for every ticket.

Request→Understand→Plan→Approve→Execute→Verify→Report
05

Organizational direction.

Team and Enterprise features add organization workspaces, administration and governance. Availability depends on plan and configuration; contact the team to discuss an organization rollout.

Collaborative PawOS workspaces
Granular RBAC and policies
Enterprise SSO and delegated access
Budgets and execution controls
Organization-wide connected workflows
Deeper team collaboration

Tools that help move engineering work forward.

PawOS is focused on engineering tasks that span a project, its tools and connected services. We are building toward more continuity between those steps, while keeping each experience within its supported access and permissions.

Why we're building PawOS.

We started PawOS because discussing a code change and carrying it out are different jobs.

When a developer sits down at a computer, they don't just read code. They install dependencies, they navigate the file system, they run commands in the terminal, they debug failing builds, and they track their work in Jira. The work is connected.

PawOS is being built to help with the steps between a request and a checked result. It can work with local projects in Desktop or CLI, and with connected repositories in Web. Each experience has its own boundaries, and PawOS reports what it could and could not verify.

EARLY ACCESS

PawOS is preparing for its next release.

See how PawOS can fit into your everyday engineering workflow. Join the early-access list and get real PawOS workflow demonstrations before the next release.

Tell us which engineering workflows matter to you and we'll share updates as PawOS develops.

Which work would you like help with?

Select the engineering tasks you would like PawOS to support.

Select every workflow that applies.

Join PawOS Early Access

We'll only use your details for PawOS early-access updates.

Your next task starts here.