April 2026 Release
April 2026 was a quieter month. It shipped a small number of real, targeted improvements rather than a major new feature area — the most notable being new control over how tool results are used in agent responses, and easier tool response mapping.
Developers maintaining custom applications should use the Developer Hub for API, SDK, package, and migration notes.
Highlights
- New action return modes control how a tool's result is used in an agent's response.
- Tool response mapping can now be generated automatically from a sample API response.
- Early groundwork for agent run tracing, which becomes visible in Studio the following month.
New in Studio
Action return modes
Tool and action steps gained return-mode options — direct, aggregate, or synthesis — that control how a result feeds back into an agent's response, rather than always being handled the same way. This gives Peer and Flow builders more control over how tool output is presented in a conversation.
Automatic tool response mapping
Building on the tool testing and response-mapping work from December and January, the tool creation wizard can now generate a response mapping automatically from a sample API response, reducing manual setup when adding a new tool.
See Custom Tools.
Agent run tracing (foundation)
Backend support and a Peer-level setting for persisting agent run traces were added this month. This is groundwork only — the visible trace review experience shipped in May 2026.
Action required
Studio and Pulse users do not need to migrate anything manually.
Technical teams that maintain custom apps, SDK integrations, or client-side tools should use the Developer Hub for migration details.