Paperful documentation¶
New here? paperful.app, then Walkthroughs. Four ways to wire it up: Example setups. Search order: How it works.
Paperful is a local workbench for a Zotero library you already keep. Open access first; campus EZProxy when you have it. Zotero is well tested. Mendeley and EndNote are seeking testers. You keep a folder copy on this machine and attach the PDFs you trust. Terms.
Clone the repo, then docker compose build and docker compose up →
http://127.0.0.1:8765 (GUI).
Docker (light / heavy packs). CLI: docker compose run --rm paperful ….
Host CLI without Docker: pipx install paperful (or uv tool install /
pip install); campus login and HTML PDF need paperful[browser]
(releases). Fetch stance:
legal and privacy.
Contributors: uv. Stability: releases.
Why this shape: Why Paperful.
Start here
- How it works
- Walkthroughs
- Example setups
- First fill: missing PDFs onto disk
- Grow the library: topic search and people you follow
- Tidy a collection: lint, identifiers, duplicates
- Paperful workbench
- Why Paperful
- Docker
- Zotero
- Commands
- Firefox add-on
- Workflows
- Do not conflate
- 1. The shell sequence
- 2. Same chain, one process
- 3. Save the slice
- Precedence
- Docker
- 4. Deep collection pass (example template)
- 5. Research pack (cited works → parents → PDFs)
- 6. Field author packs (corpus frequency → author_site)
- 7. Reachout (ask authors, do not fetch)
- 8. All-in E2E (NBA throwaway)
- What this is not
- Research pack playbook
- Dedupe
- Configuration (
config.toml) - Paperful architecture
- Mirror first
- Data flow
- Disk artifacts
- Library adapter
- LLM layer (optional, local-first)
- Identifiers and lint
- PDF text
- Circuit breaker
- Sci-Hub and presets
- Disk mirror vs cloud quota
- Ghost attachments
- Operator tooling
- Report JSON (
paperful.run_report.v1) - Run packs (
paperful.pack.v1) - Run configs
- Grey literature
- Related docs
- Developer guide
- Quiet mirror (
out/) - Paperful terms
- Releases and stability
Using paperful
- Mendeley
- EndNote
- Adapter SDK
- Source routing and circuit breaker
- Screen for problematic papers (PPS-based)
- Systematic review
- Critique (local manuscript pack)
- What it checks
- CLI
- Input formats
- Review lanes (
--lane/[critique].lanes) - Optional reviewers (
--lane reviewers/--llm) - Optional adversary (
--lane adversary) - Optional outline (
--lane outline) - Optional claims (
--lane claims) - Optional verify (
--lane verify) - Optional MARG-S (
--lane marg/--advanced) - Optional context (
--lane context/--lane context-web) - Optional AI-text extra (
--ai-model/[critique].ai_model) - House glossary (
state/glossary/) - Optional Vale (
--vale/[critique].vale) - Optional forensics (
--forensics/[critique].forensics) - Workbench
- Config
- Rewrite (apply a critique pack)
- Stuff (extra citations from the library)
- Campus EZProxy
- Research operators
- Browser sessions (Scholar, EZProxy, publishers)
- Sci-Hub
- Legal, fetch stance, and privacy
- SerpApi (Google Scholar search)
- Camofox recover lane
- GROBID sidecar
- AI for notes and Ask: what is feasible
- Optional LLM: setup and verbs
- Ask your library:
ragandask - Browser agent: local models (Ollama + browser-use)