Home

A local-first, provider-agnostic agentic coding companion

One Rust core · three faces — a terminal UI, a web UI, and a phone app.

🌸  rose → lavender → violet → cyan — the Living Rose palette that runs through every surface  🩵

---

Welcome to the blumi wiki — everything you need to install, configure, and run blumi across your terminal, browser, phone, and a whole fleet of machines. blumi is a single Rust binary whose UI-agnostic core emits one typed event stream, so every surface shows the same live session.

⭐ Enjoying blumi? Star it on GitHub — it genuinely helps others find the project.

🚀 Get started in ~60 seconds

# 1. Install (builds the single binary; also sets up the Node + uv helpers)
curl -fsSL https://raw.githubusercontent.com/ankurCES/blumi-cli/main/install.sh | sh

# 2. Pick a provider + paste a key (or point at a local model)
blumi login

# 3. Go — the terminal UI
blumi                 # or:  blumi web   (browser UI)   ·   blumi run "…"  (one-shot)

New here? Installation → Configuration → CLI Usage is the happy path.

🧭 Find your way

	Guide	What's inside
📦	Installation	One-line install, prerequisites, building from source
⚙️	Configuration	The complete settings.json reference — every section, field & default
⌨️	CLI Usage	Commands, the TUI, slash-commands, the autonomous loop
🌐	Gateway	blumi serve + the messaging-bot gateway as always-on services
📱	Mobile App	Connect the blugo phone app over your Wi-Fi
🕸️	Grid (distributed) · Demo	Run many machines as one fleet that hands off tasks
🧠	Memory & Knowledge	Semantic memory (RAG) + a code knowledge base
🎙️	Voice	Speak to / hear blumi (STT + TTS)
✨	Self-Management	Self-edited config/skills, routing, hooks, notifications, self-healing
🛠️	Development	Architecture + hacking on blumi
🩹	Troubleshooting	When something's off
❓	FAQ	Why blumi & how it works — for decision-makers and developers

💡 What blumi can do

• 🖥️ Three faces, one session — a crush-inspired terminal UI, an embedded React web UI, and blugo, a Flutter phone app that mirrors the TUI (and folds gracefully on foldables).
• 🔌 Bring your own model — Anthropic, OpenAI (and any OpenAI-compatible endpoint), Gemini, Azure Foundry, or a fully local server. Switch per-invocation.
• 💸 Cost-aware routing — auto-route simple turns to a cheap model and hard ones to the flagship; watch the $ saved.
• 🧠 Memory & code knowledge — semantic long-term memory with RAG recall + a local code index, fully offline via a bundled embedder.
• 🕸️ The grid — several machines sharing one secret form a fleet; your phone drives work that runs across all of them.
• 🤖 Always-on & autonomous — an always-on gateway, an autonomous task loop, proactive discovery, and completion notifications (desktop / bot / phone / browser).
• ✨ Self-managing — it can author its own skills, edit its own (validated) config, reload in place, and self-heal failed steps into learned fixes.

🧩 The three common setups

1. Local (one machine). Install, blumi login, run blumi (TUI) or blumi web. Nothing else needed. → Installation · CLI Usage
2. Gateway + phone. Run blumi serve as an always-on service; connect blugo over Wi-Fi (it auto-discovers the gateway on your network). → Gateway · Mobile App
3. Grid (many machines). Install on several machines, give them the same grid.secret; they auto-discover and hand off tasks. Any node — or your phone — drives the fleet. → Grid

📎 Conventions used here

• Config lives in ~/.blumi/settings.json (global) + a per-project .blumi/ overlay.
• Services are com.blumi.serve / com.blumi.gateway (launchd, macOS) or blumi-serve / blumi-gateway (systemd user, Linux).
• Secrets — API keys, the grid secret, the gateway password hash — stay in settings.json (mode 0600), never in git.

Install · Configure · CLI · Gateway · Mobile · Grid · Memory · Voice · Self-Management · FAQ

_{Made with 🌸 — Apache-2.0 · github.com/ankurCES/blumi-cli}