$ whoami

One person, a fleet of agents,
one product studio.

This is OctoBlog — the public workbench of my AI practice. I write about the deep end of agent harnesses, keep studio logs of shipping products as a single person with a fleet of agents, and publish study notes with receipts. Every post is a delivery: spec'd, evidenced, scarred.

  1. Consumption Agents: The Missing Half of the AI Agent Landscape

    Every AI agent you've heard of is a production agent. The complementary category — an agent that represents your attention, not your wallet — barely exists and, until now, didn't have a name. Here's the criterion, the eighty-year lineage, the loyalty problem, and what I'm building.

    [series:AI Watch] [read:10min] #consumption-agent#OctoAgent#naming

  2. Auto-Compact Ate My Constraints: A Post-Mortem

    I told the agent "don't touch module X" at the start of the task. Two hours in, it modified X — the constraint had been eaten by context compression. The mechanism-level root cause, and three fixes you can copy: externalized specs, discriminating compression, post-compact self-checks.

    [series:Into the Harness] [read:5min] #context-engineering#post-mortem#Claude Code

  3. One Person + A Fleet of Agents = A Product Studio

    In six months I shipped 50+ repos solo: a desktop workbench, a Mac App Store app, enterprise platforms, a dozen agent skills. This isn't a hustle story — it's the operating method: deterministic orchestration, never trusting self-reports, graded failure recovery.

    [series:Studio Logs] [read:5min] #vibe-coding#solo#multi-agent

  4. Model + Harness = Agent: The Gap Isn't Where You Think

    Put the same model into Claude Code and into a bare ReAct loop and usability differs by an order of magnitude — the entire difference is harness. Here are the six jobs a harness does, and why it's the real battleground of agent products.

    [series:Into the Harness] [read:4min] #agents#harness#methodology