Choose how to build your agent
Glean provides several ways to create an agent. Start by choosing a mode, then choose the entry point and starting asset that fit your experience. Independent Agents use a distinct execution model when work must continue with an agent-owned identity.
tip
For most use cases, start with Auto mode. Describe the outcome, review the generated draft, and switch to Workflow mode when you need more predictable execution or manual control.
The build hierarchy
Modes
- Auto mode: Describe an outcome in natural language. Glean plans the work, selects available capabilities, and creates a draft that you can refine and test. See Create agents with Auto mode.
- Workflow mode: Define a fixed sequence of steps, tools, branches, and hand-offs. See Create your first Workflow agent.
Entry points
- Agent Builder: Use the visual builder to configure, inspect, test, and publish agents. It supports Auto mode and Workflow mode.
- Natural-language Workflow creation: Describe a structured workflow and let Agent Builder generate initial Workflow mode steps. You can then edit the steps manually or with natural language. See Create a Workflow agent using natural language.
Starting assets
- Templates: Start with a pre-built agent for a common workflow, then review its instructions, tools, knowledge sources, and requirements. See Agent templates.
Code-based path
- Headless builder: Build, test, and publish an Auto mode agent from a coding environment. See Create an agent with the headless builder.
Distinct execution model
- Independent Agents: Use an agent-owned identity, supported presence, and approved credentials when a workflow must monitor events or continue without the user who started it. See Independent agents overview.
Decision table
| Choose this path | Predictability | Required control | Complexity | Technical experience | Identity requirements | Execution model |
|---|---|---|---|---|---|---|
| Auto mode in Agent Builder | Adaptive | Review and refine the generated plan | Low to medium | No coding required | Runs with the user or configured agent access | User-started, scheduled, or supported triggered runs |
| Workflow mode in Agent Builder | High | Configure each step, branch, and hand-off | Medium to high | No coding required; workflow design experience helps | Runs with the user or configured agent access | Explicit step sequence |
| Natural-language Workflow creation | High after refinement | Start with generated steps, then edit the workflow | Medium | No coding required | Same as Workflow mode | Explicit step sequence |
| Template | Depends on the template | Customize an existing configuration | Low to medium | No coding required | Depends on the template | Depends on the template |
| Headless builder | Adaptive | Manage the agent files and tests in code | Medium to high | Coding environment and Glean plugin | Depends on the agent configuration | Auto mode execution |
| Independent Agent | Depends on the workflow | Govern identity, credentials, triggers, and write tools | Medium to high | Agent-building and administrative experience | Agent-owned identity or approved service credentials may be required | Continues without an active user session |
The table describes the usual design trade-offs. Features, triggers, tools, identity options, and publishing controls depend on your Glean deployment.
A practical starting sequence
- Describe the outcome and try Auto mode.
- Start from a template if a close match exists.
- Review the draft with representative inputs and edge cases.
- Move to Workflow mode when you need explicit branches, fixed hand-offs, or repeatable step execution.
- Choose an Independent Agent only when the workflow needs its own identity or must continue without an active user session.
- Use the headless builder when you need a code-based development workflow.
For the feature and deployment details that affect each path, see the Feature and availability matrix.