paperweight is an arXiv triage CLI. It fetches recent papers, filters them against your research interests, and produces a ranked digest — optionally with LLM-powered summarization — that you can read in minutes.
Checking arXiv directly is great for discovery. paperweight is for a different job:
- keep your daily list short
- rank by your interests
- make output scriptable (
stdout,json,atom) - run the same way every day
arXiv API → metadata fetch → AI triage → keyword scoring → (optional) LLM summary → deliver
- Fetch — pull recent papers from configured arXiv categories.
- Triage — an LLM shortlists papers by title and abstract (or pass all through with heuristic fallback when no key is set).
- Score — keyword matching against titles and abstracts produces a relevance score.
- Summarize — in
abstractmode (default) the abstract is passed through as-is; insummarymode an LLM generates a concise summary from the full paper. - Deliver — output as plain text, JSON, Atom feed, or email.
pip install academic-paperweightFrom source (requires uv):
git clone https://github.com/seanbrar/paperweight.git
cd paperweight
uv sync --all-extras
source .venv/bin/activatepaperweight init # create config.yaml with safe defaults
paperweight doctor # check your setup for issues
paperweight run # fetch papers and produce a digestThe first run automatically backfills a week of papers. After that, the same
paperweight run fetches only what's new. Use --force-refresh to re-fetch
if you've already run today.
Notes:
- Default analyzer mode is
abstract(no API key required). - Triage runs with heuristic fallback if no LLM key is present.
Running paperweight with the default config prints a plain-text digest to stdout:
paperweight digest
1. CoPE-VideoLM: Codec Primitives For Efficient Video Language Models
Authors: Sayan Deb Sarkar, Rémi Pautrat, Ondrej Miksik +4 more
Date: 2026-02-13
Score: 6.24
Matched: language model, reasoning, transformer
Link: http://arxiv.org/abs/2602.13191v1
Summary: Video Language Models (VideoLMs) empower AI systems to understand
temporal dynamics in videos. To fit to the maximum context window constraint,
current methods use keyframe sampling which can miss both macro-level events
and micro-level details ...
2. In-Context Autonomous Network Incident Response: ...
Authors: Yiran Gao, Kim Hammar, Tao Li
Date: 2026-02-13
Score: 6.24
Matched: language model, reasoning
Link: http://arxiv.org/abs/2602.13156v1
Summary: Rapidly evolving cyberattacks demand incident response systems ...
Pipe to JSON for scripting, or deliver as an Atom feed or email — see CLI below.
paperweight [run-options]
paperweight run [run-options]
paperweight init [--config PATH] [--force]
paperweight doctor [--config PATH] [--strict]Examples:
# default plain-text digest to stdout
paperweight
# JSON output for scripts
paperweight run --delivery json --output ./paperweight.json
# Atom feed output
paperweight run --delivery atom --output ./paperweight.xml
# optional email delivery (requires notifier.email config)
paperweight run --delivery email
# cap processing to 20 papers (output may be fewer after filtering)
paperweight run --max-items 20
# strict checks for CI/release gates
paperweight doctor --strict
# activate a named profile
paperweight run --profile fastFull command reference: docs/CLI.md
paperweight init generates a config.yaml with all required sections. Core sections:
| Section | Purpose |
|---|---|
arxiv |
arXiv categories to watch and max results per fetch |
triage |
LLM-powered shortlisting on title + abstract (opt-in, requires API key) |
processor |
Keyword lists and scoring weights for relevance ranking |
analyzer |
abstract (default, no key) or summary (LLM-generated) |
concurrency |
Thread/worker limits for fetching, triage, and summarization |
feed |
Metadata for --delivery atom output |
metadata_cache |
Avoids repeated arXiv API calls within a TTL window |
profiles |
Named config overlays activated with --profile NAME |
logging |
Log level and optional log file path |
notifier |
SMTP settings for --delivery email |
db |
Optional Postgres persistence for runs and results |
storage |
Base directory for artifact storage |
Full reference: docs/CONFIGURATION.md
API keys and passwords can be supplied via:
- a
.envfile in the project root (OPENAI_API_KEY,GEMINI_API_KEY, etc.) ${VAR}interpolation inconfig.yaml(e.g.,password: ${EMAIL_PASSWORD})PAPERWEIGHT_prefixed env vars to override any config value
See docs/ENVIRONMENT_VARIABLES.md for details.
See docs/ROADMAP.md for quantified release goals and forward plan.
make lint # ruff check
make typecheck # mypy
make test # pytest with coverage
make format # auto-format with ruff
make all # lint + typecheck + testSee docs/CONTRIBUTING.md for the full contributing guide.