Skip to content
All writing
A reading path

AI coding agents.

4 posts · Read or watch

Start with the working set: what an agent can see and how it finds the right files. Then follow the tools and permissions that decide what it can actually do. These walkthroughs connect the moving parts to day-to-day engineering work.

Start here, then go deeper

  1. 3 min read

    How Codex Actually Finds the Right Files

    AGENTS.md, skills, MCP, search, and compaction — the layers Codex uses to narrow a big repo down to a working set.

    YouTube
  2. 8 min read

    How MCP Actually Works: The Capability Bus Behind Codex, Claude Code, and Gemini CLI

    MCP, demystified. Why it's a capability bus, not a plugin store, and what that changes about how agents reach external tools.

    YouTube
  3. 2 min read

    How Repo Rules, MCP, and Approvals Control AI Coding Agents

    The three control surfaces that decide what an agent can read, run, and change inside your repo.

    YouTube
  4. 8 min read

    Why AI Coding Agents Ship Unreviewed Work

    A review approves artifact A, a retry drops artifact B at the same path, and the saved approval still passes because it was never bound to the bytes. A read-only verifier recomputes the digest at the action boundary and refuses the replacement.

    YouTube

Pick a thread

Michael JamiesonOpen to opportunities

Software engineer building data pipelines, developer tooling, and cross-platform apps.