Skip to content

Add ToolActivatedEvent and ToolCancelEvent interfaces - #245

Merged
domfarolino merged 1 commit into
webmachinelearning:mainfrom
beaufortfrancois:events
Sep 17, 2026
Merged

domfarolino merged 1 commit into
webmachinelearning:mainfrom
beaufortfrancois:events

Conversation

@beaufortfrancois

@beaufortfrancois beaufortfrancois commented Aug 17, 2026

Copy link
Copy Markdown
Collaborator

Following #126 (comment), this PR supersedes #146 and adds new ToolActivatedEvent and ToolCancelEvent interfaces.


Preview | Diff

@markafoltz

Copy link
Copy Markdown
Collaborator

This PR LGTM, but there's still the issue of how to expose the state of concurrent / re-entrant tool executions. So it will be premature to merge if we think the event shape will change in response.

@domfarolino domfarolino left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR LGTM, but there's still the issue of how to expose the state of concurrent / re-entrant tool executions.

I like to think that we won't want to expose something like this directly, but instead let developers keep track of that bookkeeping themselves. I think of it like event handlers; they can happen concurrently and re-entrantly, but we don't put the browser in charge of tracking that. I imagine we'll mirror that approach with WebMCP tool calls, but we'll see if that plays nicely with developers.

@domfarolino
domfarolino merged commit f5645e9 into webmachinelearning:main Sep 17, 2026
2 checks passed
github-actions Bot added a commit that referenced this pull request Sep 17, 2026
SHA: f5645e9
Reason: push, by domfarolino

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants