compute:budgets

List budget grants visible for a node context.

Reference for flywheel compute:budgets.

Command Group

Compute & Executions Commands

Summary

List budget grants visible for a node context.

Effect

read-only

Usage

flywheel compute:budgets <FLAGS>

Required flags

FlagValueDefaultChoicesDescription
--node_idstringNode UUID (not a slug) from node_id in hosted:node:list or graph:get. Missing or hidden: 404 where the command loads it.

Optional flags

FlagValueDefaultChoicesDescription
--budget_sourcestringFilter by source: user | root.
--statusstringFilter by status.
--formatFORMATjson, tsv, csv, tableOutput format for command results.
--envPROFILESelect a CLI profile; unconfigured default requires FLYWHEEL_BASE_URL.
--outPATHWrite output to a file path, or use - for stdout.
--openOpen browser-bound URLs when supported.
--no-retryDisable transient-error retries.
--retry-maxNMaximum transient-error retry attempts.
--waitBlock on async operations until a terminal state is reached.
--wait-timeoutSECONDS600Seconds to wait for --wait before timing out. Defaults to 600.
--allow-selfAllow mutating the currently active credential.
--timeoutSECONDSSet the per-request timeout budget in seconds.
--idempotency-keyKEYReuse an Idempotency-Key so ambiguous write failures can be retried with the same key.
--forceForce safety-gated operations where supported.
--yesConfirm forced compute:release-all --force. Other runtime commands do not read --yes.
--debugPrint structured request debugging with secrets masked.
--verbosePrint verbose progress for long-running operations.
-h, --helpShow this help.

Examples

List budgets.

flywheel compute:budgets --node_id n_abc

compute:acquire

Rent a machine now at the outside provider that owns the offer (Lambda, Modal, Vast.ai, Prime Intellect, Nebius or RunPod). This starts paid usage: it is billed by the second at the offer's hourly price plus any provider margin the server adds, to your Flywheel credits (to the campaign's sponsor for a `root` grant), until the lease is released or its grant is used up. It needs an active `compute_grant_id` bound to the approval session (compute-grants:request-approval first). Returns `compute` with `request_state` (`accepted` or `completed`), `lease_id`, `lease_control_token`, `lease_status`, provider, `offer_id`, region, hourly price, grant balances and `auto_shutdown_at`; it carries no SSH key, so poll compute:status until the lease is usable, then call compute:connection. A call with the same --lease_control_token and grant as a pending or active lease reuses that lease instead of provisioning another, as long as its provider, offer and any --region you give match the lease; if they differ the call fails and says what to change or release. --cmd_id is only a label, not a duplicate guard. Release with compute:release when done: the machine and its storage are destroyed. With --wait, wait for usable SSH connection material.

compute:connection

Read SSH connection material for an active managed compute lease once compute:status indicates the lease is usable. Returns `compute` with `lease_id`, `lease_status`, `provider`, `offer_id`, `region`, `host`, `port`, `user`, `private_key` (the SSH private key: keep it secret), `known_hosts` and `next_retry_after_seconds`; host, port and key are empty until the lease is ready. Scoped to --lease_control_token, and only leases you own are connectable. Pass --lease_id or --node_id to pick one when several match.