caseworkctl dev grant command reference
Exchange an existing Casework approval using an explicit configured issuer connection.
Contract status
Section titled “Contract status”This page is generated from the public Clap command tree for Registry Stack source version 0.46.0 and catalog SHA-256 d43b1bf418e0b00fac52311fa3a106fa124512dbc88cf511475713af2d73aa47. Hidden implementation commands are omitted.
caseworkctl dev grant [OPTIONS] --grant <GRANT> --connection <FILE> <CLIENT> [PROJECT]Arguments
Section titled “Arguments”| Argument | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
<CLIENT> | Yes | n/a | n/a | n/a | Registered agent client ID listed under clients in the task connection file |
[PROJECT] | No | . | n/a | n/a | Existing project whose private directory receives the grant-specific header |
Options
Section titled “Options”| Option | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
--grant <GRANT> | Yes | n/a | n/a | n/a | Existing Casework-approved grant UUID; this command does not approve tasks |
--connection <FILE> | Yes | n/a | n/a | n/a | Task connection file (PlatformTaskConnection) naming the fixed target and each client’s assertion key reference |
--format <FORMAT> | No | human | human, json | n/a | Write human diagnostics and reports, or one typed JSON report |
-h, --help | No | n/a | n/a | n/a | Print help |
Generation contract
Section titled “Generation contract”After changing a public command, argument, option, default, environment binding, or help description, run cargo run --locked -p registry-cli-docs -- --write, commit crates/registry-cli-docs/catalog.json, then run npm run generate from docs/site.