Jobs_Applier_AI_Agent_AIHawk
AIHawk is a terminal job-search assistant that uses a resume to plan searches, shortlist postings and work through application forms in a visible browser. It is relevant to users who will review fit explanations and form contents rather than assume a job match or successful send. We tested package 1.0.0 at a fixed commit with Python 3.12.13. Selected modules ran against invented postings, synthetic CVs and temporary files. No personal information, real employer site, mailbox, browser engine or model gateway was used.
Eleven checks covered local Parquet search, SQLite persistence, resume text and scripted submission states. Keyword, location and exclusion filters worked on the five-row index, while old and unrelated jobs were excluded and duplicate company/title postings were merged. Text and a minimal DOCX were readable; content below fifty characters was refused. Rediscovering a job ID preserved its existing unconfirmed attempt state. CSV export retained uncertainty and wrote formula-like fields as text. These results concern deterministic filtering and record handling, not the accuracy of model-generated search plans or suitability scores.
Using a fake browser and preset gateway verdicts, the actual post-submit function distinguished submitted, unconfirmed and refused. A fake click error followed by verification failure remained unconfirmed, without a second fake click. This does not establish real-site success. The sending classifier depends on wording and treated Continue as a step even with a submit type, so it is not a strict authorization boundary. The documented live workflow sends CV and page content to a model gateway. Start with local search and records, then separately assess the chosen site, submitted content and data handling before using personal material.
Read the full review, verification scope and sources →Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-11-11
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 30
- Latest release
- jobs-20261108-084120 (2026-11-08)
- Open issues
- 2
- Recent issues with at least one comment
- —
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #1457 Power-user offer: real daily outreach volume, feedback, and a case study1 comments · 2026-10-20
- #1452 Apple ID 账号购买0 comments · 2026-10-14
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You want local shortlist and attempt records that can be inspected.
- You will review content and validate the actual target-site workflow.
- You need a proven automated application success rate.
- You require entirely local processing or a strict sending authorization boundary.
Compatibility
Quick start
Use cases
Alternatives
Comments
No comments yet. Be the first!