Explain feature generates a summary and step-by-step description of the automation Co-Pilot for Automators (Co-Pilot).

As development progresses—especially in long-running, multi-phase builds—teams routinely lose context of their work. The automation evolves through iterative prompt cycles, partial builds, refactors, and incremental condition changes. In these conditions, the value of explain feature is not just a summary, but a structured, inspectable representation of the current operational logic on the canvas, enabling developers to rapidly re-orient, review correctness, and decide what to improve next.

Explain feature overview

When using the Explain feature, Co-Pilot analyzes the automation as of the last saved version and generates an explanation that typically includes:

  • A high-level overview of what the automation is intended to accomplish, based on the current structure and configured logic.

  • A step-by-step breakdown that identifies where operations begin, how execution progresses, and how data/outputs flow from one step to the next.

  • Condition and branch visibility, calling out gates (if/else logic, filters, eligibility rules, exceptions) that can change runtime behavior or results.

  • Operational context, clarifying what each step is doing in functional terms (not just restating labels), that is especially useful when steps were created over several iterations.

This is designed to help developers quickly answer: “What does this automation do now?” and “Where do I intervene to change behavior safely?”

Explain feature use cases

Use Explain feature whenever you need to re-establish a shared understanding or reduce the risk of making a change in the wrong place. Common, high-value moments include:

  • After several rounds of prompt-driven edits (logic drift is common; /explain re-baselines the team on current behavior).

  • Before refactoring or extending the automation (confirm existing intent and identify the correct insertion point).

  • When debugging unexpected results (quickly surface the conditions and branches that could be redirecting execution).

  • During code review or handoff to another developer/team (create a consistent narrative of the automation for review and onboarding).

  • After merging contributions from multiple collaborators (validate that combined logic still matches intended outcomes).

  • When the automation becomes lengthy and it’s no longer obvious where setup and validations end and what steps drive the desired outcomes.

In short: use it any time the cost of misunderstanding current behavior is higher than the cost of a quick analysis pass.

Explain the whole scenario or selected items

You can explain the automation as a whole when you need to quickly regain context or validate current behavior, or explain a specific section or line.
  • To explain whole automation type /explain in the interface. Ensure no automation nodes or lines are selected.
  • To explain a section, select your specific items or lines and type /explain in the interface.

This feature reduces cognitive load while improving confidence that modifications are being made in the correct place.