Skip to main content
Short answers to the questions we hear most. If yours is not here, the Troubleshooting page covers specific failures, and support is at the bottom.

Getting started

No. A Kepler sign-in (Google, GitHub, or email) and a model are all you need. The RubixKube platform is a separate product that watches your environments continuously. If you use both, Kepler ships with RubixKube skills so you can pull the platform’s active issues and RCAs into a chat, but Kepler works fully on its own.
Two things: a model, and any folders you want it to read or edit (Cmd+O). You do not hand over kubeconfigs, cloud credentials, or SSH keys. Kepler uses whatever kubectl, aws, gcloud, and ssh already have on your machine, and only looks at what you already have access to.
Something you would ask a colleague on shift. Why is checkout crashlooping in prod?, What changed in the payments namespace today?, or /triage api-gateway are all good openers. Start in Observe, the default, so nothing writes while you get a feel for how Kepler works. The Quickstart walks through a full first session.
Coding agents work on a repo that holds still and remembers everything for them. Kepler works on live clusters and dashboards that drift and forget, so it builds its own memory of your systems and can watch things in the background. It can read and edit files in folders you grant, but it is built for operating systems, not for shipping features.

Safety and control

Not unless you tell it to. Every new conversation starts in Observe, which is read-only. In Assist, Kepler stops before every write and shows you the exact command. Only Yolo runs writes without a per-step approval, and you switch into it deliberately, per conversation, with Shift+Tab or /mode yolo.
With kubectl: delete, scale, drain, cordon, taint, and rollout restart or rollout undo. With helm: delete, uninstall, and rollback. Also rm -rf, terraform destroy, and delete, terminate, or stop calls on AWS, GCP, and Azure. Windows equivalents such as recursive Remove-Item are on the list too. No posture, no permission setting, and no rule you write can unlock these. The full list is in Permissions.
It stops and asks. A card shows the command and says plainly that Kepler cannot tell whether it is safe. You can trust it as read-only, which saves a rule that applies everywhere and survives restarts, or say no. In Assist and Yolo you can also run it just once. In Observe, trusting it is the only way through.
Yes. Settings > Permissions has three switches, Files, Shell, and MCP servers, each set to allow, ask, or block. Ask is the default for all three. Set a switch to ask and Kepler pauses for that kind of tool regardless of posture. These settings only ever tighten what a posture allows. Nothing in the app can loosen them on Kepler’s behalf.

Models and cost

The hosted Kepler models, available with your sign-in and no key. Or bring your own key for Anthropic, OpenAI, Google (Gemini API or Vertex AI), xAI, AWS Bedrock, or any OpenAI-compatible endpoint. Ollama gives you fully local models. Set it up in Settings > Models or with /model.
No, ever. You choose the model, so you control the spend. When a request fails, Kepler retries the same model or tells you it could not finish. It never silently downgrades to a cheaper or different model.
Kepler runs locally and is free, with no seats or cloud limits. Cloud plans add team sync, shared memory, and hosted automations. Model usage is separate: keys you bring are billed by that provider directly. Settings > Plan & Usage shows your plan and what this month has cost so far.
No. A watcher is a plain background check with no model involved. The model only runs when the watcher fires, and then only to look at what changed and suggest something. A quiet watcher costs nothing.

Data and privacy

It stays on your machine. Conversation history, memory, watchers, and settings live in a single folder in your home directory. The only outbound traffic is to the model you chose and to your own tools and integrations. There is no RubixKube server in the middle of your chats.
In your operating system’s keychain, under Kepler’s name. They are never written to a plain-text file and never sent anywhere except to the provider they belong to.
Yes. Run a local model with Ollama and pick it in the model picker. With a local model and no channels connected, Kepler makes no outbound calls beyond what your own kubectl and cloud CLIs make.
Yes. Press the ghost button beside New session in the sidebar. An incognito session reads no memory and writes none, so nothing from it shows up later. You must start it as incognito. An ordinary session cannot be made incognito after the fact.
Settings > Memory has import, rebuild, and wipe. Wipe asks for confirmation and removes everything Kepler has learned. To move memory in from another assistant such as ChatGPT or Claude, use Import from another assistant, which gives you a prompt to run there and a place to paste the result.

Platform

macOS 13 or later on Apple Silicon, 64-bit Windows, and Linux as .deb or .rpm packages on x86-64. Windows support is early: background running and full PowerShell parity are still in progress, and there is no WSL integration yet. See Installation.
Yes. Settings > Experiments > CLI helper installs a kepler command that drives the same local agent, the same sessions, and the same approval gate. Run kepler help for its commands. It is a client for the desktop agent, not a separate product, so the app still needs to be installed.
Yes. Connect WhatsApp, Slack, Telegram, or Discord in Settings > Gateway, then type /otg whatsapp (or another channel) in a session to drive it from there. Approvals arrive as a message and you reply yes or no. Channels work while Kepler is running on your machine. WhatsApp uses the same linking as WhatsApp Web and is not an official WhatsApp feature, so it can drop and heavy use may put your account at risk. See Channels.

Contact Support

Email: connect@rubixkube.ai
Please include your Tenant ID (Settings → Organization), timestamp, and screenshots.

Troubleshooting Guide

Step-by-step fixes for common issues across Dashboard, Insights, Agents, and more.

FAQ

Answers to common questions about setup, RCA, agents, and docs.

Docs Navigation

Browse all guides to learn workflows and best practices.