Skip to main content

Commands

Commands are procedural instructions that work similarly to Abilities, except they are triggered only when the user explicitly asks for them from the chat.

How commands work​

Instead of being applied proactively by the Builder, a Command stays dormant until the conversation clearly requests it. Once triggered, it can guide the Builder through a predefined approach, reference tools, and structure the execution flow.

Typical content​

Commands often include:

  • The user-facing intent that should trigger the command.
  • The step-by-step method to execute once triggered.
  • Which tools to call and in what order.
  • Constraints, required inputs, and output expectations.

Example​

A command like "Generate a weekly sales summary" can define a repeatable flow such as:

  1. Fetch the relevant reporting data.
  2. Aggregate the key metrics.
  3. Format the result as a shareable summary.

Why they matter​

Commands let you expose repeatable workflows on demand without forcing the Builder to keep applying them automatically in unrelated conversations.