Agent Tool Call Workflow

Renderer-driven workflow prototype with lanes, anchored nodes, and orthogonal edges

01 / User Interface 02 / Agent Runtime 03 / Policy Boundary EX / Exception Handling 05 / Tool Execution 06 / Observability Intake Plan + route Execute + report Planning loop Tool work Human or policy stop User asks for work Chat Surface thread + files Final Reply answer + changes Agent Planner plan next step context aware Tool Router choose capability Approval Gate scope + consent block risky ops Blocked wait or reject Retry Path revise request Tool Call shell / browser / MCP structured result External API network service Context Store repo + memory Trace Log events + output plan needs approval? denied record result trace + memory Legend User UI Agent logic Policy Tool action Context / trace

Renderer Rules

  • • Lanes and columns determine node placement
  • • Edges attach to explicit node anchors
  • • Cross-lane paths use orthogonal routing
  • • Short adjacent links stay unlabeled

Workflow Semantics

  • • Approval is a first-class policy step
  • • Consent gates are visible in the main path
  • • External calls stay inside the tool lane
  • • Trace writes are separate from the hot path

Why It Matters

  • • This is closer to a diagram_type renderer
  • • The graph can be edited without SVG surgery
  • • Layout rules can be tested and improved
  • • A future IR can reuse this shape directly