Repository navigation
fix(chat): action buttons reach the assistant only, never an autonomous agent - #91
Merged
Merged
Conversation
…us agent A button's hidden context names the page's WebMCP tools, which only an assistant is offered. Every chat of the tab hears a button, so: - an embed pinned to a configured agent no longer answers the buttons' ping nor opens on a click, and its chat ignores the action (leaving a pending one for the assistant's chat); - the back-office chat, which reopens the last conversation whatever its agent, now starts a conversation with its assistant when the open one is with a configured agent, after its start so a queued prompt cannot land in the resumed thread. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The chat itself already refuses an action when pinned to a configured agent, and moves the back-office chat to its assistant, so the host embeds' gating in lib-vuetify (and its copy of the assistant ids in lib-vue) only hid the buttons and kept the drawer closed: cosmetic, and it needed a release of both libraries. Dropped. The pinned-agent spec now drives a real enrolled agent and asserts the agent's conversation starts with what the person types: against a made-up id the turn was refused anyway, and the spec passed without the fix. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Action buttons (
DfAgentChatAction) now send their prompt only to the page's assistant, never to an autonomous agent. The fix is in the service's chat, so no release of lib-vuetify or lib-vue is needed._dev/chat-actionaccepts?agentId=and?agents=1, and a new e2e spec covers both cases (both tests fail without the fix).Why: agents are either assistants (WebMCP tools, the person's own session) or autonomous (their own identity, MCP on the server side). A button's hidden context names the page's WebMCP tools, so its request belongs to the assistant.
Heads-up: in the back office, clicking a button while a conversation with an autonomous agent is open now switches the panel to a new assistant conversation; the old one stays in the history. A drawer pinned to an autonomous agent still shows the buttons and opens on click, but sends nothing; hiding them would need the lib-vuetify change left out here.