›_ Claude Code Issues
Claude Code Issues / #17454

[FEATURE] Please hire a dev for temporary CC DEC mode alternative

Resolved 💬 4 comments Opened Jan 11, 2026 by cmpunches Closed Feb 26, 2026

Preflight Checklist

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

Problem Statement

I'm going to feel bad about submitting this one, but please hire a dev for claude for the purpose of:

  1. Disabling synchronized output (DEC mode 2026) entirely in reference to #3648 until it reaches a certain level of maturity in the VT ecosystem that it can be turned on without rendering Claude Code entirely unusable for most users.
  • In its current condition and staffing, because of how that feature is being misused, it's in that condition and has been for months while sporadic patches to individual terminal emulators get made instead of addressing a product feature shortcoming by:
  • disabling it
  • fixing the underlying contributing issue (refreshing using the whole history), and then
  • waiting for it to have high implementation adoption in the VT ecosystem
  1. Handover of the Claude Code CLI:
  • code repository
  • feature roadmap
  • overall strategy, architecture, design, and development process

This second item would be for the overall purpose of preventing recurrence of this issue and how it was handled given:

  • the level of stakes involved for Anthropic, particularly brand reputation.
  • the number of users impacted
  • how cripplingly heavily they are impacted
  • the skill implications at the source of the issue
  • how long it took to repair
  • what was done while it was being repaired
  • the strategy of patching all the different VTEs out there while the tire fire burns instead of just disabling use of the problematic feature with alternative mode in the meantime
  • the fact that hundreds of users are posting daily about this while no response is made and seemingly no progress is made beyond sporadic patches to random VTE repos to get better support for the related feature.
  • the fact that simple design changes in how the TUI works would resolve this for almost all users.
  • the fact that people are canceling their subscriptions in bulk over it

I admit that I am not in the loop on the financial arrangements behind how this is being done, but, I do have general figures and the level of money behind Anthropic's development resources and their software engineering practice maturity are not in alignment at all, it's causing an epic optics and usability problem, the kind that breaks companies sometimes, and this request would likely improve how future issues are handled.

Ref:

FYSA:
@bogini @km-anthropic @ashwin-ant @np-anthropic @wim-anthropic @anthropic-xabi @ah-anthropic @catherinewu

Note:

I did see this statment back in November:
https://github.com/anthropics/claude-code/issues/3648#issuecomment-3522999626

In my experience this is not accurate and I believe anyone who builds cli tools regularly will immediately recognize it as not accurate - there is an entire ecosystem of TUI products that do almost all of the things claude code is doing on its frontend and have been in operation for decades. Plural. There are also TUI frameworks that can be used as a fallback while the feature is disabled until maturity. Disabling a feature until its ready is a common practice in software engineering. Letting it rot broken for months at the expense of users and employer is not. Workarounds pending a more mature feature later are common.

In current industry expectations, in most modern SWE environments releases are promoted to production several times a day if not per hour so those lead time for changes get pretty small. This would have been sorted out in a few days if not hours, and would be in the future if this feature request is acted on in the right way with some good SWEBOK grounded planning cycles implemented.

Sorry to anyone this would impact if implemented -- sometimes the bug is not just the code. It is an incredibly competitive industry filled with a wide range of skill, process familiarity, and strategic experience--, the upper extremity of which works on the most advanced systems on the planet -- and the most visible, for reasons largely covered here -- which a TUI API client is not going to be -- and the level of professional investment in the people and processes that prevent this type of issue is not easy to come by.

It may also be worth considering more mature runtimes, but, out of scope for this issue.

Proposed Solution

See Above

Alternative Solutions

See Above

Priority

High - Significant impact on productivity

Feature Category

Interactive mode (TUI)

Use Case Example

N/A

Additional Context

N/A

View original on GitHub ↗

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