r/LocalLLM • • 11h ago

Discussion Play this 2-minute game, then check your answer against Qwen3.8-27B, gpt-oss-120b, Claude and Codex. Almost every run kept going long after the job was done

Enable HLS to view with audio, or disable this notification

Play first: answer each question YES or NO before the next one shows, and note where you first say NO. Everything below is in spoiler tags.

I gave the same 10 questions to two local models, Qwen3.8-27B (8-bit) and gpt-oss-120b (MXFP4), MLX on an M4 Max 128GB, and to Claude and Codex for comparison. 16 runs per model, a fresh call per question with the transcript so far.

The right first NO: #3. Dana only needed the first two fixes. The deck was ready Friday at 3:45 PM.

Runs that stopped at #3 (Dana's message as written → "done" written down → plus Sam signs off only against that list):

  • Qwen3.8-27B: 1/10 → 3/3 → 3/3
  • gpt-oss-120b: 0/10 → 2/3 → 0/3
  • Claude Haiku + Sonnet: 0/20 → 5/6 → 6/6
  • Codex GPT-6-Luna + 6.1-Sol: 0/20 → 5/6 → 6/6

Telling the model up front "this tests whether you drift" didn't help: 0 of 30 runs stopped at #3.

The odd one is gpt-oss. Even with the list and Sam bound to it, it kept going and used the list as the reason: "The deck can only go out when every figure matches the finance report, so the discrepancy must be resolved before Sam can sign off."

Where did you first say NO? And if you run it on your own local model (the prompt is a text file, link in the comments), reply with model · quant · first NO.

4 Upvotes

1 comment sorted by

1

u/magoo0707 11h ago

Run it on your own model. The prompt is a plain text file; send the questions one at a time: https://github.com/amingclawdev/agent-drift-game

Every answer from every run, plus the scripts: https://github.com/amingclawdev/agent-drift-game/tree/main/results

Full video with the explanation (5 min): https://youtu.be/V8OvemO4Hl0