CLI Reference

DailyInfo command-line interface built on click + uv.

Installation

Using uv (recommended)

git clone <repo-url>
cd dailyinfo

cp .env.example .env
# edit .env with your API keys

uv sync --python python3
uv pip install -e .

NotebookLM automation is optional. Install it only on machines where you want dailyinfo zotero-brief to talk to NotebookLM directly:

uv pip install -e ".[notebooklm]"

Using pip (fallback)

pip install -e .

Environment Setup

dailyinfo install

This command:

Validates .env �?DEEPSEEK_API_KEY and DISCORD_BOT_TOKEN must be non-empty and not a placeholder.
Creates the workspace under ~/.myagentdata/dailyinfo/ (freshrss/data, briefings/*, pushed/*).
Installs Python dependencies via uv sync (falls back to pip install -e .).

It does NOT write to the host crontab. Scheduling is expected to be driven by any external cron-like trigger (system crontab, systemd timer, container scheduler, or an agent runtime such as myopenclaw's hermes cron �?see Agent Config).

Commands

Service Management

dailyinfo start      # Start FreshRSS (Docker)
dailyinfo stop       # Stop services
dailyinfo restart    # Restart FreshRSS

Pipeline Execution

dailyinfo run                      # Run all 5 pipelines
dailyinfo run -p 1                 # Pipeline 1 (papers)
dailyinfo run -p 2                 # Pipeline 2 (AI news)
dailyinfo run -p 3                 # Pipeline 3 (arXiv CS.AI)
dailyinfo run -p 4                 # Pipeline 4 (code trending)
dailyinfo run -p 5                 # Pipeline 5 (university news)
dailyinfo run -f all               # Force regenerate every source today
dailyinfo run -p 1 -f arxiv_cs_ai  # Force regenerate one source only

dailyinfo run is idempotent: if a non-placeholder briefing already exists for today (either in briefings/ waiting to be pushed, or already archived in pushed/), the source is skipped and no AI call is made. Use -f / --force to override �?pass all to refresh everything, or repeat the flag with specific source names (matches config/sources.json).

If the primary model (deepseek-v4-pro via DeepSeek API) returns empty responses after 3 retries with exponential backoff (2s / 5s / 10s), run automatically falls back to the model in DAILYINFO_FALLBACK_MODEL (default moonshotai/kimi-k2.5 via OpenRouter) for 2 more attempts before giving up.

Push to Discord

dailyinfo push                       # Push today's briefings (all categories)
dailyinfo push -d 2026-04-22         # Backfill a specific day (YYYY-MM-DD)
dailyinfo push -c papers,ai_news     # Push only selected categories
dailyinfo push -c weekly             # Push weekly recap only (noon cron)

Scans files under ~/.myagentdata/dailyinfo/briefings/{category}/ whose name contains the target date, posts to the mapped Discord channel, and moves successfully pushed files to pushed/{category}/. push is idempotent: a day with no pending files just emits a "暂无新简�? notice and exits cleanly.

Zotero -> NotebookLM Briefing

This CLI is the capability layer for Codex/openclaw orchestration. For daily interactive use, load skills/zotero-notebooklm and let Codex run these checks, handle NotebookLM auth handoff, trigger Zotero PDF hydration, inspect notebooklm.json, and continue through manual fallback steps when needed. For new-machine setup and agent handoff details, see docs/zotero-notebooklm.md or docs/zotero-notebooklm.zh.md.

dailyinfo zotero-brief                         # Process today's Zotero additions
dailyinfo zotero-brief --date 2026-05-27       # Process one Zotero dateAdded day
dailyinfo zotero-brief --collection water      # Restrict to a Zotero collection
dailyinfo zotero-brief --force                 # Overwrite existing local output
dailyinfo zotero-brief --artifact audio        # Also request Audio Overview
dailyinfo zotero-brief --artifact video        # Also request Video Overview
dailyinfo zotero-brief --artifact both         # Request both artifacts
dailyinfo zotero-brief --open-missing-pdfs     # Open cloud-only Zotero attachments, wait, retry copy
dailyinfo zotero-brief --manual-only           # Prepare local materials only

This command is separate from dailyinfo run: it does not call OpenRouter or the DailyInfo call_ai helper. It reads the local Zotero API at http://127.0.0.1:23119, filters top-level papers by dateAdded, copies local PDF attachments when available, writes source_index.md, and lets NotebookLM generate the Chinese markdown briefing from the uploaded sources. For cloud-only PDF paths such as Google Drive placeholders, --open-missing-pdfs opens the Zotero attachment URI first, then falls back to the local file path if needed, and waits before retrying the copy. This is intended to trigger Zotero and the user's sync client to hydrate the file.

NotebookLM auth is intentionally allowed to be manual. First run:

uv run --extra notebooklm notebooklm login

Then run:

uv run --extra notebooklm dailyinfo zotero-brief --collection water --artifact audio --open-missing-pdfs

If the default NotebookLM profile directory is not writable, set NOTEBOOKLM_HOME or pass --notebooklm-home <dir> and use the same directory for both notebooklm login and dailyinfo zotero-brief.

Output is written to ~/.myagentdata/dailyinfo/zotero/YYYY-MM-DD/:

File	Purpose
`source_index.md`	Lightweight paper metadata and Chinese reading instructions uploaded to NotebookLM
`briefing_prompt.md`	Prompt to paste into NotebookLM chat when completing the run manually
`pdfs/`	Copied Zotero PDF attachments
`briefing.md`	NotebookLM-generated Chinese briefing, or a placeholder when manual action is required
`notebooklm.json`	Notebook/source/artifact ids, copied PDF status, warnings, and failures
`audio_overview.mp3`	Present only when Audio Overview downloads successfully
`video_overview.mp4`	Present only when Video Overview downloads successfully
`MANUAL_NOTEBOOKLM_STEPS.md`	Browser fallback steps for auth, upload, generation, and download

notebooklm-py is a non-official NotebookLM interface intended for personal automation. If Google changes the NotebookLM UI/API or auth is not ready, the command degrades to the local material package so the run can be completed manually in the NotebookLM web UI.

Download PDF (institutional access)

Requires Claude Code + Playwright MCP plugin. The CLI is a thin helper — real browser orchestration happens through the agent skill. See PDF Download for full setup, supported publishers, and failure handling.

dailyinfo download-pdf <doi|pii|url>           # Print download instructions for the skill
python scripts/download_pdf.py detect <url>    # Detect publisher from URL
python scripts/download_pdf.py verify <pdf>    # Verify PDF and extract metadata
python scripts/download_pdf.py doi <doi>       # Resolve DOI to article URL + publisher

Sync PDF to Zotero (linked_file)

Creates a Zotero item with a linked_file attachment. See Zotero Sync for prerequisites, setup, and design rationale.

uv run python scripts/zotero_sync.py <pdf> <doi> --json       # Copy to GDrive + create Zotero item
uv run python scripts/zotero_sync.py <pdf> <doi> --dry-run    # Preview only

Design rationale: uses pyzotero Web API with linked_file attachment (attachments:<filename> scheme) rather than imported_file, because Zotero's 300 MB cloud quota is too small for institutional PDFs (10-90 MB each). See ADR-001.

Weekly Recap

dailyinfo weekly                # 汇总过�?7 天的 AI 新闻
dailyinfo weekly --days 14      # 自定义回溯窗�?
dailyinfo weekly --force        # 覆盖今天已生成的 recap

Status & Logs

dailyinfo status    # Counts of today's briefings / pushed files
dailyinfo logs      # Tail logs/dailyinfo.log (if enabled)

Environment Variables

Create .env in the project root:

DEEPSEEK_API_KEY=sk-your_deepseek_key_here
DISCORD_BOT_TOKEN=your_discord_token
FRESHRSS_USER=owen
FRESHRSS_PASSWORD=freshrss123
# DAILYINFO_DATA_ROOT=   # optional override, defaults to ~/.myagentdata/dailyinfo

Key	Purpose
`DEEPSEEK_API_KEY`	DeepSeek API key (required — primary model: `deepseek-v4-pro`)
`OPENROUTER_API_KEY`	OpenRouter API key (optional, only needed for fallback)
`DISCORD_BOT_TOKEN`	Discord bot token used by `dailyinfo push`
`DISCORD_CHANNEL_PAPERS` / `_AI_NEWS` / `_CODE` / `_RESOURCE` / `_ARXIV`	Per-category channel IDs (missing ones are skipped, not fatal)
`DISCORD_CHANNEL_*_DEV` / `_STAGING`	Env-specific channel IDs when `DAILYINFO_ENV=dev` or `staging`
`DAILYINFO_ENV`	Environment: `prod` / `dev` / `staging` (default `prod`) — controls data dir and channel suffix
`DAILYINFO_DATA_ROOT`	Override data root (default `~/.myagentdata/dailyinfo`; env-suffixed for dev/staging)
`FRESHRSS_USER`	FreshRSS username (default: `$USER`)
`FRESHRSS_PASSWORD`	FreshRSS password
`DAILYINFO_FALLBACK_MODEL`	Fallback LLM when the primary model returns empty (default `moonshotai/kimi-k2.5`)
`ZOTERO_LOCAL_BASE_URL`	Zotero local API base URL for `zotero-brief` (default `http://127.0.0.1:23119`)
`ZOTERO_API_KEY`	Zotero Web API key for `zotero_sync.py` linked_file import (create at https://www.zotero.org/settings/keys)
`ZOTERO_LIBRARY_ID`	Numeric Zotero user library ID for `zotero_sync.py`
`GDRIVE_PAPERS_PATH`	Local path to Google Drive papers folder (ZotMoov target, same as Zotero's Linked Attachment Base Directory)
`NOTEBOOKLM_HOME`	NotebookLM profile/auth directory used by `notebooklm-py`; must match the login run

Scheduling

dailyinfo 提供幂等�?CLI 命令，由任意外部 cron 触发即可。推荐时刻表�?

Command	Scheduled time	Purpose
`dailyinfo run -p 3`	03:00	arXiv CS.AI
`dailyinfo run -p 5`	03:30	university news
`dailyinfo run -p 4`	03:45	code trending
`dailyinfo run -p 1`	04:00	papers
`dailyinfo run -p 2`	04:30	AI news
`dailyinfo push`	05:30-07:00	push to Discord

系统 crontab 示例�?

0 3 * * * cd /path/to/dailyinfo && python3 scripts/run_pipelines.py --pipeline 3 >> logs/pipeline3.log 2>&1
30 3 * * * cd /path/to/dailyinfo && python3 scripts/run_pipelines.py --pipeline 5 >> logs/pipeline5.log 2>&1
45 3 * * * cd /path/to/dailyinfo && python3 scripts/run_pipelines.py --pipeline 4 >> logs/pipeline4.log 2>&1
0 4 * * * cd /path/to/dailyinfo && python3 scripts/run_pipelines.py --pipeline 1 >> logs/pipeline1.log 2>&1
30 4 * * * cd /path/to/dailyinfo && python3 scripts/run_pipelines.py --pipeline 2 >> logs/pipeline2.log 2>&1
30 5 * * * cd /path/to/dailyinfo && python3 scripts/push_to_discord.py --categories ai_news,code,resource >> logs/discord_push.log 2>&1
0 6 * * * cd /path/to/dailyinfo && python3 scripts/push_to_discord.py --categories papers >> logs/discord_push.log 2>&1
0 7 * * * cd /path/to/dailyinfo && python3 scripts/push_to_discord.py --categories arxiv >> logs/discord_push.log 2>&1

如果你也在用 myopenclaw �?agent 生态来统一管理这些 cron，可以参�?Agent Config�?

Docker Services

Only FreshRSS runs in Docker:

docker compose up -d freshrss          # Start
docker compose down                    # Stop
docker compose logs -f freshrss        # Logs
# Web UI: http://localhost:8081

FreshRSS data is persisted at ~/.myagentdata/dailyinfo/freshrss/data/.