Chat requires a connected AI model. If you haven’t configured one yet, see AI Models & Setup.
Opening the chat
Open the chat from the chat button in the platform header — it appears in a sidebar next to your current view. You can also open it as a separate window to keep the conversation visible while you work elsewhere. The chat is available at both the Cluster and Workspace level, and automatically scopes its responses to the context you’re working in.What you can do
The assistant understands natural language and can use its tools to interact with your cluster on your behalf. Common uses include:- Investigating issues such as misconfigured resources, unreachable applications, or networking problems.
- Querying cluster resources like Pods, Deployments, Services, and ConfigMaps.
- Getting guidance on resource optimization, node allocation, and resource limits.
- Reviewing and drafting Kubernetes manifests or Helm values.
- Troubleshooting interactively by feeding the assistant additional context.
Chat modes
A mode selector tailors how the assistant responds:- Ask — Answer questions and explain, without proposing changes.
- Code — Focus on writing and editing manifests, values, and configuration.
- Plan — Break a task down into a step‑by‑step plan before acting.
Choosing a model
A model picker lets you switch between the models marked as chat enabled in AI Models & Setup. The cluster default is preselected. Switching models starts a fresh connection for the next message.Tools and reasoning
The chat uses the same tools as agents. As the assistant works, it shows which tools it is calling so you can follow its reasoning:- Kubernetes — Query resources, read logs, describe Pods, inspect events, and retrieve manifests in real time.
- Helm — List releases, inspect chart values, and review release history.
- Custom tools — Any custom MCP servers and integrations connected to your cluster.