Horizon routes every item through exactly one profile
Project brief: Your own AI-powered news radar. Generates daily briefings in English & Chinese. | AI .
At a glance
- What is it?
- Horizon collects news from RSS, Hacker News, Reddit, Telegram, X, GitHub and financial feeds, scores and deduplicates it, then writes a bilingual briefing whose shape is decided by editorial profiles you can adapt. The routing is single-profile per item, the profile files are not where your thresholds live, and the twitter extra needs a browser the Dockerfile never installs.
- Who is it for?
- Horizon suits someone who already follows a wide set of feeds and wants one digest shaped by their own criteria rather than a generic newsletter, and who is willing to write or adapt a profile file to get there.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- Thysrael/Horizon14,428 ★ · +5,864
| Repository | 2026-07-31 | 2026-11-15 |
|---|---|---|
| Thysrael/Horizon | 8.6k | 14.4k |
5,864 Stars in the last 107 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Each item routes to one profile, so a two-category story loses half
A profile is a reusable set of editorial rules covering what belongs, what is worth keeping, and what to write, and the built-in examples differ sharply in what they produce. `tech-news` gives events and context with impact and community discussion when useful, `tech-blog` gives background, solution and practical takeaways, and `ai-creator` gives a summary with timely hooks and content angles. The constraint that shapes everything else is that each item routes to one profile. Analysis, filtering and deduplication happen before enrichment, and the selected items then become a briefing grouped by profile. The consequence for a reader is that a piece of writing that is both a breaking event and a usable engineering deep dive gets one profile's treatment.
Profile files hold editorial rules, and your thresholds belong somewhere else
The routing key lives on the source: the README says to assign a profile to a source, or let AI choose. Underneath that sits a split: the README says profiles define the treatment while runtime settings reflect your reading preferences, and the minimal configuration puts score thresholds and topic deduplication in `processing.profile_settings`. That split is also why adapting a profile is described as usually not requiring Python, while your own reading preferences stay in JSON you generated from a wizard.
threshold and topic_dedup are the only dials between you and the digest
The minimal configuration shows the whole surface of those preferences: a `profiles_dir` of `"profiles"`, a `default_profile` of `"tech-news"`, and a `profile_settings` entry setting `threshold` to 7.0 alongside a topic deduplication option. Alongside per-profile thresholds, the feature set offers a length cap on the final digest and a cap on each category's share, so one busy topic cannot crowd out the rest. The consequence is that tuning is coarse. Scores come out of the model rather than from a rule you wrote, so a threshold is a cut on a number you do not see or control directly. Two profiles at the same threshold can behave very differently for reasons the configuration cannot express.
The twitter extra needs a Playwright browser the Dockerfile does not install
Full-text extraction with `trafilatura` is in the base install, so article bodies arrive without extra setup. The `twitter` extra is a different matter. It pulls `playwright>=1.40.0` and `playwright-stealth>=1.0.0`, and it also requires a Playwright browser and system packages, which the current Dockerfile does not install. The consequence is that a container build is not enough: the extra provides the Python packages, while the browser and system packages are not installed by the Dockerfile. Installing the browser and its system libraries is left to you, and the repository's own `.env` template asks for an `APIFY_TOKEN` with the note that it is required for Twitter scraping, obtained from the Apify console.
openbb is an extra, and its wheel problem has a documented manual workaround
The financial source is optional and gated behind its own extra:
uv sync --extra openbbWhen that fails because `openbb` pulls packages without wheels on your machine, the documented workaround installs the SDK manually with binaries only:
uv pip install --only-binary=:all: openbb openbb-benzingaThe consequence is a two-step install that a plain `uv sync` will not reproduce. Forcing binary-only resolution is what makes the install possible at all on a machine with no toolchain, and it is also what will make it fail if any dependency in the tree publishes only a source distribution.
restart is set to no, so the container never schedules itself
The compose file mounts `./data` and a read-only `./.env`, sets `TZ=UTC`, and leaves a comment about running daily at 8:00 AM UTC that explicitly says to adjust as needed. The service itself carries `restart: "no"` and `command: ["--hours", "24"]`, with a separate note that a one-time run uses `docker compose run --rm horizon`. The consequence is that scheduling is yours to provide. A container that runs the pipeline once and exits will not wake itself, so a digest that quietly stops updating looks identical to a digest with no interesting news, and the failure surfaces only when you notice the date on the last briefing. The image itself is built to be unprivileged, creating a user with uid 10001 and mounting `/app/data` as a volume, so state survives the container but the schedule does not.
GitHub rate limits and the Apify token decide what you can actually see
The environment template separates credentials by what they buy you. `GITHUB_TOKEN` is optional but recommended for higher rate limits, and the numbers are stated: 60 requests per hour without a token, 5000 with one. `APIFY_TOKEN` is marked required for Twitter scraping. On the model side, the template offers keys for eight providers, and the configuration names `provider`, `model` and `api_key_env` as three separate values rather than one hardcoded vendor, with `gpt-4` over `OPENAI_API_KEY` in the example. The consequence is that the AI backend is genuinely swappable while the data sources are not equally free: GitHub degrades to an hourly request budget without a token, and the X source needs an Apify token.
Five console entry points, a 0.1.0 version, and no releases to pin
Installing the project gives you six commands rather than one: `horizon` maps to the main entry point, `horizon-mcp` exposes the pipeline stages so an AI assistant can call them, `horizon-wizard` runs the interactive setup that writes `data/config.json`, `horizon-chatgpt` is a further setup entry point, and `horizon-webhook` and `horizon-wechat` are the delivery entry points. A local install is either of two shapes:
git clone https://github.com/Thysrael/Horizon.git
cd Horizon
# Install with uv (recommended)
uv sync
# Install test/development extras when needed
uv sync --extra dev
# Or with pip
pip install -e .The declared version is 0.1.0 and the repository has no GitHub releases, so there is no published artifact to pin a deployment to and no changelog to diff. The build backend is hatchling, which force-includes the `profiles` directory into the wheel as `src/_builtin_profiles`, so the built-in editorial rules travel inside the package rather than beside it.
Editorial conclusion
Horizon suits someone who already follows a wide set of feeds and wants one digest shaped by their own criteria rather than a generic newsletter, and who is willing to write or adapt a profile file to get there. It does not suit you if a story that matters has to appear under two headings, because each item routes to a single profile, or if you want your thresholds stored next to the profile that uses them, because the configuration explicitly puts score thresholds and topic deduplication in processing.profile_settings instead. Verify before deploying: which sources actually need credentials, since GitHub drops from 5000 requests per hour to 60 without a token and Twitter scraping needs an Apify token; whether the twitter extra matters to you, since the Dockerfile installs no Playwright browser; and how the container is triggered, since restart is set to no and a one-shot command does not schedule itself. The package version reads 0.1.0 and the repository has no GitHub releases, so there is no artifact to pin and the last push on 2026-11-02 is the only recency signal.
Frequently asked questions
How do I install Horizon?
Clone the repository, enter the Horizon directory and run uv sync, or pip install -e . for a pip install. The dev extra is uv sync --extra dev for pytest and other development dependencies. Python 3.11 or newer is required.
What does Horizon need in .env before it will run?
At least one AI API key. HORIZON_WEBHOOK_URL is optional for notifications, GITHUB_TOKEN is optional but recommended for higher rate limits at 60 requests per hour without it and 5000 with it, and APIFY_TOKEN is required for Twitter scraping.
Does the Horizon Docker image include everything?
No. Full-text extraction with trafilatura is included in the base install, but the twitter extra also requires a Playwright browser and system packages that the current Dockerfile does not install.
How is the Horizon container triggered each day?
The compose file sets restart to no and the command to --hours 24, and the scheduling comment says to adjust the daily 8:00 AM UTC run as needed. For a single run it uses docker compose run --rm horizon, so nothing in the container schedules itself.
What are Horizon profiles?
Reusable editorial rules defining what belongs, what is worth keeping and what to write. Built-in examples are tech-news for events and context, tech-blog for background, solution and takeaways, and ai-creator for a summary with hooks and angles.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/thysrael-horizon)Star history chart for your README
[](https://hysenlabs.com/projects/thysrael-horizon)Was this useful?