RootMind 2.6.0

Added

• POST /query/stream (#65): the same question as POST /query, with the agent's steps as server-sent events while it works: a start event (iteration limit, provider, model), one step event when a model or tool call starts and when it ends (the tool and its arguments, hits and the names of the files found, the windows read, duration, tokens), then result (the POST /query body) or error. A comment line every 10 seconds while a step runs tells a long step from a lost connection. Closing the connection cancels the question: no further model or tool calls start (a model call already sent finishes in the background and its result is discarded). Steps carry no document text. POST /query, the command line and MCP are unchanged.
• Desktop: the chat shows the agent's steps while a question runs (#65): each model call (step n of the limit), search (terms, file type, hits and the first file names), listing and read (file and page), with a running timer on the current step, so a long step is visibly working and the bounded loop is visible. After the answer the steps stay with it, collapsed ("How it searched: 5 steps, 8.9 s"). Stop now ends the question in the service too, and the message says after how many steps; steps that were running are marked as stopped. Instead of the 15-minute limit for a whole question, the app gives up only after two minutes without any sign from the service. With a backend without POST /query/stream (older than this release) the app asks as before, without steps.

Fixed

• A full-text search could take minutes on an index with very large documents (#65): highlighted snippets were computed for every row ranked above the deepest returned result, including large spreadsheet and CSV exports that a file type or folder filter dropped afterwards. On a real index (18,811 documents, 2.1 billion characters) one agent search for "Sehr geehrte" Schulz with a PDF filter took over nine minutes. Snippets are now computed only for the results that are returned; which documents are found, their order and their snippets are unchanged.

---

Downloads

File	What it is
RootMind-Setup-x64.exe	The Windows app with its background service (42.0 MB). Installs for all users of the computer and sets up the service for your account; needs one administrator approval, no Python.
RootMind-amd64.deb	The Linux app for Ubuntu and Debian: sudo apt install ./RootMind-amd64.deb. On its first start it sets up its background service as systemd user services of your account; no root needed for that.
RootMind-x86_64.rpm	The same for Fedora and openSUSE Tumbleweed: sudo dnf install ./RootMind-x86_64.rpm (openSUSE: sudo zypper install ./RootMind-x86_64.rpm).
RootMind-x86_64.AppImage	The same as an AppImage for other distributions, without installation: chmod +x RootMind-x86_64.AppImage, then run it (needs FUSE 2, libfuse2).
rootmind.mcpb	RootMind for Claude Desktop: double-click it and Claude Desktop installs it. Needs RootMind installed with Serve MCP over HTTP on (the default).
rootmind-backend-windows-x64.zip	The backend on its own for Windows, for the command line and servers. Not needed for the app.
rootmind-backend-linux-x64.tar.gz	The backend on its own for Linux (x86-64, glibc 2.35 or later), for the command line and servers. Not needed for the app.
SHA256SUMS.txt	SHA-256 checksums of these files.

Verify the download

The binaries are not code-signed yet. On the first start, Windows SmartScreen may show "Windows protected your PC" (choose More info, then Run anyway), and Smart App Control, when it is on, may block them; it has no exception for a single app. Check the files before you run them. The hash must match the line for the file in SHA256SUMS.txt:

(Get-FileHash .\RootMind-Setup-x64.exe -Algorithm SHA256).Hash.ToLower()

sha256sum --check --ignore-missing SHA256SUMS.txt
gh attestation verify RootMind-Setup-x64.exe --repo cgaeking/rootmind

Every file has a build provenance attestation that ties it to this repository and to the workflow run that built it.

Code signing policy

See CODE_SIGNING.md: the binaries are not code-signed yet; what will be signed, team roles and the privacy policy.