Remote Control web UI shows raw ANSI escape codes for local command output
Description
When using Remote Control (web UI at claude.ai/code) connected to a local CLI session, built-in commands that produce ANSI-formatted output (e.g. /context) display raw escape sequences instead of rendered text.
Steps to reproduce
- Start a Claude Code session locally
- Connect via Remote Control from the web UI
- Run
/context(or any built-in command that uses ANSI colors/formatting)
Expected behavior
The output should either:
- Render the ANSI escape codes as formatted/colored text (preferred)
- Strip the ANSI codes and show plain text (acceptable fallback)
Actual behavior
Raw ANSI escape sequences are displayed as literal text, e.g.:
[1mContext Usage[22m
[38;5;244m⛁ ⛁ [38;5;246m⛁ ⛁ ⛁ ⛁ ⛁ ⛁ ⛁ ⛁ [39m [38;5;246mclaude-opus-4-6 · 37k/200k tokens (18%)[39m
Screenshots
The same /context command rendered properly in the terminal CLI vs showing raw codes in the Remote Control web UI.
Additional context
- Remote Control is otherwise functional (message relay, tool approval work fine)
- Affects all local commands that produce colored/formatted terminal output
- Tested on Claude Code with Opus 4.6, Remote Control research preview
Broader note
The Remote Control web UI currently lacks several CLI features beyond rendering: no / command autocomplete, no /mcp toggle, no /skills browser, no /context display. At minimum, rendering the output of commands that do work would be a quick win.
Generated with Claude Code
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗