Claurst Open source

What it does

Claurst is an open-source, multi-provider terminal coding agent written in Rust. It began life as a clean-room reimplementation of Claude Code's observed behavior — built from an independently produced specification, never the original source — and has grown into its own TUI pair-programmer with a companion mascot ("Rustle"), chat forking, memory consolidation and a plugin system.

What is inside

• A rich terminal UI for interactive coding sessions, with no telemetry or tracking by the maintainer's own account
• Multi-provider AI routing across Anthropic and other providers, plus an experimental "Free Mode"
• /goal for pursuing a multi-turn objective instead of stopping after one turn, and an "ultracode" effort mode that fans work across subagents, swarms and background tasks
• /share for posting sessions as unlisted GitHub Gists, and a headless one-shot mode for scripting
• Agent Client Protocol (ACP) support, so editors that speak ACP can host it as a native agent

Pricing

Free and fully open source under the GPL-3.0 license. There is no paid tier; you bring your own API key or provider credentials.

Works with

Any editor or environment that speaks the Agent Client Protocol — Zed, Neovim and JetBrains IDEs are named integrations — in addition to running standalone as a terminal TUI or in headless/scripted mode.

How to install or connect

# macOS / Linux
curl -fsSL https://github.com/kuberwastaken/claurst/releases/latest/download/install.sh | bash

# Windows (PowerShell)
irm https://github.com/kuberwastaken/claurst/releases/latest/download/install.ps1 | iex

# via npm
npm install -g claurst
npx claurst

Model providers are configured afterward via the /connect command or a settings file.

Maintenance and safety

10.3k+ GitHub stars and commits within the last month show active development, though the project is still officially Beta (v0.1.7) and its own README flags /share, Free Mode, /goal and "ultracode" as experimental. Every tool permission is routed through ACP's session/request_permission, so a hosting editor can show a native approval dialog before the agent acts.

Who should use it

Developers who want a fast, open-source, multi-provider terminal agent that plugs into an existing ACP-aware editor rather than running in isolation — and who are comfortable running beta software with some features still marked experimental.