The interface where you curate the context.
The MCP server answers single questions. The desktop application is where a solution becomes a document, and where you decide what belongs in it.
Manual on GitHub ↗Back to the overviewGitHub Releases ↗Reference manual (PDF)The documentation on GitHub is authoritative and current. This page only summarises it.
What belongs in, and in how much detail
In the solution tree you choose per node: include, exclude or inherit, from the project down to a single file. The detail level ranges from the bare signature to the full source, and a token budget caps the size of the document.
What the desktop app brings along
Templates for the task
Built-in templates bundle a context strategy, for example for refactoring, debugging, tests or getting to grips with unfamiliar code. Each one can be adjusted.
Templates on GitHub ↗Findings along the way
Checks run while a solution loads: code quality, security, async, design and architecture, each finding with the affected places and a way to fix it.
Findings catalogue on GitHub ↗SAP Business One included
A layer profile for SAP Business One add-ons, an exclusion list for the COM interop namespaces and a test description for typical mistakes with the DI API.
Profiles on GitHub ↗What the desktop application does not do
- Windows only - for Linux and macOS there are the command line and the MCP server
- MSBuild is required - a .NET SDK or Visual Studio has to be installed
- No replacement for the IDE - no completion, no debugging, no refactoring
- Open trusted projects only - loading runs the solution's build logic and its source generators, exactly as Visual Studio does
None of it goes outside: no usage reporting, no update check, no crash reports. The application connects only to a language model you have set up yourself: for a run, for the connection test, and on the first load of a new solution while its automatic setup is switched on. For a newly registered solution it is.
Everything else is on GitHub
The desktop app manual describes every view: the solution tree, sessions and snapshots, findings, model profiles and settings.
AICB on GitHub ↗To the MCP serverQuestions about the desktop app or using it in your team? Send an enquiry



