Your inbox already knows.
Jobbox writes it down.
Every application you send leaves a trail in your mail — the confirmation, the recruiter's reply, the invite, the no. Jobbox reads that trail and keeps a board in step with it. It drafts each change; you accept it. You never type the same company name twice.
Unsigned build — macOS blocks it on first open.
Right-click the app → Open, or run xattr -dr com.apple.quarantine /Applications/Recruit.app
The same board, without the data entry.
None of this is work you weren't already doing. It's work you were doing from memory, at half past eleven, in a spreadsheet with three tabs and one column nobody has touched since June.
Amber on this page means a person is required. It shows up in exactly two places: the left column, and the Accept button.
Four steps. You're needed for two.
Setup happens once. After that the loop is sync, run, review — and review is the only one that changes anything.
-
01
Connect a mailbox you
Five minutes, once. Pick your provider, paste an app-specific password, test the connection. Gmail, iCloud, Fastmail and anything else that speaks IMAP. The setup guide has the servers, the ports, and the one switch that causes most first-run failures.
-
02
Sync jobbox
Pulls the last 90 days of your inbox and scores every message against a local filter — no model, no network, just the words. Anything that looks like your job search becomes a candidate, and each one keeps the reason it was picked.
-
03
Run jobbox
The agent reads the candidates and writes out what it thinks changed: a new application, a status move, an interview, a message filed against the right company. Every one of them names the mail it came from. A run takes a minute or two, and you can stop it mid-flight.
-
04
Review you
Accept or reject, one keystroke each. Accept is the only thing in the app that writes to your tracker. Everything before it is a draft.
Your tracker is untouched. Every tool the agent has appends a proposal and answers with the same sentence — nothing has changed in the tracker yet — because that is all those tools can do. The code that writes an application, a status or an event is reachable from one button, and you press it.
It proposes. You decide.
Automation you have to double-check is worse than no automation. So the rule isn't "trust it" — it's that everything it does arrives as a change you can read in a few seconds and throw out with one key.
Every proposal shows its source
The messages that caused it, with senders, dates and the score that flagged them. If the reasoning doesn't hold up, you can see that without leaving the card.
Rejecting costs nothing
The application stays exactly as it was. There's nothing to undo, because nothing was done — the proposal is marked rejected and the queue moves on.
The agent can't reach your tracker
It has no tool that writes one. Not a restricted one, not a careful one — none. The only path into your data runs through Accept.
It can't touch your mailbox
No sending, no replying, no deleting, no marking things read. Jobbox opens your mailbox to read it and closes it again. Marking a message handled is local to your Mac.
One place where the search is actually true.
Six columns in the order a search moves. Open a card and you get the whole history of that application — what was sent, what came back, what got scheduled — and the calls it owes you are on their own screen.
And the mail is still mail
Jobbox is a mail client too. Every card links back to the actual message, unedited, the way it arrived — including the ones you disagree with the filter about. When a proposal looks wrong, the disagreement usually started at a phrase like "thanks for applying" or "schedule a call", and that phrase is on the card.
Runs on your machine, under your login.
There is no Jobbox account, no Jobbox server, and nothing of yours on anyone's disk but your own.
A Mac
Apple Silicon or Intel. The database is one file in your application-support folder; delete it and Jobbox is gone.
A mailbox that speaks IMAP
An app-specific password, not your account password. Jobbox keeps it in the macOS Keychain and stores only a reference to it.
Claude Code, signed in
The agent is the claude CLI on your own machine, running under your own login. Your mail is read locally, by a tool you already have.
Reading your mail with a model means the model sees the mail it reads. That's the deal, and no privacy page changes it. What Jobbox controls is everything else: a run only ever sees the messages on its own list, written before the run starts, and it has no file access, no shell and no browser. When it finishes, its access is revoked.
What this version doesn't do.
v1 is deliberately narrow. Better you read this here than find it out on a Tuesday.
Stop updating the spreadsheet.
Connect a mailbox, run it once, and see what it finds in the last ninety days. If the proposals are wrong, reject them — nothing moves either way.
Unsigned build — macOS blocks it on first open.
Right-click the app → Open, or run xattr -dr com.apple.quarantine /Applications/Recruit.app