Skip to content

expose chat message agent to plugin #2254

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

expose chat message agent to plugin #2254

wants to merge 1 commit into from
+2 −1

Conversation

karl-tye
Copy link

@karl-tye karl-tye commented Aug 26, 2025 •
edited
Loading

After attempting to retrieve the agent for a particular message in my plugin, this seemed like the only available option. I believe this fits under Missing standard behavior for plugins 🤞

Looking at the design, I'm sure there's a better place to expose this information. Feedback would be greatly appreciated

@thdxr
Copy link
Contributor

thdxr commented Aug 30, 2025

i think it's under message.mode - it's still under the old name

@karl-tye
Copy link
Author

i think it's under message.mode - it's still under the old name

I can see that this is the case for assistantMsg (type AssistantMessage) later on in the chat function. However, this is not propagated via Plugin.trigger. We could extend the "chat.message" hook to be triggered on both user and assistant messages which could be interesting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@karl-tye @thdxr