Notifications
When a change is done, a notification at the bottom right says what happened, in plain words: “Scaled storefront to 5 replicas”, “Cordoned worker-2”.- A notification stays for six seconds, or ten when something went wrong, and eight when an AI assistant’s change wasn’t made because nobody approved it in time, or the assistant withdrew it. Up to three show at once; a new one makes the oldest go.
- It stays as long as the pointer is over it, or it has the focus, so you have time to read it and act.
- Some notifications have a button: Undo, or Open for something new, like the job Run now started, the objects Create made, what a view’s action created, or the address of a new port forward.
Undo
Undo in a change’s notification makes the opposite change. It’s a change like any other: it has its own command, and its own line in the Activity log.
If the undo fails (someone changed the object in between, say), a notification says “Couldn’t undo”, with the reason.
Restarts, rollbacks, drains, deletes, YAML edits, changes to several objects at once and changes an AI assistant asked for have no Undo. Restarts and rollbacks can be followed by another rollback, from Roll back…. See Actions by kind.
The Activity log
The Activity button in the header (a clock with an arrow) opens Changes this session: every change you made from Lumovi, newest first. A count on the button shows how many are new since you last looked. Each entry shows:- What happened, like “Restarted checkout”. Choose it to open the object, when it’s in the cluster you’re looking at.
- When, and the cluster, when it’s another one than you’re looking at.
- Its status: In progress, Done, Failed (with the reason), or Rejected. For a change to a Secret that failed, the reason is a code and one sentence, not the cluster’s words: “It failed (invalid). What the cluster said of the Secret isn’t kept here: it can quote its values.” The dialog that made the change still shows what the cluster said.
- Who asked, for a change an AI assistant asked for: “via Claude Code”, or “rejected, asked by Claude Code” for one you rejected, with the note you wrote.
- The kubectl command that does the same thing, with Copy command.
The log lives only as long as the session: it’s empty again when you restart Lumovi, or reload the page when it runs in your cluster. For a lasting record of who changed what, through Lumovi, see the audit log.
Changes AI assistants asked for
A change an AI assistant asked for gets a line too, once it’s over: made after you approved it, or failed, also when it would no longer have done what you saw; made without asking, where your permissions allow that; or rejected. Its notification says whose it was: “As Claude Code asked, in demo.” Changes nobody approved in time, and ones the assistant withdrew, have only a notification. In the cluster’s own audit log, they’re yours: Lumovi makes them with your credentials. Lumovi’s audit log records them as yours, through the assistant, with your answer: who approved, how long it waited, your note, or that it was made without asking. On a server, each of your open pages gets the line, and the server’s log records it too. The AI assistants page’s Activity tab lists only these. See Approving changes.Changing things safely
The guard rails around every change.
Actions by kind
Everything you can do to each kind, and the options.