Warp Enables Team-Shared Cloud Agent Tasks via CLI

Warp

Warp added the warp agent run-ambient command, enabling teams to create cloud agent tasks from the CLI that are automatically shared with all team members, making cloud-based automation visible and collaborative across the organization. The same release introduced team-scoped API keys, giving teams a way to run cloud agent pipelines under shared credentials rather than individual user accounts.


Shared Cloud Agent Tasks via CLI

Warp's January 7 release introduced a significant expansion of its cloud agent capabilities: the warp agent run-ambient command can now create cloud agent tasks that are automatically shared with team members. When a developer launches an ambient agent run from the command line, the resulting task becomes visible to the entire team — enabling teammates to monitor progress, review outcomes, and hand off or continue agent work without requiring the originating user to share anything manually.

This builds on Warp's ambient agents infrastructure, which allows background agents to run in response to events, schedules, or integrations. By making these runs team-visible by default from the CLI, Warp moves cloud agent automation out of individual silos and into shared team workflows. The command also gained support for saved prompts, so teams can standardize recurring agent tasks and invoke them consistently.

Team-Scoped API Keys

Alongside the CLI expansion, Warp introduced team-scoped API keys — credentials that are tied to the team rather than to any individual user account. These keys are purpose-built for fully automated workflows such as CI/CD pipelines and scheduled agent tasks, where no specific user context is needed. Team-scoped keys draw from the team's shared pool of add-on credits, making usage accounting cleaner for organizations running multiple automated agent pipelines in parallel.

This is a meaningful addition for enterprise and larger team deployments, where tying automation to individual user credentials creates fragility (keys becoming invalid when a user departs or rotates their credentials) and obscures attribution in audit trails.

Additional Changes

The release also added agent tips displayed beneath the warping indicator to help users discover agent capabilities during active sessions. The full terminal use model selector was added to the agents profile page, giving teams finer control over which model handles terminal-heavy agent tasks. A new agent profile switching tip provides clearer explanation of how to move between agent configurations. Several bug fixes shipped alongside these features, including improved out-of-memory handling for cloud agents and a fix for a 'parameter not set' error in Zsh when setopt nounset was enabled.