Back to Signal Feed
CodeTracked since May 21, 2026

Web UI gains MCP attach/detach/scope management with parity to TUI

The PR adds a web management panel for MCPs and new REST endpoints for MCP catalog retrieval and per-session attach/detach/scope changes, aligning web behavior with the existing TUI MCP flow and closing four previously missing parity cases.

agent-deckMCPWeb UIMCPManager

What Happened

  • The PR adds a web management panel for MCPs and new REST endpoints for MCP catalog retrieval and per-session attach/detach/scope changes, aligning web behavior with the existing TUI MCP flow and closing four previously missing parity cases.
  • The PR adds a web management panel for MCPs and new REST endpoints for MCP catalog retrieval and per-session attach/detach/scope changes, aligning web behavior with the existing TUI MCP flow and closing four previously missing parity cases.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Implemented a dedicated web MCP pane and MCP management handlers that expose catalog + attach/detach/move operations per session, and introduced an MCPManager-based path so web writes/read paths reuse existing session MCP helper APIs and produce the same on-disk MCP state as TUI.

Why Track This

Why It Matters

Users and operators can now manage MCPs directly in the web interface (browse catalog, attach/detach, and toggle local/global scope) instead of falling back to terminal-only workflows, which makes session MCP setup and maintenance faster and operationally consistent; this also enables automated MCP operations through a defined API contract. The web and TUI now share the same session persistence path, reducing risk of divergent `.mcp.json` behavior, but parity should be watched around scope validation, mutation-disabled paths, and remote-session path handling as MCP coverage grows.

Impact

Users and operators can now manage MCPs directly in the web interface (browse catalog, attach/detach, and toggle local/global scope) instead of falling back to terminal-only workflows, which makes session MCP setup and maintenance faster and operationally consistent; this also enables automated MCP operations through a defined API contract. The web and TUI now share the same session persistence path, reducing risk of divergent `.mcp.json` behavior, but parity should be watched around scope validation, mutation-disabled paths, and remote-session path handling as MCP coverage grows.

What To Watch Next

  • Watch whether agent-deck becomes a repeated pattern.
  • Track follow-up changes around Model Context Protocol.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: scope_toggle_edge_case_regression, mutation_disabled_session_403_handling.
Open Topic TimelineOpen Technical EventOpen Original Sourcescope_toggle_edge_case_regression / mutation_disabled_session_403_handling / remote_session_path_state_mapping / session_state_divergence_between_ui_and_tui

Supporting Evidence