The Pilot

The Pilot runs your job search without you. You tell it what you're looking for and set some limits. It then finds and scores jobs, applies, contacts people and follows up, reads recruiter replies, and drafts interview replies, prep notes, and posts.

You can see everything it does in a journal that updates live. When it needs a decision from you, it asks a short question, and it can send that question to your phone.

The Pilot does the same work as campaigns, so you don't need to run those yourself. They're all still there if you want to do something by hand.

How it works

The Pilot does its work in small steps called cycles. Each cycle does one thing:

looks for work ──► picks the most useful task ─┬─► finds jobs ────┐
                                               ├─► scores them ───┤
                                               ├─► applies ───────┼─► writes to the journal
                                               ├─► reaches out ───┤
                                               └─► writing tasks ─┘

1. Look for work. A small program on your computer asks the server what needs doing: questions you've answered, jobs you've approved, replies to read, searches that are due. If there's nothing, it goes back to sleep without starting the AI, so an idle Pilot doesn't use any of your Claude or Codex quota.
2. Pick a task. If there is work, it takes the most important task and starts the AI on it with a fresh, empty context.
3. Do the work. Browser tasks go to a helper agent built for that one job. One finds new jobs on a board, one scores them, one fills in a single application, and one finds a contact and writes the message. Each helper only reads what it needs, which keeps usage down. Tasks that are just writing, like reading a reply or making prep notes, the AI does itself.
4. Write it down. The result goes into the journal. If more work is waiting, the next cycle starts a few seconds later. If not, the Pilot waits for your check interval.

It does one task per cycle on purpose. Each result is saved on the server before the next task starts, so if your computer crashes, restarts, or goes to sleep, nothing is lost and the next cycle carries on from there. The program also restarts runs that get stuck and starts up again after a reboot, so you don't have to keep a browser tab open.

Starting it

1. Check that the agent is running in the dock on the right of the dashboard. If it's offline, see Getting started.
2. Open Pilot in the workspace, write your instructions, and save.
3. Press Start.

The first start links your computer to the Pilot. From then on the terminal host keeps it running after a reboot, crash, or sleep until you stop it.

Your instructions

The Instructions tab shows Goals, Searches and Research at the top. Everything else is optional and sits under Advanced settings.

• Goals. Describe what you want in your own words: the kind of role, what matters most, and any hard limits. For example, "senior TypeScript, remote, at least $150k, by October". This is the only part you have to fill in.
• Searches. The Pilot writes these from your goals. A search that keeps finding new jobs runs again soon; one that keeps coming up empty runs less often. You can see each search here, with how many jobs it found recently and when it runs next, but you can't edit them.
• Research. Searches beyond your boards; see Research below.
• Operating limits. How many applications a day, the lowest match score worth applying to, and how often to check for work.
• Networking. Off until you turn it on. Set a daily limit and how long to wait before following up, then choose how much freedom it has on each channel. Email can be Draft only, Review each, or Auto-send. LinkedIn goes no further than Review each, so nothing is ever sent there without you.
• Boards. Which job boards to search, in order. The Pilot moves to the next board each cycle so they all get searched. If you leave this empty, each search sticks to the board it was created on.
• Platforms. Where the Pilot may draft posts about you. It never publishes them; you review every one.

Each search, the job alert import, and research keep one campaign each, which stays open between runs. Pausing that campaign pauses its search or feed until you resume it, and the Pilot won't ask whether to restart it; Run now or Research now resumes it too.

Research

Boards miss many postings, mostly university and research-institute portals and lab pages. Research searches the open web for postings that fit your goals, reads each one, scores it, and adds it to the Research campaign. From there good matches are applied to like any other.

• When it runs. Once when you first set goals, then weekly, and within a day when most of your searches keep coming up empty. Research now runs it on the next cycle.
• Cap-exempt employers. Universities, their affiliated hospitals and institutes, and nonprofit or government research employers can sponsor an H-1B outside the yearly cap. When the Pilot finds evidence of that, the job gets a Cap-exempt tag that links to it. Turn on Prefer H-1B cap-exempt employers in Settings to have those jobs applied to first.
• Boards worth adding. The run summary names sites that kept turning up good postings. The Pilot never adds a board itself.
• It never logs in, signs up, contacts anyone, or applies while researching.

The goals guide the Pilot's judgment, but the limits are hard rules. The server enforces them, so the Pilot can't go over a limit however your goals are worded. You can change anything at any time, and the next cycle picks up the change.

What it does alone and what it asks about

Everything in the right-hand column turns into a question for you. The Pilot never sends, posts, or changes an application's status without your say.

Questions and notifications

When the Pilot needs your decision, it creates a question: a small card under Needs attention on the Overview tab. Anything that depends on the answer waits until you reply. To get a push notification when a question comes in, even with the dashboard closed, turn on notifications under Settings → Notifications. You do this once per device.

Most questions wait as long as you need. Login codes are different. They expire after about five minutes, and if you miss one the Pilot skips that job and moves on. Codes sent by email never reach you as questions, because the agent reads them from your inbox.

The journal and daily summary

Everything the Pilot does is logged in the journal on the Activity tab. You can filter it by type, or group it by cycle to see what each cycle did, how it went, and how long it took. The Overview tab shows the latest entries and when the next cycle is due.

Once a day, after 07:00 UTC, the Pilot writes a summary of the past 24 hours: applications sent, replies read, messages sent, and questions waiting for you. Export downloads the whole history as a file.

Interviews

When a recruiter invites you to interview, the Pilot drafts a short reply with your availability and shows it to you for approval. It never sends that reply itself. It also writes prep notes covering behavioral, technical, and system design questions plus notes on the company, and attaches them to the application.

Troubleshooting

• The host is offline. Start the agent from the dock: one click on Windows, or one of the commands it shows on macOS and Linux. The Pilot picks up again by itself once the host is back.
• The Pilot paused after several stuck runs. The host stops to avoid wasting your machine's time. Look at the terminal in the dock to see what got stuck, then start the Pilot again.
• One board keeps failing. The Pilot checks that board once and writes what it found in the journal. Usually it's an expired login, and it signs back in on the spot. Other boards keep running either way.

Next: Campaigns & skills, for doing the same work by hand.