How the run queue works

/apply is a queue, not a list. It puts one job in front of you, tailored against your default résumé, and waits for a decision. Then the next one.

The four decisions

• Send hands you off. It opens the employer's own application page in a new tab with your prepared answers in place. You press Submit there.
• Skip drops the job out of this run and does not show it again.
• Later moves it to the end of the run, so you can come back once you have thought about it.
• Finish ends the run and shows you the tray of everything that still needs a hand.

The next two cards are tailored while you are reading the current one, which is why the card is usually ready the moment you get to it. If a tailoring pass has not finished, you get the deterministic rewrite instead — never a spinner in place of a job.

Why a card says "needs a click"

Your browser blocks pop-ups it did not attribute to a click, and that blocking happens after we have already prepared the application. That case is recorded as needs a click, not as applied. Everything in that state is listed in the finish tray, and one click from there opens the tab.

There is a separate state, failed, for when our own send did not resolve. The two look identical to a counter and completely different to you: the first has a prepared application waiting, the second may not. We keep them apart for that reason.

The daily cap

Assisted hand-offs are capped per day, and the apply screen shows the number for your plan before you start. The cap is not a paywall wearing a hat — past roughly that many tailored applications in a day the response rate stops moving and duplicate detection starts working against you. It is the one limit that does not lift to unlimited on any plan.

Where the run goes afterwards

Every hand-off writes a receipt before the tab opens, so there is no application you cannot account for later. The run summary exports as a CSV, and telling us you pressed Send is what files the card on your tracker.