Vol. I · No. 579Rochester, New York, Thursday, September 24, 2026Desktop · Page B12
All workSection B · Page B12

DesktopFreeAI

An App Store for Open-Source AI, No Terminal Required

A Rust and Tauri desktop app that installs and launches 46 open-source AI tools with one click and one shared key.

Graphic5 steps
  1. CatalogJSON entry with prereqs, install steps and launch spec
  2. CheckDetects uv, node, git and Docker
  3. InstallRust runs each step and streams logs to the UI
  4. LaunchPTY terminal, webview after a port check, or background service
  5. KeyOne OpenRouter key from the keychain, mapped into the tool's env
What happens inside FreeAI, in order.Graphic: The Sahil Bachu

There are great open-source AI tools out there: Aider, OpenHands, ComfyUI, Open WebUI, n8n. Most people never try them because step one is a README full of virtualenvs, Docker and git clones. FreeAI is my fix for that. It's a desktop app store for open-source AI. Pick a tool, click install, click launch.

Every tool is an entry in a JSON catalog: its prerequisites, its install steps, how to launch it and how to hand it an API key. Right now there are 46 tools across 8 categories, from coding and audio to research and automation. Adding a tool means writing a catalog entry, not code.

Adding a tool means writing a catalog entry, not code.

The Rust backend is the real work. It runs step types like uv venv, uv pip, git clone, docker pull, docker compose, npm and plain downloads, and streams progress back to the UI as it goes. Commands run through spawn_blocking so a slow install never stalls the tokio runtime. It also checks for uv, node, git and Docker (including whether the Docker daemon is up) and can install uv for you.

Launching depends on the tool. Terminal tools open in an embedded xterm.js terminal over a real PTY. Web tools start in the background, and the app polls their port before opening a webview, so you never land on a dead page. Services run quietly with a status panel. One OpenRouter key lives in the OS keychain and gets mapped into each tool's environment, so you set it once and never paste it into a config file.

The whole thing came together on a single day, in 10 commits, one phase per commit. It still has placeholder icons, only a debug build and the default Vite README. The value ended up in the boring parts: detecting prerequisites and streaming install logs are what would let a non-developer use it without asking me for help.

More from The Work

See all 25

Audio AI

It Hands You the Synth Patch, Not the Song

A desktop sound-design assistant that listens to your track, reads your description and writes a real Surge XT preset.

Drop in a clip from your track, type something like "dark slow riser", and WingmanPro writes an editable Surge XT synth preset instead of generated audio. Audio models read the clip and an LLM writes the patch.

Continued on Page B14

Desktop

A Desktop App That Sits Through Lectures With You

Academic Companion turns syllabi, assignment PDFs and recorded lectures into deadlines, summaries and a chat over everything in a class.

A desktop class manager for students. Drop in a syllabus and it pulls out deadlines and exams. Record a lecture and it transcribes and summarizes it. It can run fully local with Ollama or use Groq in the cloud.

Continued on Page B7

Mobile AI

Every Icon on This Homescreen Started as a Sentence

A phone homescreen where every icon is a mini-app that Claude wrote and a build server compiled from a plain-English description.

Describe a tool, Claude writes it as React code, a build server bundles it, and it runs on your phone in a sandbox. Each mini-app gets storage, the mic, the calendar, the camera and AI through a native bridge.

Continued on Page B10