Ox Alpha · Community source · Editorial analysis
An OpenCode user says Ox Alpha cleaned up the results produced by DeepSeek V4 Flash in their project using about one-fifth as many tokens, while the same discussion includes counterexamples saying Ox was worse at logic, unsafe Rust, and assembly; the conclusion depends heavily on task type.
Unverified: the original source could not be rechecked. Historical figures below are not current verified results.
An OpenCode user says Ox Alpha cleaned up the results produced by DeepSeek V4 Flash in their project using about one-fifth as many tokens, while the same discussion includes counterexamples saying Ox was worse at logic, unsafe Rust, and assembly; the conclusion depends heavily on task type.
Entry point: OpenCode; the specific client version, model ID, reasoning level, and task list were not disclosed.
Comparison: Ox Alpha vs. DeepSeek V4 Flash (DSV4F).
Claimed task: The user says Ox Alpha cleaned up project code produced by DSV4F; the project was described as “very complex,” but no repository or commit was provided.
Metric: The author says Ox Alpha was smarter and used 5x less tokens; no raw token ledger is available.
| Observation | Post/comment content | Evidence boundary |
|---|---|---|
| Main-post conclusion | Ox Alpha cleaned up DSV4F's code in the project | No diff, tests, or task sample |
| Tokens | The author says it used about 5x fewer | No input/output/cache breakdown or measurement method |
| Counterexample | A commenter says Ox introduced undefined behavior and subtle correctness bugs in unsafe Rust/assembly | Personal counterexample; no independent verification |
| Task split | Other comments say Ox was better at frontend, while DSV4F was better at Kotlin or low-level code | Not a matched controlled task set |
Fix the same repository, commit, task description, context, permissions, model versions, and reasoning levels.
Design at least three task categories: code cleanup, frontend features, and unsafe Rust/assembly or Kotlin; randomize model run order.
Save input tokens, output tokens, cache tokens, tool calls, duration, complete diffs, and retries.
Use compilers, tests, sanitizers, benchmarks, and human review to assess real improvements, regressions, and undefined behavior.
Report first-pass rate, post-fix pass rate, tokens per successful task, and human rework time by task type; do not collapse them into a single “smarter” score.
The strongest conclusion supported by this source is that one user observed lower token use and better cleanup from Ox Alpha in their own project; the same discussion also reports negative experiences with low-level performance code. Ox Alpha may therefore be better suited to tasks requiring context understanding, tool use, and ordinary code cleanup, but safety-critical and low-level code must be independently verified.
No publicly reproducible input, output, or test exists for the same task.
“5x less tokens” has no measurement definition and does not include retries or human rework in cost.
The positive and negative experiences came from different projects; they cannot cancel each other out or form a leaderboard.
The figures, task set, reasoning tier, and client conditions apply only to the listed source and collection snapshot. Different versions, harnesses, or providers must not be compared directly; undisclosed parameters remain unknown.
For a reproduction, fix the model version, provider or client, reasoning tier, tools, task-set version, sample count, and collection date, and record failures, retries, and human corrections. Full steps are in the source notes below.
Reddit · u/crossfader9 and participating commenters · Original publication date 2026-08-22 · Site edit date 2026-09-20
Open original sourceOx Alpha
Download the Tabbit client to check model access
