Summary
Align the TUI’s monitoring tab labels with the web Inspector so Protocol, Network, and Console mean the same thing in both UIs.
Background
Web monitoring tabs use Protocol (JSON-RPC history), Network (HTTP fetch), and Console (stdio stderr). The TUI used Messages, HTTP Requests, and Logging for those same streams — and “Logging” was especially confusing because web’s Logs tab is MCP logging/* notifications (which the TUI does not have).
Changes
- Rename TUI tab labels:
- Messages → Protocol
- HTTP Requests → Network
- Logging → Console
- Update pane headers and
clients/tui/README.md to match.
- Reassign accelerators so each is a letter in the tab name, unique, and preferably early in the word:
- Protocol →
p (frees p from Prompts)
- Network →
n
- Console →
o (c remains Connect)
- Prompts →
m (prompts)
- Underline the accelerator letter in the tab bar even when it is mid-word (e.g. Prompts, Console).
Internal tab ids (messages / requests / logging) are left unchanged for this pass.
Out of scope
- Adding a TUI equivalent of web’s MCP Logs tab (feature gap, not a rename).
- Renaming internal tab ids / focus keys.
Acceptance
Summary
Align the TUI’s monitoring tab labels with the web Inspector so Protocol, Network, and Console mean the same thing in both UIs.
Background
Web monitoring tabs use Protocol (JSON-RPC history), Network (HTTP fetch), and Console (stdio stderr). The TUI used Messages, HTTP Requests, and Logging for those same streams — and “Logging” was especially confusing because web’s Logs tab is MCP
logging/*notifications (which the TUI does not have).Changes
clients/tui/README.mdto match.p(freespfrom Prompts)no(cremains Connect)m(prompts)Internal tab ids (
messages/requests/logging) are left unchanged for this pass.Out of scope
Acceptance
c) still worksnpm run cigreen