March 24, 2026

Build Log 06: The Git Worker.

Mar 1 — the agent got dramatically faster and smarter in one day.

Some days you ship a feature. Some days you change how the whole system thinks. March 1st was the second kind.

The Git Worker

Built a dedicated Hono-based git service running on Fly.io. It keeps warm repo clones and extracts context using ripgrep instead of feeding entire files to the model. The effect was immediate — token usage dropped from 50-100k per task down to 10-25k. Same quality answers, fraction of the cost, noticeably faster responses.

Before this, the agent was reading whole files to understand codebases. Now it searches surgically, pulls exactly what it needs, and works with precise context instead of bloated input windows.

Everything Else That Day

Automatic expertise routing — when someone types @Agent, the system figures out which specialist should handle it based on the message content. No more asking users to pick between engineer, designer, or product roles.

Smart plan mode that auto-detects whether a request needs a plan or just a direct action. Hybrid action buttons on every agent response — approve, edit, reject, right there in the message. Image lightbox for viewing screenshots and designs. A "View Changes" button that renders diffs directly in the canvas pane.

Why One Day Mattered

The git worker wasn't just an optimization. It changed what the agent could do. Lower token costs meant the agent could handle more requests per conversation. Faster responses meant users stayed in flow instead of waiting. Precise context meant fewer hallucinations and better code suggestions.

The agent was always capable. The git worker made it practical.