Discussion about this post

User's avatar
Pawel Jozefiak's avatar

Kane, the distinction you draw between orchestration and automation layers resonates with what I have learned building my own AI agent. Your point about using agents "temporarily to discover patterns" before transitioning to deterministic flows is something I stumbled into rather than planned. My agent started as a sprawling autonomous experiment, and I kept finding myself converting successful agent behaviors into simple scheduled scripts or rule-based workflows. The agent was essentially doing research and development on my behalf.

Where I have landed differently is on the question of permanence. Some of my use cases genuinely resist rule definition - not because the task is complex, but because the inputs are unpredictable. Cross-referencing unstructured information sources, deciding what is worth surfacing to me, adapting to new platforms without explicit programming. These feel like genuinely open-ended problems where the agent earns its keep ongoing, not just during a discovery phase.

The security and efficiency concerns you raise about browser automation are real though. I have avoided computer-use approaches entirely for exactly those reasons - API integrations and structured data flows wherever possible, even if it limits what the agent can do.

I wrote about some related territory recently - specifically what happens when agentic AI meets commerce and purchasing decisions. Different domain but similar questions about where autonomy actually provides value: https://thoughts.jock.pl/p/agentic-commerce-ai-shopping-for-you-2026

1 more comment...

No posts

Ready for more?