What's next

Where Nodez is heading. These are intentions rather than promises - Nodez is in alpha, built by a very small team, and the order changes as things turn out harder or easier than expected. Nothing here has a date.

Where it has got to#

Most of the foundation is in place and in daily use:

• Vaults - real folders on disk, with create, rename and delete, and edits from other apps picked up while Nodez is open
• Writing - Markdown editing, preview, wikilinks, backlinks, tags, outline
• The graph - notes and code in one map, with filters, path tracing, cluster detection, and both 2D and 3D views
• Code indexing - attach a project and see imports, calls and dependencies alongside your notes
• Sync - pull, commit, push and conflict detection through git
• Assistants - a working MCP connection that can query the graph and read and write notes
• Updates - signed in-app updates on Windows

Being worked on#

Attachments. Images and files alongside your notes, handled properly rather than as links that happen to work.

Better search. Search is fast but ranks results simply. It should understand that a title match matters more than a passing mention.

Note properties. Frontmatter is read and displayed, but editing it in the app is only partly done.

More keyboard shortcuts. The command palette covers a lot; the things you do constantly should not need it.

Planned#

A macOS release you do not have to talk your Mac into opening. Nodez builds for macOS, but the builds are not yet signed and notarised by Apple, so macOS warns you about them. Fixing this properly is on the list.

Signed Windows installers. Windows shows an "unknown publisher" warning for the same reason. Same fix, different certificate.

A gentler start with git. Right now your vault has to already be a git repository for sync to work. Setting that up - including cloning an existing one

• should happen inside the app.

Conflict resolution you can see. Today Nodez stops on a conflict and tells you, which is the safe behaviour but leaves you to resolve it elsewhere. It should be able to walk you through it.

More than one code project at a time. One attached repository proves the idea. Several is the obvious next step.

Being considered#

These are ideas we like without having committed to them:

• Deeper code understanding - a proper parser for each language rather than pattern matching, which would make the code half of the graph more precise
• Bigger graphs, drawn faster - very large projects currently need the view capped; that could be handled far more gracefully
• Richer questions from assistants - more ways for an AI to interrogate the graph rather than reading files

Not planned#

Worth being clear about, because these shape everything else:

• A sync service of our own. Sync is git. We are not building a cloud.
• A hosted version. Nodez runs on your machine.
• Live collaborative editing. Sharing happens through git.
• A mobile app. Your vault is plain Markdown, so mobile Markdown editors already work on it.
• Obsidian plugin compatibility. Nodez reads the same files, but it is not trying to run Obsidian's plugin ecosystem.

Asking for something#

If something here matters to you, or something missing does, the beta is when feedback opens. Early is the point at which it has the most influence.