anthropics / anthropics/claude-code

[Accessibility] VS Code extension: red/orange input border in Auto and Manual modes breaks focus

Abierto
#94,213 1 comentario 0 reacciones 0 asignados Ver en GitHub
area:a11y area:permissions bug platform:vscode platform:windows
Lenguaje dominante
Python
Estrellas
145k
Forks
23.1k
Métricas de merge de PR
Métricas de PR pendientes

Descripción

### Preflight Checklist

- [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code

### What's Wrong?

**Component:** VS Code extension (chat panel input)
**Version:** Claude Code extension 2.1.270, VS Code 1.135.0, Windows 10 Home 10.0.19045 (win32-x64)

**Issue**
Since a recent update, the chat input box is framed with a persistent saturated
red outline in Auto mode and an orange outline in Manual mode. The border stays
on the whole time the mode is active.

**Why this is an accessibility problem**
I'm autistic. A permanent, high-saturation red frame around the element I look
at all day is a constant sensory overload. Red and orange also read as "error" and
"warning", so the UI is effectively raising an alarm about a mode I selected
deliberately. The result is that I cannot focus on programming while the panel
is open. Both of the modes I actually use are affected, so there is no
colour-neutral option (you only left less useful modes with neutral, non-aggravating colors).

There is no setting to disable or recolour the border, and
workbench.colorCustomizations does not reach it.
This is a very important issue for me, since I cannot turn off my neurodivergence,
and the color is causing me an entirely avoidable (if you supplied ANY kind of customization)
anxiety. It is a very bad update.

Do not force distressing things on neurodivergent users.

**Expected**
A mode indicator that does not use alarm colours as a persistent frame.
Suggestions (any one would solve it):
- A setting to disable mode-coloured borders.
- A neutral or theme-derived border colour, with the mode shown by the
existing text label instead.
- Reduce the border to a transient cue (e.g. shown briefly on mode change).

**Steps to reproduce**
1. Open the Claude Code chat panel in VS Code.
2. Switch permission mode to Auto (or Manual).
3. Observe the input box outline.

### What Should Happen?

Do not show orange/red and cause me personal distress via constant sensory overload OR provide me with an option to customize colors. A neutral border, or a setting to disable mode-coloured borders. Any of the three suggestions above resolves it.

### Error Messages/Logs

```shell

```

### Steps to Reproduce

1. Open the Claude Code chat panel in VS Code.
2. Switch permission mode to Auto (or Manual).
3. Observe the input box outline.

### Claude Model

Not sure / Multiple models

### Is this a regression?

Yes, this worked in a previous version

### Last Working Version

2.1.266

### Claude Code Version

2.1.270

### Platform

Claude.ai / subscription

### Operating System

Windows

### Terminal/Shell

VS Code integrated terminal

### Additional Information

Previous version folder 2.1.266 is still on your disk, so I can confirm the regression window is between 2.1.266 and 2.1.270.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Línea de trabajo

Start with the VS Code extension chat panel and reproduce the input outline in Auto and Manual modes on version 2.1.270, then compare it with 2.1.266 to narrow the regression. Review the mode indicator styling and any available customization path; done means the persistent red/orange border is neutral, configurable, or replaced by a transient cue without breaking the mode label.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
vscode
Área
accessibility, frontend
Tipo de issue
Error
Dificultad
3/5
Tiempo estimado
1-2 días
Estado de actividad
Activo
Claridad
Bastante claro
Aptitud para principiantes
52/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.