YOU APPROVE.
THEY WORK.
Jackie runs the Claude Code agents on your own computers. Tell the Lead what you want. Workers build it in a sandbox, and nothing merges until you Allow it.
For iPhone and Linux computers
How it works
TELL IT ONCE.
One line to the Lead, from your phone or your desk. Then you only hear from it when it needs you.
Tell the Lead: from Ops on your phone, or on your desktop
It plans with you: the plan comes back as one question before anything starts
Workers build it: each on its own branch, in its own copy of the repository
You Allow the merge: one push on the lock screen, behind Face ID
Workers
EVERY WORKER
IN A SANDBOX.
A Worker can write only in its own copy of the project and has no network. Anything riskier comes to you first.
Its own worktree: a fresh copy from main, on its own branch
No network, no keys: your credentials stay out of its reach; the agent pushes its branch and opens its pull request
Risky steps ask you: merges, installs, network and anything outside its folder
In plain words: each request says what it will do and why, with the exact command one tap away
Approvals
NOTHING MERGES
WITHOUT YOU.
When the Workers are done, the Lead asks once. Allow on the lock screen and each pull request is squash-merged.
Allow needs Face ID: Deny is one tap
Merged as you saw it: if a branch moves after you look, that merge stops
Every open pull request: across your computers on one list, ready to merge first; swipe a ready one to Merge
The app
FOUR TABS.
ALWAYS.
Each tab is a board: a time, a name and one word for where it stands, with only what waits on you lit.
Ops: what waits on you, every open pull request, the work map, today’s timeline and the budget
Agents: the Lead, Foremen, Workers and the queue, and chat with Claude on your own subscription
Projects: one row per repository, and a Foreman for any one of them
Fleet: your computers, what they did, their security and their usage
Your computers
ONE LEAD.
EVERY COMPUTER.
Link each computer once. The Lead can start Workers on any of them; before it uses another computer, you Allow that from your phone, for 12 hours at a time.
A Foreman per project: it sees and acts on that project only
A queue, not an error: when a computer is full, the next Worker waits its turn and starts by itself
A budget that holds: near a usage limit the Lead prefers smaller models; at the edge, new Workers wait for the reset
Local models too: a Worker can run on an Ollama model on its own computer
More
AND
THE REST.
Your own sessions: start Claude Code in any project, answer it, interrupt it
Terminal: a real one on the computer, from the phone
Files: browse, search and read a computer’s home folder; keys are never listed
New project: adopt a repository, clone one from GitHub, or start empty
On the desktop
THE SAME BOARD,
ON OMARCHY.
Jackie for Omarchy has the phone’s four tabs on your desktop, a popup with Allow and Deny when an agent or the Lead needs you, a picker that lists your agents first, and a count in the bar.
Yours
YOUR MACHINES.
YOUR ACCOUNTS.
Your phone talks to your computers: directly, over your own Tailscale network, not through our servers
Your agents run under your accounts: Claude Code on your own subscription, or a model you host
Alerts are sealed: Apple and Expo see only “Jackie” and a generic line
No analytics. No tracking. Nothing is used by us to train a model.
What you need
IPHONE
AND LINUX.
Jackie is for iPhone. The Jackie agent runs on Linux, on each computer you link, next to Claude Code and Tailscale. The desktop app is for Omarchy.
JACKIE
You approve. They work.
Not out yet. Leave an address and you’ll be told the day it is.