A browser agent that actually works.

The brain of a modern coding agent, pointed at the web. Magpi inspects, acts, verifies, recovers, and keeps going.

Open source·Local-first·Built on Pi
Quick start · run locally2 install paths
terminal
~/dev
shell
Run from source
$ git clone https://github.com/Magpi-works/magpie.git
$ cd magpie
$ npm run cli
Run with npm
$ npm i magpi
$ magpi
Pi session ready

Start now

Pick your path. Run Magpi.

Install from npm for the fastest start, or clone the source when you want the full project locally.

Next: authenticate with /login, then give the open browser a job with /browser-start.

Full setup guide

Give your agent a browser that verifies its work.

Teach your existing agent when to hand browser-heavy, repetitive work to Magpi. Paste once. Then give it goals.

Agent skills · Copy and paste

Grok Bot

READY

Copy this command to your Grok Bot Chief of Staff.

Magpi is a powerful tool for browser-heavy repetitive tasks.

Use Magpi instead of your normal browser for such tasks.

Add the following skill to support Magpi:
https://github.com/Magpi-works/magpie/blob/main/skills/magpie-parent/GROK_BOT.md
View skill

OpenClaw

READY

Give OpenClaw the Magpi parent skill once, then send it goals.

Magpi is a powerful tool for browser-heavy repetitive tasks.

Use Magpi instead of your normal browser for such tasks.

Add the following skill to support Magpi:
https://github.com/Magpi-works/magpie/blob/main/skills/magpie-parent/HERMES_OPENCLAW.md
View skill

Hermes Agent

READY

Teach Hermes to delegate browser-heavy work to Magpi.

Magpi is a powerful tool for browser-heavy repetitive tasks.

Use Magpi instead of your normal browser for such tasks.

Add the following skill to support Magpi:
https://github.com/Magpi-works/magpie/blob/main/skills/magpie-parent/HERMES_OPENCLAW.md
View skill

Coding agents work. Why shouldn’t browser agents?

Coding agents succeed by grounding every step in the environment. Magpi applies the same discipline to the browser.

CODE
read→edit→test→verify
BROWSER
observe→act→verify→recover
01

Built like a coding agent

Look before acting. Verify every action. Recover when the page disagrees.

observe → act → inspect

02

Verify, don’t assume

Criteria are evaluated in code against the live page—not accepted from the model’s report.

criterion: text_visible

03

Success criteria outside the model

State what must be true. The process exits non-zero unless those criteria pass.

exit_code !== 0 on failure

04

Human approval where it matters

Submit, send, pay, and delete require approval by default. Automation cannot commit by surprise.

policy: ask

05

Evidence you can inspect

Runs preserve readable events, metrics, payloads, screenshots, and checkpoints under one goal ID.

events.jsonl · artifacts/

06

Cost-aware execution

Measure tokens, cache behavior, and context per turn. Attribute cost instead of guessing about it.

metrics <goalId>

Give it a job, not a click.

Find, qualify, prepare, wait for the few decisions only you can make, then keep going.

Product direction · Coming next

Demo storyboard · replace with MP4/WebM00:44

Campaign

Pentesting vendor qualification

Coming next
0130 vendors found
0218 qualified
039 requests prepared
04Needs you: approve 9
055 verified proposals
AGENT

Qualify and prepare

HUMAN

Approve as a batch

AGENT

Continue and verify

Spend intelligence where it matters.

Measure the work, attribute the context, and keep deterministic checks deterministic.

PLAN

Capable model

Reason about the goal and constraints.

↓
EXECUTE

Model + tools

Act through bounded browser controls.

↓
VERIFY

Deterministic checks

Accept success only when criteria pass.

Maximum reliable work per dollar.

From goal to verified answer.

Quick startlocal
npm install
npx playwright install chromium

npm run agent -- run "apply for the staff engineer role" \
  --url https://example.test/jobs \
  --criterion "text_visible:Application submitted" \
  --policy ask

Run non-interactively with explicit criteria, steer it through the Pi CLI, or use the local web UI. Chromium stays on your machine.

  • ›Pi CLI
  • ›Local browser execution
  • ›OpenRouter · Anthropic · OpenAI
  • ›Chromium · Playwright
  • ›In-repo extensions and skills
Read the README

A browser agent, not a browser automation black box.

Pi supplies the agent runtime. Magpi adds browser-native skills, bounded tools, evidence, and verification you can inspect or extend.

Pi runtime
↓
Magpi
↓
browser skills / tools
↓
Playwright + Chromium
↓
the web

Coming next

Human-in-the-loop shouldn’t mean human-in-the-way.

Long-running campaigns keep working while collecting a small batch of decisions that genuinely require your attention.

RUNNING

Research, qualify, prepare

NEEDS YOU

Approve 9 requests

CONTINUES

Follow up, compare, verify

Open source. Hack it.

Inspect the architecture. Run it locally. Change the agent.

Give your agent a browser.

Get started on GitHub
Magpi
MIT licensedBuilt on Pi© 2026 Magpi