Skip to content

App Builder CLI Reference

Manage Komodo Apps — list, inspect, update, and delete containerized applications running on the Komodo platform.

Terminal window
uv run komodo app --help

List all apps in your account with their names, IDs, and status.

Terminal window
uv run komodo app list
FlagDescription
-E, --environmentTarget environment

Get detailed information about a specific app, including its devfile, status, URL, and timestamps.

Terminal window
uv run komodo app get <APP_ID>

Check the deployment status of an app.

Terminal window
uv run komodo app get-status <APP_ID>

Status values: IN_PROGRESS, RUNNING, SUSPENDED, SUSPENDING, FAILED.

Update an existing app’s devfile configuration.

Terminal window
uv run komodo app update <APP_ID> --devfile <PATH>

Permanently delete an app. Also delete the .app file from your project directory afterward to avoid 404 errors on future builds.

Terminal window
uv run komodo app delete <APP_ID>

List log entries for an app. Returns log metadata and presigned S3 URLs.

Terminal window
uv run komodo app list-logs <APP_ID>

List only the most recent log entries for an app.

Terminal window
uv run komodo app list-latest-logs <APP_ID>

Retrieve a specific log entry by log ID.

Terminal window
uv run komodo app get-log <APP_ID> <LOG_ID>

Fetch and display the content of a specific log entry.

Terminal window
uv run komodo app display-log <APP_ID> <LOG_ID>

Fetch and display the most recent log content for an app. Useful for quick debugging of deployment failures or runtime errors.

Terminal window
uv run komodo app display-latest-logs <APP_ID>

Manage who has access to an app by viewing and modifying Platform RBAC custom resource roles (owner, editor, viewer). All subcommands support interactive selection when arguments or flags are omitted.

Terminal window
uv run komodo app sharing --help

Show all users with access to an app and their roles.

Terminal window
uv run komodo app sharing list [APP_ID]

Omit APP_ID to interactively pick from your apps.

Show which roles you can grant on an app (depends on your own role).

Terminal window
uv run komodo app sharing roles [APP_ID]

Grant a role on an app to another user. Supports a fully interactive flow when flags are omitted: pick an app, choose a role, then select a user from account members or enter their ID/email directly.

Terminal window
uv run komodo app sharing grant [--app-id APP_ID] [--role ROLE] [--user USER_ID_OR_EMAIL]
FlagDescription
-a, --app-idApp UUID (omit to pick interactively)
-r, --roleRole to grant: owner, editor, or viewer (omit to pick)
-u, --userTarget user ID (UUID) or email (omit to pick from account members)
-E, --environmentTarget environment

Revoke a role on an app from a user. When flags are omitted, shows who currently has access and lets you pick.

Terminal window
uv run komodo app sharing revoke [--app-id APP_ID] [--role ROLE] [--user USER_ID_OR_EMAIL]
FlagDescription
-a, --app-idApp UUID (omit to pick interactively)
-r, --roleRole to revoke (omit to auto-resolve from current assignment)
-u, --userTarget user ID or email (omit to pick from users with access)
-E, --environmentTarget environment

Build and deploy services. Default (no subcommand): uses the remote Build API — discovers services with Dockerfiles, uploads build context, streams logs, then creates or updates the app. Komodo OAuth only; no user AWS credentials needed.

Use komodo build --local when you need a local BuildKit build: buildctl exports a docker image tarball, which is uploaded via the Build API prebuilt path (Trivy, ECR, and signing run on the platform). Requires BuildKit and buildctl. Komodo OAuth only — no AWS_ROLE_ARN or AWS CLI for ECR.

BUILDKIT_HOST: Default docker-container://buildkitd. Set to e.g. tcp://127.0.0.1:1234 when using a TCP BuildKit container. Same variable applies to MCP build_app (build_mode: local), but must be configured on the MCP server process for IDE use — see App Builder — BUILDKIT_HOST.

Terminal window
uv run komodo build --help

Top-level options (when no subcommand):

FlagDescription
--local, -LLocal BuildKit image tar + Build API prebuilt upload (OAuth only; no client ECR push)
--dockerfile, -fDockerfile path relative to context for remote builds (default: Dockerfile)
--cpuBuild API worker CPU limit for remote builds and for local prebuilt uploads (default: 2000m)
--memoryBuild API worker memory limit for remote builds and for local prebuilt uploads (default: 2Gi)
--verbose, -VVerbose output
--architecture, -ATarget arch for local builds: amd64 or arm64
-E, --environmentTarget environment

Check status of a remote image build by build ID (not app UUID).

Terminal window
uv run komodo build status <BUILD_ID>
FlagDescription
--pollPoll every 5 seconds until the build reaches a terminal state
-E, --environmentTarget environment

Cancel a queued or in-progress remote image build.

Terminal window
uv run komodo build cancel <BUILD_ID>

List all services with Dockerfiles or devfile files found in the current directory and subdirectories.

Terminal window
uv run komodo build list

Check if the BuildKit daemon is accessible (relevant for local builds).

Terminal window
uv run komodo build check

Account infrastructure and networking helpers — mesh, domains, and AWS account info.

Terminal window
uv run komodo infra --help

Create a mesh networking request to connect an AWS resource in your subaccount to your deployed apps. See the App Builder — Mesh Networking guide for details.

Terminal window
uv run komodo infra mesh <RESOURCE_ARN>
ArgumentDescription
RESOURCE_ARNARN of the AWS resource to mesh (e.g., an RDS database ARN)
FlagDescription
-E, --environmentTarget environment

Check the status of a mesh request.

Terminal window
uv run komodo infra mesh-status <MESH_REQUEST_ID>
FlagDescription
--pollPoll every 10 seconds until mesh completes or fails
-E, --environmentTarget environment

Status values: IN_PROGRESS, COMPLETED, FAILED.

List assigned domains for the account.

Terminal window
uv run komodo infra get-assigned-domains

Print AWS account information for the environment.

Terminal window
uv run komodo infra get-aws-account-info

Manage secrets across three scopes: user (personal), app (application-specific), and shared (team-wide). Each scope supports the same set of subcommands.

Terminal window
uv run komodo secrets --help
ScopeCommand prefixDescription
Userkomodo secrets userPersonal secrets scoped to the authenticated user
Appkomodo secrets appSecrets scoped to a specific application
Sharedkomodo secrets sharedSecrets shared across the account

Each scope (user, app, shared) provides the following subcommands:

Create a new secret.

Terminal window
uv run komodo secrets user create <NAME> --data '<JSON>'
FlagDescription
--dataJSON object with secret key-value pairs
--data-filePath to a JSON file (or - for stdin); mutually exclusive with --data

Retrieve a secret by name.

Terminal window
uv run komodo secrets user get <NAME>
FlagDescription
--revealShow secret values instead of masking them

List all secrets in the scope.

Terminal window
uv run komodo secrets user list

Update an existing secret.

Terminal window
uv run komodo secrets user update <NAME> --data '<JSON>'
FlagDescription
--dataJSON object with updated key-value pairs
--data-filePath to a JSON file (or - for stdin)
--mergeMerge with existing data instead of replacing

Delete a secret.

Terminal window
uv run komodo secrets user delete <NAME>

Move a secret to a different scope.

Terminal window
uv run komodo secrets user move <NAME> --to <SCOPE>
FlagDescription
--toDestination scope: user, app, or shared

App-scoped secrets require an --app-id flag:

Terminal window
uv run komodo secrets app create <NAME> --app-id <APP_ID> --data '<JSON>'
Terminal window
uv run komodo secrets app get <NAME> --app-id <APP_ID>
Terminal window
uv run komodo secrets app list --app-id <APP_ID>