bus-containers — AI Platform container runner client
bus-containers — AI Platform container runner client
bus containers is the domain client for public AI Platform container-runner
APIs. It owns the client library for container status and user-owned container
run lifecycle operations.
Use it when an approved Bus account has access to non-persistent container workloads. Container runs are owned by the account in the bearer token. They are suitable for isolated jobs and hosted Codex-style workloads where usage is metered and limited by the account plan.
Common tasks
Before running container commands, authenticate with bus auth and request a
token that includes the container scopes enabled for your account:
bus auth token --scope "container:read container:run container:delete billing:read"
The token must be an AI Platform bearer JWT. By default, bus auth token saves
the normal Bus API token to ~/.config/bus/auth/api-token or
${BUS_CONFIG_DIR}/auth/api-token, and bus containers reads that file
automatically. Use --token-file, BUS_AI_TOKEN, or BUS_API_TOKEN only when
automation needs an explicit override. Literal token values are not accepted on
the command line. The service must use the JWT sub account UUID as the owner
and must not trust a client-supplied account ID.
bus containers status
bus containers run --profile codex -- sh -c 'printf OK'
bus containers runs
bus containers delete run_123
status should show the runner state returned by the API, such as a ready or
starting status. run should return a run identifier and final command output
or a structured run result owned by the current account. runs should include
that run until retention or deletion removes it. Replace run_123 with the run
identifier returned by bus containers run; deletion should return success
only for a run owned by the account in the bearer token. Another account’s run
must return an authorization or not-found response.
If billing is required and missing, or if a quota is exhausted, the server returns setup or upgrade guidance before starting the container work.
Options
--help and --version print command help or version information.
--api-url <url> selects the deployment API origin, not the
/api/v1/containers path itself; the CLI appends container endpoint paths. By
default the CLI uses the configured Bus AI/API base URL, typically
BUS_AI_API_URL or BUS_API_BASE_URL, and otherwise the deployment default.
Override it for local compose with
--api-url "http://127.0.0.1:${LOCAL_AI_PLATFORM_PORT:-8080}".
--token-file <path> reads the bearer token from a file. `–timeout