JobFlow and Browser Companion run on the user's Windows computer. Final Submit always remains a user action.
Get help
Report a reproducible problem in the public JobFlow issue tracker. If GitHub is temporarily unavailable, check GitHub Status and try again later.
Never include a resume, applicant name, address, phone number, email address, application answers, credentials, screenshots containing private data, or local file paths in a public issue.
Before reporting a problem
- Confirm that JobFlow is running and its local health check passes.
- Confirm that Browser Companion is enabled and updated to the version requested by JobFlow.
- Retry only from JobFlow. Do not retry a submission whose result is unknown.
- In the local JobFlow UI, find Privacy-safe incident history and support and download the redacted diagnostic JSON.
- Review the file, then attach it with the browser name, expected behavior, actual behavior, and the step that stopped.
The diagnostic file contains only versions, safe runtime states, aggregate counts, safety boundaries, and validated fixed error codes. JobFlow does not read private applicant values to build it and never sends it automatically.
Optional local incident history is off by default. If the user turns it on, JobFlow keeps at most 32 fixed error codes with version and time metadata. It never stores error messages, stack traces, URLs, local paths, applicant data, documents, credentials, or tokens. The history can be viewed in a downloaded diagnostic file or cleared at any time.
Safety boundaries
Browser Companion does not automate login, account creation, passwords, CAPTCHA, MFA, OTP, signatures, protected voluntary disclosures, or Final Submit. Unknown or changed pages stop safely.
Documentation
See the JobFlow README, quick start, and privacy policy.