[Feature Request] Native Elicitation support for MCP tools (Commit Message Refinement) #21231

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Context
I am the developer of git-courer, a local MCP server that acts as a Git specialist to achieve Zero tokens spent on git operations. By delegating diff analysis and commit message generation to a local AI (Ollama), we significantly reduce cloud costs.
The Gap: Elicitation Support
Currently, Opencode's MCP implementation lacks a native Elicitation (Human-in-the-loop) flow. While tools like Claude Code have already set a standard by allowing users to refine and edit agent-proposed messages before persistence, Opencode currently follows a "fire-and-forget" model.
In git-courer, we have already implemented a UI port with an Edit method, but we cannot bridge this with the Opencode host.
The Problem
• Lack of Refinement: If the local AI generates a message that needs a minor tweak, the user has no UI hook in Opencode to edit it programmatically.
• Token Waste: Without elicitation, the Cloud Agent often wastes tokens re-explaining or re-thinking changes that a simple manual edit would solve instantly.
• Market Competitiveness: As elicitation becomes a standard for professional AI agents to ensure safety and precision, its absence in Opencode limits the potential of specialized local tools.
Proposed Feature
Implement Elicitation hooks in the MCP protocol to allow tools to return a "draft" state. This should trigger an editable text buffer in the UI, enabling the user to confirm or modify the content (e.g., a commit message) before final execution.
Impact
This would allow git-courer and similar tools to provide a professional-grade Developer Experience (DX) while maximizing Token Savings.