Driftwatch V3 Released: AI-Assisted Codebase Monitoring Tool

Driftwatch V3 Build Complete

Driftwatch V3 has been completed and pushed to a public repository at bubbuilds.com. The build took 5-6 days instead of the anticipated 1-2 days, involving approximately 9,000 lines of code and costing around $160 in API credits plus a Claude Pro account.

What's New in V3

• Tracks which markdown files are oversized and at risk of silent truncation
• Flags contradicting instructions across files
• Cost tracking with recommendations on which files need attention
• Built-in markdown editor for fixing issues directly in the browser
• Snapshot export/import to track drift between scans
• Removed some features that weren't pulling their weight
• Still all in-browser with nothing stored on a server

Key Lessons from the Build

Costs & Delegation: Opus consistently thinking doing tasks itself is faster and cheaper than delegating was the single biggest cost driver. Batching all QA until after the full build and giving fixes in one shot proved cheaper than stopping after each sprint.

Specs & Prompts: A structured spec sheet before every sprint was the biggest cost saver. The developer built a "Prompt Clarifier" Claude Project that turns messy prompts into detailed markdown specs for Bub. Having Bub read the full spec and ask questions before building saved wasted tokens compared to just sending instructions.

Context Compaction: Compaction and context bloat are the biggest blockers for trusting Bub with more autonomy. Sprint recaps built into the spec template helped restore context, and important instructions are now placed in local markdown files Bub can reference instead of pasted into chat.

QA & Testing: Batching QA until after all sprints then giving everything back in one shot was more efficient for time and cost than review/fixes after each milestone.

Website Design: Mobile-first design needs to be included in specs from the start - retrofitting created lots of back and forth where small changes created new issues.

Workflow: The developer needs better organization for Claude chats and plans to study test driven development. Exporting Telegram chat history and running it through Opus helps identify where conversations break down with Bub, and Claude's research mode works well for fact checking tech specs.

What's Next

The developer plans to use Driftwatch on Bub to audit his architecture and give him a full makeover to fix delegation and other issues from this build. Next steps include building a second brain for the developer, Bub, and Claude to share that organizes unsearchable Claude Pro chats, and testing architecture upgrades while building Driftwatch Pro features.