pablo

Personal Assistant for Boring Logic & Operations

PABLO watches your pull requests and launches the right AI agent, in the right worktree, when something needs doing.

Website · Documentation · Quickstart

Quickstart

curl -fsSL https://getpablo.dev/installer | bash   # interactive: pablo on your PATH, scheduler + dashboard running

cd ~/path/to/your/repository
pablo project:new                  # a short wizard
pablo task:start <issue-url>       # branch + worktree + an agent writing the plan

Then watch your tasks on http://127.0.0.1:8321 or with pablo task:list.

You need:

• Linux or macOS;
• git;
• gh, logged in (gh auth login);
• curl, and sha256sum or shasum, to download and verify PABLO;
• a runtime, the agent CLI: OpenCode (default), Claude Code or GitHub Copilot CLI (experimental);
• an agent environment (ADE), where agents run: Orca (default), OpenChamber (OpenCode only), or none (headless: agents run in the background).

PABLO itself is a single binary: no PHP needed.
Using Jira or Linear (experimental), or want the details, such as setting your model? Read the Quickstart and the installation guide.

What PABLO never does

Agents propose; you decide. PABLO writes no code of its own: only the rebase conflict resolver agent edits files, to replay your branch. It never touches your issue tracker (GitHub Issues, Jira, Linear stay read-only), never merges or closes a pull request, and never comments or reviews. It never writes a commit of its own: commits happen only when you run /pablo-commit-and-pr, which also pushes. It pushes otherwise only with sync's sync.auto_apply (off by default), which rebases (or merges, per sync.strategy) a clean worktree onto its base branch and pushes with --force-with-lease, never plain --force, and when the conflict resolver pushes its replay of such a rebase the same way. The full list: What PABLO may change.

Learn more

• Documentation: configuration, states, agents, dashboard, troubleshooting;
• Contributing: run it from a checkout, tests and QA;
• Licence.