A terminal agent with its own identity
Claurst started as a clean-room reconstruction of Claude Code behavior, based on a written specification rather than copied proprietary source. It has since become a broader terminal coding agent. The Rust binary can inspect a repository, edit files, call shell and other tools, maintain conversations, fork chats, consolidate memory, use plugins and MCP servers, and route work through multiple model providers. Its full-screen terminal interface is a major part of the product rather than a thin wrapper around prompts.
Version 0.1.7 is explicitly a beta. The maintainers say the core agent, provider routing, and TUI are suitable for daily use, while sharing, Free mode, persistent goals, and the highest-effort ultracode workflow are experimental. Take those labels literally. They describe areas to test, not guarantees of better results.
Installation is the easy part
Release archives cover x86-64 Windows, x86-64 and Arm Linux, Intel and Apple Silicon macOS, and include checksums. Shell and PowerShell installers place the binary under the user's Claurst directory and update PATH; npm and Bun packages download a matching binary during installation. The direct archives are around 14 MB. Pinning a version is supported, which is preferable to following the latest beta automatically on a team machine.
A source build starts under src-rust with Cargo. Voice support pulls in system audio requirements, while --no-default-features builds without microphone functionality for headless or Raspberry Pi environments. None of this is unusually difficult.
First use needs a provider API key, such as ANTHROPIC_API_KEY, or configuration through /connect. The README advertises an experimental Free option, but does not turn model inference into a local operation. Claurst claims no tracking or telemetry; code and prompts still go to whichever external model endpoint you configure. Read that provider's retention and training terms, limit credentials, and exclude secrets just as you would with any coding agent.
The permission boundary needs work
Coding agents are powerful because they can read a tree, modify files, and execute commands. That makes repository trust a core security feature, not optional polish. Open issue 389 demonstrates two v0.1.7 paths controlled by a checkout's .claurst/settings.json or JSONC file. A UserPromptSubmit hook can run through the operating-system shell when the user submits a prompt, and a configured skills URL can cause an unconfirmed Git clone when /skills runs. The report says neither path presents a separate trust or content-change confirmation.
The shell hook is the decisive concern. A developer can clone an unfamiliar project, launch Claurst to ask what it does, submit an innocent prompt, and execute a command planted in project settings as their own user. Until a trust gate lands and is released, inspect .claurst before starting in outside code. Better still, use a disposable container or virtual machine with no valuable tokens, SSH agent, cloud credentials, or writable parent directories.
Issue 203 describes path traversal in MCP OAuth token filenames derived from an unchecked server name. It was generated by an automated audit and asks maintainers to verify it. Pull request 332 proposes rejecting separators, but remained open when researched. This should not be presented as a confirmed exploit; it is another reason to treat MCP server configuration and token storage as sensitive beta surfaces.
A lot of interface in an early release
Claurst offers more than the common chat-and-diff loop. Sessions, chat forks, goals that continue across turns, subagents, team-style swarms, background tasks, plugins, MCP, voice, browser-related commands, configurable effort, reviews, checkpoints, permissions, and sharing all appear in the command surface and release history. Experienced users may enjoy having those controls visible in the TUI. New users may struggle to identify which combination is dependable.
Open issue 382 reports that /session displays an empty window on macOS even while session files exist. Issue 172 says an attempt to solve a Chinese TUI cursor problem terminated after reading too many files. Issue 47 reports shortcuts failing with Ukrainian and Russian keyboard layouts. These reports are narrow and may depend on old versions or specific environments, but they reveal the less glamorous work still required around persistence, context budgeting, and international input.
ACP support is strategically useful because it separates the agent engine from the interface. The implementation currently advertises a defined subset of session methods and routes tool permissions through the editor. Confirm that your editor exposes every approval and that cancellation actually stops child processes before relying on it. Protocol compatibility can be partial even when initialization succeeds.
Project health and licensing
Claurst had 10,230 stars, 39 open issues and pull requests, and a GPL-3.0 license when researched. The last repository push was July 31, 2026, while issue and pull-request discussion continued into August. The latest release, v0.1.7, arrived July 6 with binaries for five targets and a very large set of direct commits. Development is active, though the time since the last push is longer than the daily cadence seen in some projects in this group.
The GPL license is friendly to users and contributors but matters to distributors building modified versions. The clean-room explanation is the project's position about its relationship to Claude Code, not legal advice or a guarantee for adopters. Organizations concerned about that provenance should have counsel assess it rather than treating README precedent citations as a clearance.
Should you switch?
Claurst is worth a protected trial if you want multi-provider choice, a dense terminal interface, or an ACP agent that is not tied to one editor. Use a pinned binary, a trusted repository, a limited provider key, explicit tool approvals, and isolation from personal credentials. Its native packaging and provider flexibility are meaningful advantages.
Do not switch a whole team yet. The unresolved project-settings execution path is too important, and the many experimental features widen the test surface. Claude Code, Codex, Gemini CLI, and Aider each offer a clearer supported or mature path for their core workflows. Claurst could become a distinctive open agent, but v0.1.7 is best approached as promising beta software whose permission model you verify yourself.