Known issues & roadmap

Bugs, fixes, and what's coming.

Found a bug or have feedback? Please email [email protected].

Known issues (closed beta)

IssueStatusWorkaround
Table-based or scanned CVs could produce an incomplete or empty profile fixed Fixed in v0.3.2. Table and column CVs (e.g. a tabellarischer Lebenslauf) now parse in full, and scanned/image PDFs are detected up front instead of silently seeding an empty profile. Update to the latest build — what's new.
Where's the desktop shortcut? known It's there, but there's no icon yet, so FOX3 looks like a blank file. A proper icon lands with the desktop app.
PDF CVs with side-column dates can still parse out of order known Prefer a .docx, .txt, or .md CV for the cleanest profile — table and column layouts in those now parse fully (v0.3.2). FOX3 warns when you attach a PDF and always shows you what it parsed, so you can correct it. Layout-aware PDF parsing is on the list.
Settings changes don't show known Restart the app after saving changes makes the new settings visible. Patch is coming.
Unsigned build → Windows SmartScreen / macOS "unidentified developer" warning fix planned Windows: More info → Run anyway. macOS: System Settings → Privacy & Security → Open Anyway (or run xattr -d com.apple.quarantine <file> in Terminal). A notarized macOS build is coming to remove the macOS warning; on Windows, SmartScreen stays until there's a bundled app to sign.
The "update available" notice in the control panel is easy to miss. fix planned Look for a yellow "Update available: …" line at the bottom of the Status panel (under "Run due now"). The update check itself works correctly. A more prominent banner is coming.
Tuning your digest (good/bad feedback) still needs a command-line step fix planned Run fox3 feedback to rate listings — now a proper branded command. An in-app feedback surface, to rate right from the dashboard, is on the way.
The control panel can briefly hang if force-closed during a live run investigating Not harmful. Your data and any already-scored listings are safe, and a stopped run resumes cleanly on your next run.
Company-pages / priority-employer field shows but is "in development" investigating Naming a priority employer still boosts its listings in scoring; dedicated company-page scraping is not built yet.
Multi-line CV/answer paste in the console interview can mis-split lines (Windows) mitigated Use /paste mode (end with a single .) — it always works; every turn is checkpointed so nothing is lost.
Very relaxed search constraints can hit the run budget cap before deep research by design Expected: a huge result set is fully scored, then deep research is skipped to protect cost. Tighten the region/keywords to go deeper. I'm exploring better and more efficient algorithms.

When an issue is fixed it's tagged fixed here for one release, then retired to the version history once the next build ships.

Roadmap

Just shipped in v0.3.2: more reliable CV & document parsing and cross-platform command hints. See what's new; earlier updates are in the version history.

In development

Planned

Investigating

Not planned