All commands and flags available with the ADK CLI.
The adk CLI is how you scaffold, run, deploy, and debug ADK agents. Run adk --help for the top-level command list, or adk <command> --help for the flags on a specific command.
Credentials profile to use (overrides the ADK_PROFILE environment variable and the current profile)
Most commands also accept --format json (or --format text) for machine-readable output. A few interactive commands don’t: dev, login, profiles, self-upgrade, telemetry, theme, run, and assets pull.
Project
Command
Description
adk init [name]
Scaffold a new project
adk dev
Start development mode with hot reloading
adk build
Build the agent for production
adk check
Validate project structure, config, and primitives
adk status
Show project status, integrations, and server state
adk link
Link the project to a workspace and bot
adk deploy
Deploy the agent to production
adk project upgrade
Apply ADK compatibility updates to a 1.x project
adk init
adk init my-agent
Flag
Description
-t, --template <name>
Template to use (default: blank)
-y, --yes, --defaults
Skip prompts and use sensible defaults
--skip-link
Skip the interactive linking step
--list-templates
List available templates and exit
adk dev
Runs your agent locally against your development bot and starts the Dev Console.
adk dev
Flag
Description
-p, --port <port>
Development server port (default: 3000)
--port-console <port>
Dev Console port (default: 3001)
--otlp
Export traces to an OTLP collector (default port 4318)
--port-otlp <port>
OTLP collector port (Jaeger, otel-tui, etc.)
--no-watch
Disable file watching and hot reload
--non-interactive
Emit structured NDJSON events instead of the status panel
Deploy even if enabled dependencies are unconfigured (ships them inert)
adk link
Points the project at a production bot and writes agent.json. See Project setup.
adk link --workspace <id> --bot <id>
Flag
Description
--workspace <id>
Workspace ID
--bot <id>
Production bot ID
--dev <devBotId>
Also record a development bot ID
--api-url <url>
Botpress API URL
--local
Write the whole link to agent.local.json instead
-f, --force
Overwrite an existing agent.json
Dependencies
Integrations, plugins, and interfaces are Cloud-first: these commands read and write your bot’s Cloud state. They default to your development bot; pass --target prod to act on production. See Managing dependencies.
adk integrations
Command
Description
adk integrations add <name>
Add an integration (e.g. slack or slack@1.4.2)
adk integrations remove <alias>
Remove an integration
adk integrations upgrade <alias>
Upgrade an integration (--to <version>)
adk integrations enable <alias>
Enable an integration
adk integrations disable <alias>
Disable an integration
adk integrations configure <alias>
Set config values (--set k=v, --unset k)
adk integrations list
List installed integrations (--verbose for config)
adk integrations status
Show each integration’s capability state + remediation
adk integrations info <name>
Show registry details for an integration
adk integrations search [query]
Search the registry (--interface <name> to filter)
adk integrations copy
Copy state between envs (--from, --to)
adk integrations diff
Show dependency state differences
Common flags: --target dev|prod, --alias <alias>, and --config key=value (repeatable) on add.