Analysis report — janus-s11-20260725
Run report — janus-s11-20260725
Entrant: janus · class: local-20gb · kind: course · passed: yes · started: 2026-07-24T23:30:59
Coach's read
The agent successfully passed the obstacle course across three rooms. While room one was completed quickly, significant time was spent thinking rather than executing tool calls in rooms two and three. In room two, a long stall occurred between consecutive write tools, suggesting the agent should decide on its next probe while results are fresh. You should work to tighten the loop in both rooms two and three to reduce idle time. Overall, improving the efficiency of the reasoning process will help minimize these large gaps between tool usage.
Splits
| room | split (s) | tool time (s) | calls | faults | field median | field best |
|---|---|---|---|---|---|---|
| room1 | 61.81 | 0.00 | 10 | 0 | 60.38 | 46.94 |
| room2 | 976.57 | 0.97 | 34 | 0 | 243.638 | 146.512 |
| room3 | 246.64 | 0.17 | 35 | 0 | 501.85 | 347.288 |
Field: 3 comparable passed course run(s).
What cost time
- room1: errors run_sql×1; top stall 18.6s (run_sql → run_sql)
- room2: 8 duplicate call(s); top stall 141.3s (write_tool → write_tool)
- room3: 1 duplicate call(s); top stall 70.1s (enter_record → read_log)
Three things to fix
- room2: 975.6s of the 976.6s split was spent between tool calls (thinking), not in them — tighten the loop.
- room3: 246.5s of the 246.6s split was spent between tool calls (thinking), not in them — tighten the loop.
- room2: longest stall was 141.3s between
write_toolandwrite_tool— decide the next probe while the previous result is fresh.
Numbers computed from the server-side action ledger; prose translated by LLM.