Skip to main content
Quick answers to the questions we hear most.

​
General

A terminal-native client for RubixKube. Same SRI Agent, same skills, same workspace as the console. Launched with rubix.
No. Sign up at console.rubixkube.ai once, then run rubix login from the terminal. Everything else happens over HTTPS.
No. The CLI sends your prompt to RubixKube Cloud, where the SRI Agent runs the same Guardian-gated flow as the console. Any mutating action requires explicit approval before it lands in your environment.
The docs and several SDKs are open source. The CLI itself is proprietary, installed from the public npm registry. Reach out if you need a private build for regulated environments.

​
Installation and compatibility

Node.js 18 or later. LTS versions are recommended for stability.
Yes. PowerShell and Windows Subsystem for Linux both work. Unicode renders cleanly in Windows Terminal and modern VS Code integrated terminals.
Yes. Behaves the same as running locally. Just make sure the remote host has Node.js 18+ and outbound HTTPS.
Yes. Add npm install -g @rubixkube/rubix to your Dockerfile. Set RUBIX_API_KEY at runtime so it can authenticate without a device-code prompt.

​
Auth and security

~/.rubix/auth.json. Encrypted at rest on your disk when your OS supports it (Keychain on macOS, DPAPI on Windows). On Linux, file-system permissions restrict it to your user.
Yes. Set RUBIX_API_KEY in the environment. Useful for CI and ephemeral runners. The CLI uses the env var and skips the browser prompt.
Only inside a trusted folder, and only when you ask via chat. Rubix drafts the command; running it still requires a confirmation step or explicit approval depending on your Guardian policy.
rubix logout && rubix login re-issues a fresh token. Previous tokens are invalidated server-side.

​
Scope and capabilities

Yes. Kubernetes, AWS, GCP, and Linux VMs are all reachable from the same CLI. Switch scope with /environments.
Yes. /skills skill-name runs any enabled skill. Same intent-matching behaviour as the console Chat.
Chat can summarise them and link out. Full RCA reports render best in the console because of their evidence tables and graph views. Use /console from inside chat to jump over.
Chat surfaces recommended actions and can deep-link you into the console for approval. Inline approval from the CLI is on the roadmap. For urgent cases, /console opens the right page directly.

​
CI and automation

Set RUBIX_API_KEY as a secret. Optionally set RUBIX_ENV_ID to pin the environment. Use npx @rubixkube/rubix chat --prompt "..." for single-shot invocations. See Examples for a full workflow.
A full detect-to-recommend cycle counts. Simple questions and slash commands do not.
Yes. rubix chat --prompt "..." writes to stdout, so >, >>, and | all work.

​
Getting help

Email connect@rubixkube.ai with the output of rubix --version, your Node version, and a short description. A human engineer will respond.
Yes, on the npm package page at npmjs.com/package/@rubixkube/rubix and in the CLI itself when a new release is available.

Overview

What the CLI is and who it is for.

Examples

Daily flows you can steal.