Skip to content
Skip to content
PilotPods

Local first, runs on your Mac

Run a team of AI agents from one Mac

Name a Pilot COS, give it tasks from a localhost console or the CLI, and let Pod COSs run pods of workers through Claude, Codex, Antigravity and Gemini. Budgets, approvals and a STOP ALL button keep you in charge.

Get started See the console
  • MIT licensed
  • No cloud account
  • Budgets and approvals
pilotpods
$
  • Pilot COSdirects
  • Research podrunning
  • Approvalwaiting

Why PilotPods

An operating system for agent work, on hardware you own

Four ideas hold the product together.

Local and private

One SQLite database per instance. No telemetry and no outbound calls except to the engines you choose to use.

You stay in control

Daily budget caps, approvals for risky steps, and a red STOP ALL that ends every session.

Many engines

Claude (including Amazon Bedrock), Codex, Antigravity and Gemini run work. Grok is monitor only.

Isolated instances

Run several instances side by side, each with its own data, ports and budget.

How it works

You set the goal. The Pilot COS runs the pods.

Tasks go from you to the Pilot COS, then to Pod COS leads. Each Pod COS manages a small pod of workers on the engine you choose.

  1. 1

    Create an instance

    A named instance is a private data directory, its own ports and its own budget.

    Terminal
    $ ./pilotpods init --instance default
  2. 2

    Add a pod and its COS

    Create a pod, then hire a Pod COS into it to manage the work.

    Terminal
    $ ./pilotpods pod create --help$ ./pilotpods hire --help
  3. 3

    Open the console

    Watch pods, approve steps and keep an eye on spend from localhost.

    Terminal
    $ ./pilotpods ui --open

Engines

Bring the agents you already use

Each pod runs on an engine adapter that calls the tool already signed in on your Mac. An engine that is not installed says so.

  • Claudeincl. Amazon Bedrock
  • CodexCLI
  • Antigravitylocal app
  • GeminiCLI
  • Grokmonitor only

Detect what is installed

Lists all five engines with their live install state.

Terminal
$ ./pilotpods engines list$ ./pilotpods engines detect

Console

A flight deck on localhost

The web console is served from your Mac on 127.0.0.1. See every pod, what is running, what waits for you, and press STOP ALL.

  • Pods and Pod COS leads with live state
  • Approvals waiting for your decision
  • Spend against the daily cap
  • Engines tab with install state
Terminal
$ ./pilotpods ui --open
127.0.0.1 / consoleSTOP ALL
Pods
3
Open tasks
7
Spend
$4.20
Daily cap$4.20 of $20.00
  • Research podrunning
  • Build podwaiting approval
  • Review podidle

Safety

Power with brakes

Agents work freely inside limits you set. Each limit is a real command or setting.

Budget caps

Spend is recorded against a daily cap for the instance and every record lands in the audit log.

Terminal
$ ./pilotpods spend record 1.00 --instance default

Approvals

Approval and QC decisions are written to an append only register, with a reviewer and notes.

Terminal
$ ./pilotpods audit list --help

STOP ALL

One command ends every session and stops the daemon for an instance. It needs the --all flag so it is never an accident.

Terminal
$ ./pilotpods stop --instance default --all

Local and private

Do not take our word. Check it.

PilotPods ships a command that checks its own claims on your machine.

Terminal
$ ./pilotpods verify-isolation --instance default
  • Zero outbound network calls from PilotPods itself
  • No tracking code
  • No writes outside the instance data directory

One Mac

no shared state between instances
default
  • own SQLite database
  • own port range
  • own budget cap
project-a
  • own SQLite database
  • own port range
  • own budget cap
project-b
  • own SQLite database
  • own port range
  • own budget cap
  • Back up and restore an instance: pilotpods backup, pilotpods restore
  • Append only audit log of wakes, stops, approvals and spend
  • Licence and source on your disk

Run your first pod in minutes

Install on a Mac, create an instance, and open the console. Everything stays on your machine.

Get started Read the docs
  • MIT licence
  • No telemetry
  • CLI and console
Quick start
$ ./install.sh$ ./pilotpods init --instance default$ ./pilotpods ui --open