Neurowire

Appearance

Getting started ​

Neurowire turns any blog, website, RSS, or Atom feed into clean, modern feeds. Point it at a URL and get back NWF (a compact custom format), Atom, RSS 2.0, JSON Feed 1.1, or Markdown. Bundle many sources into one mesh, group meshes into a construct, keep the history in an append-only journal, and render any feed, mesh, or construct into a self-contained HTML news page.

Three surfaces ​

Neurowire is one toolkit you can reach through three doors:

  • Library: the npm packages (@neurowire/core, @neurowire/ingest, @neurowire/taps, @neurowire/web). Fetch, parse, merge, and serialize feeds from your own code. See Library usage.
  • CLI: the neurowire binary. Point it at a URL, get a terminal view or a serialized feed, bundle meshes, watch for new posts, push to Slack. See CLI reference.
  • HTTP API: a small Hono service exposing GET /feed, /mesh, and /construct. Run it yourself and call it over HTTP. See HTTP API.

The data model is the same across all three: every parser produces a single canonical feed shape, and every serializer consumes it. Learn the model in The model.

60-second quickstart ​

1. Install the CLI ​

bash
pnpm add -g @neurowire/cli
bash
npm install -g @neurowire/cli

Node 24+

Neurowire is ESM-only and needs Node >= 24. See Installation for the full matrix.

2. Point it at a URL ​

bash
# a terminal view (no --format)
neurowire https://blog.rust-lang.org/feed.xml

# or a serialized feed to stdout
neurowire https://blog.rust-lang.org/feed.xml --format atom > rust.xml

Neurowire detects whether the URL is a feed or an HTML page. For an HTML page it follows a declared feed link, falls back to a curated per-host recipe (a tap), then to heuristic auto-detection.

3. Bundle a mesh ​

A mesh is a named bundle of sources, fetched in parallel and merged into one newest-first feed. Drop this into ai-news.json:

json
{
  "name": "AI News",
  "sources": [
    { "name": "Claude Blog", "url": "https://claude.com/blog" },
    { "name": "Simon Willison", "url": "https://simonwillison.net/atom/everything/" }
  ]
}

Then fetch it:

bash
neurowire --mesh ai-news.json --format json --limit 10

4. Follow it live ​

A mesh does not have to be something you re-run. tail polls it and prints each new entry the moment it appears, until you stop it:

bash
neurowire tail --mesh ai-news.json --interval 60s

The first tick prints what is on the front page right now, one entry per line, then the command goes quiet and only speaks when something new lands:

09:41:02  Claude Code 2.0
          Claude Blog · 2026-08-27
          https://claude.com/blog/claude-code-2

Add -f nwf to stream raw NWFJ records instead, which is what you want when the output is going into another tool rather than your eyes. See Tail.

5. Render an HTML page ​

Install the page generator and turn a mesh into a self-contained HTML page (all CSS inline, no external requests):

bash
pnpm add -g @neurowire/web
neurowire-web --mesh ai-news.json --out index.html
bash
npm install -g @neurowire/web
neurowire-web --mesh ai-news.json --out index.html

Sites with no feed ​

Some sites publish a blog and ship no feed at all. A tap teaches Neurowire to read one: a small set of CSS selectors saying where each article sits on the listing page. You do not write them by hand, tap wizard proposes them from the page's structure and verifies the result before saving:

bash
# author a tap (--yes takes the top suggestion for every field)
neurowire tap wizard https://example.com/blog --yes -o example.json

# the site now reads like any feed
neurowire https://example.com/blog --taps example.json --format atom

Drop the tap into ~/.config/neurowire/taps/ (where the wizard writes by default) and the --taps flag becomes unnecessary. No model is involved and no API key is needed, at any point.

Pull from a peer instead of fetching ​

If someone already runs a Neurowire node that journals these sources, you do not have to fetch them yourself. Register the peer once and pull:

bash
neurowire peers add https://hub.example.com
neurowire sync --peers
#   ai: 1284 new, cursor 1284, 4 requests, 812.0 KB

Later syncs move only what is new, and cost one request when nothing is. What you get back is an ordinary journal, so neurowire journal cat ai -f json and friends work on it immediately. This matters most for a laptop that is closed most of the day: a live fetch can only show you what is on the front page right now, while a node that stayed awake recorded everything you missed. See Sync for why, and Federation for how to run the node.

Where to next ​

  • CLI reference: every flag and subcommand.
  • The model: the canonical feed shape.
  • Atom format: the default serializer.
  • Journals: keep an append-only archive of what a source publishes, and query it back.
  • Tail: follow a source as a live stream, in the terminal or over SSE.
  • Sync: pull journal deltas from a peer instead of re-fetching every source yourself.
  • Recipes: practical end-to-end workflows.
  • Taps: read sites that ship no feed, and keep those readers working when the site is redesigned.