[Bug] Opus 4.7 xHigh performance degradation post-Colossus-1 rollout

Resolved 💬 4 comments Opened May 9, 2026 by Dino-dev66 Closed Jun 27, 2026

Bug Description
[PERFORMANCE] Significant degradation post Colossus-1 rollout — Opus 4.7 xHigh

CLI version: 2.1.138
Plan: Max
Model: Opus 4.7
Reasoning effort: xHigh

Since the May 6 rate-limit increase / Colossus-1 capacity rollout, day-to-day
performance on Opus 4.7 with xHigh effort has noticeably degraded across
three dimensions:

  1. Token consumption per task

Same workloads now burn through the 5-hour limit substantially faster
than before the rollout. The headline doubling of the 5-hour Claude Code
limit is, in practice, eaten up by the increased per-task token cost.
Net usable throughput on Max is flat at best.

  1. Response latency

Time-to-first-token and overall response times are visibly slower.
Previously snappy interactions now stall noticeably, especially on
longer-context turns and multi-step tool use.

  1. Overall responsiveness / stability

Sessions feel less consistent than before the rollout — more pauses
mid-stream, occasional throughput drops within a single response, and
a general impression of the model running on more constrained capacity
rather than less.

Concern:
The announcement framed the Colossus-1 onboarding as a capacity expansion
that would "directly improve service" for Pro and Max subscribers. The
lived experience on Max is the opposite: fewer effective tokens per session,
slower responses, less consistent performance.

Request:
Please flag this to the Claude Code / model-serving team for investigation.
If the new capacity is still being progressively onboarded and current
behavior is transitional, transparent communication on the timeline would
be appreciated. If Opus 4.7 effort budgets or routing were retuned in the
same window, that would be useful context as well.

Happy to provide session IDs, request IDs, and timestamps on request.

Environment Info

  • Platform: linux
  • Terminal: ghostty
  • Version: 2.1.138
  • Feedback ID: 2cce9638-eb78-4241-8662-f65b90440155

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/dino66/.local/share/claude/versions/2.1.138 (expected in multi-process scenarios)\n    at a48 (/$bunfs/root/src/entrypoints/cli.js:2657:2257)\n    at vTH (/$bunfs/root/src/entrypoints/cli.js:2657:1337)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-09T22:01:33.536Z"}]

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗