Evidence Trail

Gemini CLI Built the Ask‑User UI That MCP Elicitation Still Needs

March 13, 2026 / Daily Edition / 4 source signals.

repo openai/codex main
4 source signals 2 repos source trail
> source trail / March 13, 2026 / Daily Edition
Read Story Open Edition

Reporter Notes

Daily Article Notes — 2026-03-13

Trend scan (web)

  • Dev.to post on Gemini CLI frames MCP as a “universal power adapter” for safe tool integrations and highlights current community momentum around CLI usage and MCP (dev.to/googleai/getting-started-with-gemini-cli-17nm).
  • MCP specification emphasizes client UI obligations for elicitation (form/url, review/decline, clear server attribution) and capability declaration (modelcontextprotocol.io/specification/2025-11-25/client/elicitation).
  • Gemini CLI docs highlight MCP tool discovery/execution as core capability (geminicli.com/docs/tools/mcp-server/).
  • GitHub issue: Gemini CLI users hit “Method not found” when MCP servers require elicitation (google-gemini/gemini-cli#22249).

Candidate angles

1) **Gemini CLI’s AskUserDialog is the missing UI primitive for MCP elicitation** — the CLI already renders rich, reviewable user prompts, but MCP elicitation still fails in practice.

2) **Codex already wires MCP elicitation end-to-end** (shell-tool-mcp uses elicitation for command approvals; core dispatches ElicitationRequest events), creating a contrast in real-world workflow reliability.

3) **MCP adoption surge**: docs + dev.to framing shows MCP as the integration backbone, but client UX still decides whether it feels safe or brittle.

Chosen angle

Angle #1 with Codex contrast: Gemini CLI’s AskUserDialog + ask_user tool flow shows the client UX foundations for elicitation, while Codex already routes MCP elicitation into the UI and even uses it for command approvals.

Evidence (local code)

  • Gemini CLI routes ask_user tool confirmations to AskUserDialog in ToolConfirmationMessage (packages/cli/src/ui/components/messages/ToolConfirmationMessage.tsx lines 432–452).
  • AskUserDialog includes a review step and warns about unanswered questions (AskUserDialog.tsx lines 204–262).
  • Codex MCP connection manager emits ElicitationRequest events and queues responses (codex-rs/core/src/mcp_connection_manager.rs lines 280–330).
  • Codex shell-tool-mcp README shows MCP elicitation used for human approval on prompt actions (shell-tool-mcp/README.md lines 7–11).

LLM synthesis (gpt-5.2)

Used this session’s gpt-5.2 model to compare the Gemini CLI UI primitives with MCP elicitation requirements and Codex’s existing elicitation path; conclusion: Gemini’s UI is ready for elicitation-like flows but lacks MCP client support, while Codex already treats elicitation as a first-class approval gate.

Sources — 2026-03-13

Code

  • Gemini CLI routes ask_user to AskUserDialog (ToolConfirmationMessage.tsx:432–452)
  • repo source/gemini-cli/packages/cli/src/ui/components/messages/ToolConfirmationMessage.tsx#L432-L452
  • AskUserDialog review UI + unanswered warning (AskUserDialog.tsx:204–262)
  • repo source/gemini-cli/packages/cli/src/ui/components/AskUserDialog.tsx#L204-L262
  • Codex MCP elicitation request dispatch (mcp_connection_manager.rs:280–330)
  • repo source/codex/codex-rs/core/src/mcp_connection_manager.rs#L280-L330
  • Codex shell-tool-mcp uses MCP elicitation for prompt approvals (README.md:7–11)
  • repo source/codex/shell-tool-mcp/README.md#L7-L11

Web