💼 Job Application Agent

Find better roles, apply with verified facts, and learn from outcomes.

Get started · Privacy in 30 seconds · Safety · Privacy · Where to find it · Dashboard · Security

npx job-application-agent@latest install

npx skills add vaibhavarora14/job-application-agent

Job Application Agent is an Agent Skill that helps a coding agent discover, evaluate, complete, and track your own job applications. It uses one verified résumé, checks eligibility and duplicates, and records only confirmed submissions.

🔒 Privacy in 30 seconds

• OS credential store for profile
• One verified résumé; refuse unverifiable claims
• Never reads cookies/session files; pauses for SSO/MFA/CAPTCHA/legal
• Only records confirmed submissions (filled ≠ applied)
• Analytics/community sharing opt-out via CLI

🚀 Get started

Install it with either:

npx job-application-agent@latest install

npx skills add vaibhavarora14/job-application-agent

Then tell your coding agent:

Use job-application-agent to onboard my résumé and job preferences.

After onboarding, use natural commands:

search jobs
list discovery sources for India and global remote engineering
apply https://company.example/jobs/123
apply all relevant jobs from this thread: <URL>
run a round of 10
show attention queue
record outcome Company — Senior Engineer — interview

Requires Node.js 20 or newer and a browser-capable coding agent.

Use your preferred agent

Setup templates are available for Hermes Agent, Grok Bot, and OpenClaw:

npx job-application-agent@latest platforms
npx job-application-agent@latest platforms hermes

Replace hermes with grok or openclaw for that guide. These commands print instructions only; they do not install a Bot, change agent settings, or access candidate state. Browse the platform guides. Each template starts in review mode and requires browser validation on its host. The Grok Bot native share link is pending; use the setup prompt in the guide. The existing installer also supports Codex, Claude Code, Cursor, Copilot, and Gemini skill directories when present.

On Linux, profile storage uses the Secret Service via the secret-tool CLI. Install it with sudo apt-get install libsecret-tools (Debian/Ubuntu) or the equivalent package manager command for your distribution.

Unlike macOS Keychain or Windows Credential Manager, the Linux Secret Service has no always-running system daemon: a keyring daemon (GNOME Keyring, KWallet, or similar) must be running in the user session for secret-tool to store or read the profile. On a desktop login this is normally already the case; on headless servers, containers, or SSH-only sessions, start one explicitly (e.g. gnome-keyring-daemon --unlock --components=secrets) before first use.

For one person's agents across several trusted hosts, an optional private Cloudflare D1 backend with R2 (or a private Workers KV blob fallback) shares profile, résumé, application, outcome, round, answer, and attention state. Each host receives a separate revocable credential, and one renewable lease ensures only one host submits applications at a time. See CLOUD_STATE.md.

✨ What it does

🤖 Choose your autonomy level

An optional outreach companion qualifies contacts, stores drafts, prepares manual handoffs, and tracks replies privately. Run job-application-agent outreach policy status to inspect it. It is disabled by default, performs no automated LinkedIn/X access or sending, and keeps outreach counts separate from applications. Cloud use requires the outreach-tracking-v1 private-state migration; local use works with the managed npm installation on Node 20 or later.

• review-each — review every completed application before submission.
• routine-auto — allow routine submissions while keeping sensitive and judgment-heavy steps with you.

For durable autonomy across resumable or scheduled runs:

echo '{"mode":"routine-auto"}' | node ~/.agents/skills/job-application-agent/scripts/job-application.mjs autonomy grant --stdin

Check or revoke it at any time:

node ~/.agents/skills/job-application-agent/scripts/job-application.mjs autonomy status
node ~/.agents/skills/job-application-agent/scripts/job-application.mjs autonomy revoke

🛡️ Safety

The agent pauses for:

• passwords, SSO, MFA, and CAPTCHA;
• legal attestations and government identifiers;
• demographic or voluntary self-identification questions;
• unclear work authorization, sponsorship, location, or compensation;
• claims that cannot be verified from your profile or résumé;
• browser or operating-system permission prompts.

It never reads browser cookies or session files, bypasses access controls, or counts a filled form as a submission.

🧭 How it works

flowchart LR
    A["Verified résumé + profile"] --> B["Find active roles"]
    B --> C["Check fit + duplicates"]
    C --> D["Fill truthful application"]
    D --> E{"Needs you?"}
    E -- Yes --> F["Attention queue"]
    E -- No --> G["Submit"]
    F --> G
    G --> H["Confirm + record"]

The bundled CLI handles private profile storage, résumé import, scoring, duplicate checks, resumable rounds, attention queues, and application/outcome ledgers. The coding agent handles discovery and browser interaction under the rules in SKILL.md.

Optional LLM assist (Free.ai)

For text assists—JD parse, fit-score rationale, short why-company drafts—you can point an OpenAI-compatible client at Free.ai when your agent host supports a custom base URL and API key:

• Base URL: https://api.free.ai/v1
• Key: FREE_AI_API_KEY from free.ai/account
• Own-hardware model example: qwen7b

This is optional and assistive only. The skill CLI does not call Free.ai; deterministic score, ledger, lease, and intent commands remain the source of truth. Free.ai is not the hosted cloud apply loop, headed browser fill/submit path, or Antigravity/Codex default. Prefer own-hardware models for the OSS/grant path—not premium third-party models. Details: FREE_AI.md.

Discovery combines the reviewed SOURCES.json catalog with an anonymous community registry. Every confirmed application automatically contributes its canonical public job URL, company, role, application channel, and provider; prior confirmed ledger entries backfill during later commands after a one-command disclosure grace period. Jobs, repeatable boards, and feeds are logged pending and become visible in the public dashboard or CLI only after maintainer review. Disable both forms of community sharing independently from analytics with sources sharing disable.

New rounds derive reviewed and qualified totals from private per-lead records, including rejection reasons and revision history. Delivery reconciliation subtracts verified failed emails from effective application totals without erasing history; email access is optional, and sent email without acknowledgement remains labelled receipt unknown. See accounting.

Rounds require recorded attempts across at least three distinct discovery sources, including a successful search, and source attribution for confirmed submissions. If more than 60% of submissions come from one source, the agent must explain the concentration. Blockers and empty results are reported; fit requirements never change to meet a source quota. See round coverage.

🔐 Privacy

Candidate data, résumés, application history, credentials, and browser sessions are never committed to this repository.

Private cloud state is opt-in and isolated from public analytics/community services