llm-for-zotero vs paperjury
llm-for-zotero is much bigger: 2.9k stars against 1.1k. Over the days we have tracked them llm-for-zotero moved +56.2% and paperjury +31%, so llm-for-zotero is growing faster right now.
llm-for-zotero leads on privacy and model freedom. paperjury does not take any axis by a clear margin.
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
Deep Zotero-native integration that provides grounded, citation-linked paper chat and library-wide agent actions (reads, writes, tagging, notes) not offered by generic agents.
- Stars
- 2.9k
- Tracked growth
- +56.2%
- Maturity
- ●●●●●
- Last commit
- 1d ago
- Language
- TypeScript
- License
- AGPL-3.0
- Cost to run
- Your API key or local models
Bundles a bounded, audit-ready review→decide→patch→recheck loop with ledgered issues and edit-safety safeguards, exposed as a Claude Code skill.
- Stars
- 1.1k
- Tracked growth
- +31%
- Maturity
- ●●●●●
- Last commit
- 22d ago
- Language
- JavaScript
- License
- MIT
- Cost to run
- Runs in your Claude session — model usage billed by the provider
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 | llm-for-zotero | paperjury |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Whole-library access | ●●●●● Whole-repo analysis |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● Citation gating & confirmations | ●●●●● Severity gating & dedup |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Custom skills & settings | ●●●●● Modes & personas |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Local model support | ●●●●● Cloud LLM via session |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● Bring-your-own model/key | ●●●●● Claude-first (fixed) |
Setup ease What it takes to get a first useful run out of it. | ●●●●● Easy install + API key | ●●●●● Plugin install + session |
Which one to pick
Pick llm-for-zotero if…
Zotero-native — pick this when you want a research assistant tightly integrated with your local Zotero library for grounded citations, file-based notes, and library-wide agent workflows.
- Privacy: Local model support (5/5 against 3/5)
- Model freedom: Bring-your-own model/key (5/5 against 3/5)
Pick paperjury if…
Audit-ready review loop — pick PaperJury when you want a pre-submission, multi-round reviewer simulation that produces minimal, author-confirmed LaTeX patches and deterministic compile/compliance checks.
What people want from each one
yilewang/llm-for-zotero
u7079256/paperjury
Questions people ask
Is llm-for-zotero better than paperjury?
llm-for-zotero leads on privacy and model freedom. paperjury does not take any axis by a clear margin. llm-for-zotero is worth picking when zotero-native — pick this when you want a research assistant tightly integrated with your local Zotero library for grounded citations, file-based notes, and library-wide agent workflows.
Which of llm-for-zotero and paperjury keeps my code private?
llm-for-zotero: Local model support (5/5). paperjury: Cloud LLM via session (3/5).
What does each one cost to run?
llm-for-zotero: Your API key or local models. paperjury: Runs in your Claude session — model usage billed by the provider.
Full profiles: yilewang/llm-for-zotero and u7079256/paperjury. Everything else in Research agents.