JobniacFast

JobniacFast is a local-first desktop app and MCP server for managing candidate profiles and job postings, matching them deterministically, and generating tailored resume and cover-letter PDFs (generic, Canadian English and French, and German). It is built from a Rust core and a React and TypeScript user interface on Tauri 2, and stores its data in an embedded SQLite file. Your data stays on your machine.

Releases

Every release lists its changes in CHANGELOG.md and on the releases page. The app can check for updates itself (Settings > Updates; off until you turn it on).

Related MCP server: CoverAI MCP Server

Requirements

• Windows 11 (x64), Linux (x64, AppImage or .deb) or macOS 14 or later on Apple Silicon (.dmg). Intel Macs are not supported.

• WebView2 on Windows. Windows 11 includes it; the installer installs it if it is missing.

Install

Releases are published on the GitHub Releases page. The latest release is at https://github.com/JonHHH09/JobniacFastFs/releases/latest.

Windows:

1. Download JobniacFast_<version>_x64-setup.exe and SHA256SUMS.

2. Check the installer before you run it:

   Get-FileHash -Algorithm SHA256 .\JobniacFast_<version>_x64-setup.exe
   Select-String -Path .\SHA256SUMS -Pattern 'x64-setup'

   The two hashes must be the same. If they differ, do not run the installer.

3. Run the installer. It installs for your user only and does not ask for administrator rights. It installs to %LOCALAPPDATA%\JobniacFast.

Expect a SmartScreen warning. Until the Windows build is signed, Windows shows "Windows protected your PC". Click More info, then Run anyway, after you have checked the hash. The warning is expected for unsigned downloads.

Linux: download the AppImage or the .deb, then:

1. Check the file against SHA256SUMS: sha256sum -c SHA256SUMS --ignore-missing. Do not install a file that fails.

2. Install the .deb with sudo apt install ./JobniacFast_<version>_amd64.deb, or make the AppImage executable with chmod +x JobniacFast_<version>_amd64.AppImage and run it.

macOS (Apple Silicon): download JobniacFast_<version>_aarch64.dmg and SHA256SUMS, check the download (shasum -a 256 -c SHA256SUMS --ignore-missing), open the DMG and drag JobniacFast to Applications. A release signed with a Developer ID certificate and notarized by Apple opens normally. A release without that signature is only ad-hoc signed: macOS then says it cannot verify the app. After you have checked the hash, open System Settings, Privacy & Security, and choose Open Anyway for JobniacFast (or run xattr -dr com.apple.quarantine /Applications/JobniacFast.app). The release notes say which kind of signature the release has.

Updating: use Settings > Updates and check for updates, or download the new release and install it over the old one. Your data is kept.

Uninstall: on Windows use Settings, Apps, JobniacFast, Uninstall, or the uninstall.exe in the install folder. On macOS drag JobniacFast from Applications to the Bin. On Linux run sudo apt remove jobniacfast for the .deb, or delete the AppImage file. Your data stays in both cases (see below).

Getting started

1. Launch JobniacFast.

2. Create a profile.

3. Add jobs: paste the text, add a job from a link, or scan Arbeitnow.

4. Run a match.

5. Generate a resume or a cover letter.

The optional features (Arbeitnow, links, deleting, document export, and generation) are on by default in the desktop app. To turn one off, open Settings > Optional features; a change applies after you restart the app (turning off an MCP capability below is the exception: it applies at once). Three things are off by default and need your explicit opt-in there: Let MCP clients scan Arbeitnow, Let MCP clients add a job from a link and Let MCP clients delete profiles and jobs. They control the scan_arbeitnow_jobs (with import_arbeitnow_job), add_job_from_link, delete_profile and delete_job tools of the MCP server the app runs. The scan and the link tool reach the network, the delete tools are permanent, and MCP tools do not ask for confirmation. Turning one of the three off takes effect at once: a running MCP server restarts without that tool, and MCP clients reconnect with the new access token. If the old server cannot be confirmed stopped, Settings says it may still be running and no new server starts until it is gone; close and reopen the app to be sure. If the setting cannot be saved, nothing changes and the tool stays available. Turning one on applies after you restart the app.

Data storage

Your data is one SQLite file. The app and jobniac-cli create it, and bring it up to date, the first time they start; there is nothing to install or configure. The default location is per user and outside the install folder, so an update or a reinstall never touches it:

• Windows: %LOCALAPPDATA%\Jobniac\data\jobniac.sqlite3

• macOS: ~/Library/Application Support/Jobniac/data/jobniac.sqlite3

• Linux: $XDG_DATA_HOME/jobniac/data/jobniac.sqlite3, or ~/.local/share/jobniac/data/jobniac.sqlite3 when XDG_DATA_HOME is not set

Set JOBNIAC_DB_PATH to an absolute file path to use another file. A value that is not a clean absolute path stops the database from opening; it is never replaced by the default.

The desktop app and jobniac-cli can use the same file at the same time. To back up, close the app and any running jobniac-cli, then copy jobniac.sqlite3 (and a jobniac.sqlite3-wal or jobniac.sqlite3-shm file next to it, if one is left). To restore, copy the file back while the app is closed.

jobniac-cli migrate applies the schema to the file explicitly:

& "$env:LOCALAPPDATA\JobniacFast\jobniac-cli.exe" migrate

A new file prints Applied migrations: ...; a file that is already current prints Schema is current (...); nothing to apply. A file written by a newer version of the app is refused.

Configuration

All configuration comes from environment variables. There is no .env file, and secrets are never read from command-line arguments. The desktop app works without any configuration. The variables below override its defaults, and they are the way to configure jobniac-cli. An option marked exact 1 is on only when its value is exactly 1; true, yes and 01 are off.

In the desktop app the optional features are on by default. Turn them off in Settings > Optional features (restart the app to apply), or set the variable to 0, which wins over the setting. In jobniac-cli they stay off unless the variable is exactly 1. Deletion and link fetching change data or reach the network, so turn on only what you use. For MCP clients the Arbeitnow scan, link fetching and deletion are off until you turn on Let MCP clients scan Arbeitnow, Let MCP clients add a job from a link or Let MCP clients delete profiles and jobs in Settings (restart the app to apply). The in-app switches of the same features, and a variable set to 1 in the environment that starts the app, enable them for the app only and do not give MCP clients these tools. A variable set to anything other than 1 turns the feature off for the app and for MCP clients, and wins over the switch.

MCP client registration

JobniacFast includes an MCP server. The stdio mode is started by the MCP client:

{
  "mcpServers": {
    "jobniac": {
      "command": "C:\\Users\\<you>\\AppData\\Local\\JobniacFast\\jobniac-cli.exe",
      "args": ["mcp"],
      "env": {}
    }
  }
}

The full guide covers Claude Desktop and Claude Code, the loopback HTTP mode with its token, and how to check the registration: docs/ops/mcp-client-registration.md. The default tool list has 34 tools; the opt-in flags add tools (see that guide).

Command-line tool

jobniac-cli has these modes (exit code 0 for success, 1 for a failure with a fixed message, 2 for a usage error):

Development

Requirements: Rust (stable, or the version in rust-toolchain.toml), Node.js 22.12 or later, pnpm, and the Tauri prerequisites for your platform.

The PDFium library is not committed. Fetch the pinned, checksum-verified build into vendor/pdfium/ once before the first build (scripts/fetch-pdfium.ps1 -Platform windows-x64 on Windows); without it the desktop build fails with resource path `../vendor/pdfium/...` doesn't exist.

scripts/fetch-pdfium.sh linux-x64   # fetch the pinned PDFium library (Linux)
scripts/fetch-pdfium.sh mac-arm64   # fetch the pinned PDFium library (macOS, Apple Silicon; mac-x64 on Intel)
pnpm install --frozen-lockfile      # install the locked UI dependencies
pnpm tauri dev                      # run the desktop app
pnpm build                          # type-check and build the UI
pnpm tauri build                    # build a release bundle

On macOS the bundle config src-tauri/tauri.macos.conf.json names the Apple Silicon library (mac-arm64) only, and bundles it into Contents/Frameworks of the app, where the bundler signs it with the app (code in Contents/Resources is not signed as code). The default build is ad-hoc signed, with the entitlement in src-tauri/macos/Entitlements.adhoc.plist so that the hardened runtime loads that library; the release build uses a Developer ID when the repository secrets exist (see docs/ops/release-owner-checklist.md). Intel Macs are not supported: mac-x64 is only a fetch target.

Rust checks, from the repository root (the Cargo workspace is at the root). The PDF tests load PDFium from JOBNIAC_PDFIUM_DIR, so set it to the absolute path of vendor/pdfium/<platform> first:

export JOBNIAC_PDFIUM_DIR="$PWD/vendor/pdfium/mac-arm64"   # macOS, Apple Silicon (mac-x64 on Intel)
cargo fmt --all --check
cargo clippy --workspace --all-targets --locked -- -D warnings
cargo test --workspace --locked

See CONTRIBUTING.md for the workflow and the architecture rules.

Security

Report vulnerabilities privately, as described in SECURITY.md. Do not open a public issue for them.

License

JobniacFast is released under the MIT License. Third-party components keep their own licences. Each release ships the notices and a software bill of materials generated by the release process.

Links

• CHANGELOG.md: what changed in each version

• CONTRIBUTING.md and CODE_OF_CONDUCT.md

• docs/ops: clean-machine smoke checklist, MCP client registration, release owner checklist