pickfit

BrowseLocal AI tools

HilbertRaum

Private offline AI workspace to chat, query documents and Wikipedia locally.

Tested on macOS and Linux

Use it

macOS arm64

You need first

  • Runtimes: Node >=22.12
  • System packages: libgomp1
  • A GPU is optional
  • At least 8 GB of RAM
  1. download mac-arm64 .app.zip from GitHub releases

    mkdir -p ~/Applications && cd /tmp && curl -fL -o HilbertRaum.zip https://github.com/HilbertraumAI/HilbertRaum/releases/download/v0.1.64/HilbertRaum-0.1.64-mac-arm64.app.zip && unzip -q HilbertRaum.zip && ls -lh
  2. copy .app to ~/Applications and remove quarantine

    rm -rf ~/Applications/HilbertRaum.app && cp -R /tmp/HilbertRaum.app ~/Applications/ && ls -ld ~/Applications/HilbertRaum.app && xattr -dr com.apple.quarantine ~/Applications/HilbertRaum.app

Open HilbertRaum from your Applications folder.

Linux x86_64

You need first

  • Runtimes: Node >=22.12
  • System packages: libgomp1
  • A GPU is optional
  • At least 8 GB of RAM
  1. download Linux AppImage v0.1.64

    curl -fL -o HilbertRaum-0.1.64.AppImage https://github.com/HilbertraumAI/HilbertRaum/releases/download/v0.1.64/HilbertRaum-0.1.64.AppImage
  2. make AppImage executable

    chmod +x HilbertRaum-0.1.64.AppImage

Open HilbertRaum from your Applications folder.

What it does

  • Chat with an AI that runs on your computer
    Not tested
  • Ask questions about your documents with citations
    Not tested
  • Ask an offline Wikipedia using knowledge packs
    Not tested
  • Translate text and whole documents on your computer
    Not tested

How far pickfit got

macOS arm64

  1. Installs
  2. Opens to its setup screen
  3. 0 of 4 features work
  4. Works offline

Linux x86_64

  1. Installs
  2. Opens to its setup screen
  3. 0 of 4 features work
  4. Works offline

Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • chat with a local AI offline
  • ask questions about private documents with citations
  • ask an offline Wikipedia via ZIM knowledge packs
  • transcribe audio files locally
  • translate text and whole documents locally

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

macOS arm64

It opens to its first-run screen

  • Replayed from scratch
  • Checked on 1 Nov 2026
  • Version 0.1.64

When pickfit opened it, its first-run (setup) screen rendered. That shows it installs and starts; pickfit did not use any of its features. The launch passed again with the network off.

Differences the test machine hit

  • README: macOS .app is unsigned; allow under System Settings Privacy & Security Open Anyway
    In the test: removed quarantine with xattr -dr com.apple.quarantine before launch to bypass Gatekeeper

Linux x86_64

It opens to its first-run screen

  • Replayed from scratch
  • Checked on 1 Nov 2026
  • Version 0.1.64

When pickfit opened it, its first-run (setup) screen rendered. That shows it installs and starts; pickfit did not use any of its features. The launch passed again with the network off.

Differences the test machine hit

  • README: On Linux run chmod +x HilbertRaum-<version>.AppImage once before starting it
    In the test: AppImage also needs --appimage-extract-and-run (no FUSE) and --no-sandbox on this box (Chromium/Electron sandbox fails without user namespaces)
  • README: npm run dev launches app in developer/demo mode
    In the test: Prebuilt AppImage runs with offlineMode true and demoMode false; chat blocked by 'No model is running' until llama-server + model downloaded
  • README: Workspace creation is one-time
    In the test: Workspace persists in ~/.config/@hilbertraum/desktop/ ; to retry creation must rm -rf workspace and config dirs

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.