Skip to main content
株式会社オブライト
AI2026-08-106 min read

Reasonix: DeepSeek-Native Terminal Coding Agent (2026)

Reasonix is a DeepSeek-native AI coding agent for the terminal: a single MIT-licensed Go binary engineered around prefix-cache stability. As of August 2026 it has 33,538 GitHub stars. Here's how to install it, how it's configured, and how it compares to Claude Code, Codex, Aider, and Cline.


Reasonix (repository: DeepSeek-Reasonix) is an AI coding agent that runs in your terminal. It ships as a single Go binary with no runtime dependencies and is MIT licensed. What sets it apart is that it is engineered around prefix-cache stability — the repository description literally says "leave it running" — so it is built for sessions you keep alive for hours rather than one-off invocations. As of August 10, 2026 it has 33,538 GitHub stars and sits near the top of GitHub's weekly Trending list.

What It Does

Reasonix is the kind of agent you drive from the terminal in natural language, handing it code to explore, edit, and run. It supports both one-shot commands and interactive sessions, and the same agent is reachable from a desktop app, a browser, and a VS Code extension — not just the CLI. Because long-running work is the design target, checkpoints and undo are built in, and the agent can be run inside a sandbox.

- Single-binary distribution: written in Go with CGO_ENABLED=0; one command cross-compiles to six targets (darwin / linux / windows × amd64 / arm64)
- Multiple entry points: terminal (CLI/TUI), desktop app (macOS universal, Windows x64/ARM64, Linux x64), browser, and a VS Code extension
- Config-driven: providers, the agent, enabled tools, and plugins are all declared in reasonix.toml. No model is hardcoded
- Multi-model support: DeepSeek ships as a preset, and any OpenAI-compatible endpoint is a config entry rather than new code. Dual-model setups are supported
- Plugin system: MCP servers contribute tools, prompts, and resources; Extension Protocol v1 sidecars can additionally intercept runtime events and supply custom providers and structured UI
- Guardrails for long runs: checkpoints, undo, and sandboxed execution

The Design Bet: Prefix-Cache Stability

Most LLM APIs offer a prefix cache: if the beginning of a request matches the previous one, that portion is reused and discounted. Agents resend the same system prompts and file contents over and over, so whether that prefix survives or gets invalidated on every turn has a large effect on what you actually pay. Reasonix puts this single concern at the center of its architecture, combining cache control, stale output pruning, and an explicit context-compression tool so that the prefix stays intact even as a session runs long.

As for the payoff, the developer published a test showing an 85.2% prefix-cache hit rate on multi-turn chat, with the same scenario costing $0.000923 versus $0.015174 on Claude Sonnet — roughly a 93.9% reduction. Note that this is the developer's own measurement, not an independent reproduction. Savings depend heavily on the shape of your workload, so if you are evaluating Reasonix, plan to measure it against your own tasks.

Install and First Run

The CLI/TUI installs straight from a package manager. The desktop build is a download from the official distribution page, and the VS Code extension is added after CLI setup is complete.

# CLI / TUI (pick one)
npm i -g reasonix
brew install esengine/reasonix/reasonix   # macOS
reasonix setup                  # configure provider and model
reasonix                        # start an interactive session
reasonix run "your task here"   # one-shot execution
reasonix web                    # hand a CLI session off to the browser (added in v1.22.0)

Configuration and Plugins

Reasonix's behavior lives in reasonix.toml. Which provider to use, which tools are enabled, and which plugins load are all declarative, so swapping models never means touching Go code — any OpenAI-compatible endpoint is one added config entry. Extensibility comes in two flavors: MCP servers that contribute tools, prompts, and resources, and Extension Protocol v1 sidecars that hook into runtime events to supply custom providers and structured UI. The latter can be shipped as versioned plugin packages.

# VS Code extension (after CLI setup)
Extension ID: SivanLiu.reasonix-agent

# Building from source
Go 1.25+                       # CLI
Node 24+ / pnpm 10             # additional requirements for the desktop build

How It Compares to Other Coding Agents

Claude Code, OpenAI Codex, Aider, and Cline got here first, and against that field Reasonix reads as "the MIT-licensed option that centers DeepSeek and competes on cache efficiency." If your organization has already standardized on Claude or OpenAI, the depth of integration in Claude Code and Codex is the stronger argument; if you want everything to stay inside the editor, Cline fits; if you want a straightforward commit-to-Git workflow, Aider does. Reasonix earns its place when you are trying to hold down the cost of long sessions, or when you want to swap the underlying model from a config file.

ToolPrimary modelsDistributionLicenseNotable for
ReasonixDeepSeek-first, plus any OpenAI-compatible endpointSingle Go binary (CLI, desktop, VS Code)MITArchitecture built around prefix-cache stability; config-driven via reasonix.toml
Claude CodeAnthropic's ClaudeCLI, desktop, IDE extensionsProprietaryDeep integration with permissions, MCP, and Anthropic's workflow surfaces
OpenAI CodexOpenAI modelsLocal and cloudProprietaryWorktrees, approval modes, and sandboxing
AiderMultiple providersCLIOpen sourceWorkflow built around committing directly to a Git repository
ClineMultiple providersVS Code extensionOpen sourceConversational agent that stays inside the editor

What to Check Before Adopting It

Development is moving fast: v1.21.4, v1.21.5, and v1.22.0 all shipped across August 9–10, 2026, bringing reasonix web for handing CLI sessions to the browser, atomic-write session persistence, and MCP OAuth for remote MCP servers. The flip side is 1,004 open issues and a rapid feature cadence, so pinning a version is the sane way to put this in a production workflow. The cost claims, as noted, are the developer's own measurements and deserve a re-run against your workload. And because the agent sends code to external LLM APIs such as DeepSeek, teams that cannot let code leave the building need to audit the sandbox settings, what exactly gets transmitted, and which endpoints are in play before going further. One operational detail worth knowing: parts of the release notes are written in Chinese.

Is Reasonix free?

The tool itself is MIT-licensed open source, so it is free to use, modify, and use commercially. The LLM API calls the agent makes are billed separately, so check the pricing of whichever provider you point it at, such as DeepSeek.

Can I use models other than DeepSeek?

Yes. DeepSeek ships as a preset, but any OpenAI-compatible endpoint becomes available by adding a config entry to reasonix.toml — no code changes required. Dual-model setups that combine two models are also supported.

Does it really cut costs by more than 90%?

The developer published a test showing an 85.2% cache hit rate and roughly 93.9% cost reduction on multi-turn chat, but that is the developer's own measurement rather than an independent reproduction. The size of the saving depends heavily on your workload, so treat re-measuring against your own tasks as a prerequisite.

Should I switch from Claude Code or Codex?

Not necessarily. If you have already standardized on Claude or OpenAI, the incumbents are ahead on permissions, MCP maturity, and IDE integration. Reasonix makes sense when API cost on long sessions is the constraint, or when you want to change the underlying model from a config file.

Can I use it if company code cannot leave our network?

Not as-is. Reasonix works by sending code to an external LLM API, so you would need to audit what is transmitted, which endpoints are used, and how the sandbox is configured. Because it supports OpenAI-compatible endpoints, pointing it at an inference server you host yourself is worth exploring.

Feel free to contact us

Contact Us