co-mono/packages
Sumeet Agarwal ff5148e7cc
feat(extensions): forward message and tool execution events to extensions (#1375)
The extension system currently only forwards agent_start, agent_end,
turn_start, and turn_end events. This means extensions cannot access
streaming text (token-by-token), message lifecycle, or tool execution
progress — all of which are available to internal subscribers.

This adds forwarding for the remaining 6 agent event types:
- message_start, message_update, message_end
- tool_execution_start, tool_execution_update, tool_execution_end

These follow the exact same pattern as the existing forwarded events:
new interfaces in types.ts, exports in index.ts, and else-if blocks
in _emitExtensionEvent(). The new types are included in ExtensionEvent
and automatically flow through RunnerEmitEvent (they're not in the
exclusion list).

This enables extensions to build real-time UIs, streaming WebSocket
bridges, and other integrations that need fine-grained event access.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Mario Zechner <badlogicgames@gmail.com>
2026-02-12 20:30:46 +01:00
..
agent Add [Unreleased] section for next cycle 2026-02-09 00:17:28 +01:00
ai chore(ai): add changelog entry for copilot claude messages routing 2026-02-12 18:53:04 +01:00
coding-agent feat(extensions): forward message and tool execution events to extensions (#1375) 2026-02-12 20:30:46 +01:00
mom Add [Unreleased] section for next cycle 2026-02-09 00:17:28 +01:00
pods Release v0.52.9 2026-02-09 00:16:45 +01:00
tui Add [Unreleased] section for next cycle 2026-02-09 00:17:28 +01:00
web-ui Add [Unreleased] section for next cycle 2026-02-09 00:17:28 +01:00