$git clone https://github.com/iwe-org/iwe> Turn your thinking into queryable context
| 1 | # IWE - Memory system for you and your AI agents |
| 2 | |
| 3 | > Turn your thinking into queryable context |
| 4 | |
| 5 | [](https://crates.io/crates/iwe) |
| 6 | [](https://crates.io/crates/iwe) |
| 7 | [](https://github.com/iwe-org/iwe/blob/master/LICENSE-APACHE) |
| 8 | [](https://github.com/iwe-org/iwe/actions) |
| 9 | [](https://iwe.md) |
| 10 | [](https://github.com/iwe-org/iwe/discussions) |
| 11 | [](https://x.com/iwe_md) |
| 12 | [](https://www.reddit.com/r/iwe/) |
| 13 | |
| 14 |  |
| 15 | |
| 16 | IWE turns a directory of markdown files into a knowledge graph — a connected structure you browse from your editor and your AI queries from the command line. Same files, same links, two interfaces. No cloud, no database, no lock-in. Version everything with git. |
| 17 | |
| 18 | Write in **Markdown**, structure with links, give AI agents the **tools** to navigate your knowledge. IWE itself has no built-in AI — it works alongside Claude, Codex, Gemini, and any tool that speaks the [Model Context Protocol](https://modelcontextprotocol.io). |
| 19 | |
| 20 | ## What You Get |
| 21 | |
| 22 | - **Plain markdown, full ownership.** Your notes are `.md` files in a local directory. Read them, edit them, `git push` them. Nothing proprietary. |
| 23 | - **A graph, not a folder tree.** Link notes together and the same note can belong to multiple topics without copying the file. ([How linking works](https://iwe.md/docs/concepts/inclusion-links/)) |
| 24 | - **IDE features for your editor.** Real LSP integration with [VS Code](https://iwe.md/docs/editors/vscode/), [Neovim](https://iwe.md/docs/editors/neovim/), [Zed](https://iwe.md/docs/editors/zed/), and [Helix](https://iwe.md/docs/editors/helix/) — search, refactor, rename, autocomplete. |
| 25 | - **Structured access for AI agents.** [CLI tools](https://iwe.md/docs/cli/) and an [MCP server](https://iwe.md/docs/agentic/mcp/) let agents search, retrieve, and refactor the same notes you edit by hand. |
| 26 | - **Fast.** Built in Rust, [processes 20,000 files in under a second](docs/benchmark.md). |
| 27 | |
| 28 | ## How It Works |
| 29 | |
| 30 | IWE treats your notes as a connected structure. You organize them with two types of links: |
| 31 | |
| 32 | - **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/). |
| 33 | - **Cross-references** — regular inline links connect notes across topics, creating a web of relationships. |
| 34 | - **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. |
| 35 | - **Context from parents** — when you retrieve a note, IWE can include context from the notes above it in the hierarchy. |
| 36 | |
| 37 | This structure makes retrieval powerful — whether you're browsing in your editor or an agent is querying via CLI, ask for a topic and get its full context in a single call. |
| 38 | |
| 39 | ## Working with AI |
| 40 | |
| 41 | IWE gives AI agents structured access to your notes through two interfaces: a CLI for scripting and shell-based workflows, and an MCP server for native connection with AI tools. Both expose the same operations — search, retrieve, create, refactor — so you can choose whichever fits your setup. |
| 42 | |
| 43 | ### Integration Server (MCP) |
| 44 | |
| 45 | IWE includes a server (`iwec`) that lets AI tools like Claude Desktop, Cursor, and Windsurf work directly with your notes using the [Model Context Protocol](https://modelcontextprotocol.io). The server watches your files for changes, so edits you make in your editor are reflected immediately. |
| 46 | |
| 47 | ### Command-Line Tools |
| 48 | |
| 49 | The CLI lets you (and AI a |