--- title: "Non-Interactive Catalyst CLI Commands" url: https://docs.catalyst.zoho.com/en/ai-toolkit/ni-cli/ni-commands/ description: "Reference for the commands available in the NI CLI." last_updated: 2026-09-15T06:29:39Z service: AI Toolkit type: general related_links: - name: "Motivation" url: /en/ai-toolkit/ni-cli/motivation/ - name: "Access Non-Interactive CLI" url: /en/ai-toolkit/ni-cli/install-cli/ - name: "CLI vs NI CLI" url: /en/ai-toolkit/ni-cli/cli-vs-ni/ - name: "Interactive Catalyst CLI" url: /en/cli/v1/cli-command-reference/ repository: name: "Agent Skills" url: https://github.com/catalystbyzoho/agent-skills --- # Non-Interactive Catalyst CLI Commands The following help section details all the Catalyst CLI commands that are compatible and non-compatible with Non-interactive mode. ### Global CLI Options The following table covers the options that are possible in the Catalyst CLI:
Options Purpose
`--ni` | `--non-interactive` Turns on non-interactive mode for the command
`--dc <data-center>` Selects the data center (us, eu, in, au, ca, sa, jp, uae)
`--org <org>` Selects the organization/portal (name or ID)
`--project <project>` Selects the project (name or ID)
### Commands That Support Non-Interactive Mode The following table details all the Catalyst CLI commands that are compatible with non-interactive mode:
Command Required Options Good to Know NI CLI Command
[`catalyst init`](https://docs.catalyst.zoho.com/en/cli/v1/initialize-resources/initialize-new-project/) `--project`
  • `--org` required only if more than one org exists (a single org is chosen automatically).
  • Only `project` initialization is supported in NI mode.
  • `--force` overwrites an existing project association.
```sh catalyst init -ni --project MyProject ```
[`catalyst functions:add`](https://docs.catalyst.zoho.com/en/cli/v1/working-with-functions/add-functions/)
  • `--name`
  • `--type`
  • `--stack`
  • Replaces `functions:setup`.
  • `--integ-service` required only when `--type` is `integ`.
  • `--overwrite` required only to replace an existing function of the same name.
  • Sample class/entry-point names use built-in defaults; dependency installation is confirmed automatically.
```sh catalyst functions:add -ni --name InvoiceFetch --type bio --stack node20 ```
[`catalyst functions:delete`](https://docs.catalyst.zoho.com/en/cli/v1/working-with-functions/delete-functions/) `[function name or ID]`
  • Defaults to local deletion if no location is specified.
  • `--remote` is blocked in NI mode.
  • Delete confirmation is accepted automatically.
```sh catalyst functions:delete -ni InvoiceFetch ```
`catalyst functions:execute` `[function name]` conditional
  • Replaces `functions:shell`.
  • Function name required only if more than one function exists.
  • `--key` required only when the function has multiple named inputs.
  • `--input` and `--debug` are optional.
```sh catalyst functions:execute -ni InvoiceFetch --input '{"orderId":"123"}' ```
[`catalyst appsail:add`](https://docs.catalyst.zoho.com/en/cli/v1/add-appsail/)
  • `--name`
  • `--source`
  • Runtime (Catalyst-managed vs. Docker) is detected from `--source`.
  • `--stack` required for Catalyst-managed runtime.
  • `--platform` conditional for Java.
  • `--port` is ignored (with warning) for managed runtime.
  • `--stack`/`--build`/`--platform`/`--overwrite-config` are ignored for Docker runtime.
  • `--overwrite-config` required only to replace an existing service config.
```sh catalyst appsail:add -ni --name MyApp --source ./app --stack node20 ```
[`catalyst client:setup`](https://docs.catalyst.zoho.com/en/cli/v1/working-with-the-client/set-up-client/)
  • `--type`
  • `--name`
  • `--flavour` required only for React (`js`/`ts`).
  • `--stylesheet` conditional for Angular.
  • `--routing` optional, Angular only.
  • `--overwrite` required only if the client folder already exists.
```sh catalyst client:setup -ni --type react --name myclient --flavour js ```
[`catalyst client:delete`](https://docs.catalyst.zoho.com/en/cli/v1/working-with-the-client/delete-client/) `[client version]` optional
  • Defaults to local deletion if no location is specified.
  • `--remote` is blocked in NI mode.
  • Delete confirmation is accepted automatically.
```sh catalyst client:delete -ni 1.0.0 ```
[`catalyst slate:link`](https://docs.catalyst.zoho.com/en/cli/v1/working-with-slate/link-slate-app/) `--source`
  • `--name` and `--framework` optional (framework auto-detected; a valid `--framework` overrides detection).
  • `--template` and `--default` are ignored with a warning.
```sh catalyst slate:link -ni --source ./my-app ```
[`catalyst slate:create`](https://docs.catalyst.zoho.com/en/cli/v1/working-with-slate/create-slate-app/)
  • `--name`
  • `--framework`
  • `--template` optional.
  • No `--source` option, since create always scaffolds a fresh directory.
  • `--default` is ignored with a warning.
```sh catalyst slate:create -ni --name MyApp --framework react ```
[`catalyst slate:unlink`](https://docs.catalyst.zoho.com/en/cli/v1/working-with-slate/unlink-slate-app/) `--name`
  • An unknown or missing name fails with the list of available apps.
  • `--remove-source` optional (deletes the source directory; kept by default).
```sh catalyst slate:unlink -ni --name MyApp ```
[`catalyst pull`](https://docs.catalyst.zoho.com/en/cli/v1/pull-resources/pull-specific-resource/)
  • `[feature]`
  • `--resource`
  • Only one feature pulled per run.
  • `--overwrite` required only if the target already exists locally.
  • Enabling and pulling API Gateway rules is confirmed automatically.
```sh catalyst pull -ni functions --resource InvoiceFetch ```
[`catalyst deploy slate`](https://docs.catalyst.zoho.com/en/cli/v1/deploy-resources/deploy-to-slate/) `[name]`
  • `-m <message>` optional deploy message.
  • `--production` deploys to production.
  • `--no-wait` skips waiting for completion.
```sh catalyst deploy slate -ni MyApp ```
[`catalyst login`](https://docs.catalyst.zoho.com/en/cli/v1/login/login-from-cli/) `--dc`
  • Data center must be specified; it is not prompted.
  • `--no-localhost` and `--force` optional.
```sh catalyst login -ni --dc us ```
### Commands That Are Disabled in Non-Interactive Mode The following table details the Catalyst CLI commands that are disabled in non-interactive mode:
Command Why It's Disabled Use Instead Complete Command
[`catalyst functions:setup`](https://docs.catalyst.zoho.com/en/cli/v1/working-with-functions/set-up-functions/) It's the interactive setup wizard for the first function in a project. It walks through picking a function type, stack, and several other selections as prompts and doesn't have an option-driven equivalent for every step, so it's blocked outright rather than partially supported. [`catalyst functions:add`](https://docs.catalyst.zoho.com/en/cli/v1/working-with-functions/add-functions/) ```sh catalyst functions:add -ni --name InvoiceFetch --type bio --stack node20 ```
[`catalyst functions:shell`](https://docs.catalyst.zoho.com/en/cli/v1/working-with-functions/functions-shell/) It launches a live Node shell session for testing and debugging a function interactively, which has no meaningful non-interactive form since the whole point is a human typing commands into it. `catalyst functions:execute` (for Event, Job, and Integration functions) ```sh catalyst functions:execute -ni InvoiceFetch --input '{"orderId":"123"}' ```