> ## Documentation Index > Fetch the complete documentation index at: https://docs.duckie.ai/llms.txt > Use this file to discover all available pages before exploring further. # Autonomous Agents vs Workflows vs Runbooks > Choose the right Duckie building block for flexible support, repeatable processes, and procedural guidance An **Agent** is what you deploy. **Autonomous**, **Workflow**, and **Runbook** describe how the agent starts and how much structure Duckie should follow. These are not competing features. Strong Duckie systems often combine all three: an autonomous agent for flexible support, workflows for controlled processes, and runbooks for reusable operating guidance. ## Comparison | Concept | Best for | How it runs | What you configure | Watch-out | | -------------------- | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | | **Autonomous agent** | Broad support, triage, research, ambiguous customer requests | Starts from **Instructions**, then chooses resources and tools as needed | Model, Instructions, Tools, Callable agents, Knowledge Tags, Guidelines, Guardrails, Runbooks & Workflows | Needs clear scope, escalation rules, and careful access to write actions | | **Workflow** | Exact processes, compliance steps, approvals, routing, repeatable tool sequences | Visual graph with **Start**, **Tool**, **Decision**, and **End** nodes | Nodes, branches, Rule or AI decisions, Else paths, Ticket Data, Previous Node outputs | Less natural for broad, open-ended conversations | | **Runbook** | Flexible procedures, support playbooks, policy-guided conversations | Natural-language guidance the agent follows while adapting to context | Objective, steps, conditional guidance, tool references, snippets, escalation criteria | Not ideal when every branch and action must happen in an exact order | ## Use Autonomous Agents When Use an autonomous agent when the request is open-ended and Duckie needs to decide what to research, which tools to use, and how to respond. Good fits include: * Broad support queues * Triage across many topics * Research-heavy questions * Conversations that may need different runbooks, workflows, tools, or sub-agents * Situations where natural language judgment improves the outcome Keep autonomous agents focused with clear Instructions, scoped Tools, Knowledge Tags, Guidelines, Guardrails, and Runbooks & Workflows access. ## Use Workflows When Use a workflow when the process must follow exact steps, branches, approvals, retries, or tool order. Good fits include: * Eligibility checks * Required approvals * Deterministic routing * Compliance-sensitive paths * Multi-step tool orchestration * Reusable subprocesses that other agents or workflows can call A workflow can call Agents, Runbooks, and other Workflows from a **Tool** node. ## Use Runbooks When Use a runbook when there is a known procedure but the conversation still needs judgment and flexibility. Good fits include: * Troubleshooting guides * Policy-guided responses * Support playbooks * Escalation criteria * Procedures that are easier to maintain as natural language than as a visual graph A runbook is operating guidance, not a rigid script. If every branch and action must happen in a fixed order, use a workflow. ## Examples | Scenario | Good design | | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | Password reset | Runbook for flexible troubleshooting, workflow if security checks must happen in fixed order, autonomous agent if Duckie first needs to classify the issue | | Refund request | Workflow for eligibility and approval gates, runbook for policy-guided customer messaging, autonomous billing agent to choose the right path | | Chargeback handling | Workflow backbone for deadlines and required fields, autonomous agents for reading notes, drafting evidence, and summarizing context | | Internal review | Workflow routes the approval step, then uses Ask and Wait, Escalator, or an agent to involve a human | ## How to Decide Start with the strictest requirement: 1. If exact order or auditability matters, start with a workflow. 2. If a flexible procedure is enough, start with a runbook. 3. If the agent must choose the path, start with an autonomous agent. 4. If one part needs a specialist, add a sub-agent. 5. If a human must approve, add an approval or escalation path. ## Related Docs Configure agents that choose resources and tools at run time. Build visual process logic. Write flexible procedures. Review start modes and access settings.