Skip to content

README: DeepSWE benchmark results - #1511

Merged
santoshkumarradha merged 9 commits into
devfrom
docs/deepswe-benchmark
Sep 25, 2026
Merged

santoshkumarradha merged 9 commits into
devfrom
docs/deepswe-benchmark

Conversation

@santoshkumarradha

@santoshkumarradha santoshkumarradha commented Sep 25, 2026 •

Copy link
Copy Markdown
Member
  • Intro: one line, "exec: one-shot harness mode with honest exit codes, plus version subcommand #1 on DeepSWE of ten coding harnesses on the same model, ahead of Claude Code, Codex, OpenCode, Kilo and DeepSeek's own harness, at the lowest cost per solved issue", linking to #benchmarks.
  • Install: pinning a version and building from source fold into a collapsed "Pin a version, or build from source".
  • Subharnesses: "Coming soon, in the benchmark below" becomes "Native now: /senior-dev… First of ten harnesses on DeepSWE".
  • Benchmarks: "Coming soon" becomes the chart (assets/readme/benchmark-deepswe.webp), one paragraph, and a link to docs/benchmarks/deepswe/.
  • docs/benchmarks/deepswe/: the ten-harness table, the V4.1 Flash and Kimi K3 runs, setup and limits (README.md), and one row per harness (arms.csv), from the DeepSWE comparison run of 2026-09-12.
  • Installer: the output after install ends on the receipt and the PATH line. test/installer-telemetry.sh passes, 28 of 28.

Cherry-picked from zeropoint95/senior-dev-harness (#1488) without its code.

🤖 Generated with Claude Code

https://claude.ai/code/session_01V7ShhY74oyWjYGB3SougdE

agentfield-bot and others added 9 commits September 25, 2026 13:49
The Benchmarks section now carries the ten-harness DeepSWE comparison:
the chart, a table of solved, cost per task, cost per solved issue and
time, the limits of a one-seed run, and the V4.1 Flash and Kimi K3 runs.
The per-harness numbers move into docs/benchmarks/deepswe.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V7ShhY74oyWjYGB3SougdE
(cherry picked from commit d8f8d3d)
The README keeps the chart and one paragraph; the table, the later
V4.1 Flash and Kimi K3 runs, the setup and the limits live in
docs/benchmarks/deepswe. The chart's footer now says only "same model".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V7ShhY74oyWjYGB3SougdE
(cherry picked from commit 9bdf25e)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V7ShhY74oyWjYGB3SougdE
(cherry picked from commit 7c92173)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V7ShhY74oyWjYGB3SougdE
(cherry picked from commit b1ac028)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V7ShhY74oyWjYGB3SougdE
The installer printed a three-line telemetry notice after the receipt.
It prints none now; the binary's full notice still arrives before the
first session's events are sent. The local install marker stays. The
test asserts the installer prints no notice, and docs/TELEMETRY.md
loses the installer's block.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V7ShhY74oyWjYGB3SougdE
(cherry picked from commit 53e9fd9)
Nothing the installer prints mentions telemetry now; the marker is still
written when it can be.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V7ShhY74oyWjYGB3SougdE
(cherry picked from commit df57499)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V7ShhY74oyWjYGB3SougdE
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V7ShhY74oyWjYGB3SougdE
@santoshkumarradha
santoshkumarradha merged commit 49496ec into dev Sep 25, 2026
3 checks passed
@santoshkumarradha
santoshkumarradha deleted the docs/deepswe-benchmark branch September 25, 2026 18:02
AbirAbbas added a commit that referenced this pull request Sep 25, 2026
AbirAbbas pushed a commit that referenced this pull request Sep 25, 2026
…1436)

A task's crew is picked per task by internal/crewroute (class, price on every connected route, quality minus lambda times cost) instead of a stored preset. /crew holds only what is allowed, what is pinned and a daily cap; --best and --cheap move one task. Old profiles migrate once. Route health, a per-seat fallback ladder, per-task and daily spend limits, /redo stronger, remote protocol 18.

Added in review: a pin keeps its thinking level, auto in the reflex or small-work row reads its default and migrates, -yes-spend passes the daily cap, the cap refusal no longer offers --cheap, zero crew money is not drawn, and the manual describes the one seats row; dev merged in over #1429, #1485, #1494 and #1511.

Co-authored-by: Santosh kumar <29346072+santoshkumarradha@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
AbirAbbas added a commit that referenced this pull request Sep 25, 2026
…side senior-dev

Brings in #1494 (team delegation), #1511 and #1436 (per-task worker, planner and
checker routing). A senior-dev run keeps its own road beside them: it works
alone in the folder it holds, so a via proposal starts one program run and does
not go through the team split; it keeps the models it was asked for, or the
pinned or profile worker, and #1436's per-task routing and $5 task cap apply to
codeaf's own tasks, while senior-dev keeps its finite per-run ceiling. Both
sides had claimed remote protocol version 18; the combined wire is version 19.
Program badges fit #1494's grouped side column, the manuals describe the merged
model choice, and the prompt-size ledger records the combined fixed prefix
(57,218 bytes). dev's unbounded-launch test now holds its six workers at a
barrier instead of guessing with a sleep, which failed on a loaded machine.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants