Skip to main content
Every command the noorle CLI accepts. There are eleven.

​
Global flags

There is no --json, --format, --verbose, or --api-key flag.

​
Authentication

​
noorle login

Authenticate through the OAuth 2.0 device flow.
Opens your browser to the Portal’s device-verify page and prints a code to enter. It polls until you approve, then stores the token at ~/.noorle_token. Polling gives up after 10 minutes. The --username and --password flags are accepted but currently unused — authentication is device-flow only.

​
noorle logout

Deletes ~/.noorle_token. Reports “No active session found” when there is nothing to delete.

​
Plugins

​
noorle plugin init

Scaffold a plugin project from a template.
Templates are fetched from the platform. Run plugin list-templates to see the current set; rust, python, typescript, javascript, and go are the supported languages.

​
noorle plugin list-templates

Prints the templates the platform currently offers.

​
noorle plugin prepare

Run the project’s prepare.sh to install build dependencies.
Every template ships a prepare.sh that knows its own toolchain. A project without one prints guidance rather than failing.

​
noorle plugin build

Compile the plugin and pack it.
Runs ./build.sh through sh, then packs the result. It fails with an actionable error when:
  • build.sh does not exist
  • build.sh is not executable — run chmod +x build.sh
  • The build does not create dist/
  • The build does not produce dist/plugin.wasm
Run it from the plugin directory.

​
noorle plugin pack

Create the .npack archive from an already-built plugin.
Rarely needed on its own — build packs automatically. Use it to re-pack without recompiling. Reads dist/plugin.wasm and writes dist/{plugin-name}.npack, a gzipped tar containing: The plugin name comes from Cargo.toml, then package.json, then go.mod, then the directory name.

​
noorle plugin deploy

Upload the archive.
Requires noorle login first. Posts multipart form-data to POST /v1/capabilities/upload.

​
noorle plugin publish

build then deploy. Requires noorle login first.

​
noorle plugin validate

Check a plugin configuration file.
Validates YAML syntax and structure and prints the resolved plugin name. This is a local syntax check only — it does not contact the platform and does not run the full server-side validation the upload endpoint applies.

​
Maintenance

​
noorle check-update

Reports whether a newer CLI release exists. It does not install it — re-run the install script to upgrade.

​
What does not exist

These commands appear in older documentation and are not implemented: agent, gateway, api-call, api-key, config, env, token, session, audit, update, completion, plugin new, plugin push, plugin list, plugin info, plugin versions, plugin activate, plugin delete. Use the Portal or the management API for anything outside the plugin build loop.