claude-code - 💡(How to fix) Fix Reverter ou oferecer opção de layout clássico [1 participants]

Official PRs (…)
ON THIS PAGE

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48836Fetched 2026-04-16 06:49:35
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

Sou assinante Max e gasto 600 dólares por mês com o Claude Code.

O design anterior era limpo, funcional e direto ao ponto. O novo design não melhorou a experiência — pelo contrário, piorou.

Como dizemos no Brasil: time que está ganhando não se mexe.

Sugestão: ofereçam pelo menos a opção de usar o layout clássico para quem preferia o anterior. Muitos usuários que pagam caro pelo serviço gostariam de ter essa escolha.

Proposed Solution

Sou assinante Max e gasto 600 dólares por mês com o Claude Code.

O design anterior era limpo, funcional e direto ao ponto. O novo design não melhorou a experiência — pelo contrário, piorou.

Como dizemos no Brasil: time que está ganhando não se mexe.

Sugestão: ofereçam pelo menos a opção de usar o layout clássico para quem preferia o anterior. Muitos usuários que pagam caro pelo serviço gostariam de ter essa escolha.

Alternative Solutions

No response

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

No response

Additional Context

No response

extent analysis

TL;DR

The user suggests offering an option to use the classic layout for users who prefer the previous design, as the new design has worsened their experience.

Guidance

  • The user is experiencing a significant issue with the new design, which is affecting their work, and is requesting an option to switch back to the classic layout.
  • To address this, the development team could consider adding a configuration flag or option to allow users to choose between the new and classic layouts.
  • The team may want to gather more feedback from other users to determine the prevalence of this issue and the demand for a layout option.
  • The user's suggestion to "not fix what isn't broken" (as expressed by the Brazilian phrase) implies that the previous design was functional and effective, and that the new design may not have provided sufficient improvements to justify the change.

Example

No code example is provided, as the issue is related to design and user experience rather than a specific code implementation.

Notes

The issue lacks technical details, and the suggested solution is focused on user experience and design. The development team may need to gather more information and feedback from users to determine the best course of action.

Recommendation

Apply workaround: Offer an option to use the classic layout, as this would allow users who prefer the previous design to continue using the service without disruption, while the development team gathers more feedback and determines the best long-term solution.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING