Skip to main content

Tasks introduction

Tasks are the building blocks of automation in Brixel. They are the equivalent of tools in the LLM sense, but with a structure that makes them composable and scalable across Builders.

The shared task contract​

Every task follows a common abstraction:

  • Input schema: what data the task expects.
  • Internal parameters: configurable behavior (defaults, constraints, options).
  • Output schema: what the task produces.

Because every task exposes the same contract, Brixel can mix different task types without losing consistency.

Task types​

  • Action
    A monolithic, ready-to-use operation (e.g., "Send an email").
  • Artifact
    A visual task that introduces human interaction or displays results directly in the chat.
  • Tool (Brixel)
    A composed task that chains other tasks together (e.g., "Download a Word file and convert it to PDF"). Tools can include other tools.
  • Variant
    A task customized by a user (parameter overrides).
  • Plan Generator
    An orchestration engine that references many tasks and creates a dynamic execution plan from a user request.

How tasks fit together​