CLI Reference
Complete reference for every dynamiq CLI command — config, org, project, service, and resource-profiles — with flags and examples.
Complete reference for the dynamiq command. For installation and first-time setup, start with the CLI Overview. Command groups accept singular and plural aliases interchangeably: org/orgs, project/projects, service/services, resource-profile/resource-profiles.
dynamiq [--version] [-v|--verbose] [-h|--help] <group> <command> [flags]Options marked prompted are asked for interactively when omitted, so every command can run fully non-interactively in CI by passing its flags.
dynamiq config
Run without a subcommand to configure the CLI interactively:
dynamiq configPrompts for the API host (Enter keeps https://api.getdynamiq.ai) and your API key — a Personal Access Token. Saved values are reused by all commands.
dynamiq config show
Print the current configuration with the API key masked:
dynamiq config showCurrent Dynamiq CLI configuration:
DYNAMIQ API HOST: https://api.getdynamiq.ai
DYNAMIQ API KEY: dyn_...
DYNAMIQ ORG ID: 0d4f9a36-...
DYNAMIQ PROJECT ID: 7b1c2d8e-...dynamiq org
dynamiq org list
List organizations your token can access, as an ID / Name table:
dynamiq org listdynamiq org set
Set the current organization. Validates the ID against the API before saving it to your config:
dynamiq org set --id <org-id>--idstringrequireddynamiq project
Both commands require an organization to be set first.
dynamiq project list
List projects in the current organization:
dynamiq project listdynamiq project set
Set the current project (validated against the API):
dynamiq project set --id <project-id>--idstringrequireddynamiq service
Manage service deployments — custom containers run on platform infrastructure.
dynamiq service list
List services in the current project with their ID, name, access type, category, and hostname:
dynamiq service listdynamiq service get
Print all fields of one service:
dynamiq service get --id <service-id>--idstringrequireddynamiq service create
Create a service record in the current project:
dynamiq service create --name qa-service --access private--namestringrequired--accessprivate | public--categorystringdynamiq service deploy
Start a deployment for a service — either building from a source directory (the default) or running a prebuilt image:
# Build from source: archives the directory and lets the platform run the Docker build
dynamiq service deploy --id <service-id> \
--source ./ \
--docker-file Dockerfile \
--env-secret OPENAI_API_KEY "$OPENAI_API_KEY" \
--env LOG_LEVEL info \
--min-replicas 1 --max-replicas 3
# Or deploy a prebuilt image
dynamiq service deploy --id <service-id> --image registry.example.com/qa-service:1.0.0--idstringrequired--sourcepath--docker-contextstring--docker-filestring--imagestring--cpu-requests / --cpu-limitsstring--memory-requests / --memory-limitsstring--resource-profilestring--env NAME VALUEpair, repeatable--env-secret NAME VALUEpair, repeatable--commandstring, repeatable--argsstring, repeatable--min-replicas / --max-replicasint--target-cpu-utilizationintWith --source, the CLI packages the directory as a .tar.gz and uploads it with the deployment configuration to POST /v1/services/{id}/deploy; with --image it sends the configuration only. On success it prints Deployment successfully started with docker build. (or ... with image.).
dynamiq service status
Show the latest deployment of a service:
dynamiq service status --id <service-id>--idstringrequireddynamiq service update
Update a service's access type or description. At least one flag is required:
dynamiq service update --id <service-id> --access public --description "Public QA endpoint"--idstringrequired--accessprivate | public--descriptionstringdynamiq service delete
Delete a service:
dynamiq service delete --id <service-id>--idstringrequireddynamiq resource-profiles
dynamiq resource-profiles list
List predefined container sizes you can pass to service deploy --resource-profile:
dynamiq resource-profiles list --purpose service--purposeinference | service | fine_tuning--sort-byname | sort_order | description--page-sizeintNext steps
CLI Overview
Install and configure the dynamiq CLI — credentials, config files, and the org/project context that scopes every command.
Custom Nodes
Subclass Node to build your own workflow components — input schemas, the execute contract, the execution lifecycle, and connection handling with ConnectionNode.