goose vs ai-job-search
The two are close in size: 55.5k stars for goose, 63.2k for ai-job-search. Over the days we have tracked them goose moved +7.5% and ai-job-search +127.1%, so ai-job-search is growing faster right now.
They split the axes: goose leads on privacy and model freedom and setup ease, ai-job-search on context depth and noise control.
Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.
Where they stand today
A native, local-first agent with desktop app, CLI, and an extensible plugin ecosystem (Model Context Protocol) plus broad provider support.
- Stars
- 55.5k
- Tracked growth
- +7.5%
- Maturity
- ●●●●●
- Last commit
- 35m ago
- Language
- Rust
- License
- Apache-2.0
- Cost to run
- Your API key for cloud models; can use local models.
Local-first, end-to-end job-application framework that scrapes portals, tailors LaTeX CVs/cover letters, runs a drafter–reviewer agent pipeline, and archives applications for repeatable, owned job hunting.
- Stars
- 63.2k
- Tracked growth
- +127.1%
- Maturity
- ●●●●●
- Last commit
- 1d ago
- Language
- Python
- License
- MIT
- Cost to run
- Requires Claude Code (Anthropic) CLI / third‑party access.
Six axes, head to head
Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.
| Axis | goose | ai-job-search |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Diff/File only | ●●●●● Repo + documents |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● None mentioned | ●●●●● Reviewer + dedupe |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Extensions & distro | ●●●●● Templates & portals |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Self-hostable | ●●●●● Third-party cloud |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● BYO key & local | ●●●●● Claude + others |
Setup ease What it takes to get a first useful run out of it. | ●●●●● One-command install | ●●●●● CLI + deps |
Which one to pick
Pick goose if…
Privacy-first — run a native desktop/CLI agent locally while still using your preferred cloud or local models and many extensions.
- Privacy: Self-hostable (4/5 against 2/5)
- Model freedom: BYO key & local (5/5 against 3/5)
- Setup ease: One-command install (5/5 against 3/5)
Pick ai-job-search if…
Extensible end-to-end workflow — use it when you want a local CLI that orchestrates scraping, fit scoring, CV/cover-letter generation (LaTeX), and a reviewer agent to produce production-ready applications you control.
- Context depth: Repo + documents (4/5 against 1/5)
- Noise control: Reviewer + dedupe (4/5 against 1/5)
What people want from each one
aaif-goose/goose
Hacker News: Goose: An open-source, extensible AI agent that goes beyond code suggestions drew 249 points and 68 comments.
MadsLorentzen/ai-job-search
Questions people ask
Is goose better than ai-job-search?
They split the axes: goose leads on privacy and model freedom and setup ease, ai-job-search on context depth and noise control. goose is worth picking when privacy-first — run a native desktop/CLI agent locally while still using your preferred cloud or local models and many extensions.
Which of goose and ai-job-search keeps my code private?
goose: Self-hostable (4/5). ai-job-search: Third-party cloud (2/5).
What does each one cost to run?
goose: Your API key for cloud models; can use local models.. ai-job-search: Requires Claude Code (Anthropic) CLI / third‑party access..
Full profiles: aaif-goose/goose and MadsLorentzen/ai-job-search. Everything else in Personal assistants.