Codex on Corey Daley

From Config Hub to Competing Voices: How agent-config Became My AI Collaboration Stack

Sat, 11 Apr 2026 14:50:00 -0400

I started agent-config as a shared configuration hub: one repository to rule Claude, Codex, Copilot, and Gemini. That lasted about two iterations before the cracks showed. Forcing every AI agent to share the same configuration format was the wrong abstraction — different tools, different philosophies, different file formats. The solution wasn’t more uniformity. It was a different model of collaboration entirely.

Today agent-config is Claude-specific, but Codex is still central to how I work. The difference: Codex is no longer a configuration target. It’s a competitive collaborator. Sprint plans, blog posts, security audits — every significant output runs through a workflow where Claude and Codex produce independent drafts, critique each other’s work, and force synthesis from the tension. Two AI voices with different instincts produce better output than either would alone — just like a team of people with different backgrounds does.

Is your multi-agent workflow built for sharing configuration, or for generating the productive disagreement that makes output actually better?

Free Doesn't Mean Open: How AI Is Unbundling the Open Source Bargain

Thu, 19 Mar 2026 14:15:00 -0400

Open source was never really about the license. It was about economics — no single developer could build everything alone, so you shared the source and let the community help carry the load. AI is making that trade less necessary.

With Claude Code and Codex, a solo developer can now ship and maintain classes of software that once required a contributor community. A new model is taking shape: users file issues, maintainers decide what’s worth building, AI does the implementation. No PRs to review, no design debates in GitHub comments. Meanwhile, tools like Obsidian prove free software doesn’t require open source — and have for years. The question is no longer whether to open source, but which parts of the open source bargain still matter to you.

But here’s the counterintuitive part: AI also makes some open source values more important, not less. When software can be shipped and abandoned faster than ever, forkability, auditability, and portability become user protections that matter more. The future isn’t open vs. closed — it’s deliberate vs. reflexive.

The Blog That Builds Itself: AI Automation Behind the Scenes

Tue, 10 Mar 2026 15:40:00 -0400

What happens when you stop treating AI as a writing assistant and start treating it as a co-publisher? This blog has accumulated a full automation stack: a /create-blog-post command that pits Claude and Codex against each other in a competitive draft workflow, a Python script that generates hero images using DALL-E 3 and Claude vision, pre-commit hooks that block commits with unoptimized images, and a Bash script that handles WebP conversion and thumbnail generation automatically.

The design principle behind all of it: treat each stage as a contract, not a prompt. The meta-detail: this post was written by the same pipeline it describes.

What would your content workflow look like if you designed it the same way you’d design a software system — and which parts would you never automate at all?

The Rise of the Agent Wrangler

Tue, 10 Mar 2026 11:55:00 -0400

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’t a step down from engineering, it’s a different kind of engineering.

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’t — at least not for the people who do it well. Because when you’re orchestrating agents, your technical depth is the control surface. CS fundamentals don’t disappear; they become the language you use to catch when an agent is wrong.

Software engineers aren’t going away. They need to adapt — like they always have. Maybe the real new title is ‘Adaptability Engineer.’ Are you ready to stop coding and start wrangling?

Why I Left Notion and Built My Own AI Agent Plugin for Obsidian

Mon, 09 Mar 2026 11:45:00 -0400

I was already paying for Claude, Codex, and several other AI services when Notion started pushing its own AI add-on. The problem wasn’t just the price — it was that Notion AI couldn’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.

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’s the integration I needed and couldn’t find.

What would you build if the tool you needed simply didn’t exist yet?

Centralizing AI Agent Configurations with the agent-config Repository

Thu, 19 Feb 2026 20:26:46 -0500

If you’re juggling Claude Code, Codex, and GitHub Copilot, you know the pain of keeping each one’s configuration files in sync. My agent-config repo solves that with a single source of truth: agent instructions, reusable skills, custom commands, subagents, and prompts all live in one place, and a single make symlinks command wires them up across every tool.

Each directory is purpose-built—skills for reusable capabilities, commands for CLI tools, subagents for delegation, prompts for task-specific guidance. The setup even backs up any files it would overwrite, so you never lose existing config.

Whether you’re just starting to extend your AI tools or already deep into custom workflows, having everything version-controlled and centralized is a game changer. Are you managing your AI agent configurations in a single repository, or do you keep them scattered across tools?