<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai-Agents on Corey Daley</title><link>https://coreydaley.dev/tags/ai-agents/</link><description>Recent content in Ai-Agents on Corey Daley</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 10 Mar 2026 11:55:00 -0400</lastBuildDate><atom:link href="https://coreydaley.dev/tags/ai-agents/rss.xml" rel="self" type="application/rss+xml"/><item><title>The Rise of the Agent Wrangler</title><link>https://coreydaley.dev/posts/2026/03/the-rise-of-the-agent-wrangler/</link><pubDate>Tue, 10 Mar 2026 11:55:00 -0400</pubDate><guid>https://coreydaley.dev/posts/2026/03/the-rise-of-the-agent-wrangler/</guid><description>&lt;p&gt;People keep asking if AI is going to replace software engineers. Better question: who can still be trusted to ship production software when most implementation is delegated to agents? That role is the Agent Wrangler — and it isn&amp;rsquo;t a step down from engineering, it&amp;rsquo;s a different kind of engineering.&lt;/p&gt;
&lt;p&gt;You spend your day directing Claude Code, Codex, and similar tools through feature work, bug hunts, security audits, and codebase exploration. The job sounds easier than traditional engineering. It isn&amp;rsquo;t — at least not for the people who do it well. Because when you&amp;rsquo;re orchestrating agents, your technical depth is the control surface. CS fundamentals don&amp;rsquo;t disappear; they become the language you use to catch when an agent is wrong.&lt;/p&gt;
&lt;p&gt;Software engineers aren&amp;rsquo;t going away. They need to adapt — like they always have. Maybe the real new title is &amp;lsquo;Adaptability Engineer.&amp;rsquo; Are you ready to stop coding and start wrangling?&lt;/p&gt;
&lt;p&gt;Read more at &lt;a
 href="https://coreydaley.dev/posts/2026/03/the-rise-of-the-agent-wrangler/" target="_blank" rel="noopener noreferrer"&gt;https://coreydaley.dev/posts/2026/03/the-rise-of-the-agent-wrangler/&lt;/a&gt;
&lt;/p&gt;</description></item><item><title>Why I Left Notion and Built My Own AI Agent Plugin for Obsidian</title><link>https://coreydaley.dev/posts/2026/03/obsidian-ai-agent-sidebar-plugin/</link><pubDate>Mon, 09 Mar 2026 11:45:00 -0400</pubDate><guid>https://coreydaley.dev/posts/2026/03/obsidian-ai-agent-sidebar-plugin/</guid><description>&lt;p&gt;I was already paying for Claude, Codex, and several other AI services when Notion started pushing its own AI add-on. The problem wasn&amp;rsquo;t just the price — it was that Notion AI couldn&amp;rsquo;t talk to any of the tools I already had, and my workflow had become a copy-paste treadmill between my notes and my agents. So I switched to Obsidian and hit the same wall: no native way to use your own AI.&lt;/p&gt;
&lt;p&gt;I built the Obsidian AI Agent Sidebar plugin — an open source tool that brings Claude Code, OpenAI Codex, Google Gemini, GitHub Copilot, and any OpenAI-compatible server directly into your Obsidian sidebar, with real vault read/write access. Developed using agentic engineering and the dark factory method, it&amp;rsquo;s the integration I needed and couldn&amp;rsquo;t find.&lt;/p&gt;
&lt;p&gt;What would you build if the tool you needed simply didn&amp;rsquo;t exist yet?&lt;/p&gt;
&lt;p&gt;Read more at &lt;a
 href="https://coreydaley.dev/posts/2026/03/obsidian-ai-agent-sidebar-plugin/" target="_blank" rel="noopener noreferrer"&gt;https://coreydaley.dev/posts/2026/03/obsidian-ai-agent-sidebar-plugin/&lt;/a&gt;
&lt;/p&gt;</description></item><item><title>Attractor: When Chaos Theory Meets AI Pipeline Orchestration</title><link>https://coreydaley.dev/posts/2026/03/attractor-dot-pipeline-orchestration/</link><pubDate>Fri, 06 Mar 2026 12:00:00 -0500</pubDate><guid>https://coreydaley.dev/posts/2026/03/attractor-dot-pipeline-orchestration/</guid><description>&lt;p&gt;Most AI automation breaks for the same reason: the workflow is hidden inside scripts, prompts, and tribal knowledge. Attractor takes a different path — one borrowed from chaos theory. In dynamical systems, an attractor is a state a system naturally converges toward even through turbulence.&lt;/p&gt;
&lt;p&gt;Apply that to AI workflows, and you get directed graphs that pull multi-LLM execution through branching, retries, human review gates, and failure recovery toward a defined goal. The entire codebase is AI-generated, which makes it a working proof-of-concept of the Software Factory philosophy.&lt;/p&gt;
&lt;p&gt;If we can declaratively orchestrate AI agents today, what should we still insist on owning as humans?&lt;/p&gt;
&lt;p&gt;Read more at &lt;a
 href="https://coreydaley.dev/posts/2026/03/attractor-dot-pipeline-orchestration/" target="_blank" rel="noopener noreferrer"&gt;https://coreydaley.dev/posts/2026/03/attractor-dot-pipeline-orchestration/&lt;/a&gt;
&lt;/p&gt;</description></item><item><title>Beyond LeetCode: How AI is Transforming Technical Interviews</title><link>https://coreydaley.dev/posts/2026/02/beyond-leetcode-how-ai-is-transforming-technical-interviews/</link><pubDate>Sun, 15 Feb 2026 17:46:25 -0500</pubDate><guid>https://coreydaley.dev/posts/2026/02/beyond-leetcode-how-ai-is-transforming-technical-interviews/</guid><description>&lt;p&gt;The coding interview landscape is shifting dramatically as AI tools become standard in software development. Rather than memorizing algorithms, candidates may soon demonstrate their ability to work effectively with AI agents—breaking down projects, creating tasks in Jira, and collaborating to solve real-world problems.&lt;/p&gt;
&lt;p&gt;This shift raises important questions about what skills truly matter and how we evaluate engineering talent in an AI-augmented world.&lt;/p&gt;
&lt;p&gt;What does this mean for the future of technical hiring?&lt;/p&gt;
&lt;p&gt;Read more at &lt;a
 href="https://coreydaley.dev/posts/2026/02/beyond-leetcode-how-ai-is-transforming-technical-interviews/" target="_blank" rel="noopener noreferrer"&gt;https://coreydaley.dev/posts/2026/02/beyond-leetcode-how-ai-is-transforming-technical-interviews/&lt;/a&gt;
&lt;/p&gt;</description></item></channel></rss>