DeepSeek-Reasonix

[!IMPORTANT] Community · 加入社区 — bilingual Discord for setup help (#help / #求助), workflow showcases, and feature ideas. → https://discord.gg/XF78rEME2D

Features

• Config-driven. Providers, the agent, enabled tools, and plugins are all declared in reasonix.toml. No hardcoded models.

• Multi-model & composable. DeepSeek ships as a preset; any OpenAI-compatible endpoint is a config entry, not new code. Optionally run two models together (executor + planner) in separate, cache-stable sessions.

• Plugin-driven. MCP servers contribute tools, prompts, and resources; Extension Protocol v1 sidecars can also intercept runtime events, contribute Providers and structured UI, and ship versioned plugin packages.

• Cache-aware context maintenance. Startup injects a small stable environment summary, stale tool output is snipped/pruned before summary compaction, and the built-in tool schema contract is documented for regression review.

• Zero-friction distribution. CGO_ENABLED=0 single binary; cross-compile to six targets with one command. The result is a fully self-contained static binary — nothing to install on the target machine beyond the binary itself.

Install

Choose the path that matches how you want to use Reasonix. The CLI/TUI, desktop app, and VS Code extension all use the same local Reasonix engine.

Path A: CLI / TUI

Install the native binary through npm on any supported platform, or use Homebrew on macOS:

npm i -g reasonix                  # any OS; pulls the prebuilt native binary
brew install esengine/reasonix/reasonix   # macOS

Prebuilt archives (darwin|linux|windows × amd64|arm64) and SHA256SUMS are on every GitHub release.

Path B: Desktop app

Use the official download page for the latest desktop build.

Platform Package Architecture

macOS Universal .dmg or .zip Apple Silicon / Intel

Windows Installer .exe or portable .zip x64 / ARM64

Linux .deb or .tar.gz x64

Windows installers are code-signed through SignPath.io with a free certificate provided by the SignPath Foundation.

Path C: VS Code extension

Complete Path A first. The extension does not bundle the CLI; it starts your local reasonix acp backend and adds native chat, editor context, tool-call approvals, model selection, and workspace sessions.

• VS Code: install from Visual Studio Marketplace

• VSCodium / Eclipse Theia: install from Open VSX Registry

• Extension ID: SivanLiu.reasonix-agent · source and usage guide

Path D: Build from source

Clone the repository first:

git clone https://github.com/esengine/DeepSeek-Reasonix.git
cd DeepSeek-Reasonix

CLI

The CLI build requires Go 1.25+. The module pins a toolchain directive; keep GOTOOLCHAIN=auto so Go downloads the pinned toolchain, or install it.

make build      # -> bin/reasonix(.exe)
make cross      # -> dist/ (darwin|linux|windows × amd64|arm64)

Desktop

The desktop build additionally requires:

• Node 24+ and pnpm 10 (npm install -g pnpm@10) for the frontend

• Wails CLI matching the shared .wails-version pin

make wails-install
cd desktop
wails build

See the desktop build guide for platform webview dependencies and Linux build tags.

Quick start

CLI / TUI

These commands are for the CLI/TUI installed through Path A:

reasonix setup                      # configure a provider and model
reasonix                            # start an interactive session
reasonix run "implement the TODOs in main.go"

In an interactive session, run /init when you want Reasonix to create project instructions.

Desktop app

Download the installer for your platform from the official download page, install and launch Reasonix, then configure a provider and model in the app. The CLI commands above are not required for the desktop app.

For advanced CLI usage and configuration, see the CLI reference, Guide, and configuration paths.

Documentation

• Getting started: Guide · CLI reference · Configuration paths · ACP editor integration

• Features & troubleshooting: Subagent profiles · Context Engine v2 · Capability diagnostics · Recovery and updates · Bot guide · Checkpoints & rewind

• Engineering & migration: Spec · Task contracts & pause policy · Tool contract · Migrating from 0.x

• Extension development: Extensions · Plugin packages and Manifest v1 · Extension Protocol · Go SDK and starter

Star History