deploy deploys the runtime described by the current project’s lifecycle config. It does not build an image first; use launch when you want build and deploy in one command. Use release for the .agentkit/agentkit.yaml cloud release pipeline, IM channels, or frontend release flow.
deploy
Read agentkit.yaml, select the local, cloud, or hybrid strategy from common.launch_type, and write deployment state such as runtime id, endpoint, or local container state back to the config file.
deploy runs service preflight checks before deployment. In an interactive terminal it prompts when required services are not enabled; use launch --preflight-mode when an automated build-and-deploy flow must control preflight behavior explicitly.
Harness Deploy
With --harness <name>, the CLI reads <name>.harness.json from the current directory, converts it into runtime environment variables, creates a temporary lifecycle config, and deploys a Harness runtime. If you pass --discovery-url, also pass at least one allowed client id through --allowed-id.
Harness deploy creates or updates a cloud runtime and may rewrite harness.json in the current directory with endpoint, runtime id, and auth information. Confirm the working directory, Harness name, and target project before running it.
