Autopilot

It only does what you told it it could do.

Autopilot isn’t a faster button. It’s the set of limits an automated search runs inside - the floor you set, the two controls that decide how much you’re in the loop, and a page that tells you which of them actually stops a submission. Off until you switch it on.

Autopilot OffDefault score floor · 80Undo window · 30 minDefault limit · 5/day
What you setthree numbers · /settings

The bar, as the product actually states it

Not a wishlist of titles and salaries - those shape which jobs you match in the first place. These three decide what an unattended run is allowed to do with the matches you already have.

Minimum match score80
range 50–100 · default 80

The reranker’s own 0–100 score. Below it, a job is not a near miss you hear about later - it is never a candidate. The floor starts at 50, not 0, because a near-zero floor would auto-apply to weak matches, which is never what an opt-in wants.

Auto-submit above80
starts equal to your minimum · raise it to open a hold band

Raise this above your minimum and everything in between waits for one click instead of going out. Left alone the band is empty, so nothing changes until you ask for it.

Autopilot daily limit5 / day
range 1–25 · default 5

Applications autopilot may start in a UTC day. Separate from - and inside - your 10-a-day cap on every application, the ones you send yourself included.

The floor is a floor, not a preference. Autopilot cannot widen it on its own - not to fill the day’s budget, not because the week was quiet. A run that finds nothing above your bar arms nothing.

What you choosetwo controls · three outcomes

How much you want to be in the loop

There is no mode picker in the product - there is a toggle and a stepper, and these are the three states they reach. Every one obeys the same bar and the same rails.

settings · Review before submitting ON · Auto-submit above = your minimum (80)

Every armed application: 30 minutes, cancellable

It sits at awaiting_confirmation with the whole fill plan readable - each field, each value, and a marker on the answers that were AI-drafted. Cancel inside the window and it never submits; it reverts to an ordinary application, written and waiting, that you can send by hand whenever you want.

Do nothing and it submits

This is the part worth being precise about. The window is a stop, not a gate. If you never open it, the application goes out at the end of the 30 minutes.

The undo is a real cancel, not a recall: it stops the submission before the employer ever sees it. Nothing in LandEarly can retract an application that has already landed - the tracker’s “withdrawn” marks your own record, and telling the company is a note you send them.

In every modeOff until you turn it onNever applies below your scoreThe same gates as a manual applyEvery state on the timeline
What it does while you’re asleep

A run is six steps, and none of them is a judgement call.

The design handoff for this page drew a night log - twenty-three postings seen, twenty skipped, a reason beside each one. It’s a good idea and it isn’t what happens. Selection is one query; the postings it doesn’t return were never candidates and leave no row behind. So here is the honest version, which is less cinematic and more checkable.

  1. 01
    every 30 min

    The cron wakes and asks who opted in

    One query for users with the switch on, then one event each. If you turned it off since the last cycle, the per-user run re-reads the switch before doing anything.

  2. 02
    step · plan

    It works out today's remaining budget

    Your daily limit minus what autopilot has already started since 00:00 UTC. At zero the run ends here, and the plan is memoized - a retry reuses the same budget and the same candidates rather than compounding.

  3. 03
    step · select

    It picks candidates, best first

    One query carrying every rail above at once, ordered by score then freshest, cut to the remaining budget. Nothing outside it is seen, drafted, or read.

  4. 04
    step · arm

    Each one goes through the ordinary apply path

    The same call a paste-a-job uses - duplicate guard, qualification gate, tailoring from your real history. Autopilot only arms. It has no private route to an employer and skips no gate the manual path enforces.

  5. 05
    step · notify

    It emails you the whole batch, not a highlight reel

    One summary per run, listing every role it armed. The email’s copy is generated from your review setting, so it never promises a window the worker won’t honor - it says “review or stop” only when there is genuinely something to stop.

  6. 06
    then

    The gates run again at the last moment

    Your all-applications daily cap and the per-company cap are re-checked at submit time. A failure doesn’t queue or retry - it disarms the application and leaves it as an ordinary one with a live submit button.

One application, its whole timelineapplication_events
draft → generatingCreated by the autopilot run, marked with the origin that makes it countable against your daily limit.
reviewRésumé, cover letter and screening answers written against this specific posting.
awaiting_confirmationThe form is filled and the fill plan is readable - every field, every value, plus which answers were AI-drafted. This is the screen the undo window is spent on.
submitting → submittedCarries the attempt marker that makes a crashed run refuse to click twice, then the verified receipt.

What this is not: a log of the road not taken. A posting that never cleared your bar leaves no row, because it was never a candidate - the selection is a query, and the jobs it doesn’t return are simply not returned. The record is of what happened, in full, to everything autopilot actually touched.

If you want to know why a job you saw yourself never got an application, the answer is one of the limits on this page rather than a line in a report - and the fastest way to find it is that the job is missing from your matches, or scored below your floor.

The constraints

Eight limits you don’t get to set.

The three dials are yours. These aren’t - there is no screen where they can be loosened, which is the only reason they’re worth anything as a promise. Every one is a clause in the query that picks candidates, or a gate the application has to pass on its way out.

Un-scorednever

A match the reranker hasn’t judged yet has no score to compare against your floor, so it is excluded outright rather than given the benefit of the doubt.

Freshness30 days

Older postings aren’t candidates. Applying early is the point; an unattended run working through a backlog is the opposite of it.

Same company3 active / 30d

The cap that keeps you from reading as spam to one employer. Checked again at the moment of submission, not just when the application was created.

Same jobonce, ever

If an application already exists for that posting in any status, autopilot never opens a second one.

Seniority+2 bands

A role two or more levels above your own is refused even when the reranker scored it above your floor. Unattended is the wrong moment for a stretch application.

Where it can file11 systems

An explicit allowlist, not a denylist. Anything that needs an account with the employer, or a form we can’t finish cleanly, is left for you - auto-arming it would only manufacture work.

Dismissedexcluded

A match you waved off stays waved off. Dismissing is the fastest way to tell an unattended run what you think of a role.

Knockoutsgate first

The same qualification check the manual path runs. A job whose stated requirements you plainly don’t meet is stopped before anything is written, not after.

Two of these are worth stating as the negative, because a promise is easy to make and hard to check. There is no company blocklist and no automatic block on your employer - dismissing a match is the control that exists. And nothing here expires: no setting decays toward more automation, and none decays back toward less.

Where the line is

Autopilot decides whether. AI Apply decides how.

They’re separate on purpose, and the separation is literal: autopilot’s whole job is to call the same function a paste-a-job calls. You can run AI Apply with autopilot off forever, approving every application by hand, and not one thing about the tailoring changes.

AutopilotThis page

The permission and the limits. It never writes a word of your application.

  • Which matches qualify - the score floor, the freshness window, the rails
  • Whether a submission gets a window to stop it, or waits for your click
  • How many it may start in a day, and when it stops for the day
  • Whether it runs at all, which is off until you say otherwise
AI ApplySeparate page

The craft and the delivery. It only ever runs on a job autopilot has already cleared.

  • Rewriting your résumé against the specific posting
  • Drafting the cover letter and the screening answers
  • Filing through the 11 applicant systems it can finish unattended
  • Getting there while the posting is still fresh
See AI Apply - how an application actually gets written and filed
Asked directly

The questions people actually have at 2am.

A feature that spends your money on a real employer with nobody watching should answer these in writing, including where the answer is “no, and here’s what we do instead”.

A new accountAutopilot · Off
Autopilotoff
Review before submittingon
Applications autopilot has sent0

It does not switch itself on after setup, after a trial, or after an update, and there is no code path that writes that flag except the toggle in your settings. Turning it off stops the next cycle from arming anything; anything already inside its 30-minute window is stopped from the application itself, where the cancel button is.

How many can it send in a night?

Your autopilot limit, which starts at 5 a day and sits inside your cap of 10 on every application from every source. Both reset at midnight UTC and neither borrows against tomorrow. A run that has spent the budget ends without touching the database.

Can it apply to my current employer?

There is no company blocklist, and nothing reads your work history to build one - a handoff for this page claimed otherwise and it was wrong. What stops a company is you dismissing its roles in your matches, which excludes them permanently, plus the cap of 3 active applications at one company in 30 days.

What if I want it to stop right now?

The toggle stops the next cycle from arming anything. It does not reach back into work already underway - an application inside its 30-minute window is cancelled from that application, where the button is, and one already submitted has already been sent.

Does it invent things about me to clear a bar?

It can’t, and not because autopilot is careful - because it runs the ordinary apply path, where every résumé line has to trace to something you actually wrote. Autopilot skips no gate the manual path enforces; it only removes the click that starts one.

Will an employer know it was automated?

Applications arrive through the company’s own applicant system with your name and your documents. We add no markers and never apply on behalf of anyone but you. The retention and access rules are on Trust & Safety.

What happens if I ignore it for a month?

Nothing changes on its own - there is no decay back to review-first, and no setting expires. In the window mode applications keep going out at your daily limit; in the hold mode the held ones stop after 24 hours and wait for you rather than sending themselves.

Autopilot

Set the floor now. Turn it on whenever you’re ready.

Start with autopilot off and 3 applications on us - apply by hand until you’d rather not, then change exactly one setting.