Qbit CLI
An open-source Rust and Tauri agentic terminal: bring your own model keys, a unified timeline, and transparent tool calls.
- 127 ★ on the repository
- Last commit
Extended access
Why this level
- The app executes project code and commands with local-machine rights, and accepted edits land straight in the working directory.
Install
- Works in
Manual install
brew tap qbit-ai/tap && brew install --cask qbitThe first install method from the README, for macOS.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The app executes project code and commands with local-machine rights, and accepted edits land straight in the working directory.
This is third-party code. Review the repository files before installing.
What it does
Qbit is a Rust and Tauri 2 desktop app that puts the model conversation, tool output and terminal into one timeline. Projects open through quick-access shortcuts, and the model is picked from several providers with no Qbit subscription of its own — only your own API keys. Model-generated edits can be reviewed and tweaked right in the UI before they apply, every tool call expands with a full trace, and sub-agents get their own detailed view of their tasks and results. Built-in git integration shows diffs, and both MCP servers and the project's own agent skills are supported.
Who it is for. Developers who want an agentic terminal with full tool-call transparency and their own model keys, with no subscription to a separate service.
Good fit when
- Answers from different models need comparing on the same task without switching between each provider's own app.
- A model-generated edit needs a manual tweak before it applies, rather than an all-or-nothing accept or revert.
- A sub-agent is running a subtask, and its own separate progress matters more than the overall session log.
- Git diffs need checking right inside the tool, without switching to a separate git client.
Not a fit when
- No API keys of your own exist for any model provider: Qbit doesn't bundle a model or subscription, only the shell around one.
- A hosted cloud service with no local macOS or Linux install is needed: this is a desktop app that runs locally.
- A mature, frequently updated codebase matters most: check the README and GitHub commit history before counting on active support right now.
Example request
Open this project, compare Claude's and GPT's answers to the same refactoring task, and show the diffs side by side.Limitations
Qbit bundles no model and takes no subscription — you need your own API keys with chosen providers, and their cost runs separately from the app itself. The Linux release build is assembled by hand from the release archive, including manually installing the binary into `PATH`; other systems need a source build via `just`. The repository's last commit is dated 2026-03-26, with no public activity in the codebase since. MIT licensed; Model Context Protocol support and MCP integration are covered in a separate documentation section.
How to disable. On macOS, remove it with `brew uninstall --cask qbit` (if installed via Homebrew) or drag it to the trash. A source-built binary is removed manually from the build directory.
FAQ
How do I install Qbit on macOS?
`brew tap qbit-ai/tap`, then `brew install --cask qbit`. That's the first install method from the README.
Do I need a subscription to Qbit itself?
No. The app is free and open source, but it needs your own API keys with chosen model providers — Qbit doesn't bill you for them.
How do I install on Linux without building from source?
Download the release archive with curl, extract it with `tar -xzf`, then copy the binary into `/usr/local/bin` with `sudo install -m 755`.
Can I see exactly what a sub-agent is doing?
Yes, sub-agents get their own detailed view of tasks and results, not just the main session's general log.
Does Qbit support MCP servers?
Yes, a dedicated documentation page (`docs/mcp.md`) covers wiring up MCP servers alongside the project's own agent skills.
Discussion
No questions or reviews yet.
Related
CLI toolsTwo Rust commands for the terminal: qq answers a quick command-line question, and qa performs a single step with files and commands
A Rust coding agent with a native GUI, a terminal mode, an ACP mode for Zed and an MCP server
A coding agent for the terminal and desktop: it does not count "done" without tests or a diff and works with DeepSeek, GLM, Kimi, Claude, Codex and Gemini
An MCP server that gives an agent screenshots, DOM, logs and IPC of a running Tauri v2 app and lets it click through the interface
A Rust SDK for coding agents and the ready-made abstract CLI: REPL, 34 tools, MCP, graph memory, Anthropic and OpenAI, JSON output for CI
A Rust CLI for language models from a terminal: an answer, an image, a video, OCR, commit messages and shell commands
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Qbit (this card) | no | 127 | |
| Clisbot | no | 130 | Clisbot orchestrates several third-party CLI agents in parallel; Qbit is a standalone terminal with its own UI over a chosen model |
| OpenClaw | no | 393,956 | a different feature and provider set; the common ground is open code and no lock-in to a single model subscription |
README in short
The README emphasizes transparency and no subscription, with separate docs on workspaces, agent modes, tool use, MCP, and the project's own SWE-bench evaluations.