JobFlow is a local-first, AI-centered job application workflow for Windows. It turns a resume, approved applicant facts, and an official job page into a reviewable application packet, then provides user-present browser assistance that stops before final submission.
Alpha software: JobFlow does not claim universal ATS compatibility. Final Submit is always a trusted user action. Unknown external state is never retried automatically.
- Imports resumes and supporting material into Windows DPAPI encrypted storage.
- Connects to an existing Hermes, OpenClaw, or supported loopback model without copying model credentials into the project.
- Uses AI to reconstruct experience entities, preserve metrics, and produce source-grounded Claim candidates.
- Collects one reusable Candidate Profile and Answer Bank, with explicit review for sensitive or missing facts.
- Starts from an official company career page, verifies the job and approved ATS route, and builds one application review packet.
- After one application-specific approval, fills approved values, attaches approved materials, and advances only through verified non-final controls while the user is present.
- Stops at final review so the user can inspect the page and personally click Submit.
- Optionally polls only the exact public company or supported ATS job sources the user approves, for at most seven days, and places matched roles in a local candidate inbox.
- Keeps application preparation manual and user-present: a discovered candidate does not open Apply, create an application, fill a field, upload a file, or advance a form until the user chooses it and completes the normal review gates.
- Download and extract the latest source ZIP.
- Double-click
Install JobFlow.cmdonce. - Install JobFlow Browser Companion from Chrome Web Store or Microsoft Edge Add-ons when the installer opens its listing.
- Double-click
Start JobFlow.cmdfor normal use. - If startup fails, run
Check JobFlow.cmdand follow the first failed check.
The installer copies the application into a fixed, versioned directory under the current Windows account. Candidate data, queues, reports, and encrypted private material remain in a separate data directory, so the extracted download can be removed after installation. Running a newer installer upgrades the application without replacing that data; the Start menu also provides signed update, health check, rollback, and uninstall shortcuts.
Installed builds can check the fixed stable GitHub release channel only after the user clicks Check for updates. JobFlow accepts an update only when its canonical manifest is signed by the pinned release key and its source archive passes the signed hash, size, layout, and public-content boundary. A failed post-update health check restores the previous version. Source checkouts do not self-update and never replace their working tree.
To explore without private data, run Start JobFlow Demo.cmd. The demo uses fictional content, disables real AI and file intake, and removes its temporary state when closed.
See the full quick start for Browser Companion setup and recovery guidance.
JobFlow can reuse an already configured:
- Hermes or OpenClaw Agent on Windows or WSL;
- Ollama, LM Studio, LocalAI, llama.cpp, or vLLM loopback server;
- advanced command adapter through
JOBOPS_AI_COMMAND_JSON.
An AI connection is accepted only after a structured capability test. Agent requests use an isolated, zero-tool channel. JobFlow does not extract, return, log, or persist API keys, tokens, cookies, executable paths, or model credentials.
- Private applicant values remain behind
secure-ref:*references and DPAPI encryption. - Claims require source evidence and applicant approval before external use.
- Login, CAPTCHA, MFA, account creation, credentials, legal declarations, signatures, and unknown answers stop for the user.
- The only unattended feature is explicit, expiring, read-only job discovery. Background application opening, Apply, form filling, uploads, navigation, final Submit, email, and recruiter contact are not implemented.
SUBMISSION_UNKNOWNnever triggers an automatic retry.- Knowledge sources are read-only.
| Capability | Alpha status |
|---|---|
| Windows install, signed update with rollback, health check, and bilingual local UI | Available |
| Encrypted onboarding, Candidate Profile, Answer Bank, and Claim review | Available |
| Existing Agent or loopback-model connection | Available with capability gate |
| Visible official-company job discovery and verified Apply routing | Available with user authorization |
| Expiring read-only background discovery to a local candidate inbox | Available for exact approved HTTPS sources; maximum seven-day authorization |
| User-present company, Greenhouse, Lever, Workday, Ashby, and SmartRecruiters assistance | Bound routes only; live compatibility varies |
| Approved field fill and material attachment | Available per approved application |
| User-present local queue cadence, pause, and manual run | Available; every run requires a user click |
| Redacted diagnostics and optional local fixed-code incident history | Available; manual download only, no automatic transmission |
| Unattended application processing or final submission | Not implemented; final Submit is permanently user-only |
Synthetic and saved-page tests are engineering evidence, not proof that every live ATS page is compatible.
.\scripts\install-jobflow.ps1
.\.venv\Scripts\python.exe -m unittest discover -s tests
.\.venv\Scripts\python.exe -m jobops.public_releaseThe project is intentionally Windows-first because secure applicant storage uses DPAPI. Runtime state, databases, review packets, encrypted private files, and local release reports are excluded from the public repository.
- Quick start
- Support
- Browser Companion privacy
- Architecture
- Roadmap
- Release checklist
- Security policy
- Contributing
- Changelog
When reporting a problem, use Privacy-safe incident history and support → Download diagnostics in the local UI. The JSON contains only versions, states, counts, safety boundaries, and validated fixed error codes. Optional incident capture is off by default and keeps at most 32 local records when explicitly enabled. It does not include resume text, answers, Claim text, error messages, stack traces, URLs, local paths, credentials, tokens, or secure references, and JobFlow never transmits it automatically.