Skip to content
MathStructPublic

About

A graph native editor for knowledge/code

Resources

Stars

1 star

Watchers

0 watching

Forks

Repository files navigation

Moonkale — a wizard tending a kale plant under a full moon

Moonkale on the desktop: activity bar, Explorer, the vault as a graph, a file in the code editor Moonkale on a phone: rich note above a Rust file, the bottom bar

Moonkale

A graph-native code and knowledge editor.

Latest release Docs License: MIT

Warning

Moonkale is a prototype. Expect bugs, missing pieces and significant breaking changes: settings, file formats, the extension API and the package layout will all change without migration paths. Try it, and please don't rely on it yet.

The idea

Code editors, note-taking apps, database tools and no-code tools are separate worlds. Moonkale opens folders and databases and shows everything as one graph: files, symbols, wiki-links, tables and relations are nodes and edges, and every editor (code, rich text, table, graph, flow, terminal) is a view on that graph. Language servers, indexers and LLM agents work on the same graph through the same interface as the user.

It is written in Rust with Dioxus: one codebase for desktop, web and Android. It is extension-driven: the built-in editors are extensions with no privileged access.

The long-term goal is a graphical editor for factor graphs (Lenticulum.jl), where a diagram stays a diagram instead of becoming code.

What works today

Tested on Linux (desktop and browser) and on one Android phone:

  • Folders, local or on another machine over SSH, in a Sources panel that follows changes made on disk, with quick open, a command palette, and find & replace across files.
  • Code editing with syntax highlighting for the core languages and language-server support (diagnostics, hover, go to definition, completion, rename). There are two editors: CodeMirror, and a pure-Rust one.
  • Notes: a WYSIWYG Markdown editor with [[wiki-links]], backlinks, KaTeX formulas and front matter, plus a Typst preview.
  • Graph view in 2D and 3D, GPU-rendered, for a folder's files, links and symbols, usable with 100k nodes.
  • Databases: SQLite, DuckDB (including folders of CSV/Parquet files), Turso, redb, RocksDB, embedded HelixDB and LadybugDB (Cypher, Linux only), as tables and as graphs, read-only for now.
  • Terminal: stack traces in it become clickable graphs.
  • Git: changes, diffs, staging, commits and history as a graph.
  • Search: keyword search, plus meaning-based search when an embedding model is configured.
  • Change history: a record of every edit (yours, an agent's or git's), with restore.
  • LLM agents: Claude Code (on a subscription), Anthropic, OpenAI-compatible and Ollama. They read, search, query and edit behind an approval gate. There is also an MCP endpoint for external agents.
  • Extensions: WebAssembly extensions, and a node-based flow editor with a Lux.jl block library (off by default).
  • Server mode: moonkale-server serves the same app to a browser or to the phone. (Only test in local network!! Still has some security flaws)

Windows and macOS builds are produced but untested: nobody on the project has those machines. Area by area, with what is still missing: Status.

Planned

  • A refactor into a library with a small core: extensions, sources and server routes added without editing the shell, and one store for Moonkale's own state that can sync between devices.
  • Writes to the embedded databases (the OLTP side), and more data sources: Postgres, TypeDB, FalkorDB, Redis (only stubs today).
  • Projects that combine several sources, and links across them.
  • The Julia side, in a separate repository: a Julia package source, a ModelingToolkit editor, and the Lenticulum.jl factor-graph editor.
  • Shared editing on one server: accounts, presence, merged edits.
  • Comments anchored to files, rows and nodes, with GitHub issues as one kind of comment. Also Jupyter notebooks and Unicode input (\int → ∫).
  • Fewer JavaScript dependencies: the terminal and a code editor already have Rust replacements.

The design notes behind all of this, one note per decision, are the documentation site.

Install

Download from the releases page. Releases are named by date, YYMMDD-proto (e.g. 260927-proto), and the files moonkale-<release>-<platform>; <release> below stands for that name.

platform file install
Arch Linux moonkale-<release>-arch-x86_64.pkg.tar.zst sudo pacman -U <file>
Debian 12+ / Ubuntu 22.04+ moonkale-<release>-debian-amd64.deb sudo apt install ./<file>
Nix / NixOS (from source) nix profile install github:MathStruct/Moonkale
Debian/Ubuntu (tarball) moonkale-<release>-linux-x86_64.tar.gz unpack, ./bin/moonkale, or ./install.sh ~/.local
Android (arm64) moonkale-<release>-android-arm64.apk sideload, or adb install -r <file>
Windows / macOS .msi / .exe / .dmg unsigned and untested, see the install page

Details and troubleshooting: Install. New to it? Getting Started explains Moonkale for people who use VS Code and Obsidian. To build it yourself: Development.

Feedback

Bugs, ideas and "I cannot get it to work" all welcome: open an issue. Reports on Windows and macOS are especially useful, since that's the only testing those builds get. More in Feedback.

License

MIT, see LICENSE. Built binaries also contain third-party software under its own permissive licenses: DuckDB, LadybugDB, wasmtime, Typst, tree-sitter, ICU4X, CodeMirror, Milkdown, xterm.js, KaTeX and its fonts (OFL). No GPL-only dependency is included. The full list: Licensing.

Moonkale is a MathStruct project.

About

A graph native editor for knowledge/code

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages