The runtime command group manages AgentKit runtimes, covering listing, inspection, log retrieval, version history, releasing, updating, and deletion.
Sign in with runtime-management permissions first. Runtimes are scoped by provider and region. Replace example names with results from runtime list; save and use runtime IDs in automation. For BytePlus:
On read commands, --json selects JSON output. On runtime update, it takes a JSON request body. These uses are not interchangeable
runtime list
List all runtimes.
runtime show
Show details of a runtime, optionally a specific version.
When --json is used for the current runtime and the runtime is bound to a Tool, the output includes toolId.
Deleting a runtime stops its service, making it unavailable to existing callers. Check callers, associated resources, the ID, and region first. --yes skips confirmation
runtime delete
Delete a runtime.
runtime logs
Show logs for a runtime instance.
runtime attach
Open an interactive terminal inside a running instance of the runtime, the same shell the console’s instance terminal provides. Press Ctrl-] to detach, which leaves the instance running. When the runtime has scaled to zero and has no instance, one is started automatically before attaching; a runtime using custom_jwt authentication cannot be auto-started without a token, so run agentkit invoke run once first.
runtime versions
List a runtime’s version history.
runtime release and runtime update --auto-release change the live version; resource changes can also affect charges. --no-wait means the request was submitted, not that the new version is ready
runtime release
Release (publish) a runtime version, making it live.
runtime update
Update a runtime’s configuration. This does not release the new version unless --auto-release is passed.
Gateway details and update restrictions
runtime list displays gateway information, and runtime show includes gateway mode, instance ID, and name. Filter runtimes by their gateway
Gateway mode, instance, and network configuration are creation-time settings. runtime update --json rejects changes to these fields. Create a runtime under a new name and migrate callers when a different gateway is required
Check publication results
Use runtime versions to confirm the revision, then runtime show to inspect current state. For an instance that is not ready, inspect startup failures with runtime logs. Logs may contain user requests and business data; handle them according to project requirements
Commands in runtime attach act on the live instance. Changes are not written back to the local project or image. Rebuild and publish project changes when they must persist 
