@composio/slim@0.27.0
Composio released @composio/slim@0.27.0, adding session hooks that can intercept and block tool executions before running or before results reach the agent.
Why this signal matters
In version 0.27.0 of @composio/slim, session hooks are introduced to allow blocking tool calls prior to execution or intercepting results before they reach the agent. The create() and update() functions now accept a hooks array; setting hooks on update() replaces the full list, and passing null clears all hooks. Hooks are incompatible with experimental.sessionConfigId. Blocked calls via session.execute() and session.executeMeta() return resultType: 'blocked' , an empty data object, the hook's message in error , and a blockReason . Provider integrations report this as a failed call containing that message, and responses include hookResults when applied. Additionally, session.proxyExecute() and ctx.proxyExecute() now return a resultType of either 'completed' or 'blocked'. Because blocked requests yield no HTTP response, callers must verify resultType before reading HTTP status properties.
Actionable summary
Composio @composio/slim@0.27.0 introduces session hooks in create() and update() to block tool calls or results. Blocked calls return resultType: 'blocked' across execute, executeMeta, and proxyExecute methods.
- Agent usefulness
- 77/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Verify and update TypeScript code invoking session.proxyExecute() and ctx.proxyExecute() to check resultType before reading HTTP status.
- Do not use hooks simultaneously with experimental.sessionConfigId in session configuration.
- Handle resultType: 'blocked' when processing outputs from session.execute() and session.executeMeta().