CLI reference
This reference covers the published Hyfens CLI v0.1.10, checked on 24 September 2026. Use hyfens <command> --help from the installed release for the exact options and required values.
Global options
| Option | Purpose |
|---|---|
--verbose | Emit additional diagnostic detail. |
--json | Request machine-readable output where the command supports it. |
--project PATH | Select a project directory. |
--no-color | Disable colored output. |
--non-interactive | Disable interactive prompts. |
--version, -v | Print the executable version. |
Published command tree
hyfens --help | -h | help
hyfens --version | -v | version
hyfens login [--host URL] [--profile NAME] [--device]
hyfens logout
hyfens status
hyfens doctor
hyfens mcp [--profile NAME] [--debug]
hyfens profile list|show|use|remove|current
hyfens auth login|status|logout
hyfens init
hyfens analyze
hyfens release android|ios
hyfens patch android|ios
hyfens rollback
hyfens cleanup
hyfens inspect
hyfens verify <patch-file>
hyfens keys generate|inspect
hyfens serve
hyfens deploy
hyfens rollout create|inspect|transition
hyfens bundle export|verify|import|admit
Every listed command and subcommand accepts --help. The v0.1.10 root command list does not include later untagged commands. In particular, do not assume an upgrade command is present in this release.
Release, patch, verification, and deployment
| Command | Documented purpose | Important boundary |
|---|---|---|
hyfens release android|ios | Create a target-specific baseline through the normal Flutter release build. | --metadata-only skips the build and is not release evidence. |
hyfens analyze | Check project changes against a selected baseline and report unsupported inputs. | Use the installed release’s help for project and release selection. |
hyfens patch android|ios | Compile and sign a supported patch against an exact release. | It does not replace native/store changes or expand the supported change set. |
hyfens inspect | Inspect local artifact metadata. | Inspection does not mean a control plane accepted or a device applied it. |
hyfens verify <patch-file> | Check artifact bytes against the selected release/trust material. | Verification is local artifact evidence, not delivery evidence. |
hyfens deploy | Register metadata, upload the signed bytes, and promote through the selected self-hosted control plane. | Requires authorized scope and preconditions. Success does not prove device delivery. |
hyfens rollback --to base | Request the bounded signed rollback to the baseline. | An older patch is not made replayable. |
Authentication and environment
Human commands can use the active CLI profile. In CI, the tagged v0.1.10 documentation identifies a scoped service/API key supplied via HYFENS_TOKEN from a CI secret store. Do not put the value in command arguments, profile/project files, logs, artifacts, or images. See CI authentication.
The release docs describe a managed default endpoint but explicitly do not promise public signup, hosted release downloads, production availability, or an SLA. The current published app update workflow documented here is self-hosted; there is no public direct API contract in this reference.
Common command options
Use hyfens <command> --help on v0.1.10 for the complete syntax and validation rules. The options below are the material tagged command options relevant to the documented workflow.
| Command | Options |
|---|---|
login | --host URL, --profile NAME, --device; --ca-cert PATH for a custom certificate authority. --email is a compatibility option. |
init | --dry-run, --force, --flavor, --entrypoint. |
analyze | --release, --flavor, --entrypoint. |
release android|ios | --architecture (default arm64), --mode (default release), --flavor, --entrypoint; --metadata-only is a test shortcut that skips the normal build. |
patch android|ios | --release, --flavor, --entrypoint. |
rollback | --release, --to base. Only rollback to the trusted store-installed baseline is supported. |
cleanup | --scope builds|patches, --release, --confirm. This removes one explicitly confirmed mutable local target; inspect the selected release and scope before confirming. |
serve | --host (default 127.0.0.1), --port (default 18080), --release, --allow-lan. This is a development server; exposing it beyond loopback is opt-in. |
deploy | --release, --patch, --endpoint, --token, --organization-id, --application-id, --environment-id, --ca-cert, --expected-version (default 0), --display-version (default local). --token is sensitive; supply CI authorization through HYFENS_TOKEN from a secret store instead of a command argument. |
The rollout create|inspect|transition administrative commands also appear in the v0.1.10 command tree. Their presence does not establish that runtime cohort eligibility and device delivery are available, so this reference does not describe a customer rollout procedure.
Toolchain and target boundary
The release manifest requires Dart ^3.13.0; the documented tested family is Flutter 3.47.x and Dart 3.13.x. Release builds pin Flutter 3.47.1. Hyfens evidence targets Android and iOS. macOS/Linux/Windows x64 and arm64 are CLI host archives, not mobile runtime support claims.
No released evidence in the inspected v0.1.10 materials establishes React Native, DartNative, web, or desktop app patching. Many Dart/Flutter language features remain partial or untested; consult the versioned support matrix before relying on a patch.
Local developer server
hyfens serve is a development server, not a production delivery host. The tagged CLI documents defaults 127.0.0.1:18080; LAN binding requires the explicit --allow-lan option. Review the installed version’s hyfens serve --help before exposing a local process.