CLI Tools - NOFire AI

Connect CLI tools to bring live command output into NOFire’s system context. Before a deploy, that context shows what the change touches. When something breaks, the same output is the evidence NOFire reasons over.

No credentials stored. Each toggle lets SREs run that CLI tool through the NOFire AI CLI, using credentials already on their own machine (kubeconfig, ~/.aws, and more). Only read-only commands are permitted.

Step 1: Turn on the tools your SREs need

Go to the Connections tab and click Connect on CLI Tools.
To allow a tool, turn its toggle on. To remove that connection, turn the toggle off.

Each toggle is its own connection. Turning it on creates that connection right away. Turning it off deletes it. There is no Save step.

Toggle	What it allows
kubectl	Kubernetes — get, describe, logs, top
aws (cli)	AWS CLI — describe, list, get (read-only)
git	Git — status, log, diff, branch
gcloud (cli)	Google Cloud CLI — describe, list, get
helm	Helm — list, status, get, history
terraform	Terraform — show, plan, output, state list
bash	General shell — cat, grep, ps, df, ls (read-only)

Step 2: Connect from the CLI

Once a tool is turned on, an SRE reaches it through the NOFire AI CLI:

Create a CLI API key in Account → API Keys (see API Keys).
Run nofireai auth login and paste the key.
Start a session with nofireai chat start.

Getting Started covers authentication, chat commands, and keyboard controls for the CLI.