Huly CLI examples

Projects and issues

# List every accessible project
huly projects list

# Get PROJ-123 as structured JSON
huly issues get PROJ 123 --json

# Create an issue with a Markdown description
huly issues create \
  --project PROJ \
  --title "Fix login flow" \
  --description-file ./body.md

# Inspect the available issue commands and inputs
huly issues --help
huly issues create --help

Workspace search

Search across the connected Huly workspace and request JSON when another command will consume the result.

huly search "customer import" --limit 20
huly search "customer import" --limit 20 --json

Comments and guarded deletion

Consequential commands require --yes, making destructive intent explicit in both interactive and automated use.

huly comments delete \
  --project PROJ \
  --issue-identifier 123 \
  --comment-id 0123456789abcdef \
  --yes

Attachments and file output

huly attachments download 0123456789abcdef \
  --output ./attachment.bin

Binary-producing commands require --output, so binary data never corrupts terminal or JSON output.

JSON input

Use JSON for nested objects, arrays, unions, or repeatable operations. Explicit flags override values supplied through JSON.

# Supply the complete operation input from a file
huly issues create --input-file ./new-issue.json --json

# Start with JSON and override one field
huly issues create \
  --input-json '{"project":"PROJ","title":"Draft title"}' \
  --title "Final title" \
  --json

Next: automate Huly

Learn how JSON output, exit codes, warnings, and non-interactive confirmation behave in shell scripts and CI jobs.