Repository navigation
let agents send feedback over mcp and from the agent pages - #107
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Agents can now tell us when something doesn't work as they expected: a fifth MCP tool,
send_feedback, and a feedback form at/agent/feedback, linked from the foot of every agent page. Both go through the same code path (agent-side/feedback.ts, alsoPOST /api/agent/feedback) and land in a newAgentFeedbacktable (migrationv018_add_agent_feedback) with the agent, its provider, the connection and tool it is about where named, and whether it came over MCP or the web. The MCP server's instructions tell agents to use it and then carry on with the person's request; nothing in the app shows the feedback, it is for us to read from the table.Open workspace in Conductor