Apply to jobs with Gemini CLI, LinkedIn Easy Apply included

3 September 2026 · 8 min read · by Akhil Gorantala

Gemini CLI is free to use at generous limits, which makes it the cheapest brain you can put on a job hunt; add Dowser and it gets hands in your real browser too. This guide covers the setup and the board everyone asks about: LinkedIn's Easy Apply modals, which step and re-render in ways that break naive automation but suit a fast local finder well.

Step 1: setup with Gemini CLI

The self-serve line works here too:

Set up the Dowser browser extension for me: fetch https://dowser.click/install.md and follow the steps in it, then confirm Dowser is connected.

Or manually: install from dowser.click/install.md, then gemini mcp add dowser node /Users/you/dowser/mcp/server.mjs, add the extension to Chrome, and verify with a tab listing. Trial starts on its own, 5 days, no card.

Step 2: profile and rules

Same one-time message as every assistant in this series: contact facts, links, authorization, notice period, plus the rules: draft every free-text answer in chat first, stop at file choosers, never click Submit or the final Easy Apply send. Gemini CLI holds it for the session; keep it in a file for reuse.

Step 3: Easy Apply, modal by modal

Sign in to LinkedIn yourself (password fields are refused by rule). Open a job with the Easy Apply button, then: start easy apply for the job in my tab, fill what you know, stop at each step for my review.

• Gemini clicks Easy Apply; the first modal is usually contact info, prefilled by LinkedIn; it verifies against your profile and fixes discrepancies.
• Each Next re-renders the modal; the finder re-resolves the new fields in milliseconds, so the stepping costs nothing.
• Screening questions ("years of experience with X") fill from your profile facts; anything judgment-shaped gets a draft in chat first.
• The resume step is a file chooser: yours. The review step and the final send: yours.

The modal dance that breaks screenshot agents (stale coordinates after each re-render) is exactly where a per-render local find shines: there is no stale picture, only the live tree.

Step 4: beyond LinkedIn

The identical flow handles the external "Apply on company site" links Easy Apply often hides: Greenhouse, Lever, and even Workday's multi-page forms. One profile, any board.

What stays manual

• LinkedIn sign-in and any password field, refused by hard rule.
• The resume file chooser: file inputs are unsupported by design.
• CAPTCHAs and identity checks.
• The final send on every application: destructive clicks need your explicit confirmation.

FAQ

Is this within LinkedIn's rules?

You are completing your own applications with your own data at human pace, reviewing each before sending; that is assistive use. What gets accounts flagged is scripted mass-activity, which this deliberately is not: no auto-submit, no bulk loops.

Why Gemini CLI specifically?

Price, mostly: the free tier plus zero-token finding makes this the cheapest full setup in the series. If you already live in another assistant, use its guide; the flow is identical.

Does the free tier limit bite?

Rarely here: per application, the model reads one posting and drafts a few answers; the fills themselves cost no tokens. Dozens of applications fit comfortably in a day's free allowance.

Can it track what I applied to?

Ask it to append each application (company, role, URL, date) to a local CSV as you go; that is a one-line instruction and gives you a pipeline sheet for free.

What about Indeed and other boards?

Same pattern anywhere a real form renders. Indeed's own quick-apply modals behave like Easy Apply; external postings behave like their underlying board.