GitHub recently announced that Copilot CLI now supports bring-your-own-key (BYOK) and locally running models. Developers can route CLI requests through their own model provider or run a local model entirely offline. But model selection is a starting point, not a destination. The harder problem is what happens when AI starts taking actions across your software delivery pipeline. Triggering builds. Interacting with your CI/CD configuration. That's where the architectural choices underneath a CLI tool start to matter. Two different definitions of "terminal AI" GitHub's announcement extends what Copilot can do at the developer's individual workstation. There is no organization-level control that enforces which model a team uses or produces an auditable record of what the agent did and why. For teams running AI in automated workflows, it's a meaningful gap. GitLab Duo CLI starts from a different premise.…