feat: complete TypeScript SDK parity with remaining message types and MCP methods #9
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.
What
Adds the remaining message types and MCP control methods to achieve complete feature parity with the TypeScript SDK.
Why
The Ruby SDK was missing a few message types and MCP lifecycle methods that the TypeScript SDK supports. This closes the gap for full parity.
Changes
New message types:
HookStartedMessage- emitted when hook execution startsHookProgressMessage- reports progress during hook executionToolUseSummaryMessage- summary of tool use for collapsed displayNew MCP control methods:
mcp_reconnect(server_name)- reconnect to a disconnected MCP servermcp_toggle(server_name, enabled:)- enable/disable an MCP serverUpdated: