Skip to content

jobdork 0.16.2

Choose a tag to compare

@github-actions github-actions released this 05 Nov 16:44
· 146 commits to main since this release
Immutable release. Only release title and notes can be modified.
36f7722

Download

For Download
Mac with Apple Silicon (M1 or later) jobdork-0.16.2-macos-arm64.dmg
Mac with an Intel processor jobdork-0.16.2-macos-x86_64.dmg
Windows 10 or 11, 64-bit jobdork-0.16.2-windows-x64-setup.exe
Linux, 64-bit (x86-64): any distribution jobdork-0.16.2-linux-x86_64.AppImage
Linux: Ubuntu 22.04+, Debian 12+, Mint jobdork_0.16.2_amd64.deb
Docker (a NAS or a server) docker pull jessengolab/jobdork:0.16.2
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.2_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.2-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.2-macos-arm64.dmg --bundle jobdork-0.16.2-macos-arm64.dmg.sigstore.json --repo jessn-dev/jobDork

The image jessengolab/jobdork:0.16.2 is exactly:

jessengolab/jobdork@sha256:3fefcba5b53784bea76e87ead53054117a616ec26056016ed71eef8915dabb6a

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:3fefcba5b53784bea76e87ead53054117a616ec26056016ed71eef8915dabb6a \
  --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

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

Changed — 2026-11-05 — version 0.16.2

0.16.2 carries the 8 entries below, everything since 0.16.1. For you:

  • jobdork on Linux. An AppImage for any 64-bit distribution from 2022
    on, and a .deb for Ubuntu 22.04+, Debian 12+ and Mint 21+, with updates
    that put themselves in place as on a Mac or Windows. ARM Linux stays
    from source.
  • Ask Claude Code, in the desktop app. A new Ask page: a question
    about your job search, answered by Claude Code through jobdork's tools
    only. Each question is checked first, and anything off the job search
    gets "jobdork doesn't allow this". Needs Claude Code installed and signed
    in.
  • A quieter look. Labels in sentence case, one type scale, figures
    that line up, one filled button a page, plain status dots and tags, and
    deletes that are red only where they confirm. Every page, setup step and
    both themes; the guide's pictures are new.
  • Fixed: the Resume page's PDF preview was blank in the Mac app; an AI
    key read back from the keychain showed No key held; removing an AI
    line left its key held and kept.
  • Changed: Gemini CLI is now Antigravity CLI (agy) on the AI
    page, with the line that runs.
  • Security: pypdf 6.21.4, for seven known vulnerabilities in reading a
    PDF.

Updating from 0.16.1: Update under Settings, Updates (or the banner's
Update) downloads 0.16.2, checks it, puts it in place and opens it
again, with no dragging on a Mac. Linux has no earlier version to update
from: install it from the release page. Nothing in the database or the
config changes.

Changed — 2026-11-05 — A quieter, plainer look

The dashboard's look, polished after an audit with
unslop by Damir Sokolovsky (CC BY
4.0). Nothing moved between pages and no feature changed:

  • Labels in sentence case. Last scan, Match, Progress and the
    table headers were capitals with wide spacing.
  • One type scale. 25 font sizes became 9, and nothing is heavier than
    semibold.
  • Figures line up. Scores, counts and run figures use fixed-width
    digits, the one detail used everywhere.
  • The Dashboard's buttons. Run a scan is the one filled button.
    The three that delete sit apart at the end of the row, plain until
    pointed at, then red. AI buttons say they may cost money with an amber
    icon instead of an orange outline.
  • Status. A coloured dot and the word (Interested), not a filled
    capitals pill. The current status in a post is outlined in its colour.
  • Tags. The yellow boxes on a job post are plain tags; a warning has
    an amber dot. In the guide they are now Tags to know.
  • Run figures sit in one strip split by hairlines, not five equal
    cards.
  • The mark is one colour on a plain tile; the AI page's icon is a chip,
    not a sparkle. The menu uses the same greys as the pages.
  • Welcome page left-aligned: no capitals line above the headline, the
    three points as plain lines under a rule, the start button filled, with
    no lift or glow on hover.
  • One main button a page. Each setup step's Continue, Start the
    first scan
    , Ask and a job post's Apply are filled; Apply
    anyway?
    turns it amber.
  • Deleting. The first step of a delete (the Dashboard's three,
    Remove all on the Search page, Remove N job posts, Remove
    jobdork
    ) is a plain button with a red icon; the step that confirms it
    stays red.
  • Choices (provider, period, feedback kind) are separate buttons that
    wrap cleanly, the chosen one tinted like the menu, not filled blue.
  • No coloured side stripes on notes, the coding-agent box, Ask's
    answers, notices and warnings: a whole hairline box, amber-tinted for a
    warning.
  • Resume cards: plain initials instead of rainbow tiles, and a bar
    coloured only when something falls short; the same for the parts of an
    ATS match.
  • Checks on a document read Passed or Read this with a green
    or amber dot, not ok and READ in coloured text.
  • Small fixes: the file pickers drawn like the buttons; notes, Ask and
    feedback typed in the interface's font, not a code font; Remove in a
    list no longer in the figures' font; Active sources a dot, not 15
    green words; the dark mode switch says On and Off; the Cover letters
    table's buttons fit the Resume page's column; setup's What will be
    searched
    no longer ends in ": ." before any job title is added.

Checked on every page and setup step, light and dark, and at phone width.
The guide's pictures were retaken, and its Dashboard, Job posts, job post,
Resume and AI pages say what the buttons, tags and checks look like now.

Added — 2026-11-05 — Ask Claude Code, from the desktop app

A new Ask page in the desktop app: type a question about your job
search and Claude Code answers through jobdork's tools, from your job posts,
resume and applications, and can save documents and suggest resume
additions for your OK. Follow-ups continue the conversation; Stop and
New conversation are beside Ask. Only job-search questions are
sent: each is checked first by a small Claude model with no tools, which
fails closed, and anything else gets "jobdork doesn't allow this". The run
has jobdork's tools and nothing else (no commands, files, web, other MCP
servers or your own Claude Code settings), and a system prompt that repeats
the rule. At most 2,000 characters a question and 30 questions an hour.
Claude Code only (agy cannot be limited to jobdork's tools); the desktop
app only (jobdork/ai/ask.py, /api/ask). The guide has a page for it,
and the AI page no longer says jobdork never calls your agent.

Added — 2026-11-04 — The desktop app for Linux: an AppImage and a .deb

jobdork now installs on 64-bit Linux like on a Mac or Windows, from the
next release on: jobdork-<version>-linux-x86_64.AppImage, one file
that runs on any distribution from 2022 on with no password, and
jobdork_<version>_amd64.deb for Ubuntu 22.04+, Debian 12+ and Mint,
installed with sudo apt install ./jobdork_<version>_amd64.deb, in the menu
and on the PATH. Until now Linux meant running it from source.

  • The window is pywebview's Qt engine, carried inside (PyQt6 and Qt's
    web engine; DECISIONS.md, 2026-11-04): nothing else to install. The
    system's own libraries are left to the system; the .deb names them. Qt
    parts the window never uses (QML, 3D, multimedia, speech, SQL), and the
    GTK theme and CUPS printing plugins, which would carry the build
    machine's GTK and CUPS, are left out.
  • Update works as on the others: checked against the release's
    checksums and build attestation, then the AppImage is swapped in once
    jobdork has quit and opens again; a .deb is installed by
    pkexec apt-get install once jobdork has quit (the desktop asks for the
    password), then jobdork opens again, the old version if the password was
    not given. Where it cannot, the Downloads folder opens and the update
    window says what to do.
  • The scheduled scan and a coding agent start the AppImage by its own
    file ($APPIMAGE), not the folder it unpacks to for one run, which is
    gone when it quits.
  • Removal: Settings, Remove jobdork, then delete the AppImage or
    sudo apt remove jobdork.
  • Built and checked in CI (desktop.yml): on Ubuntu 22.04 (the oldest
    glibc Qt runs on), attested like the other installers, the AppImage tool
    and runtime fetched pinned by version and SHA-256. Then the .deb is
    installed with apt on bare Ubuntu 22.04, 24.04 and Debian 12 containers,
    every library its files need is looked for (none may be missing), its
    self-test runs and it is removed; the AppImage's self-test runs; and the
    window is opened on a virtual screen and photographed. The release page
    lists both downloads and SHA256SUMS.txt covers them.

Tried before CI, in emulated x86-64 containers: those checks found a .deb
missing libwayland-server0 on Ubuntu 24.04; a time zone database missing
on a bare system (the Linux build now carries tzdata, as Windows does); the
build machine's NSS, X11 and graphics libraries clashing with a newer
system's, which kept Qt from starting OpenGL; and Ubuntu 24.04's apt picking
a stand-in sound library for libasound2. All fixed, and the window drew
the setup page on Ubuntu 24.04. ARM Linux stays from source.

Fixed — 2026-11-03 — A removed AI line takes its key with it

Removing a reader or checker on the AI page (or switching it to another
provider) left its key held, and kept in the keychain when you chose
Remember keys, with nothing on the page that used or showed it any more:
only Forget saved keys in Settings took it out. Now Save forgets
every AI key no line uses (OpenAI, Anthropic, Gemini, Groq, and the Ollama
key once no Ollama line sends it), in memory and in the keychain, as
Forget does, and a note names it ("Removed the Groq key: no line uses
it now"). A key set in the environment, outside jobdork, is left alone
(api.forget_unused_keys, after the AI page is saved).

Fixed — 2026-11-03 — Keys say where they are kept

An AI key read back from the keychain after a restart or the idle wipe
showed No key held on its line, though it was held and used: the page
knew "memory" and "environment" only. And neither the AI page nor the
Sources page said whether a key was kept in the keychain or only until
jobdork closes. Now an AI line says key kept in this computer's
keychain
or key held until jobdork closes, and the Adzuna and USAJOBS
cards say the same beside Ready. Forget and Remove say on hover
that they take the keychain's copy too (they always did). jobdork knows
which keys are kept from what it saved there or found there this run
(keystore.kept), so the page never asks the keychain on a poll, which can
prompt on a Mac. The Sources page of the guide no longer says keys are kept
in a file: that stopped in 0.15.2.

Changed — 2026-11-03 — Gemini CLI is now Antigravity CLI (agy)

Google moved Gemini CLI's people onto Antigravity CLI, whose command is
agy, so the AI page's gemini mcp add -s user ... line no longer ran for
most people. The page now gives Antigravity CLI (agy):
agy mcp add jobdork -- <jobdork> --mcp, which adds jobdork for every
folder, and agy mcp list then shows it. Antigravity CLI, by hand
names the file agy really writes, ~/.gemini/config/mcp_config.json
(Gemini CLI's was ~/.gemini/settings.json). Both checked against agy
1.4.8 in a scratch home folder. The guide, README and run notes say
Antigravity CLI.

Fixed — 2026-11-03 — The Resume page's preview was blank in the Mac app

In the app on a Mac, choosing a tailored resume (or a PDF resume of your
own) on the Resume page showed a blank white box where the PDF should be,
with no error. The browser dashboard showed it. The page shows a PDF from a
blob: address it makes itself, and that blob takes on the page's
Content-Security-Policy, whose frame-ancestors 'none' WebKit (the app
window's engine) then applied to the PDF too: it would not be shown inside
any page, its own included. Chrome does not apply it there. Now the policy
says frame-ancestors 'self': the page can show its own PDF, and no other
site can frame the page (web/serve.py). Checked in the app window itself
on the guide's made-up data.

Security — 2026-11-03 — pypdf 6.21.4

CI's security job failed on every pull request: pip-audit found seven
known vulnerabilities (CVE-2026-119203 to -119209) in pypdf 6.21.2, the
version in requirements.lock and requirements-desktop.lock (the CI lock
had 6.21.3, still short of four of the fixes). pypdf reads a PDF resume, so
these are in what the installers carry. All three locks now pin 6.21.4 with
its PyPI hashes, and pyproject.toml asks for at least 6.21.4. pip-audit
finds nothing in any of them; the tests pass on it.