pi-extension-lifecycle

The Pi agent loop processes tool execution through inner and outer loops, managing event sequencing from turn_start to turn_end. It structures context, before_provider_request, tool_call, and tool_result events to govern extension timing and message delivery.

Tool-call sequencing in Pi agent workflows follows a structured lifecycle that governs execution order and event handler capabilities. It defines specific input and output structures for tool_call and tool_result events to ensure reliable extension design.

To manage abort and interrupt behavior in Pi-driven workflows, you intercept the agent turn using event handlers. The lifecycle reference documents specific interrupt points and abort mechanisms to safely halt tool execution and control message delivery.

Message delivery semantics across Pi agent turns distinguish between steering messages and follow-up messages. Steering intercepts and guides an active turn, while follow-up messages queue for subsequent execution after the current tool execution lifecycle completes.

You need the extension lifecycle reference when designing new extensions, integrating tools, or building event handlers for Pi coding agents. It provides the necessary lifecycle diagrams and empirical session-data patterns required for safe, reliable extension development.

Yes, you can use this lifecycle reference to document event handler capabilities for Pi agent extensions. It details the input and output structures for core events like context, tool_call, and turn_end, satisfying requirements for extension documentation.