Skip to content

jobdork 0.16.3

Choose a tag to compare

@github-actions github-actions released this 06 Nov 13:30
· 121 commits to main since this release
Immutable release. Only release title and notes can be modified.
201fcb1

Download

For Download
Mac with Apple Silicon (M1 or later) jobdork-0.16.3-macos-arm64.dmg
Mac with an Intel processor jobdork-0.16.3-macos-x86_64.dmg
Windows 10 or 11, 64-bit jobdork-0.16.3-windows-x64-setup.exe
Linux, 64-bit (x86-64): any distribution jobdork-0.16.3-linux-x86_64.AppImage
Linux: Ubuntu 22.04+, Debian 12+, Mint jobdork_0.16.3_amd64.deb
Docker (a NAS or a server) docker pull jessengolab/jobdork:0.16.3
Checksums of the installers SHA256SUMS.txt

Mac: open the .dmg and drag jobdork into Applications. Windows: run the setup; it installs for you alone, no administrator needed. Linux: make the AppImage a program (its Properties, or chmod +x) and open it, or install the .deb: sudo apt install ./jobdork_0.16.3_amd64.deb. Not sure which Mac you have? Apple menu → About This Mac: "Chip" is Apple Silicon, "Processor … Intel" is Intel. From source: the ways to run it. New to jobdork? The user guide shows every page of the app.

The first time you open it

The installers are not signed yet, so each system warns once:

  • macOS says it cannot check jobdork for malicious software. Click Done,
    open System Settings → Privacy & Security, scroll down to the line about
    jobdork and click Open Anyway, then Open Anyway again.
  • Windows shows "Windows protected your PC". Click More info, then Run anyway.

Verify Build Package

An installer: compare its SHA-256 with SHA256SUMS.txt, or with the GitHub CLI:

gh attestation verify jobdork-0.16.3-macos-arm64.dmg --repo jessn-dev/jobDork

Each installer's signed attestation is here too, as <installer>.sigstore.json, to check it without asking GitHub:

gh attestation verify jobdork-0.16.3-macos-arm64.dmg --bundle jobdork-0.16.3-macos-arm64.dmg.sigstore.json --repo jessn-dev/jobDork

The image jessengolab/jobdork:0.16.3 is exactly:

jessengolab/jobdork@sha256:46c67b91984f22cd51abc9ce8d8d81f653bd80d334c88b2b3f8e8f0ad3cdc372

Built, scanned, checked and signed by this repository's workflow after approval.
Verify it before you run it, then pull it by that digest:

cosign verify jessengolab/jobdork@sha256:46c67b91984f22cd51abc9ce8d8d81f653bd80d334c88b2b3f8e8f0ad3cdc372 \
  --certificate-identity-regexp '^https://github.com/jessn-dev/jobDork/\.github/workflows/docker\.yml@' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

The installers are unsigned: how to open them. Privacy: PRIVACY.md.

What changed

12 changes in this release, newest first (click to read)

Changed — 2026-11-05 — version 0.16.3

0.16.3 carries the 11 entries below, everything since 0.16.2. For you:

  • Follow-up reminders. Your computer notifies you on the day a next
    step on My applications is due, while jobdork is open and after a
    scheduled scan; Settings → Notifications turns them off.
  • Track an application you sent, at the top of My applications: the
    job post's link and the day you applied.
  • A master resume. Setup advises keeping one (every job, project and
    skill), jobdork tells it from a regular resume, and the Resume page says
    which it read.
  • Closing jobdork with a scan scheduled asks whether to keep it. A
    schedule turned off is kept in Settings, to run now or turn back on.
  • Ask looks like a chat, Enter asks, and you choose the model.
  • One keychain item for every kept key, so an update asks the Mac
    keychain once, not once per key.
  • The AI tools tab says what to ask your coding agent when it is your
    only reader.
  • Fixed: Remove jobdork left the job posts and the app behind on a
    Mac; now it removes what you chose and moves the app to the Trash. A
    closed jobdork no longer keeps running.
  • Checked: a small fact-checking model (bespoke-minicheck) as the AI
    checker: not better than qwen3.8:27b (docs/AI-MODELS.md).

Updating from 0.16.2: Update under Settings, Updates (or the banner's
Update) downloads 0.16.3, checks it, puts it in place and opens it
again. On a Mac the keychain may ask once more for each key you kept, the
one time they move into the single item; choose Always Allow. Nothing
in the database changes; the config gains settings only when you change
them (notifications.reminders, ask_on_close, schedule_saved,
resume.kind).

Added — 2026-11-05 — Follow-up reminders as your computer's notifications

A next step on My applications (a phone screen, a follow-up email) used to
show only inside jobdork, in red once its date had passed. Now your
computer reminds you on the day it is due, with the same notifications a
scan uses: Follow-up due today: Phone screen, Acme, or one notification
naming several when more are due at once.

jobdork looks when it opens, every ten minutes while it stays open (a date
comes due at midnight), and after each scheduled scan, so with a daily scan
on the reminder comes that day even with the window closed. Each next step
is told once for its date, kept in the database, so reopening jobdork does
not repeat it; a new date is told again on its day. Settings →
Notifications
has Turn off follow-up reminders
(notifications.reminders in config.yaml).

core/reminders.py does it. Tests cover which next steps are due (today and
before, not on an ended application, oldest first), the words of one and of
several, each told once for its date and again for a new one, a notification
that did not show not counted as told, the setting off, and the setting read
and written.

Added — 2026-11-05 — Closing jobdork asks about a scheduled scan; a schedule turned off is kept

Closing the jobdork window said nothing about a scheduled scan, so it was
easy to think closing stopped it, or that jobdork had to stay open for it.
Neither is so: your computer's scheduler starts the scan with jobdork
closed, and it stops when it is done. Turning a schedule off also lost it:
setting it up again meant picking the days and time again.

Now closing the desktop app with a scan scheduled asks Keep the scheduled
scan?
, saying when it runs: Keep it and close, Turn it off and
close
, or Cancel. Don't ask again when I close jobdork stops the
question (ask_on_close: false); Ask when I close jobdork, under the
schedule in Settings, brings it back. A job still running is asked about
first, as before. The question is the page's own: the window holds the close
back, the page says it is asking, and a page that does not answer within
three seconds lets the window close anyway, so jobdork is never stuck open.

A schedule turned off, here or in Settings, is kept (schedule_saved):
Settings shows Off. Kept from before: every day at 08:00, with Run it
now
and Turn it back on.

web/app.py ask_before_closing holds the close and asks the page through
window.run_js (pywebview's evaluate_js wraps it in eval, which the
page's policy refuses); api.close_question says whether to ask;
api.schedule_save keeps the plan when turning it off and takes
every=saved. Tests cover the page asking and the window held, a page that
cannot ask (closed anyway), nothing scheduled (no question), the question
only for a schedule this copy runs and not when turned off, a kept schedule
written, read back and turned on again, nothing kept to turn on, and a kept
schedule jobdork cannot read ignored. Checked in a real app window on a
temporary folder: the page asked, the window stayed open, and Keep it and
close
closed it.

Added — 2026-11-05 — The AI tools tab says what to ask your coding agent

With a coding agent as the only reader, a job post's document buttons said
what to ask the agent, but the AI tools tab's editing help (Tailor my
resume
, Keyword ideas (AI), Skills to highlight, Recruiter
feedback
, Revise: 5 versions, Recruiter feedback on this letter)
had nothing to give it: the guide said to ask the agent "directly", with no
instructions, advert or rules behind the question.

Each of those buttons now says what to ask your agent, with Copy (the
pasted bullet, paragraph or letter goes with it). The agent's get_brief
takes the editing kinds (resume_edits, keywords, highlight,
feedback, revise, with text for a revision or a letter) and gives
exactly what a model would have been given; it answers you in its own chat,
following the same rules (only what your resume says, quoting it), and
nothing is saved under the tab (save_document refuses those kinds). The
server refuses the tools in that mode with the same question to ask
(409), as it does the documents. The agent's connection instructions say
so.

The guide's AI and job window pages say what the buttons do with an agent.
Tests cover the editing briefs (each kind, the user's text in a revision,
revise without text or with too much refused, nothing written or saved) and
the tools refused with what to ask when the agent is the only reader.

Added — 2026-11-05 — Track an application you sent, from its link

My applications listed only job posts jobdork had found and you marked
applied. A job you applied to somewhere else, or before you used jobdork,
could be brought in only by adding it on the Sources page and then marking
it applied, dated the day you did that rather than the day you applied.

Track an application you sent, at the top of My applications, takes the
job post's link and the day you applied (today unless you change it; a day
still to come is refused). The post is read into Job posts as Add a Job
Post
does, marked applied, dated that day in its stages, and listed. When
the page cannot be read, the form asks for the job title and employer
(and the place, and the advert if you have it): with the advert the post is
scored like any other; without it, it is tracked with nothing to score
against. A job already at interviewing or offer is left there, and a post
jobdork already had is not added twice.

api.track_application and POST /api/application/track do it;
Store.set_status takes the day a change was made (when) for its history.
The guide's My applications page explains it. Tests cover tracking from a
pasted advert (applied on its day, listed), from a title and employer alone
(each asked for), the day (real, YYYY-MM-DD, not in the future, nothing
stored when refused), a job further along left as it is, and a link read or
not readable (asking for more).

Added — 2026-11-05 — A master resume, told apart from the one you send

jobdork now knows the difference between a master resume (your private
archive of every job, part-time and freelance work, volunteering, projects,
presentations, awards, certifications and skills, never sent as it is) and
a resume you send, and advises the first:

  • Setup's resume step says to upload your master resume if you keep
    one, and the one you send otherwise; the welcome page's list of steps says
    the same.
  • jobdork guesses which it is when you upload (search/master.py):
    "master" in the file's name settles it ("MasterResumeJaneDoe.pdf" too);
    otherwise a long text (1,700 words or more) counts most, and three pages or
    more, ten or more dated entries and archive sections (volunteer work,
    awards, presentations, publications, freelance or part-time work, hard
    and soft skills) add to it. Tried on eight real
    resumes: the 1,849-word master was taken for one, and none of seven sent
    resumes of 290 to 1,566 words over two to five pages was. The guess is
    written to the config (resume.kind), as it is the only time the file's
    own name is known.
  • This resume is on the Resume page, and in setup after the upload, says
    which jobdork took it for and why, and changes it: My master resume or
    A resume I send.
  • With a master resume: How a tracking system reads it no longer marks
    it down for being over two pages; a tailored resume's prompt says it is
    choosing from an archive (writer.MASTER_NOTE); the card says Your
    master resume
    .
  • A resume longer than the AI reads (20,000 characters) gets a note:
    what comes after is not seen, and a claim about it is marked unsupported.
  • jobdork setup in a terminal gives the same advice, and says which
    it took the resume for.

The guide's Resume page explains a master resume; Getting started, the
overview, the AI and job-window pages, the glossary, README.md, the run and
CLI guides, CONFIG.md and ARCHITECTURE.md name it, and DECISIONS.md says
why. AI-MODELS.md adds the reader and checker pairs measured on a master
resume: gpt-oss:20b as checker as well as reader raised the rate to 18%. Tests cover the guess (the file name, a long archive, a
long CV that is sent, a designed resume with little text, archive
sections), your choice winning over it, the length check, the setting, the
page's report, and the tailoring prompt with and without a master.

Fixed — 2026-11-05 — Remove jobdork removes it, and a closed jobdork is not running

In 0.16.2 on a Mac, Settings → Remove jobdork with everything ticked
seemed to remove nothing: the job posts were still on the page, and jobdork
was still in Applications after quitting. It had removed them, but:

  • The page kept asking the server, which opened the database again and
    left a new, empty one; the Job posts page still showed the list it had.
    Now, once you confirm, the window shows only jobdork was removed and
    one button, the page asks nothing more, and the server answers nothing
    but quitting (410 for anything else).
  • The program stayed. The page said to drag it to the Trash, and it was
    expected to go by itself. Now quitting removes what you chose once more
    (whatever was opened since is gone too), then moves the program to the
    Trash: the Mac app (only jobdork's own bundle, checked by its bundle id,
    and not a copy run from its disk image or a hidden translocated one) and
    a Linux AppImage (into the desktop's Trash, as freedesktop.org lays it
    out). A .deb still needs sudo apt remove jobdork; Windows has its
    uninstaller.
  • What macOS keeps for the window under ~/Library (WebKit's storage,
    caches, cookies, saved window state and preferences, by the app's bundle
    id) was left, as was Ask's empty working folder. Both go now, and nothing
    else in ~/Library is touched.

Closing the window ends jobdork, on a Mac, Windows and Linux. Ask's
Claude Code run is stopped with it, and the program ends at once after the
server stops (app.exit_now): a scan's fetches, on threads Python would
otherwise wait for, no longer keep it running unseen. A scheduled scan you
turned on still runs without the window, and ends when the scan does.

Tests: the server refuses everything but quitting after a removal; the
Mac's window traces go and another app's do not; a folder given to the
removal never reaches the real ~/Library; only jobdork's own Mac bundle
or an AppImage is moved, and an AppImage lands in the Trash with its
.trashinfo; and the program ends at once with a thread still busy. The
guide's Settings page, the desktop notes and PRIVACY.md say what happens
now; the CLI guide lists jobdork uninstall, and ARCHITECTURE.md names
core/uninstall.

Changed — 2026-11-05 — Changelog entries wait in files of their own, so pull requests do not conflict

Every pull request added its entry at the top of docs/CHANGELOG.md, so any
two open at once changed the same lines: whichever merged second was blocked
by a conflict and had to be merged again by hand (#128 and #129 both were).

Each pull request now adds one file to docs/changes/ with its entry
instead. scripts/changelog.py check says whether each is well formed (the
tests run it, so CI refuses one that is not), and the release pull request
runs scripts/changelog.py collect, which moves them all into the changelog
above the newest entry, newest first by date and then by when each was
added, and deletes the files. Release pages read the changelog as before.
scripts/tag_release.py refuses to tag while an entry is left waiting, so
none is left off a release page, and scripts/set_version.py does not count
the waiting entries as pages that name a version.

CONTRIBUTING.md, the pull request template, docs/changes/README.md and the
changelog's opening say where an entry goes now. Tests cover the check
(heading, kind, date, one entry a file, no separators), collecting (order,
placement above the newest entry and the backlog left where it is, files
deleted, nothing changed when one is malformed) and every entry waiting in
the repository.

Checked — 2026-11-05 — A small fact-checking model as the checker: not better

bespoke-minicheck (7.7B, 4.7 GB in Ollama), a model built only to say
whether a document supports a claim, was measured as jobdork's checker
against qwen3.8:27b: the same 262 claims from gemma4:26b verdicts on
twelve job posts and one master resume, with jobdork's script rules applied
to both. It flagged fewer claims (5.3% against 6.5%), but by passing more,
not by being right more: of the 25 claims the two disagreed on, read by hand
against the resume and the advert, qwen3.8:27b was right on 21 and
bespoke-minicheck on 2, both settled by jobdork's gap rule rather than the
model. It passed skills the resume never names and flagged ones it does. It
also answers only yes or no, with no quote for the script to check. Not
adopted; the result is in docs/AI-MODELS.md, and the guardrails item in
Still outstanding is narrowed to the rewrite pass.

Added — 2026-11-05 — One command tags a release

python scripts/tag_release.py tags a release once its pull request is
merged. It asks whether the release is major, minor or patch (or take it as
an argument) and counts the version on from the last release tag: from
v0.16.2, patch is 0.16.3, minor 0.17.0, major 1.0.0. It tags only when:

  • pyproject.toml and every page name that version (a tag that differs is
    refused by the release run anyway, and a tag can never be moved);
  • main's last commit is the merge of release/<version>, from a merged
    pull request;
  • every check on that commit finished and passed (a skipped one is fine; one
    still running stops it, to run again later);
  • the tag exists neither locally nor on GitHub.

Then you type the version to confirm, it tags and pushes, and opens the
release run in the browser. Approving the release environment stays
yours: that is the sign-off. A working copy with changes is refused, so
nothing is lost by its git checkout main and git pull --ff-only.
SECURITY.md's release steps name it. Tests cover the version count, the
release merge and the checks (tests/test_tag_release.py); nothing in them
runs git or reaches GitHub.

Changed — 2026-11-05 — Ask looks like a chat, and you choose the model

The Ask page is laid out like a chat app now. Before the first question:
the jobdork mark, a line picked at random for each conversation ("Which job
post should we look at first?"), and the message box in the middle, with
what Ask can reach under it. Once you ask, the page is the conversation:
your questions on the right, the answers under them as text (headings, lists
and bold shown) with a Copy button, and the box at the bottom. The box
grows as you type.

  • Enter asks, Shift+Enter starts a new line; before, only
    Ctrl+Enter (Cmd+Enter) asked, and Enter alone did not.
  • The model is chosen in the box: Sonnet, Opus, Haiku, or Claude Code's
    default. It can change between questions, is kept for next time on this
    computer, and is checked against that list on the server: nothing else is
    ever passed to claude --model. The check before each question stays on
    Haiku (ai/ask.py, MODELS).
  • + starts a new conversation and a square button stops one, in the box.

The guide's Ask page shows both views and says that Ask does not use the
readers and checkers on the AI page. SECURITY.md (the model list), PRIVACY.md,
the desktop notes and DECISIONS.md (the Ask decision, with why a coding
agent is still not a checker) say so too.

Changed — 2026-11-05 — One keychain item for every kept key

An unsigned Mac app is asked "jobdork wants to use your confidential
information stored in jobdork in your keychain" after each update, and with
a keychain item for each kept key it was asked once for each: an AI key, the
Ollama key, Adzuna's and USAJOBS's could mean four or five password
prompts. Every kept key is now in one item, as JSON, so an update asks once;
choose Always Allow and it does not ask again until the next update.

Keys kept the old way move into the one item the first time it is read,
which may ask once more for each of them that one time; their own items are
then removed. Forget saved keys, Remove jobdork and removing an AI line take
keys out of the one item, and any left the old way (core/keystore.py).
Tests check that every key lands in one item, that old items move and go,
that reading every key asks the keychain for one item, and that a damaged
item reads as no keys kept. The guide's Settings page and DECISIONS.md say
it asks once for all keys.