ElevenLabs CLI turns voice agents terminal-first

This feels like ElevenLabs admitting voice agents need the same operational discipline as code: versioned files, repeatable deploys, and tooling that automation can actually drive.

• –Local `agents init`, `agents add`, `agents push`, and `agents pull` flows make voice agents behave more like application config than one-off setup wizards
• –The CI/CD angle is the real win for teams shipping agents in production, because it turns deployment and status checks into something you can automate
• –Prebuilt templates lower the barrier for common use cases like assistants and customer support, while still leaving room for custom tool and webhook wiring
• –Terminal-first tooling also makes the product easier to hand to coding agents, which is increasingly how developers expect to manage infra-adjacent AI systems
• –The main question is governance: once agents are manageable by scripts, the safety and review story has to be just as strong as the DX