garden target

Show which Garden backend commands talk to

garden target

Print the active target, how it was chosen, and where its services live.

garden resolves the target in this order, first match winning:

1. –target <name> explicit, one command
2. GARDEN_TARGET explicit, one shell
3. the checkout’s pin written at clone time
4. the build default dev builds → dev, releases → prod

Step 3 is why a dev checkout and a prod checkout can sit side by side: the same binary follows whichever one you’re standing in.

Flags

Flag	Type	Default	Description
--target	string	—	Garden backend to talk to (prod|dev); defaults to the checkout’s own target

garden target set

Pin this checkout to a target

garden target set <prod|dev>

Record which backend this checkout belongs to, in its own config. Commands run anywhere inside it then use that target without a flag, whichever garden binary you invoke.

Run this once per existing checkout. New checkouts are pinned by garden clone.

Flags

Flag	Type	Default	Description
--target	string	—	Garden backend to talk to (prod|dev); defaults to the checkout’s own target

Always current

Generated from the CLI itself. Run garden target --help for the same reference offline, pinned to the version you have installed.