Claude Sonnet 5.5 (effort default (no --effort flag) · thinking on) on Schedule a 40-task build DAG on 3 workers with exclusive resources
AClaude Sonnet 5.5default · thinking on · Claude Code 2.1.299 (headless -p) · cloud · 2026-10-16 · by @bobsiopener
- Estimated cost
- $0.07
- Wall time
- 2m
- Human step-ins
- 0
- Outcome
- Pass
Compare with other models on this task →
Summary
Exact prompt
# Task: schedule a build `tasks.json` describes 40 build tasks: duration (minutes), dependencies, and resources each task holds while running. There are `workers` identical workers (each runs one task at a time) and resource limits (at most `db: 1` and `net: 2` tasks holding that resource concurrently). Tasks can't be preempted; a task may start only when all its deps have finished (start ≥ max dep end time). Produce `schedule.json`: {"t00": {"start": <int minute>, "worker": <0..workers-1>}, ...} for ALL tasks, minimising the makespan (time the last task finishes). Also write `plan_notes.md` with your makespan and the lower bound you computed (max of critical path and total work / workers). You may write code. No network.
Validator checks deps, worker overlap, resource limits; must match or beat critical-path list scheduling (makespan 98; lower bound 91). 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. schedule.json must contain exactly the 40 tasks, each with a non-negative integer start and a valid worker index. 2. No task starts before all its dependencies finish. 3. No two tasks overlap on the same worker. 4. At no start time do concurrent tasks exceed the db (1) or net (2) resource limits. 5. Makespan <= the reference critical-path list-scheduling makespan.
Setup notes: Use Case Scout batch 4 case d12-build-scheduler (offline fixture). Prepared with batch4/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/key.json`. 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.071897. Score: pass. 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.07
- Wall time
- 2m
- Human step-ins
- 0
- Turns
- 6
| Model | Input tok | Output tok | Cost |
|---|---|---|---|
| AClaude Sonnet 5.5anthropic/claude-sonnet-5.5effort default (no --effort flag) · thinking on | 120,645 | 2,453 | $0.07 |
Reproduce this run
- Use the use case prompt on the use case page.
- 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. - It counts as a success only if it meets every success criterion: 1. schedule.json must contain exactly the 40 tasks, each with a non-negative integer start and a valid worker index. 2. No task starts before all its dependencies finish. 3. No two tasks overlap on the same worker. 4. At no start time do concurrent tasks exceed the db (1) or net (2) resource limits. 5. Makespan <= the reference critical-path list-scheduling makespan.
- 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?
Automated checks
Trust 80% comes from these checks (how Trust % works).
- Run date is not in the future : passed
- Model is in the dated pricing table : passed
- Cost recomputed from tokens matches : passed
- Cached tokens are consistent : passed
- Output throughput is plausible : passed
- Autonomy matches step-ins : passed
- Step-ins do not exceed turns : passed
- Retries agree with first-try result : passed
- Evidence log SHA-256 matches : passed
- Evidence log is substantial : passed
Evidence log
[
{
"duration_api_ms": 37342,
"stop_reason": "end_turn",
"session_id": "[REDACTED]",
"total_cost_usd": 0.0718967,
"usage": {
"input_tokens": 12,
"cache_creation_input_tokens": 9046,
"cache_read_input_tokens": 111587,
"output_tokens": 2453,
"output_tokens_details": {
"thinking_tokens": 232
},
"server_tool_use": {
"web_search_requests": 0,
"web_fetch_requests": 0
},
"service_tier": "standard",
"cache_creation": {
"ephemeral_1h_input_tokens": 9046,
"ephemeral_5m_input_tokens": 0
},
"inference_geo": "global",
"iterations": [
{
"input_tokens": 2,
"output_tokens": 373,
"cache_read_input_tokens": 21227,
"cache_creation_input_tokens": 358,
"cache_creation": {
"ephemeral_5m_input_tokens": 0,
"ephemeral_1h_input_tokens": 358
},
"type": "message"
}
],
"speed": "standard",
"fallback_credit": null
},
"modelUsage": {
"claude-sonnet-5-5": {
"inputTokens": 12,
"outputTokens": 2453,
"cacheReadInputTokens": 111587,
"cacheCreationInputTokens": 9046,
"webSearchRequests": 0,
"costUSD": 0.0718967,
"contextWindow": 1000000,
"maxOutputTokens": 128000,
"thinkingTokens": 232,
"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": 6,
"subtype": "success",
"api_error_status": null,
"result": "I wrote `schedule.json` and `plan_notes.md`. The schedule has a makespan of 96 minutes against a lower bound of 91, so I haven't proven it optimal.\n\n- **Lower bound:** 91, from your formula. The critical path is 81, and total work is 273 minutes over 3 workers, which is 91.\n- **Resource check:** the `db` tasks total 88 minutes on a capacity-1 resource, so the schedule needs at least 88 minutes on that count alone. That is below 91, so 91 stays the binding bound.\n- **Method:** I built the schedule with a randomized priority-list heuristic and a local search that ran for 60 seconds. `ortools` isn't installed, so I couldn't use an exact solver. A longer search or an exact solver might close the remaining 5 minutes, but I didn't try either.\n- **Checks:** I didn't run a separate validator. The scheduler enforces dependencies, the `db`/`net` limits and worker capacity as it places each task. I then assigned workers greedily by start time.\n\nThe scheduler script is at `../tools/s.py`, outside the work directory.",
"ttft_ms": 3574,
"type": "result",
"duration_ms": 97897,
"uuid": "[REDACTED]",
"ttft_stream_ms": 2740,
"time_to_request_ms": 263,
"first_content_frame_ms": 2741,
"queued_turn_count": 0,
"result_index": 0
}
]