Skip to main content

​
First run

After installation, launch with no arguments: 
rubix
The first run prompts you to sign in via device-code flow. A short code and URL appear; open the URL in any browser, paste the code, approve. Takes about 30 seconds. Credentials persist at ~/.rubix/auth.json. You do not re-login every time.

​
Starting a chat

The default command launches the interactive chat UI: 
rubix
You land in a terminal chat with your default environment selected. Type a question and hit enter. 
> What is the health of the payments service?
The SRI Agent responds with cited evidence, the same way the web console does. Follow-up questions preserve session context.
Rubix CLI session showing the user asking 'How is my infra doing?', the agent's thought 'Evaluating Infrastructure Status', an action calling get_observability_stats(), and a response stating the environment has 67 active issues and 68 total insights.

​
Scripting a single prompt

To send a prompt and exit (useful in CI or for saving shell aliases): 
rubix chat --prompt "What is the health of every production environment?"
The agent answers, prints the result, and exits. Combine with --session-id to append into an existing conversation.

​
Resuming a session

List previous sessions: 
rubix sessions
Resume the one you want: 
rubix chat --session-id <id>
Or from inside chat, run /resume and pick from the list.

​
Switching environments

The active environment determines the scope of the next question. Switch on the fly: 
/environments
Pick from the menu. Any follow-up question runs against the new scope.

​
Switching the AI model

Some accounts have access to multiple model options for chat. Switch inside a session: 
/models
Or from the shell: 
rubix model set <model-id>

​
Feeding shell output into chat

When you want the agent to read command output directly, run the command in your shell, then drop into chat and run: 
/send
The last command’s output gets added as context for your next question. Avoids fragile copy-paste.

​
Keystroke shortcuts

Enter submits. Shift+Enter adds a newline.
Type / anywhere to open the slash menu. Arrow keys navigate, enter confirms.
/paste inserts clipboard content cleanly, bypassing terminal paste truncation that can mangle long inputs.
/exit or /quit, or Ctrl+C.

​
Logging out

rubix logout
Clears local credentials. Next rubix run will prompt for the device-code flow again.

​
Where to go next

Configuration

Where credentials and settings live, how trust is scoped per directory.

Commands

Complete reference for top-level commands and slash commands.

Examples

Concrete daily flows: on-call triage, post-deploy verification, cost reviews.

Troubleshooting

Login issues, stale auth, proxy problems.