How to use DeepSeek-Reasonix? DeepSeek native terminal programming agent

Sat, 06 Jun 2026 22:26:00 +0800

esengine/DeepSeek-Reasonix is a terminal-oriented AI programming agent. It is different from many “CLIs with a layer of OpenAI API”. The project is positioned as DeepSeek-native: designed around the stability of DeepSeek’s prefix cache, making long sessions cheaper and more suitable for always-on work.

The description in the README is very straightforward: a config- and plugin-driven harness, a single static Go binary, and models, agents, tools and plug-ins are all declared in reasonix.toml.

What problem does it solve?

There are many terminal programming agents now, but the common problems are also obvious:

The configuration is hard-coded and it is inconvenient to change the model;
The tool access method is not uniform;
In long sessions, the prompt keeps changing and the cache hit rate is poor;
Each mission is restarted, and the token cost is high;
I want to use DeepSeek, but the existing tools may not be optimized according to the characteristics of DeepSeek.

The focus of Reasonix is not “yet another chat CLI”, but rather using DeepSeek’s prefix cache as the centerpiece of its design. If the prefix is stable in a long session, cache hits are better, and the cost and speed will be more controllable.

Core Design

Several features listed in the project README are worthy of attention:

Config-driven: provider, agent, tools, and plugins are all configured through reasonix.toml;
Multi-model: DeepSeek flash/pro and MiMo have presets, and can also be connected to any OpenAI-compatible endpoint;
Composable: allows the two models of executor and planner to divide the work;
Plugin-driven: External tools are accessed through the stdio JSON-RPC sub-process, compatible with MCP ideas;
Built-in tools: built-in tools self-register during compilation;
Single static Go binary: Simple to deploy, no need to drag a bunch of runtimes.

For those who like to put the development environment in the terminal, this direction is very refreshing. The configuration file is the console, and the plug-in is the capability boundary.

Suitable for how to use

Reasonix is more suitable for these scenarios:

You are already using DeepSeek for coding tasks;
I hope there is a resident programming agent in the terminal;
Want to optimize long session costs around prefix cache;
Want to combine tools and plug-ins through configuration;
Want to use OpenAI-compatible endpoint to switch between different models;
Like Go’s single-file binary deployment approach.

It’s not necessarily suitable for users who don’t touch the terminal at all. If you prefer the built-in IDE experience, Cursor, Copilot, or Claude Code may be more convenient. Reasonix’s temperament is more of an engineer’s toolbox: configuration, plug-ins, terminal, long sessions.

The difference between ## and Claude Code / Codex

Tools such as Claude Code and Codex are more like complete products, while Reasonix is more like a configurable Agent harness.

You can understand it this way:

Tools	What is more like	Who is it suitable for
Claude Code / Codex	Out-of-the-box programming Agent	People who want to complete tasks quickly
Cursor	AI development environment within IDE	Heavy graphical interface and project editing users
DeepSeek-Reasonix	Agent framework for DeepSeek and endpoint workflows	People who want to control configuration, tools and costs

The advantage of Reasonix is controllability and DeepSeek optimization, but the price is that you need to understand the configuration and plug-ins, and you won’t have to do it bit by bit like a commercial IDE.

Think clearly before using

The stronger the terminal programming agent’s ability, the greater the risk:

There must be boundaries for file reading and writing, command execution and network access;
The source of the plug-in must be trustworthy;
Long session caching is not permission isolation;
Pay attention to the responsibilities of planner and executor when collaborating with multiple models;
Do not expose production keys and server credentials directly to Agent;
After automatically modifying the code, you still need to run tests and reviews.

If you plan to use it for a long time, it is recommended to run it in your personal project first, and then gradually connect it to the official warehouse. Especially for Agents that can execute shells, permissions should be given starting from a small age.

Summary

The value of DeepSeek-Reasonix is that it combines the cost-effectiveness of DeepSeek with a terminal programming agent. It is not the most “fool-like” tool, but it is very attractive to people who are willing to adjust configurations, connectors, and long-term terminals.

If your goal is to “use DeepSeek to make a controllable, low-cost, long-session local terminal programming agent”, Reasonix is worth trying. If you only occasionally let AI change a few lines of code, it may be more worry-free to directly use a ready-made IDE plug-in.

Reference sources

esengine/DeepSeek-Reasonix - GitHub

What do you think of the Go language official repository? Understand the evolution of Go from source code

Sat, 06 Jun 2026 22:26:00 +0800

golang/go is the official repository for the Go programming language. It is not only a source code repository, but also an important entrance to the Go compiler, runtime, standard library, tool chain, issue discussions and language proposals.

If you just write business code, you may not necessarily read it every day; but if you want to understand why Go is designed this way, the official repository cannot be avoided.

What’s in the warehouse

The official Go repository contains:

Go compiler;
runtime;
Standard library;
go commands and toolchains;
test and build scripts;
issue and proposal discussion;
release related changes.

Many of the capabilities you usually use, such as goroutine, channel, GC, standard library network package, and module tool chain, can all be found here.

Suitable for whom to watch

Suitable for these people:

Go backend developer;
People who want to understand Go runtime and scheduling;
People who follow the evolution of Go versions;
People who write high-performance services;
People who do language, compiler or standard library research;
People who encounter standard library boundary issues and need to check the implementation.

It is not recommended to go through the entire warehouse from the beginning. You can start with standard library packages that you are familiar with, such as net/http, context, and sync.

Learning Go is not just about grammar

The core of Go is not the complexity of syntax, but the engineering trade-offs:

Concise syntax;
Strong standard library;
Concurrency model;
Quick build;
Uniform format;
Easy to deploy;
Restraint in language evolution.

Understanding these design trade-offs is more useful than memorizing the syntax.

Summary

golang/go is the root of the Go ecosystem. Ordinary developers can use it as an entry point to check the behavior of the standard library, pay attention to version changes, and learn the runtime.

If you have been writing Go for a while, occasionally reading the official source code will be more solid than just watching the tutorials.

Reference sources

golang/go - GitHub

Go on KnightLi Blog

How to use DeepSeek-Reasonix? DeepSeek native terminal programming agent

What problem does it solve?

Core Design

Suitable for how to use

Think clearly before using

Summary

Reference sources

What do you think of the Go language official repository? Understand the evolution of Go from source code

What’s in the warehouse

Suitable for whom to watch

Learning Go is not just about grammar

Summary

Reference sources