difyctl works in one active workspace at a time, taken from a flag, an environment variable, or your stored default. For the order those take priority, see How difyctl Picks a Workspace.
difyctl get workspacelists the workspaces you belong touse workspaceswitches the active one Cloud
List Your Workspaces
Flags
Examples
See your workspaces and which one is active:Output
Default table:
-o json:
Exit Codes
See Output Formats and Exit Codes for the full scheme.
Switch Your Workspace Cloud
use workspace switches your active workspace on the server first, then updates the stored default in hosts.yml. If the switch fails (the workspace doesn’t exist, or you’re not a member), your local state is left untouched.
Arguments
workspace-id: the workspace to switch to, fromget workspace. In a terminal, omit it to pick from your workspaces, the current one marked*. In a non-interactive session (script, CI, pipe), it’s required.
Flags
Only the global flags.Examples
Pick interactively from your workspaces:--workspace instead:
Output
On success, the new active workspace is confirmed on stdout:Exit Codes
See Output Formats and Exit Codes for the full scheme.
How difyctl Picks a Workspace
Apps live in exactly one workspace, so every command that targets one needs a workspace to run against.difyctl resolves it in this order, taking the first value it finds:
- The
--workspace <id>flag on the command itself. Applies to that invocation only. - The
DIFY_WORKSPACE_IDenvironment variable. - Your stored default, written to
hosts.ymlin the config directory when you sign in and updated byuse workspace.
2.
Workspace IDs are UUIDs, so pass an ID from get workspace, not a workspace name. A value that isn’t a UUID fails as a usage error.