
IWE (iwe.md)
io.github.iwe-orgPublished by GitHub account iwe-orgv0.32.0Updated Nov 7, 2026
Markdown knowledge base as agent memory. Runs against the notes directory it is started in.
Overview
Turns a local folder of linked Markdown notes into shared memory an AI agent can read, write and organize alongside you.
- What you can do
- Read and search the notes in the folder the server is started in
- Save decisions, plans and lessons as ordinary Markdown notes
- Look up past work and summarize what is already in the knowledge base
- Organize and link notes so related ideas stay connected
- When to use it
- Useful when you want an agent to keep project context across sessions instead of starting from zero, and you want that memory stored as readable Markdown files you can edit, back up or put in git.
- Requirements
- Runs as a local process via npx from the npm package, started with your notes directory as its working directory. The notes folder should be initialized first with the IWE CLI. No IWE account, API keys or environment variables are declared; connecting an AI agent depends on that agent's own setup.
Installation
In SourceWeft
- Open IWE (iwe.md) in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
IWE: a Markdown knowledge base you and your AI agent work on together
Your notes are your agent’s memory. IWE is where you work on them together.
iwe.md · Download for Mac · Docs · Reddit
[Crates.io] [License] [Documentation]
Too many AI conversations start from zero. You explain your project, your decisions, your reasoning — then find yourself explaining it all again next session. Your own notes live somewhere else, out of the agent's reach.
Or worse, the agent “remembers” something in its own internal memory, but you can't easily see what it saved or correct what it got wrong. And that memory doesn't travel with you to the other agents you work with.
IWE gives you and your AI agents one shared place to work, right inside your project: a folder of connected Markdown documents — specs, plans, decisions, and more. Keep your own ideas there, ask your agent to save what you learn together, and return to that context as your work grows. You can read, edit, and organize those documents yourself — and they stay yours.
[Watch the IWE intro video on YouTube]
Choose how you work
There are four ways to work with IWE. Mix and match them to fit your day:
All four work with the same Markdown documents. Draft a spec in your editor, develop it with Claude/Codex, browse it in the iWe app, or search it from the CLI. Use any combination you like; each tool also works independently.
Bring your own AI. Neither the IWE CLI nor the iWe Mac app includes an AI model. Both work on their own as tools for your notes. When you want AI help, use your existing Claude/Codex agent — in terminal or directly in the Mac app.
[iWe for Mac showing project plans and connected documents]
[Bug tracking with charts] [Technical documents with code] [Release documents]
Plans · Charts · Technical documents · Releases — click a screenshot to see the iWe app in action on iwe.md.
Why IWE
- Shared context. Your agent can use the same notes you write for yourself. Notes link to each other, and one note can belong to several topics, so you can follow an idea wherever it connects.
- Memory you can read. Decisions and lessons saved by your agent are ordinary notes you can browse, correct, or delete.
- Your notes stay yours. Everything is Markdown in a folder on your machine. Back it up, sync it, or keep it in git. You don't need an IWE cloud account to keep your notes; connecting an AI agent involves that agent's own setup and account requirements.
iWe for Mac
If you'd like a dedicated space for your notes, use the native Mac app. Open a folder of notes and you get a fast, keyboard-friendly space to write and browse. You can also connect your existing Claude/Codex agent to work alongside you.
- Works with your Claude/Codex agent. Connect the agent you already use, ask questions about your notes, and have it draft or reorganize them. Watch its edits appear in the document as it works.
- Room to experiment. Each agent run is one undo step — try an idea, and roll it back if you don't like it.
- Follow your ideas. Jump between related notes, search in a few keystrokes, and view Mermaid diagrams right in your documents. Your editor and other tools can keep working on the same files.
Open a notes folder and start with a note about something you're working on. Once Claude/Codex is connected, try asking it to summarize that note or help you develop an idea.
Your Own Editor
Keep writing in Neovim, Helix, VS Code, or Zed. IWE adds link autocomplete, backlinks, search, and safe renaming across your notes.
Follow the guide for your editor, open your notes folder, and try linking two notes with autocomplete. You can use IWE for your own writing without connecting an AI agent.
CLI
Prefer the terminal? Use IWE to search, create, and reorganize notes, or work it into your scripts. The CLI has no AI built in: these commands work on their own. Your existing Claude/Codex agent can use IWE's tools too.
Install with Homebrew, or choose another option from the installation guide:
Then run these commands inside your notes folder:
iwe find lists your notes; --lexical searches their content. Explore more in the CLI reference and workflow examples.
Claude/Codex
You can use IWE entirely through your agent. Ask Claude/Codex to save decisions, look up past work, and organize what you've learned. The agent works with your notes through IWE, and you can open those files yourself whenever you want.
IWE isn't tied to one AI. The same notes work with Claude Code, Claude Desktop, Codex, Gemini, Cursor, and any tool that supports the Model Context Protocol.
Give Claude/Codex a memory — for Claude Code, install the plugin, then run /iwe:init in any project you want remembered. For Codex, follow the agent connection steps below.
Then ask it to save a decision from your current work, and open the note it creates in your project.
Connect another agent — with Homebrew installed, install IWE:
Run iwe init in your notes folder, then follow the agent connection guide to add the iwec MCP server with that folder as its working directory. For other installation options, see the installation guide.
Once connected, ask your agent: “Explore my IWE notes and summarize what's here.”
Or let the agent set itself up — paste this into any agent that can run commands:
Learn More
- Getting Started — install and set up
- Working with AI — connect your agents
- Usage Guide — everyday workflows
- Examples — how people use IWE
- CLI Reference and MCP Server — for the technically curious
Ready-made workspaces: dev-workspace — project memory for a coding agent · marketing-workspace — campaign memory for a marketing agent.
Get Involved
Trying IWE with your own notes? Tell us what felt useful and where you got stuck. Questions, rough edges, and examples of how you use it are all welcome in Discussions.
IWE is open source. You can also report a bug or help improve the documentation.
Community: Twitter/X · Reddit · Discussions
Building on IWE? The CLI and MCP server are the supported ways to integrate today. Tell us what you depend on so we know what not to break.
License
Source: README.md at commit 7cdf04c
Tools
0Version history
14- v0.32.0LatestNov 7, 2026
- v0.31.0Nov 5, 2026
- v0.30.0Nov 3, 2026
- v0.29.3Oct 29, 2026
- v0.29.1Oct 24, 2026
- v0.29.0Oct 20, 2026
- v0.28.0Oct 17, 2026
- v0.27.0Oct 16, 2026
- v0.26.1Oct 8, 2026
- v0.26.0Oct 8, 2026
- v0.25.0Oct 2, 2026
- v0.24.2Sep 21, 2026
- v0.24.1Sep 17, 2026
- v0.24.0Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts