Skip to main content
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

  1. Open Connections and click Connect on CLI Tools.
  2. 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.

​
Step 2: Connect from the CLI

Once a tool is turned on, an SRE reaches it through the NOFire AI CLI:
  1. Open API keys, click Create token, and choose CLI token (see API keys).
  2. Run nofireai auth login and paste the key.
  3. Start a session with nofireai chat start.
Getting Started covers authentication, chat commands, and keyboard controls for the CLI.

​
Test the connection

  1. In a chat session, ask NOFire AI to run a read-only command, for example “run kubectl get pods in the payments namespace”.
  2. NOFire AI asks you to approve the command, then returns its output. Output in the reply confirms the tool is on and the CLI is authenticated.

​
Troubleshooting

The toggle for that tool is off. Open Connections, click Connect on CLI Tools, and turn it on. The change takes effect on the next command.
The command runs on your own machine with your own credentials. Run the same command in your terminal first. If it fails there, fix the kubeconfig, AWS profile, or gcloud login it needs.
Only read-only commands are permitted. The table above lists the subcommands allowed for each tool.