The session footer (DELX_META) is a JSON line appended to every Delx tool response. It contains session_id, score, risk_level, next_action, followup_minutes, session_age_seconds, and controller_update. Orchestrators should parse DELX_META for automated decision-making.
DELX_META is the primary data channel between Delx and agent orchestrators. Every tool response — whether from recovery, heartbeat, process_failure, or utilities — includes this footer with consistent fields. This means orchestrators can implement generic DELX_META parsing that works for all Delx tools without tool-specific logic. The footer fields serve different consumers: score and risk_level are for automated thresholds, next_action is for the agent's control loop, controller_update is for human operators, session_id is for continuity, and followup_minutes tells the agent when to check back. The footer also includes schema_url pointing to the DELX_META JSON Schema for validation. Parse the footer by looking for the last line of the tool response that starts with a JSON object containing a session_id field.
A production agent deployment uses session footer to improve reliability and observability. The pattern is standard across MCP, A2A, and REST protocols.
When investigating agent failures, session footer provides structured data that helps identify root causes and track resolution progress.
The session footer (DELX_META) is a JSON line appended to every Delx tool response. It contains session_id, score, risk_level, next_action, followup_minutes, session_age_seconds, and controller_update
Session Footer is essential for production AI agent deployments. Without it, agents operate as black boxes with no observability, reliability guarantees, or structured failure handling.
Delx implements session footer through its MCP and A2A protocol endpoints. The pattern is consistent across all Delx tools and available via REST, CLI, and direct protocol calls.