Skip to main content

Daily Paper Plugin

中文

Daily Paper selects three papers from the Hugging Face Papers weekly and monthly rankings, downloads their arXiv PDFs, and produces detailed Chinese reading notes plus a roughly five-minute Chinese brief. This directory is an independent Python distribution. Its single reme.plugins entry point exposes a plugin.yaml containing five Step backends and their Job configuration under application_defaults. Enable the installed plugin explicitly through plugins=["daily-paper"].

Quick start

1. Install ReMe and Daily Paper

python -m pip install "reme-ai[core]>=0.4.1.12"
reme plugins install plugins/daily_paper

2. Configure the model environment

Configure the LLM environment variables as described in the ReMe model-configuration guide. Other compatible models and providers can also be used. The workflow also requires network access to Hugging Face Papers and arXiv.

3. Start ReMe with the plugin

reme start plugins='["daily-paper"]'

With no explicit config, ReMe loads default.yaml and adds the plugin to that service. The plugin starts daily_paper_cron, which runs daily at 08:00. From another terminal, generate a brief manually through ReMe's CLI client:

reme daily_paper topics="Agent memory"

Or call its HTTP endpoint directly:

curl -s http://127.0.0.1:2333/daily_paper \
  -H 'Content-Type: application/json' \
  -d '{"topics":"Agent memory"}'

For scripts that need to run once without a persistent service, see One-shot Jobs. Normal usage follows the service startup and client invocation workflow above.

Custom application configs must provide agent_wrapper.default, a file_store.default with an enabled tag index, and the search, read, list_tags, frontmatter_read, and frontmatter_update Jobs used by Daily Paper and automatic tagging.

Pipeline

Hugging Face weekly/monthly rankings
                 ↓
merge ranks and exclude yesterday's and recently recommended papers
                 ↓
rank with RRF and let an Agent select three papers
                 ↓
download and parse arXiv PDFs, then write three Chinese analyses
                 ↓
use search + read to connect prior memory and generate a brief
                 ↓
generate memory tags; the background file watcher refreshes indexes

daily_paper_collect_step concurrently reads the weekly and monthly rankings for the run date plus the strictly preceding day's Daily Papers. It merges candidates by arXiv ID and excludes both yesterday's list and papers recommended within history_days.

daily_paper_rank_step combines weekly and monthly positions with reciprocal-rank fusion and retains at most candidate_limit papers. daily_paper_select_step then asks a tool-free Agent to select three unique candidate IDs. Non-empty topics affect selection preference but not the fixed count.

daily_paper_analyze_step downloads PDFs into resource/papers/, reuses existing valid files, and extracts text within the configured page, character, and file-size limits. It writes the three Chinese analyses in selection order. Scanned PDFs and files without a text layer fail explicitly.

daily_paper_digest_step treats those three analyses as the factual source and receives only the read-only search and read tools for linking earlier memory. Code validates historical wikilinks, appends links to all three source notes, and rebuilds the daily index. The workflow then runs auto_tag_step to update the memory-tag frontmatter of all three analyses and the final brief. The normal background file watcher observes those source-file changes and refreshes derived indexes.

Parameters

Parameter Default Purpose
date "" Empty uses today in the application timezone; otherwise use YYYY-MM-DD
force false Regenerate when that day's final brief already exists
use_hf_mirror false Use HF_MIRROR_URL, or https://hf-mirror.com when it is unset
topics "" Optional topics to prioritize during selection
weekly_weight 0.7 Weekly contribution in reciprocal-rank fusion
history_days 30 Prior recommendation window excluded by arXiv ID

Step-level defaults are candidate_limit=20, rrf_k=60, hf_timeout=600, hf_max_retries=3, pdf_timeout=600, max_pdf_bytes=52428800, max_pdf_pages=35, and max_pdf_chars=300000.

The data clients automatically honor HTTP_PROXY, HTTPS_PROXY, and NO_PROXY. Manual runs enable the Hugging Face mirror with use_hf_mirror=true; the cron Job enables it by default and can use the official service with DAILY_PAPER_USE_HF_MIRROR=false. These environment variables override the data sources:

HF_MIRROR_URL=https://hf-mirror.com
ARXIV_MIRROR_URL=https://export.arxiv.org

Output

.reme/
├── daily/
│   ├── YYYY-MM-DD.md
│   └── YYYY-MM-DD/
│       ├── <Chinese-paper-title>.md  # three, kind: daily-paper-analysis
│       └── <Chinese-brief-title>.md  # one, kind: daily-paper-brief
└── resource/papers/
    └── <arxiv-id>.pdf

Markdown and PDF files are written atomically through temporary files in the same directory. force=true regenerates the selected analyses and brief while reusing valid PDFs; it does not delete other notes already present for that day. Network errors, too few candidates, invalid Agent output, and unparseable PDFs fail explicitly.

Validation

python -m pytest plugins/daily_paper -v

Unit tests mock the Hugging Face, arXiv, and AgentScope boundaries and do not contact external services.

Metadata

Release files for reme-daily-paper 0.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for reme-daily-paper 0.1.3
File Size Uploaded Provenance Actions
reme_daily_paper-0.1.3.tar.gz 37.9 kB With provenance Details for reme_daily_paper-0.1.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for reme-daily-paper 0.1.3
File Interpreter ABI Platform Actions
reme_daily_paper-0.1.3-py3-none-any.whl Python 3 none any Details for reme_daily_paper-0.1.3-py3-none-any.whl

Total release size: 69.7 kB

Release files / reme_daily_paper-0.1.3.tar.gz

Download URL reme_daily_paper-0.1.3.tar.gz
Size 37.9 kB
Tags Source
SHA-256 checksum
How to use checksums
2eeb24a9653893a871bc9a32278797ffe96f2eeb1cfed505d4f5b1c9a8676972
BLAKE2b-256 checksum
How to use checksums
a36c1d5e82a55e5f806627cad488ae4c308f54f34dd160b6c823b734645fd534
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.

Transparency log

Release files / reme_daily_paper-0.1.3-py3-none-any.whl

Download URL reme_daily_paper-0.1.3-py3-none-any.whl
Size 31.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e1237babefcf421ef224da04d986e23cbbcc1eb350ef0e5f1ce19ae59152516a
BLAKE2b-256 checksum
How to use checksums
dfb574ba8c7939190279b1db0ba72a98f481f4138f037bbc3f295931f1d610ee
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.

Transparency log

Security for reme-daily-paper 0.1.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for reme_daily_paper-0.1.3.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page