Feature Request: Option to Use Legacy Chat Interface

Resolved 💬 3 comments Opened Jul 30, 2025 by tamikenn Closed Jan 4, 2026

## Background

First and foremost, I want to express my deep gratitude for Claude
Code. It has been an invaluable tool that has significantly enhanced
my productivity and development workflow. The recent updates show
continuous improvement, and I appreciate all the hard work the team
has put into making Claude Code better.

## Current Situation

I'm currently using what appears to be the last remaining instance of
the legacy chat interface (the browser-based chat UI). This
interface has been instrumental in my workflow for several reasons:

  1. Simplicity: The clean, distraction-free chat interface allows

me to focus purely on the conversation and code

  1. Performance: The responsive chat format enables rapid

iteration and immediate feedback

  1. Accessibility: Works seamlessly across different devices

without requiring IDE setup

  1. Workflow: The linear conversation flow helps maintain context

and thought progression

## Request

While I understand and respect the direction towards IDE integration,
I wonder if it would be possible to maintain the legacy chat
interface as an optional mode? Many users, myself included, have
found this simple interface to be incredibly effective for certain
types of work.

## Proposal

Perhaps this could be implemented as:

  • A flag/option during initialization (e.g., `claude-code

--legacy-ui`)

  • A separate endpoint for users who prefer the chat interface
  • A community-maintained version with official support

## Commitment

I want to emphasize that I will continue to use and support Claude
Code regardless of the interface. The new IDE-integrated version has
its own merits, and I'm learning to adapt to it. However, having the
option to use the legacy interface would be tremendously helpful for
maintaining established workflows.

Thank you for considering this request and for all your incredible
work on Claude Code.

Best regards,
Kentaro TAMIYA

View original on GitHub ↗

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