Put Miles on your
pull requests.

Coding agents open pull requests all day. Somebody still has to check they're green, merge them, update the ones that fell behind, and chase the one that's red. That somebody is usually you, at your keyboard, with six tabs of CI open.

The Engineer is Miles doing that work on your own Mac, through the Miles app. It isn't a cloud sandbox with a copy of your code: it uses the checkout you already have, the git and GitHub CLI you're already signed in to, and the project's own scripts for its checks. It reads before it touches anything, runs your checks before it claims something works, and asks before anything that changes your repo.

This post is the recipe: set it up, connect GitHub, ask it for work, and — the part we're most excited about — let your other agents hand it their PRs.

Set it up

Six steps. The first four are the Engineer itself; the fifth is optional and keeps PR work moving while your Mac sleeps.

The GitHub token, exactly

Only needed for step 5. Create a fine-grained personal access token, pick Only select repositories, choose the repos the Engineer should work on, set an expiration, and grant these repository permissions:

Ask it from anywhere

Same Engineer, same leash, three doors.

What it does with a pull request

Six jobs have a written playbook — the same steps a careful senior engineer would take. Anything else, describe in plain words.

The leash

Handing an AI your terminal should feel uncomfortable. Every command is classified by its shape before it runs, and the strictest part of a command wins.

On top of the leash, the playbooks are careful in the boring ways that matter: it never checks out a branch over your uncommitted work (a dirty folder ends the job with Not done and a note), it switches back to the branch you were on, and it treats PR descriptions, review comments and CI logs as information — if one of them contains instructions aimed at Miles, it reports them rather than following them. Every job ends the same way: Done or Not done, why, the PR link, and exactly which commands it ran.

Hand it off from OpenClaw (or any agent)

If you already run coding agents — OpenClaw, a CI bot, your own scripts — they can pass their PRs to the Engineer instead of pinging you. The agent never gets the keys to your repo: the work runs on your Mac or through your token, and every push and merge still waits for your Approve.

1 · Give the agent a Miles API key

In Miles: Settings → API Keys → New key. Name it after the agent ("OpenClaw") so its handoffs are labeled in your runs. Copy it once — Miles never shows it again.

2 · Add the skill (OpenClaw)

We publish a ready-made OpenClaw skill. Drop it into your workspace's skills folder:

mkdir -p skills/miles-engineer
curl -o skills/miles-engineer/SKILL.md https://heymiles.app/api/skills/miles-engineer/SKILL.md

Then give it the key in ~/.openclaw/openclaw.json:

{
  skills: {
    entries: {
      "miles-engineer": { enabled: true, env: { MILES_API_KEY: "miles_live_…" } }
    }
  }
}

The skill teaches OpenClaw the rules: check the setup first, hand off with its own task id so a retry never doubles up, never claim a PR is merged until Miles says done, and when a task is waiting on approval, tell you what and where — never try to approve it another way.

3 · Or call the API directly

Any agent or script can do the same with one request:

curl -X POST https://api.heymiles.app/api/v1/engineer/tasks \
  -H "Authorization: Bearer $MILES_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "merge_when_green",
    "repo": "acme/app",
    "pr": 214,
    "externalId": "openclaw-task-9f2",
    "slack": { "channelId": "C0123ABCD", "threadTs": "1727300000.123456" }
  }'

It answers right away with a task that's running — or queued with the reason, like your Mac being asleep. Pass a Slack thread and the approval card and the result land in that thread. Follow along with GET /api/v1/engineer/tasks/:id, or subscribe a webhook to engineer.task.* events. Everything else — the six actions, errors, cancel — is in the API reference.

A few honest notes

• Your Mac has to be awake for code changes. Fixing CI and addressing comments need your checkout. Handed-off tasks wait for the Mac (up to a day by default) and start within seconds of it coming back. With the GitHub token, merges, reviews and branch updates don't wait.
• One Mac job at a time. Two jobs in one checkout would fight over branches, so the Engineer runs Mac jobs in order. A job waiting on your approval holds the line until you answer.
• It doesn't sit on slow CI. If checks are still running, merge when green stops with "checks pending" and lists them — hand it back later, or have your agent do it. No silent loops.
• Fine-grained tokens can't read GitHub "Checks". In the GitHub-API lane the Engineer falls back to commit statuses, Actions runs, and whether GitHub says the PR is clean to merge.
• Plans. Miles for Mac and agent runs come with Pro and Team. Each Engineer job is one agent run — Pro includes 50 a month, Team 100 per seat, pooled. macOS 13+ on Apple silicon today.

What's next

Runs started from Slack and the API showing up live in the Mac app, a hosted Mac for teams that don't want a laptop in the loop, and a native GitHub connection so there's no token to paste. If there's a PR chore you'd hand off tomorrow, tell us — support@heymiles.app.

---