atsfill reads the application form behind a job posting, fills it with your answers, and checks what the hiring system will receive before anything is sent. It is built for agents with a shell: every command prints one JSON document and exits with a code a script can branch on.

• read lists a form's fields with their ids, types, options and whether they are required.
• fill is a dry run: it fills the form, reads it back field by field, and never submits.
• send fills again and submits only when every answer reads back as given.
• Submitting is off until you enable it per hiring system, in a config file the agent does not write.
• A posting already sent is refused unless you pass --resend.

Supported hiring systems

Any other system returns unsupported, so the caller can fall back to driving a browser itself.

Why atsfill?

An agent applying through a generic browser carries each system's quirks as prose, rereads it every run, and checks the form before submitting only because an instruction says so. atsfill moves the quirks into one adapter per system and makes the check code: a send whose read-back differs from the answers is refused.

Install

atsfill runs on Linux and macOS with Python 3.14, which uvx fetches if needed.

uvx atsfill install-browser

This downloads the Camoufox browser build atsfill is pinned to: 1.3 GB, about 2.5 GB once unpacked.

Every push to main that passes CI is also published as a dev release; uvx --prerelease allow atsfill runs the newest.

Quickstart

1. List the form's fields:

   uvx atsfill read https://job-boards.greenhouse.io/acme/jobs/1234
   

2. Write your answers to answers.json, keyed by field id. Files take an absolute path:

   {
     "first_name": "Ada",
     "last_name": "Lovelace",
     "email": "ada@example.com",
     "resume": "/home/ada/resume.pdf"
   }
   

3. Dry-run the fill. It ends ready when every answer reads back as given:

   uvx atsfill fill https://job-boards.greenhouse.io/acme/jobs/1234 --answers answers.json
   

4. Allow the system to submit in ~/.config/atsfill/config.toml:

   submit = ["greenhouse"]
   

5. Send. A submitted result carries the evidence of the send:

   uvx atsfill send https://job-boards.greenhouse.io/acme/jobs/1234 --answers answers.json
   

A dry run is not invisible: some systems save answers or the resume as they are typed. atsfill status lists each system's side effects, whether it is allowed to submit, and how far atsfill has verified it: the systems. A send through an adapter no send was verified on goes ahead with a warning.

How it works

flowchart LR
    CLI[atsfill CLI] --> Core
    Core -->|detect, read, fill, read back, submit| Adapter[adapter for the system]
    Adapter --> Browser[headless Camoufox]
    Core --> Gate{read-back matches,<br>submit enabled,<br>not already sent}
    Gate -->|yes| Submit[submit]
    Gate -->|no| Refused[refused]

Each command launches its own headless Camoufox, a Firefox build patched to hide automation, with a fresh context and one saved device identity. The core owns every rule about when a send is allowed; an adapter only knows its system's page.

Every result has a status (ready, refused, submitted, blocked, unknown, unsupported) and, when it is not clean, a reason code. The exit code is 0 for ready and submitted, 1 otherwise, 2 for a usage error.

More

• Architecture decisions: the contract, the submit gate, the browser, sessions.
• Hiring systems: every system mapped so far, in backlog order, and each one's form as observed.
• atsfill --help for every command and option.