Edit your repo in place
Browse files and edit code with tabs, syntax highlighting, and familiar shortcuts.
- Customize themes, fonts, and editor settings.
- Save and reload with conflict detection.
- Access recent files and view code problems.
A local-first Markdown workspace. Open a folder of notes, attach a code repository, and see how they actually connect, then hand that same graph to your AI agents over MCP.
Beta version is coming Downloads are paused until it lands.
Downloads are paused while the build is prepared for beta. There is nothing to install today.
Beta version is coming. Windows and macOS builds will both be published on this page when the beta opens. Still no account and no server: the app reads and writes plain files on your disk.
Edit your repository and chat with AI without leaving your workspace.
Browse files and edit code with tabs, syntax highlighting, and familiar shortcuts.
Chat alongside your notes and code. Choose your provider and model per workspace.
Nodez does not own your knowledge. It reads a folder, builds an index beside it, and gets out of the way.
Markdown files on disk with wikilinks, backlinks, an outline, and preview. Delete the app tomorrow and your notes still open in anything.
Attach a read-only source root. Files, symbols, imports, and package dependencies land in
the same graph as your notes, under .nodez/. Explore it flat in 2D, or in a
3D force layout you can orbit.
Trace a path from a decision note to the file it constrains. Every edge records whether it was extracted or inferred, and points back at a real line.
Copy one config and your agent can query the graph, search notes, and write them back, while the attached repo stays read-only.
Pull, commit, and push the vault from inside the app. When there is a conflict it stops and shows you, rather than picking a winner.
The full index stays queryable while the canvas draws a capped view. Re-indexing happens on commits, not on every keystroke.
The chat panel inside Nodez runs on the same MCP server anyone else can point at. Bring your own agent and it gets the identical tools, with no export step in between.
{
"mcpServers": {
"nodez": {
"command": "node",
"args": [".../scripts/nodez-mcp.mjs"],
"env": {
"NODEZ_VAULT_DIR": "~/Documents/MyVault"
}
}
}
}
A desktop app that reads a folder of plain Markdown notes and, optionally, a read-only code repository, and builds one graph of both: files, wikilinks, backlinks, code symbols, imports, and package dependencies. No proprietary database, no account.
Same local-first, Markdown-on-disk territory as Obsidian, plus a code repository in the same graph as your notes, and that graph exposed to AI agents over MCP instead of a plugin ecosystem.
Yes. It reads and writes plain files on disk, with no server or account required. Sync between machines happens over Git, which you control.
Free while in alpha. There is no account and no server. The app reads and writes plain files on your disk.
Yes, over MCP: query_graph, search_notes, read_note,
write_note, impact_of, explain_edge,
shortest_path, and rebuild_graph. An attached repository stays
read-only.
Both, from the beta. The attached repository opens in a tabbed CodeMirror editor with language-aware highlighting, and a chat panel supports Codex, Claude Code, Grok, and OpenCode against the active vault over the same read-only MCP tools an outside agent gets. Free models are available through OpenCode.