Skip to content

Claude Sonnet 5.5 (effort default (no --effort flag) · thinking on) on Make a unified-diff patch applier correct (offset search, no-newline markers, create/delete, atomic failure)

AClaude Sonnet 5.5default · thinking on · Claude Code 2.1.299 (headless -p) · cloud · 2026-10-19 · by @bobsiopener

Trust 80%Fully autonomoussuccess · first try
Estimated cost
$0.14
Wall time
1m
Human step-ins
0
Outcome
Pass

Compare with other models on this task →

Summary

Exact prompt

# Task: make the patch applier correct `patcher.py` provides `apply_patch(diff_text, root)` which applies a unified diff to the files under directory `root`. It works for the simplest diffs but breaks on real ones and can leave a half-patched tree behind. Fix it (rewrite freely) so it follows `PATCH_RULES.md` exactly. Keep the names `apply_patch` and `PatchError`. Python standard library only; do not shell out to `patch` or `git`. No network. The grader runs a hidden unittest suite that builds small directory trees in temporary folders, calls `apply_patch`, and checks the return value, the exact bytes of every file afterwards, and that `PatchError` is raised (with the tree unchanged) where the rules say so.

The starting applier strips paths wrongly, requires explicit counts, ignores offsets and newline markers, rewrites files hunk by hunk (half-patched trees on failure) and accepts malformed hunks. Tests check exact bytes and an unchanged tree after every failure. Original benchmark task written for usecaserank.com (not based on a specific public post). Headless, offline run on a reproducible fixture. Each run's notes say how its cost was measured (estimates are marked).

Success criteria: 1. All 13 hidden unittest cases pass (git headers and tab timestamps, omitted counts, offset search with carry, +1 before -1, +/-50 limit, no match before previous hunk, no fuzz, no-newline markers, CRLF content and blank context lines, create/delete, failing create/delete/modify, atomic multi-file failure, malformed diffs and unsafe paths).

Setup notes: Use Case Scout batch 7 case g03-unified-diff-apply (offline fixture). Prepared with batch7/prepare.sh; hidden key/tests kept outside the agent's work dir. Prompt = TASK.md verbatim. Scored with the scout's scorer: `python score.py WORKDIR KEYDIR`. Tools: Read/Write/Edit/Glob/Grep/Bash, web disabled. Single run, no retries. Claude Code's own reported cost for claude-sonnet-5.5: $0.138797. Score: 13/13. Cost is an ESTIMATE: measured tokens x pricing.json list price (Claude Pro subscription, nothing billed); input_tokens include cache reads and writes. Single run.

Estimated cost List-price estimate; not actually billed.

Metrics

Estimated cost
$0.14
Wall time
1m
Human step-ins
0
Turns
3
Model usage
ModelInput tokOutput tokCost
AClaude Sonnet 5.5anthropic/claude-sonnet-5.5effort default (no --effort flag) · thinking on64,9587,611$0.14

Reproduce this run

  1. Use the use case prompt on the use case page.
  2. Same setup: Claude Sonnet 5.5 (anthropic/claude-sonnet-5.5, effort default (no --effort flag) · thinking on) via Claude Code 2.1.299 (headless -p), cloud.
  3. It counts as a success only if it meets every success criterion: 1. All 13 hidden unittest cases pass (git headers and tab timestamps, omitted counts, offset search with carry, +1 before -1, +/-50 limit, no match before previous hunk, no fuzz, no-newline markers, CRLF content and blank context lines, create/delete, failing create/delete/modify, atomic multi-file failure, malformed diffs and unsafe paths).
  4. Log model, tokens, wall time, human step-ins and the evidence log, then submit it as a reproduction. A different model? Submit a head-to-head rerun.

How runs are scored: Methodology.

Was this useful?

⇄ Rerun on another model

Automated checks

Trust 80% comes from these checks (how Trust % works).

Evidence log
[
 {
  "duration_api_ms": 59832,
  "stop_reason": "end_turn",
  "session_id": "[REDACTED]",
  "total_cost_usd": 0.1387967,
  "usage": {
   "input_tokens": 6,
   "cache_creation_input_tokens": 14405,
   "cache_read_input_tokens": 50547,
   "output_tokens": 7611,
   "output_tokens_details": {
    "thinking_tokens": 3618
   },
   "server_tool_use": {
    "web_search_requests": 0,
    "web_fetch_requests": 0
   },
   "service_tier": "standard",
   "cache_creation": {
    "ephemeral_1h_input_tokens": 14405,
    "ephemeral_5m_input_tokens": 0
   },
   "inference_geo": "global",
   "iterations": [
    {
     "input_tokens": 2,
     "output_tokens": 561,
     "cache_read_input_tokens": 19912,
     "cache_creation_input_tokens": 7032,
     "cache_creation": {
      "ephemeral_5m_input_tokens": 0,
      "ephemeral_1h_input_tokens": 7032
     },
     "type": "message"
    }
   ],
   "speed": "standard",
   "fallback_credit": null
  },
  "modelUsage": {
   "claude-sonnet-5-5": {
    "inputTokens": 6,
    "outputTokens": 7611,
    "cacheReadInputTokens": 50547,
    "cacheCreationInputTokens": 14405,
    "webSearchRequests": 0,
    "costUSD": 0.1387967,
    "contextWindow": 1000000,
    "maxOutputTokens": 128000,
    "thinkingTokens": 3618,
    "canonicalModel": "claude-sonnet-5-5",
    "provider": "firstParty",
    "costBasis": "list"
   }
  },
  "permission_denials": [],
  "terminal_reason": "completed",
  "fast_mode_state": "off",
  "fast_mode_disabled_reason": "sdk_opt_in_required",
  "subagent_stats": {
   "spawned": 0,
   "requested": {
    "background": 0,
    "foreground": 0,
    "unset": 0
   },
   "started_in_background": 0,
   "max_depth": 0,
   "spawned_by_subagents": 0,
   "completed": 0,
   "failed": 0,
   "killed": {
    "parent": 0,
    "user": 0,
    "system": 0
   },
   "refused": {
    "depth_limit": 0,
    "concurrency_limit": 0,
    "budget": 0
   },
   "by_type": {}
  },
  "safety_stops": 0,
  "is_error": false,
  "num_turns": 3,
  "subtype": "success",
  "api_error_status": null,
  "result": "I rewrote `patcher.py` to follow `PATCH_RULES.md`. `apply_patch` and `PatchError` keep their names, and it uses only the standard library. I ran one scenario in a temp directory, not the hidden suite, and it behaved as expected. One diff had a modify (CRLF line, missing final newline) and a create with a new parent directory. A second diff whose first hunk didn't match raised `PatchError` and left the tree unchanged.\n\n- **Parsing:** it reads and writes bytes, and splits only on `\\n`, so `\\r` stays ordinary content. Each hunk body is read by the header's line counts. A hunk with too few or too many lines raises `PatchError`.\n- **Sections:** a section with no hunks, a duplicate path, or both paths `/dev/null` raises `PatchError`. So does a diff with no sections.\n- **Matching:** hunks apply in order to the progressively patched content, using the base, offset and \u00b150 search from rule 6. A hunk can't match before the end of the previous hunk's new lines. The final line's missing-newline state must also match.\n- **Delete:** the patched content has to be empty, which means the removed lines equal the whole file.\n- **Atomicity:** it computes every result in memory first and writes only if all sections succeed. If a write fails partway, it undoes the writes, deletions, created files and created directories, then raises `PatchError`.\n\nI made two choices where the rules were silent. A stray `+`, `-` or space line after a hunk's counts are met raises `PatchError`, unless it begins the next section's `---`/`+++` header pair. A blank line after the counts is ignored. After a successful delete, empty parent directories are left in place.",
  "ttft_ms": 1834,
  "type": "result",
  "duration_ms": 60193,
  "uuid": "[REDACTED]",
  "ttft_stream_ms": 1073,
  "time_to_request_ms": 245,
  "first_content_frame_ms": 1073,
  "queued_turn_count": 0,
  "result_index": 0
 }
]

Get new runs and ranking changes weekly