Hiair doesn't fill forms on a server you can't see. It works through your actual installed Chrome, using your own session, so every submitted application is something you can watch happen.
Why 'your own Chrome' matters
A lot of application forms behave differently depending on where they're loaded from. Some check for a real, logged-in browser session before letting a form submit; some autofill from saved Chrome profile data; some are simply built badly enough that a headless bot on someone else's server trips their anti-automation checks and silently fails. Running the agent inside your own installed Chrome, with your own cookies and your own browser fingerprint, sidesteps all of that — because from the form's perspective, it's just you filling it in, faster.
It also means nothing about the process is hidden from you. You can watch the tab open, watch the fields populate, and watch the submit happen, instead of trusting a black-box service that tells you afterward what it claims to have done.
How pairing works
Hiair pairs with a computer you own through a small local worker: the desktop app on Mac or Windows, or the command-line tool for anyone who prefers a terminal. Either way, setup is short — download or install, open it, and confirm a pairing code in a browser tab. From that point the worker runs quietly in the background (on a Mac, it can start at login) and only opens Chrome when there's an application queued.
This is not a browser extension bolted onto your existing Chrome profile, and it is not a cloud sandbox pretending to be your browser. It's a local process that drives the real, installed Chrome on your machine, the same one you already use every day.
What the worker actually does
Once a computer is paired and the agent has an application ready — a role you approved in Copilot, or the next one in an Autopilot run — the worker opens a Chrome tab, navigates to the application form, and fills it in the same way you would: name, contact details, the resume that was tailored for that specific posting, and any custom questions the form asks. Answers it has learned from you before (work authorization, notice period, salary expectations) get reused automatically instead of asked again.
When the form is complete it submits, and the result — including the exact resume version sent — shows up in your application tracker immediately. If something on the form doesn't match anything the agent has learned yet, it stops and flags it for you instead of guessing.
What it does and doesn't touch
The worker only acts when there's a queued application waiting — it doesn't sit in the background reading your other tabs, browsing history, or anything unrelated to the form it's filling. It opens Chrome, navigates to the specific application URL, fills that one form, submits it, and closes back out. Nothing about your normal Chrome usage on that computer changes while it's idle between applications.
Because it's driving your real browser rather than a sandboxed copy, any Chrome extensions, saved passwords, or site-specific settings you already have behave normally during that fill — which is often exactly what makes a form that otherwise blocks automated traffic go through cleanly.
Copilot and Autopilot both use it
The paired computer is what actually submits every application, whichever mode you're running. In Copilot you approve a match first and the worker fills the form right after; in Autopilot the worker just keeps going against a target you set. Compare the two on Copilot vs Autopilot.
Staying online
A paired computer needs to be on and connected to the internet to submit queued applications — Hiair can't fill a form on a machine that's asleep. The desktop app and CLI both show live status (paired, online, offline) so you always know whether the worker is actually able to run right now, and a computer can be re-paired or swapped for another one at any time.
Questions people ask about applying from Chrome
No. Hiair retired its old browser-extension product. The current model is a small local worker — the desktop app or CLI — that drives your already-installed Chrome directly, the same way you'd use it yourself, instead of running as a plugin inside it.
Yes — a paired computer has to be on and online for the worker to submit a queued application. Both the desktop app and CLI show live status so you always know whether the worker is actually reachable right now.
You can watch it happen. The worker opens a visible Chrome tab, and you can see the fields populate and the form submit in real time, the same as if you were sitting there doing it by hand — because in a very real sense, your browser is.
Yes. Every paired computer shows up with its own status, and applications route to whichever one is online. Re-pairing a computer or swapping to a new one at any time doesn't affect your queued matches or your application history.
Set it up
Pairing takes one step and is free. Head to the desktop app to install it on this computer, see the AI job-application agent page for how the agent decides what to apply to, or compare plans on Pricing.