A LinkedIn job application agent you control.

when Claude's or ChatGPT's session was revoked, the key is wrong or your access ended, the run says the AI needs reconnecting and waits, charging no job for it, and carries on by itself the moment the provider is connected again in Settings (or on Try now, or after half an hour). A real outage or rate limit is waited out with waits that grow across jobs.

in the toolbar popup: two side-by-side buttons. Upwork opens first unless you make LinkedIn the default (one click in the popup, or Settings → LinkedIn).

type a job title or describe the role in your own words (LinkedIn's AI job search understands descriptions), add a location, pick On-site / Remote / Hybrid, date posted, experience level, job type and sort order, set a target number of jobs, and press Start. LinkedIn opens on that search with the Easy Apply filter already on.

the classic job search and the new AI-powered job search, plus Recommended / Collections pages and single job pages.

docked to the LinkedIn page: scans every job on the results page, marks which are Easy Apply and which you already applied to, and lets you tick the ones to apply to. "Apply to N selected" starts; the panel shows Job i of N, the current job and step, applied / skipped / failed counts, a speed control (1x to 3x) and Pause, Skip and Quit buttons, like a human assistant working through the list.

opens each job, presses Easy Apply, picks your resume by name, fills every step of the form, presses Submit, closes the confirmation and continues to the next job; when the page is done it turns to the next results page until the target is reached. Jobs applied to earlier are never repeated.

phone, email, city, years of experience (overall and per skill), salary, notice period, work authorization, visa sponsorship, relocation, on-site and remote preferences, education, languages and a standard message are saved once under Settings → LinkedIn and used on every form. Your own rules ("when the question contains X, answer Y") come next. Only questions none of that covers go to your chosen AI provider, which answers from your Facts Bank and profile; every AI or hand-typed answer is remembered and reused, and you can edit or delete remembered answers at any time.

an AI answer it is not confident about is filled in and shown for a quick check; a question nobody can answer pauses the run on that job so you answer in LinkedIn's own form and press Continue (or choose "skip the job" behaviour instead). If nobody answers within a few minutes, the run moves on by itself.

auto-submit is on by default and can be turned off per run or in settings; the agent then stops on the review step for you to press Submit, and continues once you have.

when a run finishes or is stopped, a results tab opens with the status, jobs applied out of the target, the success rate and the per-job outcomes, and a form to start the next search.

with the answers given on each form, exportable as JSON.

jobs that send you to the employer's own careers site are applied to as well, in the same run. The agent follows LinkedIn's Apply link into a tab of its own, reads the page, fills the form from your saved answers and the Facts Bank (phone widgets with a country picker get your country chosen first, then the national number), uploads the resume you keep in Settings → LinkedIn → External websites, writes a short cover letter when a box asks for one, ticks the required consents (also the ones drawn as a styled box over a hidden checkbox, and required declarations), and submits. It works its way through multi-step forms, forms embedded in a frame from another site (Jobvite, Talemetry, Greenhouse) and job pages that need an "Apply" press first, signs in or creates an account with the email and password kept in settings when a careers portal insists on one, and stops for you (with a Continue button on the site and in the panel) when a CAPTCHA, an email verification or an unknown login is in the way. One approval covers every site; each site gets a time budget (6 minutes by default, counted from the last time the page moved on, three budgets at most) and is marked failed with the reason if it cannot be finished. When a page stops moving, the agent asks the AI for a different way with the page facts (what is scrolled, covered, disabled, empty, and the messages shown) and a wider set of moves (a press by mouse, keyboard or script, a scroll, a key, closing what covers the page, a step back); on the round after that it shows the AI a picture of the tab (Claude and ChatGPT; taken only then, never kept) so icons, steppers, widgets and overlays the outline cannot carry are seen; a job is given up only after five unchanged rounds, and the way that worked is kept in the site's notes. A three-way choice in the popup, the panel and settings — Easy Apply only (the default), External websites only or All jobs — decides which jobs a run applies to; choosing external websites on a filtered results page reloads it without LinkedIn's Easy Apply filter so those jobs are listed, and choosing it while the run waits for LinkedIn's daily limit continues at once with the external-website jobs. The panel explains, with a button to Settings, when the one-time website access has not been granted yet. With "All jobs", LinkedIn's daily Easy Apply limit does not stop the external-website jobs: they continue, and the Easy Apply ones wait for tomorrow. With auto-submit off, the agent fills everything and waits for you before the final Submit on the site too.

an entry Workday has already taken in one of its search boxes ("Sweden (+46)" under Country Phone Code, "LinkedIn" under How did you hear about us?) is read as the field's value, so it is not chosen again every round; the phone number goes into the Phone Number box alone, never into the code box beside it.

on company sites every typed field and every chosen pick list is left for real once filled, and the field being edited is left before a button is pressed, so sites that check or save a field when you leave it (Workday among them) take the value instead of calling it empty after Save; a phone box with its own country picker keeps your country whatever digits it reformats; buttons are named by their own words; the second address line and a referrer's email box are left to the AI; and a page bouncing between two states, or reloading after a press, is recognised as standing still rather than repeated.

the panel shows "External website: <step>" while it works, the popup and settings show the step and any question the site has for you, the history marks these applications as external-website ones with a link to the application page, and the site's tabs close when the application ends.

every wait is random so no two applications take the same time, there is always a pause of several seconds before Submit and between jobs, and after a handful of applications the agent takes a longer break. 3x is the pace of 0.10.0; 1x, the default, waits about two and a half times longer.

when LinkedIn answers "Save this job and apply tomorrow", Easy Apply waits 24 hours and then continues by itself (the LinkedIn tab is reopened if it was closed), with a "Try now" button if you want to check earlier. Meanwhile jobs that apply on company websites keep the run going when website access is allowed. The limit is never guessed from a stuck page: when Easy Apply forms stop opening, the results are loaded afresh and those jobs get another go first.

the first time the LinkedIn answers form opens, blank fields are filled from what the extension already knows — the imported Upwork profile and the Facts Bank (name, email, phone, LinkedIn URL, website, city and country, years of experience, education, languages) — and marked as prefilled until you check and save them.

the agent panel docks to the right edge of LinkedIn's page, next to the job details, and its pop-ups ("Your application was sent", "Update profile") are closed with "Not now" so the next job proceeds.

a run does not stop halfway. When LinkedIn's daily Easy Apply limit is reached, an "All jobs" run carries on with jobs that apply on company websites until Easy Apply is available again; an "Easy Apply only" run asks you first (Yes, company websites / No, wait for Easy Apply) and goes on with company-website jobs by itself if you do not answer within a minute, so your choice of jobs is respected and an unattended run still keeps applying. A failed job is recorded and the run moves on to the next; a streak of failures leads to a quick recovery (pop-ups closed, page read again or reloaded), not a stop. If your AI can't be reached, nothing is sent and the job is tried again after a short wait. When every job in the results is done, it looks for new jobs every 20 minutes. Jobs that failed twice recently are not ticked again automatically.

when an Easy Apply step will not move on (a field the agent does not recognise, a message that keeps coming back, a button in another language), the form is shown to your AI, which fills what is missing and presses the button that moves on. It never presses Submit or anything that leaves the form, and its answers are remembered once LinkedIn accepts the application, so the same question is answered without the AI next time.

on employers' websites the agent keeps notes per site (and per hiring platform, such as Workday or Greenhouse): the route that worked and the last thing that failed, used on the next application there. It asks your AI again after a hiccup before giving up, and changes approach when a page does not react.

when an employer's Apply button opens the form in a new tab or window, or a chain of them, the agent carries on there; sign-in windows are left to the site and a tab that closes leads back to the one before. When the application ends, sent or not, every tab it opened is closed (a switch in Settings → LinkedIn → External websites), and the outcome with its reason stays in the results.

on employers' websites the cookie or consent banner is accepted first, in any frame, so the form behind it (or one that loads only after consent) can be filled.

when a careers site wants an account and no portal password is set, the agent makes a strong one, creates the account and keeps the password in Settings → LinkedIn → External websites so you can sign in later. Your AI only ever sees a placeholder; the extension types the real password, and passwords are never saved with an application's answers.

on careers sites that want an account first, the agent fills the whole form, including styled dropdowns such as a country list, ticks the terms, privacy and data-notice boxes (never newsletter, job-alert or talent-pool ones), answers "How did you hear about this job" with LinkedIn, and presses Register (or the form's Save or Continue) once nothing required is empty.

the Control page on applywithai.app lists the questions waiting and takes the answer right there (a text box, or the question’s own choices); it goes straight to the extension, which remembers it for every later form and lets a run that is going try the jobs that waited. The answer is never kept by the website, never cached and never sent anywhere but the extension; every waiting question is reachable, 25 a page.

when a form asks something only you know and nothing saved answers it (a date of birth, a driving licence, a certificate), the agent never guesses and never stops the run: the question waits in Settings → LinkedIn → Questions for you (the toolbar icon shows how many), the job is set aside, and the run goes on. Answer once and every later form, Easy Apply and company sites alike, uses the answer; the jobs that waited are tried again. Whatever plainly follows from your facts is derived rather than asked: today's date, a start date from your notice period, a salary converted to the currency and period asked, salary expectations, conflict-of-interest and planned-leave declarations, a location you are outside of, a language you do not list, years with a tool or industry.

say once whether you hold one and which categories (such as B); licence questions on every form are answered from it.

forms that take only PDF get a PDF, made by itself from your Word resume (real text, simple layout) or uploaded by you, with a download to check it; a site that turns a Word file down gets the PDF instead.

every "Needs you" moment on a company website (a CAPTCHA, an emailed code, a sign-in) ends by itself after a few minutes; the job is skipped and the run continues towards your target. Sign-in pages with a way to register ("Create a candidate profile") are registered on, and fields meant as bot traps are left alone.

a "Needs you" moment on a company site waits three minutes for you; once two in a row in a run went by with nobody pressing anything, the next ones wait one minute, so an unattended run loses less time to sites it cannot get through. The card on the site, the LinkedIn panel and the popup say which wait applies, and your first press on Continue, Pause, Skip or Stop puts the waits back to three minutes. The hand-over before Submit with auto-submit off always keeps its full time.

on company sites the agent attempts the verification checkbox and Google's supported 3×3 or 4×4 image grids using your existing vision-capable Claude or ChatGPT connection. It sends only the puzzle image and instruction, rechecks replacement tiles, and continues only after a fresh verification response. Stops, uncertain answers, blocks and unsupported challenges are handed back to you rather than retried indefinitely.

file fields carry their section's heading and words, documents/attachments fields take the resume, uploads are checked against what the site shows (PDF fallback, refusals named), and a stuck page gets the resume attached before another way is tried.

your own `@ailavo.com` address on every application, Easy Apply and company sites (company sites since 0.14.8); the agent reads verification codes and links from it and continues by itself. "Email on applications" in Settings → LinkedIn → Company sites chooses the mailbox (default) or your own email; Easy Apply offers the mailbox once it is added to the LinkedIn account's verified addresses.

company websites open in the same window as the LinkedIn tab, so a run keeps going there while you use another Chrome window.

a LinkedIn job run's waits are timed by the extension's background rather than by the tab, so Chrome slowing a hidden tab's timers does not slow the run; the run's tab is kept from being discarded by the memory saver; and a watchdog reloads a page whose run has gone quiet, which carries on from where it was. As long as the computer is on, the run continues. (0.14.3) Since 0.14.4 the same holds for every page the extension works on: company-site applications, all LinkedIn campaigns and Upwork forms. (0.14.4) A run whose tab LinkedIn signed out (it landed on LinkedIn's public site) pauses with a note for you instead of being sent back again and again.

the wait ends on its own even if Chrome was restarted, the extension updated or the computer slept through the time, and the LinkedIn tab is reopened if it was closed.

an entry sorted under a heading in Workday's search results (LinkedIn under Social Media) is chosen from the opened entries, and a pick counts as chosen only once Workday shows it beside the box; otherwise the agent is told what the list offers instead of the form stalling at Save on a field it believed filled.

when a page stops moving, the resume goes into an empty file field once per field and never when the page already shows the file (sites that list uploads apart from the drop zone, such as Oracle Recruiting), so an application no longer carries the same file five times over.

Workday's hidden radios ("Have you worked here before?", "Previously employed by…") are read whole, so No can be chosen and the form moves on; radio questions on other sites that only have a generated name get their real question from the words around them.

Workday's "Select One" style buttons open a list the agent now reads and picks from; when its guess is not in the list, the options the list offers are reported and the right one is chosen next. Job links on a careers search page and forms inside a frame of any container are read too.

iCIMS careers portals, which draw the sign-in, the form and the questions in a frame of their own site, are worked inside that frame step after step; and on every company site a plan such as "open the list, type, choose, Save and Continue" is carried out to its button, where a click that merely opened something used to end the turn.

on company job pages the agent finds the apply control when it says "Solliciteer direct", "Jetzt bewerben", "Postuler" or "Candidati", when only its address says apply, or when its words are drawn beside an empty link laid over a styled button, instead of reporting a page with no apply button.

pressing Enter in a search box with suggestions (Oracle Recruiting's Country, Workday's prompts) picks from the list and never sends the page's form the plain way, which used to land some sites on a server error page and lose the application.

when a site says "Please correct the errors below", the agent is told which fields the site marked as wrong and what they hold, even when they sit in a collapsed section, so the fix goes to the right field.

on a company site the "Give up after" minutes count from the last time the page moved on, and a new page now counts as moving on, so a portal that takes you through eligibility, sign-in, account, form and upload as separate pages (iTrent) is no longer cut off as "standing still" while it is going forward.

when a company site's form is filled, saved and comes back exactly as it was (the same step, the same empty fields, the same words), the agent treats it as a page that did not move rather than as progress, tells the AI the site kept nothing and asks for another way, and gives the job up after its rescue rounds instead of repeating the lap for twenty minutes; a site that keeps each entry is unaffected.

verification-code boxes named "digit 1 of six" (Oracle Recruiting) are counted like one-character boxes, a code drawn one character per cell in the email is read as one, and a number of the wrong length (a job number) is never taken for the code; the form's own required CV field is fed even when a resume parser on the page already holds the file; and a Hebrew "we will be in touch shortly" after sending the CV is read as the confirmation it is.

a country or phone-code list that does not know "+46" is searched for your country's name instead, and when the form has a separate code field the phone number box gets the national digits the site accepts.

on company sites a city box's suggestions (Google's place list on SmartRecruiters), a country picker that draws only part of its list (Recruitee's phone code), and search boxes whose list offers other things are all read and chosen from; when nothing matches, the agent is told what the list offers and picks from that. SuccessFactors boxes that suggest only entries starting with the typed words ("How did you hear about us?") are opened by their own arrow and chosen from the whole list.

when a company-site form has several buttons saying the same thing (an "OK" under every question, as on Typeform), each is named by the question before it, so the agent presses the one that belongs to what it just filled.

an "Apply now" that is only an email address is reported as such straight away, instead of being pressed again and again.

when a company site empties the resume field after an upload and asks for the CV again, the agent attaches it once more instead of insisting it is already there.

a LinkedIn tab sent to sign in pauses the run with a note for you, a tab that left the jobs pages is sent back to your search, and after three fresh loads without an answer the run waits an hour before trying again.

a job LinkedIn says is no longer accepting applications is skipped with that reason; a pane slow to show its apply button is waited for and opened again, then tried once more later before anything is recorded. Company-site applications are cut off only when they stand still for the "Give up after" minutes, not for being long, and the record says which it was.