Mac and Windows Tools APIs: Choosing the Right Automation Layer
Choose an automation boundary that matches the task, then document the platform differences that matter for Mac and Windows runners.
Read the guideFIELD NOTES / TOPIC
Tool Runners, in practice.
Read focused tool runners articles and connect the ideas to the rest of your tools API workflow.
A tool runner provides a controlled place for an action to execute. It needs a clear input contract, a prepared environment, bounded execution, and a structured result. Setup and cleanup are part of that responsibility.
These articles show how to make a workflow repeatable without hiding its assumptions. Decide how cancellation works, separate infrastructure failure from target failure, and review the safety of repeated actions before adding retries. Keep the execution record useful to both the caller and the person responsible for operating the environment. Review question: What happens if preparation succeeds but execution is cancelled halfway through, and which component owns cleanup and the final result?
Articles in this collection
Structured Logs for Reliable Tool Runners
Make a tool run explain itself. Design structured events that show what happened, which attempt produced the result, and what an operator should do next.
Read the guide
Tool Runners and Test Flows: Build a Repeatable Workflow
Turn a collection of tool calls into a repeatable test flow with explicit state, bounded retries, and results that explain what happened.
Read the guide