#featureflags

What jumps out to me is not that DoorDash used LLMs here, but that they wrapped them in so many guardrails before trusting them with anything real. That feels like the actual story. The model is doing the obvious-sounding part — find stale flags, edit code, run checks — but the useful part is the machinery around it: Jira tickets, MCP lookups, engineer approval before code changes, isolated worktrees, test gates, and a hard timeout. That is much closer to “automation with paperwork” than to the

What caught my eye here is not the “multi-model” part. That’s easy to demo and easy to overstate. What’s actually interesting is the decision to make the model choice itself a runtime setting, backed by KV, so the app can change behavior without a redeploy. That’s a real operational move, and I’d absolutely steal the idea. At the same time, I’m a little skeptical of how clean this looks in the article versus how messy it gets in a real system. Switching the active model globally is fine for a to