Keep project documents, decisions, and a work board together in a desktop workspace. Connect your existing AI tools, keep your Markdown in your project folder, and decide when the work is done.
Free, with the source code available under the FSL.
Choose the folder where your project lives. It can be an existing repository; your code and documents stay where they are.
Include the Markdown documents you already have, and capture planned work as tickets on the board.
Connect a compatible AI tool and ask it to read the project and work on a ticket.
MCP is the connection that lets a compatible AI tool read and update this project.
The tool hands finished work back to Verification with what it changed and checked. You review it in your usual tools and decide whether it is done.
Documents stay ordinary Markdown files in your project folder. Include the documentation you already have where it is, without moving it into a new structure. Read and review it in Knightbook, and edit it in the editor you already use.
Documents and tickets give the next session, yours or an AI tool's, the context the last one left behind. The board shows where each piece of work stands and what it depends on.
Example ticket: Export the board as CSV
An AI tool moves finished work to Verification with the evidence it gathered. Passing checks is not acceptance: you decide whether the work is done. Reviewing content is a separate decision, recorded on its own.
No. Planning and coding happen in the AI tool you already use. Knightbook keeps the project context and work records that tool reads and updates.
Yes. Choose its local folder. Setting it up adds a .projectspace folder for Knightbook's records; your code and existing Markdown stay where they are, and you choose which documents to include.
In the project folder you choose. Your documents stay where they are, and Knightbook's tickets and records sit beside them in .projectspace. An AI tool you connect, and its provider, handle what they read under their own terms.
Read and review them in Knightbook, and edit them in your usual editor; Knightbook shows the changes when you come back to it. Editing formatted documents inside the app is not part of the current release.
No. Your AI tool starts Knightbook's connection itself, separately from the window, so it can work in the projects you have allowed while Knightbook is closed. When you open the window again, it shows what changed. Checked so far with Claude Code on Linux, not yet on Windows or macOS.
No. Your project is ordinary files in a folder. Move them between computers yourself, for example with Git; Knightbook does not sync them or run Git for you.
There are installers for 64-bit Windows 10 and later, macOS 13 and later on Apple silicon and Intel, and 64-bit Debian and Ubuntu Linux. Knightbook connects to AI tools that support MCP, and copies a ready-made configuration for Claude Code, Claude Desktop, Codex and OpenCode. So far it has been tested with Claude Code on Linux; the installers have not yet been tried on a clean computer for each system. If something does not work, report it on GitHub Issues.
Yes, Knightbook is free. Its source code is public under the Functional Source License (FSL-1.1-ALv2): you can use, change and share it for any purpose except offering it, or something built from it, as a competing commercial product. Two years after each version is released, that version is also available under the Apache License 2.0.
Free, with the source code available under the FSL.
