AI Agents vs Automation
Working notes on when fixed automation is enough and when agentic workflows are worth it.
Core distinction I keep using: automation follows a predefined path. Agentic systems pursue an outcome and choose paths along the way.
If the path is known, automation usually wins. If the path is unknown but the outcome is clear, an agent can help.
That distinction keeps me from using "agent" as a synonym for "smart automation." A workflow can use an LLM and still be plain automation if every step is fixed. A workflow becomes agentic when the system chooses tools, changes plans, or decides what information to gather next.
Quick decision table
| Situation | Default choice |
|---|---|
| Repetitive, stable process | Automation |
| Many edge cases, shifting context | Agent |
| High-risk action (money/data deletion/permissions) | Automation + approval gate |
| Need strict determinism | Automation |
| Need adaptive tool selection | Agent |
Simple model
Automation means "do steps 1,2,3 exactly."
Agent means "get result X, and re-plan if needed."
I treat agents as planners with tools, not as magic workers.
Concrete examples
| Job | Better starting point | Why |
|---|---|---|
| Send a weekly report from known dashboards | Automation | source, format, and schedule are stable |
| Investigate why a metric moved | Agent | path depends on data, logs, docs, and context |
| Resize uploaded images | Automation | deterministic transform with clear success criteria |
| Triage a support ticket with multiple systems | Agent with approval gates | context gathering is variable, final action may be risky |
| Reconcile invoices against known rules | Automation first | rules are explicit; exceptions can escalate |
Most teams should start with the boring option. Agents are useful when the workflow has meaningful uncertainty, not when the team simply wants a modern label.
Common mistake
Using an agent for a checklist problem.
This adds cost and latency without adding real value. If a finite workflow solves it cleanly, I start there.
The opposite mistake is also common: forcing automation onto a problem where the exception paths dominate. If humans keep adding "one more if statement" for every customer, vendor, or system variant, the workflow may need an agentic planner or at least an LLM-assisted triage layer.
Starter architecture
Start with one planner, two or three tools, an explicit stop condition, human approval for risky actions, and step-level trace logs.
Only add more agents after one-agent reliability is boring.
When I would upgrade automation to an agent
I look for three signals: the workflow requires context gathering from multiple sources, the correct next step depends on what was just discovered, and humans can define success clearly without being able to list every path upfront.
If all three are true, an agent may be worth the extra operational burden. If only one is true, I usually keep the automation and add a small human-review or classification step.
Operating cost
Agents need traces, tool permissions, evals, fallback behavior, and monitoring. They also create product questions: when should the system ask for help, when should it stop, and who owns a bad action?
That cost is worth paying only when adaptability creates enough value. Otherwise deterministic automation is faster, cheaper, and easier to debug.
Trend signals behind this note
- OpenAI shipped agent-building primitives on March 11, 2025: New tools for building agents.
- Google Cloud framed broader enterprise agent adoption in December 2025: 5 ways AI agents will transform the way we work in 2026.
- Stack Overflow 2025 survey shows high AI usage with mixed trust and maturity: AI section, 2025 survey.
Takeaway
Choose by task shape, not by trend. Unknown path plus clear outcome is the agent zone; known path plus clear steps is automation territory.