Your personal AI morning briefing. arXiv papers, Hacker News stories, GitHub trends, weather, and optional extras are collected overnight, summarised for you, and published as your own searchable digest site.
After you create your own repo from this template, start with the setup wizard. It is now the main sign-in, GitHub authorization, and deployment entry point: choose the briefing shape you want, add your LLM key, and let Linnet prepare the repo handoff. The current self-hosted path uses GitHub Actions and Pages behind the scenes; you do not need to run a server or accept dashboard lock-in.
English demo · 中文示例 · Start setup in English · 用中文进入设置向导 · Manual config guide
Start here after creating your repo The setup page is now the main sign-in, GitHub authorization, and deployment flow for new users.
English UI: https://yuyangxueed.github.io/Linnet/setup/
中文界面: https://yuyangxueed.github.io/Linnet/setup/zh/
After the first deploy, Linnet tries to set the repo's About -> Website field to your GitHub Pages URL. If GitHub permissions block that optional step, paste the Pages URL there manually.
Linnet acts like a small AI secretary for your morning routine. It checks the sources you care about, filters the noise with an LLM, and leaves you with a polished briefing before the workday starts.
| Source | What it gives you |
|---|---|
| arXiv | New papers matching your keywords, with AI summaries |
| Hacker News | High-signal AI/ML stories above your score threshold |
| GitHub Trending | Trending repos in your area |
| Weather | Today's forecast for your city |
Optional sources such as postdoc jobs and supervisor-page monitoring live behind the extension system, but most users do not need them on day one.
The setup wizard also exposes language-specific tagline extensions:
hitokotofor Chinese briefings, no key requiredquote_of_dayfor English briefings, requiresAPI_NINJAS_KEY
Linnet keeps the generated daily, weekly, and monthly archives in your published site, so the briefing stays searchable instead of disappearing into another feed.
Use Use this template → Create a new repository on GitHub.
If you are just setting up your own briefing site, prefer Use this template over Fork. Forks still work, but they are more likely to hit extra GitHub friction around Actions and setup.
Open the repo you just created, then install the Linnet Bridge GitHub App to that target repository.
This is the lower-friction path. It lets Linnet write files, GitHub Actions secrets, workflow settings, and GitHub Pages config for you without asking you to mint a PAT.
This is the main sign-in, authorization, and deployment entry point after you create your repo:
- English UI: https://yuyangxueed.github.io/Linnet/setup/
- Chinese UI: https://yuyangxueed.github.io/Linnet/setup/zh/
You no longer need to deploy your own copy of /setup/ first just to get started.
At the top of the wizard:
- click Install GitHub App if you have not already installed it
- click Authorize GitHub so this browser can finish the setup flow
Then continue through the normal steps:
- briefing mode, source selection, and source detail tuning in Steps 1-2
- optional extra secrets and delivery channels in Step 3
- LLM provider, API key, model choices, and theme controls in Step 4
In Step 5, choose your target repository and click Deploy to GitHub.
The default one-click path uses the Linnet Bridge GitHub App flow, not a PAT. Behind the scenes, a successful deploy will:
- write the generated config files in a single commit
- create or update the needed GitHub Actions secrets
- enable
daily.yml,weekly.yml,monthly.yml, andpages.yml - configure GitHub Pages for workflow-based publishing
- set the repository About -> Website link to your Pages URL when permissions allow it
- trigger the first
Daily Digestrun
Most users should not need to click anything else after Step 5. Watch these two workflows in your repo:
- Daily Digest — generates the first issue and commits the published data
- Deploy Astro Site to GitHub Pages — builds the site and publishes it
Your site should go live at https://<your-username>.github.io/<repo-name>/ a few minutes later.
Linnet will also try to put that URL in the repository's About -> Website field. If the About link still points to the template repo after setup, replace it with your Pages URL manually so the site entrance is easy to find from the GitHub repo header.
GitHub Pages provisioning can lag slightly behind the API call on a brand-new repo, so give it a short moment before assuming it failed. If repo or org policy blocks app installation, Actions, or Pages, fall back to the manual config guide.
The repo stays simple if you remember four things:
enabled: true/falseturns each source or sink on and off.display_ordercontrols the section order in the final digest.llm.provider,llm.base_url,llm.api_key_env, and the two model IDs define how LLM calls are made.- Detailed per-source settings live in
config/extensions/<name>.yaml.
Minimal example:
display_order:
- weather
- arxiv
- github_trending
- hacker_news
weather:
enabled: true
arxiv:
enabled: true
github_trending:
enabled: true
hacker_news:
enabled: true
language: "en"
llm:
provider: "openrouter"
scoring_model: "google/gemini-2.5-flash-lite-preview-09-2025"
summarization_model: "google/gemini-2.5-flash-lite-preview-09-2025"
base_url: "https://openrouter.ai/api/v1"
api_key_env: "OPENROUTER_API_KEY"If you want to hand-edit everything, start from dev_docs/manual-config.md.
- Built-in source plugins live in
extensions/ - Shared conventions live in
extensions/README.md - New extensions can start from
extensions/_template/
- The website is the default output
- Optional delivery channels live in
sinks/ - Shared sink conventions live in
sinks/README.md - Secrets stay in GitHub Secrets or environment variables, not committed YAML
Example:
sinks:
slack:
enabled: true
max_papers: 5
max_hn: 3
max_github: 3GitHub Actions cron uses UTC. The default daily run is 09:30 UTC on weekdays so the US stock signal board runs after New York has rolled into the trading day. Edit those cron lines directly in your repo if you want different times.
python -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt
export OPENROUTER_API_KEY=sk-or-... # or another env name that matches llm.api_key_env
python main.py --mode daily
python main.py --dry-run
python main.py --mode weekly
python main.py --mode monthlyRun tests:
PYTHONPATH=. pytest tests/ -qThis repo is friendly to both human contributors and AI coding agents.
If you are modifying repo code or docs, start with:
If you are mostly helping someone configure their own repo or digest site, start with:
Suggested prompt for agents:
Please read llms.txt, extensions/llms.txt, sinks/llms.txt, and the relevant SKILL.md under skills/ before making changes or suggesting configuration edits.
If you build an interesting setup, please share it in Discussions.
For implementation problems, config help, extension ideas, or sink requests, use the repo's issue templates.
If this repo saves you time, helps you track your field, or gives you a strong starting point for your own briefing workflow, you can support it here:
Support is optional. Contributions, fixes, ideas, and new integrations are just as valuable.
The public site is built with Astro, which makes the GitHub Pages flow pleasantly simple.
This project also benefited from many open-source repositories, maintainers, and examples. If you notice a project that should be credited more explicitly, open an issue or PR and I will gladly add it.
MIT — see LICENSE. Contributions welcome.
