Migrating from hutly

The CLI used to be published as @intellia/hutly-cli with a hutly command. It is now @intellia/cli with an intellia command. The commands, flags and output are unchanged; only the names below moved.

The old names still work for now. Each use prints a deprecation warning on stderr and is reported to Intellia so we can see what still needs moving. Plan to move scripts, CI pipelines and config files over before the old names are removed.

Switch the package

Uninstall the old package first. While it is installed, a hutly command stays on your PATH and old scripts keep running through it; once it is gone, any script you missed fails with command not found instead.

npm uninstall -g @intellia/hutly-cli
npm install -g @intellia/cli
intellia --version

Rename your settings

When both names of a setting are set, the INTELLIA_ one wins. INTELLIA_AGENT_INVOCATION is the exception: agent mode is on when either name is 1.

Rename the config files in place; their contents keep the same format:

mv .hutlyrc.yaml .intelliarc.yaml
mkdir -p ~/.intellia && mv ~/.hutly/credentials ~/.intellia/credentials

Inside the platform

Workflow bash nodes and Sammy’s sandboxes already have intellia installed and set the INTELLIA_* variables. They also still set the matching HUTLY_* variables ($HUTLY_PAYLOAD, $HUTLY_OUTPUT_FILE and the rest), so existing scripts keep running. New scripts should read the INTELLIA_* names. A hutly command in a bash node or sandbox still runs, but it prints the deprecation warning and is reported like any other use.