Skip to main content
An agent that works the way you work. You already have tools, habits, and conventions. px0 automates them. You describe a recurring chore in plain English, and px0 writes it as a workflow you can run, schedule, and edit directly from your terminal. Everything stays on your machine. Your workflows, your notes, and your conventions are plain Markdown files in a directory you own. There is no server, no account, and no state stored in the cloud. But your workflows don’t stop at your laptop. Through Composio, px0 reaches the apps you already use: GitHub, Slack, Gmail, Notion, Linear, Jira, and over a thousand more.
That opens an interview - one question at a time, until px0 has the job, what it reads, where the result goes, when it runs, and what makes the output right. It writes the request back for you to approve or reword before anything is built. Enter on a blank line ends the questions early. px0 then asks about anything still genuinely ambiguous, finds the tools the job needs, and shows you the list before authorizing anything. Tools that can post or send get called out, so you can drop the ones you did not ask for. Then it writes the workflow file and prints its id, which you can override when it asks.

​
What px0 is for

  • Recurring reports you assemble by hand every week.
  • Chores that follow the same steps every time: draft the release notes, precheck a pull request, triage overnight alerts, file the standup update.
  • Work that has to sound like you, because px0 follows conventions you write down once.
  • A searchable library of everything you read, so you can ask questions across it later.

​
Workflows you could build

Each of these is one sentence you type into px0 workflows new, and each becomes a file you can edit and put on a schedule.

​
How it fits together

  • Workflows are the unit of work: Markdown files with YAML frontmatter, generated from your description and editable by hand.
  • Tools are how a workflow reaches outside px0. Most route through Composio, and apps authorize themselves the first time a workflow needs one; a few reach this machine directly - a file, a shell command, a URL.
  • Guidelines are your conventions, inlined verbatim into prompts so output comes back in your voice.
  • Brain is the library of what you have read and kept, searchable and askable.
  • Runs are the record of everything px0 did, so any output can be traced back to its inputs.
px0 has no model backend of its own. It shells out to a coding agent CLI you already sign into - claude, gemini, pi, or opencode - and reuses that CLI’s own login, model choice, and rate limits. What leaves your machine spells out exactly what that means for your data.

​
Start here

Installation

Install px0, pick a model backend, and scaffold your store.

Quickstart

Get a real output in a handful of commands.

Core concepts

The store, workflows, tools, guidelines, brain, and runs.

CLI reference

Every command, grouped by the entity it acts on.