Skip to main content

enowiki

Structural intelligence and gardening for your Obsidian vault — the library and eno CLI.

A markdown vault grows into a pile. Notes go orphaned, stubs never get finished, pages drift into saying the same thing twice, and every "what does my vault know about X?" costs a full-text grep plus a fat LLM read. enowiki indexes the vault into a queryable surface and gardens it — from the command line, with no LLM dependency and no model runtime to stand up.

The PyPI distribution is enowiki (the bare eno was already taken on PyPI by an unrelated package). The command, the config vars, and the import eno module are all just eno.

Install

pip install enowiki

Requires Python 3.12+. The core has no network dependency at all.

Quickstart

export ENO_VAULT_DIR=~/vault      # or pass --vault to any command
eno index                         # build the index (writes <vault>/.eno/index.db)
eno hygiene                       # frontmatter contract audit
eno search "mechanism design"     # paths + excerpts, not full notes
eno search "mechanism design" --kind text  # full-text body search

There is no default vault path — a tool that operates on your notes should never guess which directory that is. Set $ENO_VAULT_DIR or pass --vault. The index lives at <vault>/.eno/ (override with $ENO_DIR). Add --json to any command for machine-readable output.

For a project estate, run flip index --root /path/to/Projects, set the eno vault to that common Projects directory, and pass the resulting registry to eno index --flip-registry .... Eno indexes one visible filesystem copy per Flip UID instead of every repo document or worktree clone. Repeat --include-root NAME to compose complete roots such as an Obsidian vault. Use ENO_READ_ONLY=1 for a shared retrieval process whose writes must remain with the owning notebooks.

What it does

Retrieve — search, note, neighbors, frontier, hot. Graph-aware, excerpt-first retrieval over frontmatter, wikilinks, tags, and headings. Queries return paths and small excerpts, not whole notes, so nothing loads your vault into a prompt.

Garden & check health — orphans, stubs, stale, broken-links, hygiene, garden. The garden command writes a dated report back into the vault (under 9 Vault Health/) so it's wikilinkable, graph-visible, and indexable by eno itself. Structural changes always keep a human in the loop — eno never auto-merges or auto-deletes.

Write back — create-note and append-to-note file notes with provenance frontmatter (origin: llm, an author wikilink), so later gardening passes stay provenance-aware.

The [llm] extra

The LLM-backed features are behind an optional extra and import their model dependency lazily — the structural core above needs none of it:

pip install enowiki[llm]
  • eno fold — distills a date range or a topic (by wikilink, folder, or tag) into a structured, cited rollup note, with supersession metadata and fold-of-folds level stacking. Extractive-only, with a count-check that flags any numeric claim or citation date not present in the sources.
  • eno tiling — body-content semantic dedup: finds notes that say the same thing in different words, in two confidence bands. A signal for human review, never an auto-merge.

Both route through somm, which owns provider selection and is local-first (ollama) by default — vault prose never has to leave your machine. Call these without the extra installed and you get a clean pip install enowiki[llm] hint, not a crash.

The rest of the family

enowiki is the core of a small workspace. Two sibling packages put the same index behind other faces:

  • eno-mcp — an MCP stdio server exposing the read/write tools to coding agents.
  • eno-service — a FastAPI face on the read endpoints, for sibling tools.

See the project README for the full picture.

License

MIT — see LICENSE.

Metadata

Release files for enowiki 0.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for enowiki 0.5.0
File Size Uploaded Provenance Actions
enowiki-0.5.0.tar.gz 104.8 kB With provenance Details for enowiki-0.5.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for enowiki 0.5.0
File Interpreter ABI Platform Actions
enowiki-0.5.0-py3-none-any.whl Python 3 none any Details for enowiki-0.5.0-py3-none-any.whl

Total release size: 180.9 kB

Release files / enowiki-0.5.0.tar.gz

Download URL enowiki-0.5.0.tar.gz
Size 104.8 kB
Tags Source
SHA-256 checksum
How to use checksums
e9f5a8586d8b746106e6f9552729716148aa701372cfd449d00774568f3cff5a
BLAKE2b-256 checksum
How to use checksums
79e08d41d84bc76e5428e8cfc9f51804a38690ebe1fe6429424221e25e4f3809
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.

Transparency log

Release files / enowiki-0.5.0-py3-none-any.whl

Download URL enowiki-0.5.0-py3-none-any.whl
Size 76.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
37170484b507881434c77d00f6268302af92a02ff99676f4cef354f46910bf49
BLAKE2b-256 checksum
How to use checksums
a30f970626ff1f465c1552ea6f0541c8abf9c7794be876e9e3899604c038d77a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.

Transparency log

Security for enowiki 0.5.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for enowiki-0.5.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page