Skip to contentText Pally
All recipes
Work

Wrangle your coding agents

Three agents running on your Mac, one text for status. Approve, steer, and ship from your phone.

Text Pally: How are my coding agents doing?
or message Pally on Telegram
Or scan to text Pally from your phone
You: how are my coding agents doing?
Pally: checking your sessions.
Pally: three running. api-auth: done, tests green, waiting on your ok to open the PR. dashboard-redesign: mid-run, wiring the new charts. data-migration: paused, wants permission to run the migration against your local db.
You: let the migration run, and tell dashboard to use recharts not d3
Pally: migration's running and dashboard-redesign is switching to Recharts. still want the api-auth PR opened?
You: yes
Pally: PR's up: github.com/you/api/pull/98

The routine

How it works

MMac

Pally can start and supervise real coding agent sessions, Claude Code or Codex, on your own Mac, each in its own isolated checkout. Ask for status, answer their permission requests, and redirect a run mid-flight, all from your texts.

  1. With the Pally Mac app installed, terminal control on, and a folder granted, tell Pally what to build and where.
  2. One text gets the real state of every session: running, finished, or waiting on you.
  3. Steer a run mid-flight: switch libraries, tighten scope, or ask what it changed.
The full routine

With the Pally Mac app installed, terminal control on, and a folder granted, tell Pally what to build and where. It starts a Claude Code or Codex session in an isolated checkout, so parallel tasks never collide.

One text gets the real state of every session: running, finished, or waiting on you. When an agent hits something risky, the request comes to your texts and you answer in plain words.

Steer a run mid-flight: switch libraries, tighten scope, or ask what it changed. Sessions run guided by default; hands-free mode inside its checkout is opt-in, per task.

Good for

  • Checking every running session with one text
  • Answering an agent's permission request from your phone
  • Redirecting a run that's headed the wrong way
  • Keeping parallel tasks in isolated checkouts
  • Kicking off the next task the moment you think of it

Things to try

You: start a coding task on the webapp repo: fix dark mode on the settings page
You: how are my coding agents doing?
You: tell dashboard-redesign to use recharts instead of d3
You: what exactly did api-auth change? show me the evidence

Before you start

Common questions

Where does the code run?

On your own Mac, through the Pally Mac app, in folders you granted. Each task works in an isolated checkout under your own developer accounts. Your code stays on your machine.

How is this different from Ship it from your phone?

Ship it queues one coding task on a GitHub repo and texts you the PR. This is the view for agents on your Mac: several sessions at once, live status, permission requests in chat, and mid-run steering.

Will an agent do something risky without asking?

Not by default. Risky actions pause and the request reaches you in your texts. You can opt a task into hands-free mode inside its own checkout.

Keep going

Related recipes

Pre-meeting briefsWalk in knowing who's in the room, your history, and what's still open, without doing the homework.Meeting memoryEvery decision, owner, and open question from your meetings, remembered and answerable.Slack sentryMentions instantly, busy channels in batches, bot noise demoted: Slack without keeping the tab open.

Last updated October 11, 2026.

Have your own recipe in mind?

Anything you'd hand a great assistant, you can hand Pally. Just describe it in a text.

Text Pally: hey pally
or message Pally on Telegram
Or scan to text Pally from your phone