Files
crewAI/lib/cli
João MouraandClaude Opus 5.5 9d5fd32661 fix(cli): deploy push reads AMP's source_type, so a ZIP deployment gets the new code (#7980)
#7345 made push follow how AMP holds a deployment's code, read from a
`zip_deployment` boolean on the status. AMP's status never sends that field:
it sends `source_type` ("zip", "studio", "github", "any_git"). So push always
fell back to the local origin remote, and a ZIP deployment whose project has a
git remote was redeployed by uuid — AMP rebuilt the ZIP it already held, not
the code being pushed.

Seen on a real deployment: after raising crewai to 1.15.26, `crewai deploy push`
rebuilt the stored 1.15.23 ZIP ("CrewAI version detected: 1.15.23"), with no
upload. `zip_deployment` is still read first when a server sends it.

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-12 15:45:13 +00:00
..

crewai-cli

CLI for CrewAI — scaffold, run, deploy and manage AI agent crews without installing the full framework.

Installation

pip install crewai-cli

This pulls in crewai-core (shared utilities) but not the crewai framework itself, so commands that don't need a crew loaded — crewai version, crewai login, crewai org list, crewai config *, crewai traces *, crewai create, crewai template * — work standalone.

Commands that load a user's crew or flow (crewai run, crewai train, crewai test, crewai chat, crewai replay, crewai reset-memories, crewai deploy push, crewai tool publish) require crewai to be installed in the project's environment. They print a clear error if it is missing.

To install both at once:

pip install crewai[cli]