Huly CLI

Huly CLI

Use npx -y @starhui/huly-cli@latest to work with Huly through @firfi/huly-mcp.

For local development inside this repository, huly is also acceptable after pnpm build && pnpm link --global.

Quick Checks

1. Confirm the CLI is available:

   npx -y @starhui/huly-cli@latest --version
   

2. Check sanitized config from existing environment variables first:

   npx -y @starhui/huly-cli@latest context
   

3. If required config is missing, ask the user whether to pass an explicit dotenv file with --config <path>.
4. If project is omitted for issue commands, set HULY_DEFAULT_PROJECT or pass --project.

Never print real tokens, passwords, or full .env contents. npx -y @starhui/huly-cli@latest context is safe because it returns sanitized config.

Common Commands

List projects:

npx -y @starhui/huly-cli@latest project list --json

Discover statuses before creating or updating issues:

npx -y @starhui/huly-cli@latest project statuses HULY --json

List issues:

npx -y @starhui/huly-cli@latest issue list --project HULY --status-category active --limit 20 --json

Get an issue:

npx -y @starhui/huly-cli@latest issue get HULY-123 --project HULY --json

Create an issue:

npx -y @starhui/huly-cli@latest issue create --project HULY --title "Short imperative title" --description "Markdown body"

Update an issue:

npx -y @starhui/huly-cli@latest issue update HULY-123 --project HULY --status Done

Search:

npx -y @starhui/huly-cli@latest search "query text" --limit 10 --json

Raw Tool Access

Use raw calls when the first-class CLI does not expose an upstream MCP tool:

npx -y @starhui/huly-cli@latest tools --filter document
npx -y @starhui/huly-cli@latest call get_issue --field project=HULY --field identifier=HULY-123 --json
npx -y @starhui/huly-cli@latest call list_projects --data '{"limit":10}' --json

--field key=value coerces true, false, null, and numbers. Use --data or --file for nested JSON.

Safety

• Use --json for agent parsing.
• Read before write: inspect the project/status/issue before mutating it unless the user gave exact values.
• Destructive commands require confirmation; only pass --yes when the user explicitly requested deletion.
• Prefer status names from project statuses; do not invent workflow statuses.
• If a command fails due to auth/config, report the missing sanitized fields from npx -y @starhui/huly-cli@latest context; do not expose secrets. Only retry with --config <path> after the user confirms which dotenv file to use.

Useful Mapping

• Projects: project list, project get, project statuses, project create, project update, project delete.
• Issues: issue list, issue get, issue create, issue update, issue delete, issue label, issue unlabel, issue move.
• Global search: search.
• All upstream MCP tools: tools and call.