MindForger: a Qt and C++ thinking notebook with a Markdown editor attached

The problem MindForger targets: notes you cannot find or relate

The README opens with a list of complaints rather than a feature list: documents, sketches and remarks spread across the file system, the cloud, the web and Post-it notes; fear about the privacy of that material; the inability to find a note again after writing it; and no sense of how notes relate to each other. That framing sets the audience. MindForger is aimed at a single person keeping private remarks such as ideas, personal plans, gift tips, how-tos, dreams, business vision, finance strategy and auto coaching notes. It is not a team wiki, not a shared knowledge base and not a publishing pipeline. The homepage is mindforger.com, and the README describes the application in two ways: as a thinking notebook inspired by how a human mind works, and as a Markdown editor or IDE that respects privacy. Those two descriptions are the two halves of the product, and the repository layout reflects them: a Qt project file at the top level, an app/ directory, a lib/ directory, a man/ directory for the manual page, and a doc directory. Everything in the README assumes local storage and a desktop session.

How the notebook, the outliner and the Markdown editor fit together

The README does not publish an architecture diagram, so the mechanism has to be read from what it does state. There are two named surfaces: the Thinking Notebook, described as a personal knowledge management tool, and the Markdown Editor, described as an open, free and well performing Markdown editor or IDE. The release notes add the structural vocabulary. Version 2.0.0 is titled Wingman, Notebooks Tree and Libraries, which tells you that notes are grouped into notebooks, that notebooks are presented as a tree, and that libraries exist as a container above them. Version 2.1.0 adds autolinking colorization, so links between notes are recognized and highlighted rather than typed as explicit syntax. Version 2.2.0 adds Rewrap, Snap, WebEngine, KaTeX and Mermaid, which means rendering of math and diagrams happens inside the application through an embedded web engine, and that paragraph reflow is a first-class editing command. The practical consequence is that the outliner and the editor are two views over the same note, and the value of the tool comes from the links between notes rather than from any single document. If you only want a text editor, the notebook layer is overhead you will not use.

Installing MindForger and writing a first linked note

The README points at wiki pages for macOS, Windows, Ubuntu, Debian, Fedora, FreeBSD, Arch Linux, NixOS, openSUSE and WSL, and at the Snap Store for a Snap package. It also lists a tarball option pointing at the GitHub releases page, and nightly builds for macOS (.dmg), Windows (installer) and a tarball produced by the Ubuntu workflow. On a system with snapd, the Snap route is the shortest path named in the README. The command below is the standard snap install invocation for the package name shown in the Snap Store badge.

snap install mindforger

After it completes, the application should be available as mindforger in your desktop menu or from a shell. If you prefer a build from source, the repository ships mindforger.pro at the top level, which is the qmake project file for the Qt build, and the wiki has separate build pages for macOS, Windows, Ubuntu, Debian, Fedora, Gentoo, NixOS and WSL. There is also a documented container path, described in the README as build and run in container.

git clone https://github.com/dvorka/mindforger.git
cd mindforger
qmake mindforger.pro
make

The README also notes that a manual page is installed, so once the binary is on your PATH you can read the same reference offline.

man mindforger

For a first real use, open the application, create a notebook, and write a note in Markdown. The 2.1.0 release added autolinking colorization, so a reference to another note is colored once the target exists. The 2.2.0 release added Rewrap, which reflows a paragraph to the current width, and Mermaid and KaTeX rendering, which means a fenced Mermaid block or inline math is rendered through the embedded WebEngine view rather than shown as raw text. The README does not document an import command for existing note collections, so moving an existing folder in is a manual step you should test on a copy first.

Where MindForger is the wrong tool

The README's own honesty section is the clearest limitation. It states that the main development branch may not receive updates, that the author adds a small feature or fixes a bug as needed, and that the project is not and will not be dead. It also states the IAGNI principle, I Am Gonna Need It, as the reason a GitHub issue or bug report may not be implemented. Read plainly, that means feature requests are not a queue you can join. If your team needs a committed release cadence, a deprecation policy or a support contract, this is the wrong project, and the README says so before you install anything. The second limitation is scope. Topics on the repository include linux, macos and windows, and installation is documented for desktop distributions and WSL, but there is no mobile client, no web service and no sync layer in the README. A third is the interface stack: 2.2.0 brings in WebEngine for KaTeX and Mermaid, which means rendered math and diagrams depend on an embedded browser component being present and working in your build. If your distribution splits WebEngine into a separate package, a source build can produce an editor that shows the raw block instead of the rendered output. The README does not document that failure mode, so treat it as something to check after installing rather than something the project promises to handle.

MindForger compared with Obsidian and with plain Markdown files

The comparison people search for is MindForger versus Obsidian, and the difference is in distribution and governance rather than in the note format. Both keep notes as Markdown files and both build links between notes. Obsidian is a closed-source application distributed as a binary with a plugin ecosystem and a paid sync service; MindForger is GPL-2.0 C++ and Qt, with source, a qmake project file and distribution packages, and the README lists no plugin system and no sync. The second alternative is not an application at all: keeping Markdown files in a directory and editing them in any editor. That approach wins on longevity and on tooling, since grep, git and any editor work on the same files, and it loses exactly what MindForger adds, which is the notebook tree, the outliner view and autolinking colorization that shows relationships while you read. A reasonable split is to keep the files in git regardless of which editor you use, because the README describes notes as local files and does not describe a proprietary store. That keeps the exit path open if the project's update cadence stops suiting you.

Licence, packaging and the real cost of keeping MindForger current

MindForger is GPL-2.0. The LICENSE file is at the top level, and the repository also carries a licenses/ directory, which is where third-party component licences usually live in a Qt project of this shape. For individual use the practical consequence is that you can run, study and modify the code, and that if you distribute a modified binary you take on the obligations the GPL-2.0 text sets out. Linking the application into a proprietary product is a different question, and the answer depends on the GPL-2.0 terms as they apply to your distribution, not on anything the README says. That is a question for a lawyer, and this article does not answer it. On maintenance, the last push to the default branch was on 2026-09-14, and the two most recent releases are 2.2.0 on 2026-09-13 and 2.1.0 on 2026-09-03, so the codebase is currently receiving changes. Note the gap before that: 2.0.0 is dated 2024-02-16. The upgrade cost is therefore not a steady drip. It is long quiet periods punctuated by releases that add dependencies, and 2.2.0 is exactly that kind of release, since it brings in Snap packaging and WebEngine alongside Rewrap, KaTeX and Mermaid. If you build from source, budget for a Qt and WebEngine toolchain, and if you install from a package, budget for the lag between a release and your distribution picking it up. The README also points at Repology for packaging status, which is the place to check before assuming your distribution is current.

Editorial conclusion

Adopt MindForger if you want a single local Qt application that holds an outliner, a Markdown editor and a notebook tree over plain files, and you accept that the README frames the project as one person's daily tool rather than a roadmap with contributors. Do not adopt it if you need sync, mobile clients or a plugin ecosystem, because none of those appear in the README or the repository layout. Verify first that a package exists for your distribution or that you are willing to build from source, and read the Getting started and User documentation pages on the wiki before you move existing notes into it, since the README does not document rollback or an import path.

Frequently asked questions

Official sources

1. dvorka/mindforger on GitHub
2. License: GPL-2.0
3. Project website
4. README
5. Releases