Set up your job pipeline

Four steps, once. Everything is stored on your own machine.

1. Your resume checking…

Attached to every application. Saved into the extension's resume/ folder as resume.pdf — the name it looks for, whatever your file is called.

Drop your CV here
or click to choose — PDF, DOC or DOCX, up to 10 MB

2. Your details checking…

What gets typed into application forms, and what the matcher ranks jobs against. Saved to both files at once so they can never drift apart.

3. Mistral API key checking…

Reads each job description to pull out skills and experience, and fills the forms the agent applies through. Without one, nothing gets enriched and the matcher finds nothing. Free key from console.mistral.ai. Paste several separated by commas if you have them.

This is the only place you need to put it — every service and the browser extension read the key from here. No .env files to edit.

4. Sign in to job portals checking…

LinkedIn, Indeed and Naukri show nothing at all to a signed-out browser. This opens the pipeline's own Chrome below — sign in once and the session is kept. The ATS boards need none of this: Greenhouse, Lever, Workday, SmartRecruiters and Oracle work straight away.

5. Resume tailoring checking…

Optional. Every application can carry a resume rewritten for that specific job. This is the one part that runs on your machine rather than in Docker, because it uses the coding agent you are already signed into — the container has no access to your subscription. Applications work fine without it; they send your base resume.

Rewrite each resume for the job being applied to.