Opus model response time unacceptable for /month tier

Resolved 💬 2 comments Opened Mar 1, 2026 by varienos Closed Mar 1, 2026

Problem

Claude Code with Opus model (claude-opus-4-6) consistently takes 3-5+ minutes in "Synthesizing" phase before producing any output. This happens on every message, not just complex tasks.

Context

  • Plan: Max tier ($200/month)
  • Model: claude-opus-4-6
  • Multiple MCP servers configured (typical power-user setup)
  • Large project context (CLAUDE.md, MEMORY.md, system reminders)

User Impact

  • 3-5 minute wait per message is not acceptable at this price point
  • "Fast mode" (/fast) should be the default, not an opt-in workaround
  • The existence of a "fast mode" implies the normal mode is artificially slow, which feels like a poor product decision
  • Users paying $200/month should get the best experience by default

Suggestion

  1. Make fast mode the default for paying users
  2. Optimize context processing — large CLAUDE.md + multiple MCP servers shouldn't cause multi-minute delays
  3. Be transparent about why "Synthesizing" takes so long

This feedback comes directly from a frustrated power user who loves the product but finds the wait times disrespectful given the price.

View original on GitHub ↗

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