Code Assistant CLI
A Rust coding agent with a native GUI, a terminal mode, an ACP mode for Zed and an MCP server
- 187 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The autonomous loop reads and changes project files and runs shell commands
- Browser mode acts as you on sites after login, and connected MCP servers widen the agent's access
Install
- Works in
Manual install
cargo build --releaseBuild from a repository clone with Rust installed. The binary lands in `target/release/code-assistant`.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The autonomous loop reads and changes project files and runs shell commands
- Browser mode acts as you on sites after login, and connected MCP servers widen the agent's access
This is third-party code. Review the repository files before installing.
What it does
Code Assistant is an autonomous coding agent written in Rust. It reads code, searches the project, edits files and runs commands, showing what each tool actually returned to the model. It runs in four modes: `code-assistant` opens a native window on Zed's GPUI, `--tui` gives a terminal, `acp` connects the agent to editors like Zed, and `server` starts a headless MCP server for Claude Desktop. Model providers include Anthropic, OpenAI, Google Vertex AI, Ollama, OpenRouter, SAP AI Core, Groq, Cerebras, Mistral and more. The agent picks the tool-call syntax to fit the model: native function calling, XML tags or caret blocks. It offers per-project sessions with branching, sub-agents, permission tiers, a command sandbox and context compaction when the window fills up. When a project formats on save, the agent runs the formatter and reconciles its own edits with the result without rereading files. It keeps encoding, byte order mark and line endings as they were. Word, Excel, PowerPoint and PDF documents are read as Markdown.
Who it is for. Programmers who want an open Rust agent with a readable interface and a choice of provider, and Zed or Claude Desktop users who want to plug it in as an external agent.
Good fit when
- An agent loops on edits and the tool-call list shows what it handed the model at each step
- The project auto-formats on save and the agent's edits after the formatter usually fall apart
- Files sit in an old encoding or with CRLF line endings and cannot be rewritten into another format
- A web app is under test and the agent opens the browser itself while a human logs in without showing the agent the password
- You want a single agent for the window, terminal, Zed and Claude Desktop with shared provider setup
Not a fit when
- You need a vendor's own agent with its subscription: Code Assistant works with the API key of the provider you choose
- The platform is outside Windows, macOS and Linux and has no ready builds
- Team policy forbids agents from running commands on their own and there is no way to verify the sandbox and permission tiers
- You need long-term project memory: the author lists it as a direction, not a finished feature
Example request
Explain this repository's structure and find where payments are handledLimitations
- A provider API key or a local model is required: subscription sign-in is not described. Settings live in the Settings screen and JSON files.
- Ready builds exist for macOS (Apple Silicon and Intel), Linux x86_64 and Windows x86_64. Building from source needs Rust, a set of system libraries on Linux and the Metal Toolchain on macOS.
- Project memory, restricting tools to git-tracked files and fuzzy block matching are on the author's roadmap and not built yet.
How to disable. Quit the app and delete the binary or `.app`. For MCP mode remove the `code-assistant` entry from the Claude Desktop config, and for ACP the entry in `agent_servers` in Zed settings.
FAQ
How do I connect Code Assistant to Claude Desktop?
Open Settings, Developer tab, Edit Config and add a `code-assistant` server with the command pointing to the binary and the argument `server`. The README example sets `SHELL` to `/bin/zsh`. After a restart Claude Desktop gets the agent's tools.
How do I use Code Assistant in Zed?
Add a server under `agent_servers` in Zed's `settings.json` with the command `code-assistant` and the arguments `acp --model <name>`. The provider key goes into that server's environment variables.
What is format-on-save handling in Code Assistant?
When your formatter changes a file after an agent edit, Code Assistant runs it and reconciles the model's own changes with the result. Follow-up edits do not break and no tokens go to rereading files.
Does the agent see my password when logging in through the browser?
No. The browser session hands the login to a human, so the agent acts as you without seeing the credentials.
Which model providers are supported?
Anthropic, OpenAI, Google Vertex AI, Ollama, OpenRouter, SAP AI Core, Groq, Cerebras, Mistral and more. You pick one in Settings with suggestions for common options, with no JSON editing.
Discussion
No questions or reviews yet.
Related
CLI toolsA Python terminal coding agent in the manner of Claude Code: reads the repository, edits files, runs commands, with memory, sub-agents and MCP
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
Code graph and project memory in one Rust program: the agent gets excerpts with file and line citations
Over twenty skills for coding agents: MCP and hooks, plan mode, a bug-fix protocol, prompting and a bash safety hook
CodeGraph (Rust)
codegraph-rust
A Rust code graph for agents: four MCP tools show what an edit will touch, how the architecture fits together and where the fragile spots are
A Rust coding agent for the terminal with parallel agents, goals, Claude Code-format plugins and your own model endpoint.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Code Assistant (this card) | no | 187 | |
| goose | no | 56,269 | an open Rust agent with desktop, CLI and API and dozens of MCP extensions, while Code Assistant focuses on a transparent interface and format-on-save handling |
| OpenCode | no | 224,828 | a terminal and desktop agent with build and plan modes, while Code Assistant offers a GPUI window and an MCP server mode |
README in short
The page describes the agent, a quick start from a ready build and a source build. It then covers its differences: a readable interface, format-on-save handling, encoding preservation and document reading. After that come features, four launch modes with Zed and Claude Desktop examples, and a roadmap.