DeepSeek-Reasonix Latest Updates and Release Notes: Versions v1.25.0–v1.25.2 Explained

The latest stable releases of DeepSeek-Reasonix (v1.25.0 through v1.25.2) introduce streaming markdown rendering, desktop stability fixes, adaptive planner research, and expanded model support including the DeepSeek-v4-pro model.

DeepSeek-Reasonix is a Go-based AI assistant platform developed by esengine that powers multiple front-ends through a single transport-agnostic controller. Whether you use the CLI, Wails desktop application, or npm package, all surfaces share the same core engine. This article breaks down the latest updates and release notes from the structured JSON release log at release-notes/releases.json.

---

DeepSeek-Reasonix v1.25.2: Desktop Stability and Agent Reliability (2026-08-14)

Version 1.25.2 focuses on polishing the user experience and making autonomous agent operations more reliable.

Expanded Reasoning Display Mode

Completed reasoning chains now remain open across messages, inline transcripts, and sub-agent previews. This eliminates the friction of re-expanding context when reviewing multi-step agent workflows.

Memory Tools Respect Auto and YOLO Modes

Memory approval prompts no longer interrupt Auto and YOLO execution modes. The control.Controller now correctly bypasses interactive confirmations when these safety-override modes are active, matching the behavior of other tool categories.

Adaptive Planner Research

The planner agent in internal/control/controller.go runs iteratively until either a valid plan is submitted or hard safety limits trigger. This replaces the previous fixed-round cap that could terminate planning prematurely on complex tasks.

Desktop Session and UI Stability Fixes

The Wails desktop front-end (desktop/bot_runtime_app.go) received targeted fixes for:

• Session-switching prompt corruption
• Pinned-chat restoration after application restart
• Project-tree rendering loops
• Transcript scrolling glitches

Source: release-notes/releases.json under the v1.25.2 entry.

---

DeepSeek-Reasonix v1.25.1: Provider Compatibility and Goal-Mode Fixes (2026-08-13)

Version 1.25.1 addresses gateway compatibility and refines goal-tracking behavior.

Sidebar and Transcript Restoration

Post-upgrade state migration now correctly restores sidebar configuration and transcript scroll positions.

DeepSeek and Anthropic Gateway Compatibility

Updated client code respects the official 384K output token ceiling for DeepSeek and Anthropic API endpoints, preventing request rejections on long-context operations.

Goal-Mode Verification Fix

The update_goal(complete) handler now detects and prevents infinite loops when the same completion signal repeats, a regression introduced in v1.25.0.

Web Search Results as Foldable Cards

Search results render as a separate, collapsible card with numbered footnotes, reducing clutter in the main transcript.

Source: release-notes/releases.json#v1.25.1.

---

DeepSeek-Reasonix v1.25.0: Streaming Rendering and Agent Progress (2026-08-13)

Version 1.25.0 introduces foundational improvements to real-time output handling and agent economics.

Streaming Markdown Rendering

List items in streaming responses render as completed DOM elements immediately, eliminating the "flash of raw markdown" that previously appeared during token-by-token generation.

Smarter Command Safety Classification

The safety classifier now applies argument-aware rules rather than blunt command-name matching. This reduces false-positive blocks for safe commands with suspicious-looking arguments.

Agent Progress Guard with Pricing

The progress guard mechanism now prices incremental progress, enabling longer honest investigations without triggering the truncation that previously cut off thorough agent runs.

DeepSeek Responses Preset Expansion

The builtin preset now includes deepseek-v4-pro alongside deepseek-v4-flash, selectable via the model configuration in your TOML config file.

Source: release-notes/releases.json#v1.25.0.

---

How to Run DeepSeek-Reasonix After Updating

All three distribution channels consume the same control.Controller implementation, ensuring consistent behavior.

CLI Launcher

reasonix --config ~/reasonix/config.toml --channel stable

The binary located at cmd/reasonix/main.go (generated via make) initializes the controller and starts the terminal UI.

Desktop Application

reasonix-desktop --channel stable

The Wails entry point at desktop/bot_runtime_app.go wraps the identical controller logic in a native window.

npm Package

npm install @esengine/reasonix
node -e "require('@esengine/reasonix').run({channel:'stable'});"

The npm wrapper at npm/reasonix/package.json spawns the Go binary transparently.

Source: README.md, desktop/bot_runtime_app.go, npm/reasonix/package.json.

---

Key Source Files for Release Tracking

File	Purpose
release-notes/releases.json	Structured release notes for all stable versions
REASONIX.md	Byte-stable system-prompt specification
internal/control/controller.go	Core transport-agnostic controller
desktop/bot_runtime_app.go	Wails desktop entry point
cmd/reasonix/main.go	CLI entry point (make-generated)
npm/reasonix/package.json	npm package configuration

---

Summary

• v1.25.2 improves desktop stability and makes memory approvals respect Auto/YOLO modes while introducing adaptive planner research loops.
• v1.25.1 restores UI state correctly after upgrades, fixes goal-mode loops, and adds collapsible web search cards.
• v1.25.0 delivers streaming markdown rendering without flash, argument-aware safety rules, priced agent progress guards, and deepseek-v4-pro support.
• All versions share the same control.Controller core, ensuring feature parity across CLI, desktop, and npm distributions.
• Release data lives in machine-readable JSON at release-notes/releases.json for programmatic access.

---

Frequently Asked Questions

Where are the official DeepSeek-Reasonix release notes stored?

The project maintains structured release notes in release-notes/releases.json on the main-v2 branch. This JSON file contains dated entries for every stable version with highlights, new features, improvements, and bug fixes arrays, making it both human-readable and machine-parseable.

What is the byte-stable system prompt mentioned in the releases?

REASONIX.md contains the standing system-prompt instructions that serve as the prefix for all model interactions. The "byte-stable" guarantee means this prefix never changes in a way that would alter tokenization, ensuring reproducible behavior across versions.

How do I switch between stable and development channels?

Pass the --channel flag to any front-end: stable for production releases (documented here) or dev for bleeding-edge builds. The controller in internal/control/controller.go validates the channel parameter and loads corresponding configuration schemas.

Which DeepSeek models are supported as of v1.25.0?

The DeepSeek Responses preset includes both deepseek-v4-flash (fast, cost-effective) and deepseek-v4-pro (maximum capability). Configure your preferred model in the TOML configuration file under the provider's model field.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}