kubectl memorisation, no grepping logs, no clicking through five dashboards. Ask the question you would ask a senior engineer, get a cited answer backed by the Agent Mesh.
This tutorial set takes you from first query to daily driver. Start at Basics if you are new, skip ahead if you are not.
Why Chat
Natural language
Plain English. No query language to learn.
Answers with evidence
Every claim cites the underlying signal. Verify in one click.
Context aware
The session remembers the thread. Follow-ups do not start from scratch.
Multi-agent backend
Observer, RCA Pipeline, Memory, and Guardian all feed the answer.
Works across environments
Same prompts work for Kubernetes, AWS, GCP, and VMs in one workspace.
Runs skills on demand
Invoke any enabled skill with a slash command or by intent.
The difference, in two lines
The old way on Kubernetes:api-gateway is a Kubernetes pod, an ECS task, a GCE instance, or a process on a VM.
The tutorial series
Chat Basics
Open the interface, type your first query, read the response. About ten minutes.
Troubleshooting with Chat
Real debug flows: OOMKilled, ImagePullBackOff, CrashLoopBackOff, latency spikes. About fifteen minutes.
Advanced Chat
Role-shaped workflows for SREs, DevOps, and platform engineers. About twenty minutes.
Chat for cost analysis
Rightsizing, anomaly hunting, weekly budget reviews, all through Chat. About fifteen minutes.
The four prompt shapes that work
Health checks
Health checks
Use for the daily read.
Change correlation
Change correlation
Use when something just broke.
Investigation
Investigation
Use to pull a specific slice for a deep dive.
Cost and capacity
Cost and capacity
Use for weekly rightsizing.
Slash commands worth knowing
The slash menu shows up when you type/ in the chat box.
Where to start
- New to Chat
- Already using Chat
- Specific question
Work through the series in order:
- Chat Basics, ten minutes.
- Troubleshooting with Chat, fifteen minutes.
- Advanced Chat, twenty minutes.
- Chat for cost analysis, fifteen minutes.
Quick reference
Five prompts that cover most of daily use:What is failing?- morning triage.Why is <service> slow?- focused investigation.What changed in <namespace> in the last hour?- post-deploy check.Validate this(with YAML uploaded) - pre-deploy safety.Explain <concept>- learn a Kubernetes or AWS concept using your own resources as examples.
⌘K in the console, or rubix in your terminal.
Common questions
Does Chat work across environments?
Does Chat work across environments?
Yes. The same prompts work for Kubernetes, AWS, GCP, and Linux VMs. Use
/environments to scope to one, or ask broadly and Chat will include every environment in the workspace.Where does Chat run?
Where does Chat run?
The SRI Agent that powers Chat runs in RubixKube Cloud. The Observer in your environment provides signals. Raw logs stay with you unless you explicitly enable broader streaming.
Can Chat apply changes to my infrastructure?
Can Chat apply changes to my infrastructure?
Chat can recommend and draft changes. Applying anything requires explicit approval and is bounded by Guardian policies. See How to Automate Incident Remediation.
Is there a terminal version?
Is there a terminal version?
Yes. Install with
npm install -g @rubixkube/rubix, launch with rubix. Same agent, same skills, terminal-native UX.Related guides
How to add custom agent skills
Turn your best prompts into reusable skills.
How to Monitor Infrastructure Health
Dashboard-first view of the same data.