Visitar URL original
feat(mcp): support boolean elicitation approvals by Nomadcxx · Pull Request #33748 · anomalyco/opencode · GitHub
Skip to content

feat(mcp): support boolean elicitation approvals - #33748

Closed
Nomadcxx wants to merge 1 commit into
anomalyco:devfrom
Nomadcxx:rama/mcp-elicitation-boolean-tui
Closed

Nomadcxx wants to merge 1 commit into
anomalyco:devfrom
Nomadcxx:rama/mcp-elicitation-boolean-tui

Conversation

@Nomadcxx

@Nomadcxx Nomadcxx commented Jun 25, 2026 •

Copy link
Copy Markdown
Contributor

Issue for this PR

Refs #23066
Refs #28567

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

Adds the first MCP elicitation path for TUI sessions. The MCP client now handles elicitation/create form requests for flat boolean schemas during tool calls, stores pending requests, emits asked/replied events, and exposes instance HTTP/SDK endpoints for the TUI.

The TUI renders a human approval prompt with the requesting server name and distinct accept, decline, and cancel actions. Unsupported schemas, URL mode, auth probe clients, timeouts, and disconnect cleanup return cancel so tool calls do not wait forever.

This slice does not add URL mode, broader JSON Schema form types, web UI, desktop UI, or model-callable approval tools.

How did you verify your code works?

  • bun run typecheck
  • cd packages/opencode && bun test --timeout 30000 test/mcp/elicitation.test.ts test/mcp/lifecycle.test.ts test/mcp/oauth-auto-connect.test.ts test/mcp/oauth-browser.test.ts test/server/httpapi-mcp-elicitation.test.ts test/server/httpapi-mcp-oauth.test.ts
  • cd packages/tui && bun test --timeout 30000 test/cli/cmd/tui/sync.test.tsx
  • bun run --filter @opencode-ai/tui typecheck
  • bun run --cwd packages/opencode build
  • Manual dev-build test: started the rebuilt TUI from this branch, connected a repo-local stdio MCP demo server, called elicitation-demo_request_approval, confirmed the TUI prompt rendered with the server name and checkbox label, accepted the prompt, and verified the MCP tool returned {"action":"accept","content":{"allowDemo":false}}.
  • git diff --check

Screenshots / recordings

Live TUI prompt from the dev build:

MCP elicitation TUI prompt

Manual round trip after accepting the prompt:

MCP elicitation accepted result

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

@github-actions

Copy link
Copy Markdown
Contributor

The following comment was made by an LLM, it may be inaccurate:

No duplicate PRs found.

(The search only returned the current PR #33748 itself and one unrelated PR about LLM command-approval classifier. There are no other open PRs addressing the same MCP elicitation boolean approvals feature.)

@Nomadcxx Nomadcxx mentioned this pull request Jun 25, 2026
1 task done
@Nomadcxx
Nomadcxx force-pushed the rama/mcp-elicitation-boolean-tui branch 4 times, most recently from b54b292 to 69ceccf Compare June 25, 2026 03:18
@Nomadcxx
Nomadcxx force-pushed the rama/mcp-elicitation-boolean-tui branch from 69ceccf to 9e33259 Compare June 26, 2026 12:43
@venkman-del

Copy link
Copy Markdown

This is great but does it require your full stack of changes from #23066?

@github-actions

Copy link
Copy Markdown
Contributor

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

  • The PR was created more than 1 month ago
  • The PR had fewer than 2 positive reactions
  • Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants