DeepSeek-Reasonix
DeepSeek-native AI coding agent for your terminal. Engineered around prefix-cache stability, leave it running.
Runssource: GitHubhomepageGoMITcommit 61750da510c4
Go, MIT licensed. The project labels itself: agent, agent framework, ai agent, ai coding, cli, coding agent, deepseek and developer tools.
DeepSeek-Reasonix runs. An Argusic agent installed it in 0.5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Reasonix builds as a single Go binary (bin/reasonix), answers --help with full usage including CLI/TUI, web, serve, ACP, and bot subcommands, passes all 147+ test packages with 0 failures, and produces valid JSON diagnostics via doctor --json.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 97.3 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- TestLoadIncludesStableGlobalPreferencesAndFeedback flaky: pinned guidance sort order flips when alpha-user and zeta-feedback get identical timestamps1 minute
- go: not found - Go toolchain missing0.5 minutes
- Install time
- under a minute
- Cold machine to finish
- 19 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- go test ./... exited 0 (all 147+ packages); SDK tests passed (go test ./sdk/go/... exited 0); binary answers --help and version; doctor --json returns valid JSON with provider config
- Model tokens used
- 74,001
- Exact commit tested
- 61750da510c4
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
/bin/sh -lc 'export GOROOT=$HOME/go export GOPATH=$HOME/gopath export PATH=$HOME/go/bin:$GOPATH/bin:$PATH cd /work/repo/sdk/go && go test ./... 2>&1' in /work/repo succeeded in 325ms: ok github.com/esengine/DeepSeek-Reasonix/sdk/go 0.164s ? github.com/esengine/DeepSeek-Reasonix/sdk/go/examples/fullsidecar [no test files] ok github.com/esengine/DeepSeek-Reasonix/sdk/go/examples/starterextension 0.001s All tests pass, build succeeds, SDK tests pass. Let me compile the final report. tokens used 74,001 All tests pass, build succeeds, SDK tests pass. Let me compile the final report.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 0.5 minutes, faster than the median of the 32 comparable projects Argusic has measured.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 3 times, so the result is not a one-off.
Of the 33 agent projects Argusic has installed and timed, DeepSeek-Reasonix was the 3rd fastest to reach a running state, and 25 of 33 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 0.5 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
agentagent-frameworkai-agentai-codingclicoding-agentdeepseekdeveloper-toolsdshdsh-plugininkllmprompt-cachingr1terminaltool-usetuitypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/deepseek-reasonix)Questions
- Does DeepSeek-Reasonix run?
- Yes. DeepSeek-Reasonix runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test DeepSeek-Reasonix?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 61750da510c4. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test DeepSeek-Reasonix?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does DeepSeek-Reasonix take to install?
- 0.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does DeepSeek-Reasonix need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing DeepSeek-Reasonix?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does DeepSeek-Reasonix compare with the alternatives?
- Of the 33 agent projects Argusic has installed and timed, DeepSeek-Reasonix was the 3rd fastest to reach a running state, and 25 of 33 reached one at all.
- Where is the evidence for DeepSeek-Reasonix?
- All 3 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.