Skip to main content
The CLI keeps all configuration in your home directory. Nothing lives alongside your projects unless you explicitly opt into a trusted folder.

Configuration files

Do not hand-edit these. Use rubix login and rubix logout for auth, slash commands for preferences, and /untrust to remove a folder from the trust list.

Folder trust

When you run the CLI inside a folder for the first time, Rubix asks whether to trust that folder. Trusting a folder enables:
  • Reading local files with /paste or for skill inputs.
  • Running shell commands the agent drafts without re-prompting each time.
  • /send of shell output directly into chat.
Untrusted folders keep you in pure chat mode (no file or shell access). If you want to revoke trust for the current folder:
Or remove entries manually by editing ~/.rubix/trust.json if that is what you prefer.

Switching environments

Inside chat:
Pick one from the list. The choice is remembered for the current session. To change the default environment for future sessions, pick it once and then let Rubix remember it (the CLI asks).

Switching the AI model

Inside chat:
From the shell:
Model availability depends on your plan. Enterprise accounts can restrict available models per workspace.

Switching agents (apps)

If your workspace has multiple agent configurations (for example, different personas), you can switch which one new sessions default to:
Current sessions keep their original agent binding until you start a new one.

Console and docs shortcuts

From inside chat, open the web console or this documentation in your default browser:
Saves a trip through the address bar when you want to cross-check something.

Clearing the current session

Two levels of clearing:
  • /clear wipes the visible conversation history for readability. The session itself is preserved server-side.
  • /new starts a fresh session with no history at all.

Sensitive data and redaction

The CLI does not log your prompts or responses anywhere local. Session content is stored in RubixKube Cloud according to your workspace retention policy. To delete a session entirely, run rubix sessions to list sessions, then delete through the web console.

Where to go next

Commands reference

Every top-level and slash command.

Troubleshooting

Auth, proxy, and Node.js issues.