Skip to content
Back to search

iwe

Markdown knowledge graph — LSP for your editor, CLI + MCP memory for your AI agents

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/iwe-org/iwe with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/iwe-org/iwe'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/iwe-org--iwe/badge.svg)](/listings/iwe-org--iwe)

HTML

<a href="/listings/iwe-org--iwe"><img src="/api/listings/iwe-org--iwe/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 195 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # IWE: a Markdown knowledge graph for you and your AI agents
  2. IWE turns a folder of Markdown files into a knowledge graph. You browse and refactor it from your editor through an LSP server, and your AI agent queries it through a CLI and an MCP server. Same files, same links. It is written in Rust and needs no database, no cloud and no account.
  3. It is for people who want database-style queries on their notes — "all drafts under this subtree", "every accepted decision in Q1" — without moving them into an actual database.
  4. [![GitHub stars](https://img.shields.io/github/stars/iwe-org/iwe?style=flat)](https://github.com/iwe-org/iwe/stargazers)
  5. [![Crates.io](https://img.shields.io/crates/v/iwe.svg)](https://crates.io/crates/iwe)
  6. [![Downloads](https://img.shields.io/crates/d/iwe.svg)](https://crates.io/crates/iwe)
  7. [![License](https://img.shields.io/crates/l/iwe.svg)](https://github.com/iwe-org/iwe/blob/master/LICENSE-APACHE)
  8. [Quick start](#quick-start) · [How it works](#how-it-works) · [Editor](#in-your-editor) · [CLI](#cli) · [AI agents](#ai-agents) · [Mac app](#iwe-for-mac) · [Templates](#workspace-templates) · [Comparison](docs/comparison.md) · [iwe.md](https://iwe.md/?ref=readme-header)
  9. **English** · [简体中文](README.zh-CN.md) · [한국어](README.ko.md) · [日本語](README.ja.md) · [Deutsch](README.de.md)
  10. `````console
  11. $ iwe find --lexical "rename" --limit 2
  12. - [IWE Rename](cli-rename) -> [Inclusion Links](inclusion-links) <- [How to Use in Command Line](cli), [Files Renaming](feature-renaming)
  13. - [Files Renaming](feature-renaming) -> [IWE Rename](cli-rename) <- [IWE](index)
  14. $ iwe tree -k index
  15. - [IWE](index)
  16. - [Architecture](architecture)
  17. - [Benchmark](benchmark)
  18. - [Data Model](data-model)
  19. - [Keys and Cross-References](keys)
  20. - [How to Use in Command Line](cli)
  21. ...
  22. $ iwe retrieve -k feature-renaming
  23. ````markdown #feature-renaming
  24. ---
  25. title: Files Renaming
  26. includedBy:
  27. - key: index
  28. title: IWE
  29. sectionPath:
  30. - Features
  31. ---
  32. # Files Renaming
  33. ...
  34. `````
  35. Output from this repository's own [`docs/`](docs/) folder, shortened where marked `...`. A search hit comes back with what it links to (`->`) and what links to it (`<-`); a retrieved note comes back with where it sits in the graph.
  36. ## Quick start
  37. ```bash
  38. brew install iwe-org/iwe/iwe
  39. ```
  40. Also on npm (`npm install -g @iwe-org/iwe`) and Cargo (`cargo install iwe iwes iwec`); see the [installation guide](https://iwe.md/docs/getting-started/installation/).
  41. Then, in a folder that already has Markdown files:
  42. ```bash
  43. iwe init
  44. iwe find
  45. iwe tree
  46. ```
  47. From here, set up [your editor](#in-your-editor), connect [your agent](#ai-agents), or both.
  48. If IWE is useful to you, a star helps other people find it.
  49. ## How it works
  50. IWE treats your notes as a connected structure built from two kinds of links:
  51. - **Nesting.** A link on its own line means "this topic includes that subtopic". Your notes form a tree you can browse and refactor. IWE calls these [inclusion links](https://iwe.md/docs/concepts/inclusion-links/).
  52. - **Cross-references.** Regular inline links connect notes across topics.
  53. - **Multiple parents.** The same note can live under several places at once. A "Meditation" note can belong to both "Health" and "Productivity" without duplicating the file.
  54. - **Context from parents.** When you retrieve a note, IWE can include context from the notes above it in the hierarchy.
  55. [![The documents of IWE's own documentation as a graph](docs/docs-index.svg)](docs/feature-visualization.md)
  56. *IWE's own documentation: the 52 documents under its index and their 720 sections, exported with `iwe export` and laid out by Graphviz. [Draw your own](docs/feature-visualization.md).*
  57. What you get:
  58. - **Plain Markdown, full ownership.** Your notes are `.md` files in a local directory. Read them, edit them, `git push` them.
  59. - **Retrieval by structure, not similarity guessing.** Fuzzy and full-text search find the entry point; the graph turns a hit into usable context: parents, children, cross-references.
  60. - **Refactoring that keeps links intact.** Rename, extract, inline and delete update every reference.
  61. - **Checked writes.** Frontmatter and document structure are validated against per-type [document schemas](https://iwe.md/docs/concepts/document-schema/), and an edit can declare how many documents and blocks it may touch, so a mismatch aborts before anything is written.
  62. - **Fast.** The graph for 20,000 notes builds in under a second on a laptop ([benchmark](docs/benchmark.md)).
  63. - **No built-in AI.** IWE works on its own as a tool for your notes. When you want AI help, it works alongside the agent you already use.
  64. How it differs from marksman, markdown-oxide, Obsidian and zk, including where IWE is weaker: [How IWE compares](docs/comparison.md).
  65. ## In your editor
  66. IWE gives your editor IDE-like features for Markdown notes. It works with [Neovim](https://iwe.md/docs/editors/neovim/), [Helix](https://iwe.md/docs/editors/helix/), [VS Code](https://iwe.md/docs/editors/vscode/), [Zed](https://iwe.md/docs/editors/zed/), and any editor that supports the Language Server Protocol.
  67. - **Navigate.** Go to definition, find references (backlinks), search notes by title or content.
  68. - **Rename.** Rename a file and every link to it is updated.
  69. - **Extract and inline.** Pull a section into a new note, or embed a note back into its parent.
  70. - **Auto-complete and hover.** Link suggestions as you type, previews on hover.
  71. - **Inlay hints.** Parent references and link counts shown in place.
  72. - **Format.** Normalize documents, update link titles, convert between headers and lists.
  73. Editor plugins: [iwe.nvim](https://github.com/iwe-org/iwe.nvim) · [vscode-iwe](https://github.com/iwe-org/vscode-iwe) · [zed-iwe](https://github.com/iwe-org/zed-iwe)
  74. ## CLI
  75. | Command | What it does |
  76. |---|---|
  77. | `find` | Search with fuzzy and full-text ranking, plus filters over frontmatter and graph edges |
  78. | `retrieve` | Get a document with its linked context in one call |
  79. | `tree` | Show the hierarchy from any starting point |
  80. | `update` | Guarded edits: frontmatter changes and targeted block operations |
  81. | `schema` | Infer the store's schemas, or validate documents against them |
  82. The full set — `new`, `extract`, `inline`, `rename`, `delete`, `squash`, `stats`, `normalize`, `export` and more — is in the [CLI reference](https://iwe.md/docs/cli/), with [workflow examples](docs/cli-workflows.md) in this repository.
  83. ## AI agents
  84. The same notes work with Claude Code, Claude Desktop, Codex, Gemini, Cursor, and any tool that supports the [Model Context Protocol](https://modelcontextprotocol.io).
  85. **Claude Code** — install the plugin, then run `/iwe:init` in any project you want remembered:
  86. ```text
  87. /plugin marketplace add iwe-org/skills
  88. /plugin install iwe@iwe-org
  89. /iwe:init
  90. ```
  91. **Any MCP agent** — point it at the MCP server. `iwec` serves the directory it runs in, so set the working directory to your notes:
  92. ```json
  93. {
  94. "mcpServers": {
  95. "iwe": {
  96. "command": "iwec",
  97. "cwd": "~/notes"
  98. }
  99. }
  100. }
  101. ```
  102. Without installing anything, `npx` fetches the server on demand: use `"command": "npx"` with `"args": ["-y", "@iwe-org/mcp"]`. More in the [agent connection guide](https://iwe.md/docs/agentic/).
  103. Or let the agent set itself up — paste this into any agent that can run commands:
  104. ```text
  105. Set up IWE for my notes: install it (brew install iwe-org/iwe/iwe,
  106. npm install -g @iwe-org/iwe, or cargo install iwe iwes iwec), run `iwe init`
  107. in my notes directory, then add the `iwec` MCP server with its working
  108. directory set to that folder.
  109. Docs: https://iwe.md/docs/agentic/
  110. ```
  111. ## iWe for Mac
  112. iWe is a free native Mac app for the same folder of Markdown: a native SwiftUI editor, no Electron, built on the same Rust engine as the CLI. Open a folder of notes and you get a keyboard-driven space to write and browse, with your existing Claude Code or Codex agent editing the document in front of you. Your editor and other tools keep working on the same files.
  113. **[Download the DMG from iwe.md →](https://iwe.md/app/?ref=readme-download)** · free · macOS 15 or later · no account
  114. <a href="https://iwe.md/app/?ref=readme-shot"><img src="https://iwe.md/images/app/GH-screen-1.1.png" alt="iWe for Mac showing project plans and connected documents" width="820"></a>
  115. - **Works with the agent you already have.** Ask about your notes, or have the agent draft and reorganize them. Its edits appear in the document as it works.
  116. - **One undo step per agent run.** Try an idea, and roll it back if you don't like it.
  117. - **Keyboard first.** Optional Vim keys, search in a few keystrokes, jumps between related notes, Mermaid diagrams rendered in the document.
  118. **Your agent, writing in the page** (2 min) — Claude Code tightens a paragraph, writes a new section, then adds a chart of the open bugs that redraws as each bug changes stage.
  119. https://github.com/user-attachments/assets/e57763df-46c9-4aea-92a2-ddd0d1010091
  120. **Vim keys for your notes** (2 min) — Move block by block, follow links, search, cut and paste bullets, undo and redo, all without leaving the keyboard.
  121. https://github.com/user-attachments/assets/c3edd2cb-4b7c-4f68-9eda-58aa740c1b23
  122. **[More screenshots, and both videos with captions, on iwe.md →](https://iwe.md/app/?ref=readme-video#videos)**
  123. ## Workspace templates
  124. A template is the starting content of a whole workspace: documents, schemas, the workspace config, and the instructions and skills your agent runs with. Each one is an ordinary repository of Markdown you can read before you use it.
  125. - [Dev Workspace](https://github.com/iwe-org/dev-workspace) — a knowledge base for a software project, kept by your coding agent: product, specs, plans, bugs, releases and learnings as a graph.
  126. - [Marketing Workspace](https://github.com/iwe-org/marketing-workspace) — campaign memory for a marketing agent: 67 launch venues, a CRM, posts, replies and leads.
  127. - [Seventeen Centuries](https://github.com/iwe-org/seventeen-centuries-workspace) — Marcus Aurelius, Machiavelli and Nietzsche as one graph: 843 passages and 331 concepts, 42 of them traced through all three books.
  128. To use one, clone its repository and work in that folder with the CLI or your editor, or pick it in iWe for Mac under File ▸ New Workspace from Template…. More templates, and how to submit your own, are in the [template registry](https://github.com/iwe-org/templates).
  129. ## Get involved
  130. Projects already build on IWE, as an agent-memory backend and as the graph layer of other tools: see the [running list](https://github.com/iwe-org/iwe/discussions/362), and add yours so we know what not to break. The CLI and the MCP server are the supported ways to integrate today.
  131. Questions, rough edges and examples of how you use it are welcome in [Discussions](https://github.com/iwe-org/iwe/discussions). You can also report a [bug](https://github.com/iwe-org/iwe/issues) or help improve the [documentation](docs/).
  132. **Community:** [Twitter/X](https://x.com/iwe_md) · [Reddit](https://www.reddit.com/r/iwe/) · [Discussions](https://github.com/iwe-org/iwe/discussions)
  133. ## License
  134. [Apache License 2.0](LICENSE-APACHE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.