Apply¶
The Apply step opens the job application page in your browser. Kairos prepares everything — you make the final call.
Usage¶
kairos apps set <job-id> applied # record that you applied (now)
kairos apps set <job-id> applied --at 2026-11-04 # ...or on an earlier day
Workflow¶
flowchart LR
Ready[Resume Tailored] --> Open[Open Browser]
Open --> Page[Application Page]
Page --> User[You Submit Manually]
User --> Confirm[Mark as Submitted]
- Kairos checks that a tailored resume exists and is approved
- Opens the job URL in your default browser
- You fill in the application form and upload the tailored resume
- Confirm submission via CLI or Web App, status updates to "Submitted"
Why Semi-Automatic?¶
- Respect for employers: No mass bot applications
- Quality control: You review every application
- Platform TOS: Automated submission violates most platforms' terms
- Your judgment: Some fields need human context (cover letter, salary, visa questions)
Application Tracking¶
Every status change is kept in a timeline (decision 0006), so you can see when an
application moved and who moved it: you (manual), an agent (agent), or, later, a
reply read from your mail (email).
kairos apps list # Jobs you applied to, latest change first
kairos apps list -s interview # Only those in one status
kairos apps log <job-id> # The job's timeline, oldest first
kairos apps set <job-id> interview --kind technical -m "45 min with the team"
kairos apps undo <job-id> # Undo the latest change (kept as an undo)
<job-id> is the full id or its first characters, as lists print it.
A role no board found, such as a referral, a LinkedIn post or a company's own form, is added from its link (decision 0007):
kairos jobs add <url> -t "Software Engineer" -c Acme -l Sydney --country AU \
-d posting.txt --sponsors-visa -m "Referred by Sam"
It is saved as matched under platform manual, which Kairos never re-checks against a
site.
| Status | Meaning |
|---|---|
applied |
You sent the application |
in_review |
The company has it and is looking at it |
assessment |
A take-home, online test or similar |
interview |
An interview round; --kind says which (recruiter, technical, onsite, final) |
offer |
You received an offer |
rejected |
The company said no |
withdrawn |
You pulled out |
A change cannot be dated in the future or before the job's last change; undo the later
change first. Setting a job's current status again is refused. kairos jobs apply and
kairos jobs status still work and record the same events.
Status suggestions from your mail¶
Kairos can read replies from your mail archive in Kioku and suggest the status changes they imply. It never changes a job on its own: every suggestion waits for you to accept it.
op run --env-file=.env.op -- uv run kairos-server # the API needs the Kioku token
kairos apps sync # Read new mail, suggest changes
kairos apps inbox # Review what it found
kairos apps accept <id> # Record it, dated when the mail arrived
kairos apps accept <id> --job <job-id> --status assessment # Correct it first
kairos apps ignore <id>
How a sync works:
- Each mailbox is read back to where the last sync stopped. A mailbox's first sync reads back to your earliest application, but no more than 60 days.
- A message is kept when its sender is a job's contact address, when it comes from an applicant tracking system (Greenhouse, Lever, Workday, Moka, ...), or when it names an applied company in its subject or sender name. Everything else is dropped unread.
- The LLM reads each kept message, up to
mail_batchper sync. It labels the message and picks the job it is about.
A mailbox Kioku has not synced for more than a day is flagged as stale: no suggestions from it does not mean no replies came.
The API reads the Kioku token from KAIROS_KIOKU_ACCESS_CLIENT_ID and
KAIROS_KIOKU_ACCESS_CLIENT_SECRET. Keep them as op:// references in a .env.op (see .env.op.example) and
start the API under op run.
[tracking]
mail_accounts = [] # Kioku mailbox slugs; [] = every enabled one
mail_lookback_days = 60 # How far back a mailbox's first sync reads
mail_batch = 30 # Most messages the LLM reads per sync
mail_sync_minutes = 0 # Sync this often while the API runs; 0 = off
Archiving closed postings¶
Saved postings you have not applied to yet (status new, analyzed or matched) are
re-checked against their site, and the ones the site reports closed are archived:
closed_at is set and they drop out of the job list (GET /jobs?include_closed=true
still returns them). A posting is archived only on an explicit answer: a 404, Seek's
isExpired, LinkedIn's "No longer accepting applications", or the career-site API saying
the post is gone. Network errors and rate limits leave it for the next run. Adzuna cannot
tell, so its postings are never archived this way. Searching and finding a posting again
reopens it.
uv run kairos jobs check # Check every open posting now
uv run kairos jobs check --older-than 24 # Only those not checked in the last day
While the API runs it does this by itself every availability_check_hours (default 24):