How to use Juju.wait from the command line

See first: How to use a custom wait condition

Jubilant provides an entrypoint to run Juju.wait from the CLI. It replaces juju wait-for, which is not available in Juju 4.

See more: juju wait-for removed

Install and run the CLI

Install the CLI with uv:

uv tool install jubilant

See more: uv | Tools

General usage:

jubilant wait
    [--error <ERROR>]
    <READY>

The READY and ERROR CLI arguments are passed as Python expressions, different from how Juju.wait is used in code. Those expressions have access to three variables: jubilant (the jubilant module), juju (the jubilant.Juju instance), and status (the jubilant.Status object).

For example, this CLI invocation:

jubilant wait 'jubilant.all_active(status, "myapp")' \
    --error 'jubilant.any_error(status)'

is equivalent to the following Python call:

juju.wait(
    lambda status: jubilant.all_active(status, 'myapp'),
    error=lambda status: jubilant.any_error(status),
)

In code, error is a callable accepting status so you can write error=jubilant.any_error.

Tip

You can also use the CLI without installing it:

uvx jubilant wait --help

To upgrade the CLI:

uv tool upgrade jubilant

Configure logging modes

See first: Configure Jubilant logs

By default, jubilant wait follows brief logging mode:

user@host:~$

jubilant wait 'jubilant.all_active(status)'

2026-09-08 01:31:43,040 [snappass-test] status: active (snappass started)
2026-09-08 01:31:43,040 [snappass-test/0] status: active (snappass started)
2026-09-08 01:31:45,454 Ready condition succeeded 3 times (jubilant.all_active(status))

Use --quiet to suppress all output except errors:

user@host:~$

jubilant wait 'jubilant.all_active(status)' --timeout 2.0 --quiet

2026-09-08 01:33:47,550 Wait timed out after 2.0 seconds

Or --verbose to enable verbose logging mode:

user@host:~$

jubilant wait 'jubilant.all_active(status)' --verbose

2026-09-08 01:34:25,406 INFO jubilant.wait [snappass-test] status: active (snappass started)
2026-09-08 01:34:25,406 INFO jubilant.wait [snappass-test/0] status: active (snappass started)
2026-09-08 01:34:25,406 DEBUG jubilant.wait wait: status changed:
+ .model.name = 'mymodel'
+ .model.controller = 'concierge-k8s'
+ .model.cloud = 'k8s'
+ .model.model_status.current = 'available'
+ .apps['snappass-test'].charm = 'snappass-test'
+ .apps['snappass-test'].charm_origin = 'charmhub'
+ .apps['snappass-test'].charm_name = 'snappass-test'
+ .apps['snappass-test'].charm_rev = 9
+ .apps['snappass-test'].exposed = False
+ .apps['snappass-test'].base.name = 'ubuntu'
+ .apps['snappass-test'].base.channel = '20.04'
+ .apps['snappass-test'].charm_channel = 'latest/stable'
+ .apps['snappass-test'].scale = 1
+ .apps['snappass-test'].provider_id = '15a4d580-0623-4d27-ae40-c99527ce5417'
+ .apps['snappass-test'].address = '10.152.183.162'
+ .apps['snappass-test'].app_status.current = 'active'
+ .apps['snappass-test'].app_status.message = 'snappass started'
+ .apps['snappass-test'].units['snappass-test/0'].workload_status.current = 'active'
+ .apps['snappass-test'].units['snappass-test/0'].workload_status.message = 'snappass started'
+ .apps['snappass-test'].units['snappass-test/0'].juju_status.current = 'idle'
+ .apps['snappass-test'].units['snappass-test/0'].juju_status.version = '3.6.28'
+ .apps['snappass-test'].units['snappass-test/0'].leader = True
+ .apps['snappass-test'].units['snappass-test/0'].address = '10.1.0.215'
+ .apps['snappass-test'].units['snappass-test/0'].provider_id = 'snappass-test-0'
2026-09-08 01:34:27,856 INFO jubilant.cli Ready condition succeeded 3 times (jubilant.all_active(status))

jubilant wait CLI reference

jubilant wait
    [-h]
    [--delay DELAY]
    [--error ERROR]
    [--successes SUCCESSES]
    [--timeout TIMEOUT]
    [--juju-cli-bin JUJU_CLI_BIN]
    [--model MODEL]
    [--quiet | --verbose]
    READY

positional arguments:
  READY                 Python expression for the READY condition

options:
  -h, --help            show this help message and exit
  --delay DELAY         delay in seconds between status calls (default: 1.0)
  --error ERROR         Python expression for the error condition (default: None)
  --successes SUCCESSES
                        number of times `READY` must evaluate to true for the wait to succeed
                        (default: 3)
  --timeout TIMEOUT     overall timeout in seconds (default: 180.0)
  --juju-cli-bin JUJU_CLI_BIN
                        path to the Juju CLI binary
  --model MODEL         the Juju model to operate on, otherwise use the current Juju model
  --quiet               suppress all output except errors
  --verbose             increase verbosity

The jubilant wait CLI returns the following exit codes:

Code	Meaning
0	The READY condition succeeded.
1	The ERROR condition evaluated to true, or an exception was raised while evaluating an expression or waiting.
124	The wait timed out.
130	A keyboard interrupt (Ctrl-C) was received while waiting.