# MindForger: a Markdown notebook that keeps your notes on disk

> MindForger is a Qt-based thinking notebook and Markdown editor for people who want personal knowledge management without a cloud account. Its GPL-2.0 licence, its outliner model and its packaging story are the parts worth examining before you move your notes into it.

**dvorka/mindforger** — Thinking notebook and Markdown editor.

- Repository: https://github.com/dvorka/mindforger
- Website: https://www.mindforger.com/
- Stars: 2,721 · Forks: 173
- Language: C++
- License: GPL-2.0
- Published: 2026-09-14 · Updated: 2026-09-14 · Language: en
- Canonical page: https://hysenlabs.com/projects/dvorka-mindforger

## The problem MindForger targets: notes you cannot find again

The README opens with a blunt framing: people drowning in information but starving for knowledge, with remarks spread across the file system, cloud services, the web and Post-it notes. That is the gap MindForger claims to fill. It is not a general-purpose text editor with Markdown highlighting bolted on; the project describes itself as a human mind inspired personal knowledge management tool, and the two screenshots in the README show the two modes it cares about, a thinking notebook and a Markdown IDE.

The intended user is an individual, not a team. The README asks whether you are afraid of your knowledge privacy and whether you can find what you wrote once you have written it. Those questions point at a single person keeping private remarks: ideas, personal plans, business vision, finance strategy, coaching notes. There is no account system, no sharing model and no server component described in the repository. If your requirement is a shared knowledge base with permissions, this is the wrong shape of tool.

## Outliner, Markdown files and a notebook tree

The mechanism visible from the repository is a Qt desktop application, written in C++, built through the `mindforger.pro` project file at the repository root, with sources under `app/`, libraries under `lib/`, third-party code under `deps/` and manual pages under `man/`. The README presents two views over what is fundamentally the same content: a thinking notebook that behaves like an outliner, and a Markdown editor for direct text work.

The 2.0.0 release notes name a Notebooks Tree and Libraries, which suggests the navigation model is a tree of notebooks grouped into libraries rather than a flat list of files. The 2.1.0 release added autolinking colorization and something called Wingman; 2.2.0 added Rewrap, Snap packaging, WebEngine, KaTeX and Mermaid. KaTeX and Mermaid imply that rendered math and diagrams appear inside the editor through an embedded web engine, which is a heavier dependency than a plain text widget but also the reason those features exist at all.

What the repository does not show is a synchronisation layer. There is no server directory, no database schema and no daemon in the top-level entries. The design assumption appears to be that your notes live as files you control, and that the application is a lens over them.

## Installing MindForger and opening a first notebook

The README does not inline install commands. It links to a wiki page per platform, and the practical entry points are the Snap package, the distribution packages tracked on repology and pkgs.org, and the release tarballs. On a machine with snapd, the Snap Store badge in the README points at the canonical package name:

```bash
snap install mindforger
```

After installation, the README says to check the manual page, which is the only first-party command reference the repository ships:

```bash
man mindforger
```

The manual page is where you should look for the flag that points the application at a directory of Markdown files. The README does not reproduce that flag, so read `man mindforger` before assuming a path argument exists.

If you prefer not to use Snap, the releases page carries tarballs and the README links separate build instructions for macOS, Windows, Ubuntu, Debian, Fedora, Gentoo, NixOS and WSL, plus a Docker build-and-run page. Building from source means a Qt toolchain and the vendored dependencies in `deps/`; that is a normal C++ desktop build, not a one-line install. For a first real use, create a directory, put a few Markdown files in it, and point the application at that directory using whatever the manual page documents. The notebook tree should then show those files as entries you can open in the editor view.

## Where MindForger is the wrong tool

The clearest limitation is stated by the author in the README itself. The project is described as perfect to me, and the text says that even if the main development branch does not receive updates, the author uses it daily and adds a feature or fixes a bug as needed. It also says issues and bug reports may not be implemented, with the acronym IAGNI. Read plainly, that is a single-maintainer project with no commitment to external feature requests.

The last push to the repository was on 2026-09-14 and releases 2.1.0 and 2.2.0 landed in September 2026, so the code is not dormant today. But the maintenance model matters more than the timestamp. If your team depends on a feature that does not exist yet, the README gives you no process that will produce it. There is also no plugin or extension API described in the repository material, so extending MindForger means patching C++ and rebuilding, not writing a script.

Second, the GPL-2.0 licence is a real constraint for anyone embedding the editor in a commercial product. Third, features such as KaTeX, Mermaid and WebEngine rendering pull in a browser engine, which is a large surface for a notes application and a plausible source of packaging friction on minimal Linux installs. If you want a plain, dependency-light Markdown viewer, that trade-off works against you.

## MindForger compared with Obsidian and plain Markdown editors

The obvious comparison is Obsidian, which people search for alongside MindForger. Both keep notes as local Markdown files and both present a graph or tree over them, but the difference in approach is where the logic lives. Obsidian is built around a plugin ecosystem in JavaScript, so behaviour is extended by installing community plugins without recompiling. MindForger is a compiled Qt application with the notebook and outliner behaviour built into the binary; the repository shows `app/`, `lib/` and `deps/` and no extension directory. If you want to change how it behaves, you change the C++ and rebuild.

The second difference is packaging philosophy. MindForger targets distribution channels: Snap, Debian, Fedora, Arch, openSUSE, NixOS, FreeBSD, plus nightly builds for macOS and Windows. Obsidian ships as a proprietary application from a vendor site. If your constraint is a package manager and an auditable build, MindForger fits that constraint better; if your constraint is a rich third-party plugin catalogue, it does not.

Against a plain editor such as a stock Markdown mode, the difference is the notebook layer. A plain editor gives you a buffer and a file path. MindForger adds the outliner view, the notebook tree and libraries, and the rendering features added in 2.2.0. Whether that layer is worth a Qt install and a GPL-2.0 binary is the decision you are actually making.

## Upgrade path, packaging and licence obligations

Upgrades follow the channel you chose. Snap users get new versions through `snap refresh`; distribution users wait for the maintainer of their package, and the README points at repology and pkgs.org to see which versions are packaged where. Tarball users download a new release and replace the old one. The repository also documents nightly builds: a macOS .dmg from GitHub Actions, a Windows installer from AppVeyor, and a tarball nightly from the Ubuntu workflow. Nightly artifacts are not releases, and the README does not describe a migration or rollback procedure for moving between them, so treat them as test builds.

The licence is GPL-2.0, and the repository carries a `LICENSE` file plus a `licenses/` directory for bundled components. GPL-2.0 is a copyleft licence with source-distribution obligations if you convey the software or a derivative. That is a statement about the licence text, not legal advice; if you plan to redistribute MindForger inside a product, have someone qualified read the terms and the bundled component licences rather than assuming they are uniform.

The upgrade cost that is easy to miss is the build toolchain. Because the application is C++, keeping a fork current means tracking Qt and the vendored dependencies in `deps/`. A user who only installs the Snap package pays none of that. A user who patches the source pays it on every upstream change.

## Conclusion

Adopt MindForger if you want a local Markdown notebook with an outliner view and you are comfortable with a project whose README says the main development branch may not receive updates. Do not adopt it if you need multi-user sync, a stable plugin API or a documented roadmap; none of those appear in the repository material. Before committing, install the 2.2.0 release on your own machine, confirm that `man mindforger` documents the flags you rely on, and read the Getting started and User documentation pages on the wiki. The licence is GPL-2.0, so check how that interacts with your own distribution plans rather than assuming permissive terms.

## FAQ

### What is MindForger?

It is a Qt-based thinking notebook and Markdown editor, described in the README as a human mind inspired personal knowledge management tool. It runs as a desktop application with an outliner-style notebook view and a Markdown editor view.

### How do I install MindForger on Linux?

The README points to a Snap package as one option, and the command is `snap install mindforger`. It also links installation pages for Ubuntu, Debian, Fedora, Arch Linux, openSUSE, NixOS and FreeBSD, plus tarballs on the releases page.

### Is MindForger still maintained?

The last push to the repository was on 2026-09-14, and releases 2.1.0 and 2.2.0 shipped in September 2026. The README nevertheless states that the main development branch may not receive updates and that the author adds features or fixes bugs as needed.

### How does MindForger compare with Obsidian?

Both keep notes as local Markdown files, but MindForger is a compiled Qt application with its notebook behaviour built in, while Obsidian is extended through community plugins. MindForger is distributed through Snap, distribution packages and tarballs, which suits people who install from a package manager.

## Sources

- [dvorka/mindforger on GitHub](https://github.com/dvorka/mindforger)
- [License: GPL-2.0](https://github.com/dvorka/mindforger/blob/master/LICENSE)
- [Project website](https://www.mindforger.com/)
- [README](https://github.com/dvorka/mindforger/blob/master/README.md)
- [Releases](https://github.com/dvorka/mindforger/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/dvorka-mindforger