What actually happens when Hiair applies to a job in your Chrome

Not a hidden server, not a browser extension bolted onto your profile — the agent drives your own installed Chrome to fill and submit the form you'd have filled yourself.

Joy De Medici · September 17, 2026

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 built well enough that a headless bot on someone else's server trips their anti-automation checks and silently fails. Hiair sidesteps all of that by running the agent inside your own installed Chrome, with your own cookies and your own browser fingerprint — from the form's perspective, it's just you filling it in, faster.

Pairing a computer

Hiair pairs with a computer you own through a small local worker — the desktop app on Mac or Windows, or a command-line tool for anyone who prefers a terminal. Setup is short: install it, open it, confirm a pairing code in a browser tab. From that point the worker runs quietly in the background and only opens Chrome when there's an application queued.

This is not a browser extension bolted onto your existing profile, and it isn't a cloud sandbox pretending to be your browser. It's a local process driving the real, installed Chrome on your machine — the same one you already use every day.

What the worker does when it runs

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 the 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 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 or browsing history. 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.

Both Copilot and Autopilot submit through the same paired computer — the review step happens before the worker ever opens the tab, not after.