Skip to main content
config manages the lifecycle project’s agentkit.yaml, and with --global it manages user-wide defaults in ~/.agentkit/config.yaml. Project config is used by build, deploy, launch, status, and destroy; global config provides default cloud provider, region, credentials, and infrastructure settings.

config

Without --global, the command reads or updates the current project’s lifecycle config. When no specific field is passed and the terminal is interactive, the CLI opens a configuration wizard; in non-interactive environments, pass flags explicitly. When used with --init, the CLI creates the default lifecycle config first and then applies the project-level fields from the same command. Launch-mode-specific fields are written under the mode selected by --launch_type, or under cloud when --launch_type is omitted. Export MODEL_AGENT_API_KEY in the current terminal before running this example. Double quotes let the shell expand the variable; lifecycle config does not automatically resolve a literal ${MODEL_AGENT_API_KEY} passed in single quotes
The configuration command writes the expanded model API key to agentkit.yaml. Add that file and .env to .gitignore and .dockerignore before running it to keep credentials out of version control and the image

config —global

With --global, the command reads or updates ~/.agentkit/config.yaml. Project-level fields such as --cloud_provider cannot be combined with --global; switch the default provider through the global --provider flag or --set defaults.cloud_provider=<provider>.
Commands resolve environment variables first, then project config and user-wide config. Every product command also accepts global --provider volcengine|byteplus to override the cloud provider for that command. Region values must be lowercase, hyphen-separated region codes such as cn-beijing or ap-southeast-1; values containing paths, query strings, uppercase letters, or non-region hostnames are rejected.

Configure an exclusive gateway

Select an existing exclusive gateway before creating the runtime, and remove independent runtime network configuration from that strategy. Bindings cannot change after creation; see exclusive runtime gateways
Last modified on September 19, 2026