My AI changed things I did not ask for. What now?
Short answer
Ask Kai-Zen what changed and why, then ask your AI to undo what you do not want; nothing goes live without your yes.
Before you start
Words used here (1)
- Kai-Zen
- Kai-Zen is the planning agent: it finds out what you want, chooses the way, hands the work to other agents and reports back.
Deeper
See what changed. In GilbApp's chat, with Claude Code connected and Code in switched on, the line Changed in under your AI's answer counts the files added, changed and removed, and Files lists them. In a terminal, the window where you type commands, or for an earlier day, ask your AI: what did you change, and why? The answer How do I see what changed, and who changed it? shows how.
Why it may have happened. For a change you name, Kai-Zen, the planning agent, has only that change built; anything else it sees, it notes and does not do. Some things still come without your asking:
Choices made for you. What only you could have told it but it had to choose, Kai-Zen writes down as an assumption, a choice it made for you that you can change, and lists every assumption for your one approval at the end.
What every app gets. The first step sets up a ready-made core app with a sign-in, and Agent.Coder, the agent that writes your app's code, makes the pictures the app needs, such as a logo, itself.
Ask which it was. An agent is your AI following one written procedure, its standing instructions, for one kind of work.
Say what you want instead, in the same chat, for example: You changed the colours of the start page, and I did not ask for that. Put them back as they were. If it was an assumption, reply with what you want; Kai-Zen changes it and asks once more. Something that should only work a little differently is fixed in a new change. When a whole approach was wrong, or a change broke something else, ask your AI to undo it: Agent.Coder adds a new version that reverses the change; nothing is deleted, and the tests run again. Undoing changes the code only; it does not take back what was written to a vault. The answer Can I undo what I've built, or go back to an earlier version? says more.
Nothing goes live by itself. Some acts Kai-Zen never does without you: putting work live (open to the people who will use it), ending a record or deleting a vault, giving access to a vault, spending more than the budget, and changing a goal you set. Once a change is live, it asks you to check it, and fixes what you send back until you approve.
Be asked first. In GilbApp's chat, Approve before each write on the card at the start of a session makes a card ask before each write, the saving of a file, or each command; one not answered in 10 minutes counts as declined. In the fold under an answer that reads such as 12 steps, a line that starts Refused: is an act that did not go through, such as a write outside the folder. In a terminal, Claude Code or Codex may ask to allow a tool or a command before it runs; refuse what you do not want.
In your vault. What an AI connected with ▸ CONNECT AI writes in a vault is written as its AI vault, a small vault that stands for that AI; what an AI writes from GilbApp's chat is written as the person who uses it. GilbApp shows no earlier value of a field; the answer How do I see a record as it was before (its history)? says what you can see.
If it keeps doing what you did not ask, see My AI does not do what I ask. What now?
This answer is written for a computer screen.
Source: Standards: Kai-Zen.Update (Build: Build only this change. Note anything else you see; do not do it), Kai-Zen.AskRules (Assume, Stop, EndApproval), Kai-Zen.HumanCheck (Ask, Fix), Proc_v_Rollback (only when the person asks; wrong approach, or a change broke something unrelated; not for adjusted behaviour; revert, nothing deleted; tests run again), Agent.Coder (GilbStack 7a: images). GilbApp 49b1ae53 (https://gilb.com/app/version.json, read 13 November 2026): src/components/agent/CodeFolderParts.tsx:49 (Refused:), :57 (Changed in), :81-96 (Approve before each write), :161-183 (Files). Claude Code bridge (https://gilb.com/app/claude-code-bridge.mjs, read 13 November 2026: a write or command question not answered in 10 minutes is declined). Live answers, sentences shared: Can I trust what the AI suggests and builds?; How do I see what changed, and who changed it? (who writes as whom; Refused:); How do I change the product while a project runs?; Can I undo what I've built, or go back to an earlier version?; How do I know what my AI is working on right now, and whether it is stuck? (10 minutes); How do I see a record as it was before (its history)?; My AI does not do what I ask. What now?.
Checked against GilbApp d529620.