Insurgently

Obsidian plugin· Active · beta · not yet released

Clusters

The research layer: search, neighbours and trails over any corpus, as a CLI and an MCP server.

Clusters roadmap

What's planned for Clusters, release by release. The order can change as people use it. Questions and ideas are welcome in the repo's Discussions. How the three plugins fit together, and where their work reaches outside Obsidian, is on the roadmap across the plugins.

  1. 0.1Beta17 items
  2. 0.2Community directory4 items
  3. 0.3Your collections in Claude3 items
Built so far

collections from books, notes and Bases; the nonfiction and fiction lenses, and lenses of your own; indexing with a dry run, a spend limit and runs that pick up where they stopped; search with filters, passages, neighbours in other books and disagreements; topics as notes with Graph view colours; write-up drafts with every quote checked; a survey of a collection's fields; undo for every run.

0.1 — Beta

next

A public beta through BRAT, alongside Model Hub and Books & Shelves. First, in order, what the first real index (a shelf of 35 books, 2026-10-05) showed needs fixing. Plan: docs/plans/2026-10-05-first-use-fixes.md.

  • The Collections tab catches up after a run. After Index, Find topics or Survey, a collection's row keeps its old state until settings are closed and opened again. The row updates when its job ends.
  • A run in progress shows on its collection's row and in its dialog, with its progress, after the job dialog is closed. Today the only trace is Open jobs.
  • Books that couldn't be split into passages are named on the collection's row and at the top of the next dry run, with the fix in one line. Today the only sign is a line in the end-of-run report.
  • Size on disk. A collection's row and its dialog say how much its index takes on disk, beside its cards and topics.
  • The Index dialog in two layers: the counts, the cost and the Index button first; what is split into passages, what is read again and why, where the index lives and the undo line under a fold. When the run ends, a short summary (passages read, cards made, cost, what failed or was left out) with the full report under a fold, and Done as the only action.
  • Dry-run numbers that read as a contradiction ("3 books to split, 2 passages to read"): the dialog says that the passages of books not split yet are counted once they are, so the count will grow.
  • "Passages", not "units", in the Index dialog and the run summaries. The guide already says passages.
  • Converting AZW3 and MOBI books becomes a setting with a default, asked once and remembered, in place of a question before each run.
  • Actions where they act: Preview a collection's passages moves into the Index dialog, and the rest of the command list is reviewed one by one for a place in settings or a dialog.
  • An icon per source kind on the Collections tab: books, notes, Bases.
  • Setup says when an update to Model Hub or Books & Shelves is available, from Obsidian's own check.
  • Spend per run on the Collections tab. Runs record their cost.
  • Keep a collection up to date on its own: a switch per collection, off by default, that reads only what changed, within a spend limit per day.
  • Cheaper, Balanced or Better, per run: one pick on the Index dialog mapped onto Model Hub's provider order, the extract tier and reasoning, for that run only.
  • Screenshots and a short demo for the README and the guide
  • A first collection end to end on real notes, with the costs in Model Hub's ledger checked against the dry runs
  • Tag 0.1.0; a beta thread on the Obsidian forum

0.2 — Community directory

planned
  • Submission to the Obsidian community directory, and fixes from its review
  • The name checked against "Cluster", which is already in the directory
  • Model Hub's skills folder through its API, in place of reading Model Hub's settings
  • Lenses for notes and Bases. The built-in lenses are shaped for books; notes, journals and the rows of a Base want their own. A design session first: what a note's card is, which fields come from its properties

0.3 — Your collections in Claude

planned

Needs Model Hub 1.0, which brings the Hub's tool registry and its MCP server. Clusters registers what it can do with the Hub and runs no server of its own.

  • Ask a collection a question from the Hub's panel or from Claude Code, Claude Desktop or Codex, and get the passages back with the book and place each comes from
  • Follow a passage to its neighbours in other books, and to the places that disagree with it, from the same agent
  • Read a card or a topic note as the agent needs it, so a write-up drafted outside Obsidian quotes your index, not its memory

Exploring

Not scheduled. Research or a design comes first.

  • Lenses for other kinds of source: web clips, transcripts
  • Voices inside a passage: who is speaking, as a field you can filter by
  • A cluster map: a two-dimensional view of the cards, beyond what Graph view shows
  • Faster topics for large collections: clustering off the main thread
  • Comparing lenses and models on your own examples

Not planned

So you know before you ask.

  • Mobile. Clusters is desktop only, like Model Hub.
  • Any telemetry sent to the author.

Read from ROADMAP.md in the plugin's repo.

How the plugins feed each other →