interactive_feedback
Collects interactive user feedback via a Web UI, enabling AI agents to present summaries or questions, wait for confirmations, and receive additional instructions.
Instructions
Open a Web UI to collect interactive feedback from the user.
This tool is the PRIMARY communication channel with the user. The full list of "when to call" scenarios lives in the project's gl-mcp-feedback user rules; this docstring only covers the runtime contract that the tool itself enforces.
Strict prohibitions:
- While this tool is available, DO NOT invoke Cursor's built-in
AskQuestion. Route every question through summary as a
numbered list.
- DO NOT end the turn with a plain-text reply when there is
substantive content for the user to read. Put it in summary.
- When the user skips without feedback, re-call this tool to ask
why; only stop on explicit termination
(结束 / 不用了 / stop / done).
- Allowed parameters: project_directory, summary,
timeout, plus conversation_id, which a Cursor hook fills
in: never set it yourself. Names like question / choices /
options belong to AskQuestion and will fail schema
validation here.
summary writing rules:
- Markdown: headings (##), lists, tables, code fences, bold for
key decisions. Include modified file paths and explicit
questions when applicable.
- NEVER pass an empty string or the placeholder phrase
我已完成了您请求的任务。 — runtime validation rejects them
and you must re-call with a real summary.
Queued messages:
While you work between two calls, the user can keep typing in the
Web UI; those messages are queued (at most 3) and reach you in one
of two ways, both under a header starting with
（你工作期间，用户追加了 N 条消息:
- After any tool call, a Cursor hook appends the queue to that
tool's result. Images are saved as local files whose paths are
listed in the block: open them with ``Read``.
- On your next call to this tool, the queue is returned
immediately, without waiting for a new reply.
Either way they are NOT an answer to the ``summary`` you just
passed: treat them as new instructions in the given order, act on
them, then call this tool again.Args:
project_directory: Absolute or relative project path. Defaults to cwd.
summary: Required Markdown summary. No empty string, no placeholder.
timeout: Seconds to wait for user feedback. Values above 600 are
capped, so always pass 600.
conversation_id: Filled in by a Cursor hook. Never set it yourself.
Returns:
ToolResult: TextContent with the user's text feedback plus
MCPImage objects for any uploaded images. An empty result
means the user skipped — re-call to ask why. A result starting
with [interactive_feedback TIMEOUT] means the user has not
replied within the wait limit — re-call to keep waiting.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| summary | No | Markdown summary of the AI's current work / plan / question, rendered in the Web UI. MUST be filled in with substantive content; empty strings and placeholder phrases (e.g. "我已完成了您请求的任务。") are rejected at runtime. | |
| timeout | No | Seconds to wait for user feedback. Values above 600 are capped, so always pass 600. | |
| conversation_id | No | Filled in automatically by a Cursor hook to identify the conversation. NEVER set this yourself; always leave it empty. | |
| project_directory | No | Project directory path. | . |