Skip to content
PawOS Docs

Overview

Unattended investigate → plan → implement → validate on a real ticket.

Autonomous Work drives a real engineering cycle against a connected ticket — investigate, plan, implement, and validate — without a human present for each step, using the same execution engine and Coding Runtime a normal chat session uses, orchestrated headlessly.

It is not a second, separate coding engine. A dedicated ConversationRuntime instance is fed the ticket as a synthetic request and drives the same tool-calling loop a human-typed request would.

Lifecycle

  1. 1

    Investigate

    Real evidence is gathered — console output, network requests, repository history, prior engineering memory — before anything is proposed.

  2. 2

    Plan

    A concrete implementation plan is drafted and tracked as a live TODO list.

  3. 3

    Implement

    Edits are applied using the same file-editing mechanism described in Coding → Code Editing.

  4. 4

    Validate

    Real tests and the validation pipeline run against the change.

  5. 5

    Report

    A structured engineering report captures what was found and changed, persisted as real memory.

Partially implemented

Deploying as part of this lifecycle, where applicable, goes through the same Infrastructure Runtime and approval gate as a manual deploy request — it is not automatic for every run.

How it works

What you see

  • An unattended run for a ticket: investigation, plan, implementation, checks, completion and charge.
  • Eligibility, connection status, your Ticket Wallet balance, ticket details, evidence and the final result.
  • Before/after evidence and a summary of what was fixed, in your Ticket Wallet history.

What PawOS does

  • PawOS investigates the ticket and repository, works in an isolated copy, applies and checks the fix, and records evidence.
  • Ticket Wallet credits are separate from Paw Compute and are charged only when a ticket is successfully completed.
  • Each ticket is charged at most once.

Permissions

  • Autonomous Work never installs software, changes system settings or skips your organization’s approval rules.
  • Each connected service offers specific actions — see Connectors for what each one supports.
  • A blocked, failed or unverified run is never reported as completed.

Records

  • Completion is backed by the repository state, check results, changed files and the charge record.

Good to know

  • You need an eligible plan, a connected account, a repository and Ticket Wallet credits to start a run.

Related