/ai

Building in public. Shipping tools developers actually use.

The era of the vibe coder is here. I've been one since MySpace — 30 years of building on and off. Only a couple public-facing projects in this era. The play from here: ship and prove.

Curtis AI Chat v1.0.0 — and why it's called Curtis

v1.0.0 ships today. Eight features, 30+ providers, the agent layer for Obsidian. Also: why the plugin is named after the person whose existence made mine possible, and what that has to do with building code that outlasts me.

Twenty-one hours, thirty-nine PDFs, zero GPU

Extracting text from ~39 image-only Grok chat-export PDFs into Obsidian-vault markdown via a local CPU-only vision model. Three Windows-specific bugs worth writing down.

The reframe that landed before 'agent OS' was a category: OS, not tool

Eleven months ago I wrote down a one-line reframe that predicted where the agent stack was going: integration is the moat, models are commodity, the unit is the operating system, not the tool. The industry caught up. Here's what held up and what didn't.

Polyglot AI chat for Obsidian. 30+ providers, agent mode with vault tools, multi-model arena, voice I/O, inline diff rewrite. The v1 successor to Curtis Chat.

Verifiable multi-agent consensus for Claude. The coordination layer frameworks punted on — Nostr-native event signing, post-quantum (ML-DSA) signatures, MCP server.

The earlier name for what's now Curtis AI Chat. Started as ObsidiBuddi, became Curtis Chat at v3, evolved into Curtis AI Chat at v1 (new plugin ID, fresh major version). This page is the evolution story.