KubeBolt docs
GitHub

Meet Kobi: one AI, two modes

Kobi is KubeBolt's AI SRE. Kobi Copilot answers when you ask and ships in every edition; Kobi Autopilot acts on its own under your rules on KubeBolt Cloud.

Kobi is KubeBolt’s AI SRE — the same character everywhere in the product, working in two modes:

Copilot never changes anything by itself: every fix is a proposal that runs only when you click Execute, under your role, and lands in the audit trail. The difference between the modes is who drives.

When does a human sign off in Autopilot?

That depends on Autopilot’s operating mode — configurable per organization on KubeBolt Cloud:

Kobi Copilot investigating an incident and proposing a fix you approve.
Kobi Copilot investigating an incident and proposing a fix you approve. KubeBolt 2.1.1
Operating modeWhat executesHuman sign-off
Suggest onlyNothing — Kobi investigates and proposes; you apply the commands yourselfNot applicable (never executes)
Approve & ExecuteEvery action, after your approvalEvery action waits for it
AutonomousLow-risk actions, automaticallyDestructive / high-risk actions always wait for it

A resolved incident is “auto-resolved” either way — the incident view marks whether an action paused for a human sign-off, as an attribute, not a different status.

The rest of the guardrails

Beyond the operating mode, Autopilot’s autonomy is bounded by:

Where to go next