March 14, 2026

Build Log 02: Deploy Day.

Feb 22 — production deploy, CI/CD agent tools, and a VS Code extension.

Three days after the first day. The core loop was working locally. Time to make it real.

Production and Auth

Deployed to production with GitHub and Google OAuth. Not glamorous, but necessary — you can't test a collaboration tool alone on localhost. Real users need real auth and a real URL.

The Agent Touches the Pipeline

This is where it got interesting. Added 7 CI/CD agent tools: dispatch workflows, read build logs, check run status, create releases, rollback deployments — all from chat. The agent isn't just answering questions anymore. It can take actions on your deployment pipeline.

That's a meaningful line to cross. A chatbot gives you information. An agent that can trigger a rollback gives you leverage.

VS Code Extension

Built the VS Code extension with a task list, chat UI, and per-message model selector. Developers shouldn't have to leave their editor to collaborate. The extension is a first-class surface, not an afterthought.

The model selector was a small detail that mattered — letting the user pick the right model per message means they're not locked into one provider's strengths and weaknesses for every question.

Three Days In

Auth, deployment, CI/CD tools, and an editor extension. The product went from "runs on my machine" to "deployed, authenticated, and capable of touching infrastructure."

The agent isn't a chatbot anymore. It's a teammate with access to the deploy button.