← Changing your mind while building
Can I try an idea on the side without changing the main app?
Short answer
Yes: tell your AI it is a trial, to build on a branch, a side copy of the code, and not to put it live.
Deeper
Agent.Coder, the agent that writes your app's code, keeps the code with Git, the program programmers use to keep versions of their code. An agent is your AI following one written procedure, its standing instructions, for one kind of work. Its rules say all work is done on a branch, a side line of the code with its own saved versions. The main line of the code gets that work only when it is merged in, that is, joined into it. Work that must not go live yet is not merged: its branch is kept, with a note saying why.
So, to try an idea, tell Kai-Zen, the planning agent, or your AI in Terminal, the window where you type commands, in your own words that it is a trial: build it on its own branch, show it to me, and do not merge it or put it live. The rules put all work on a branch and keep work that must not go live yet out of the main line, so the main code stays as it is until you agree to bring the trial in. The standards have no separate trial mode: ask in your own words, and check afterwards what your AI did. If you like the result, say so, and it is brought in as a change; if not, the rules still keep the branch: work that is not brought in is parked, pushed to the GitHub copy of your code with a note saying why. The rules do not describe throwing a branch away. The answer How do I change the product while a project runs? shows how a change is shaped, built, checked and put live.
How you see a trial. Agent.Coder hands back a piece that passed its tests, the checks that show it works, with an address on your own computer to open it in the browser; that address works only on your computer. Kai-Zen never puts anything live without your go.
Kai-Zen also tries ideas itself. When it is not sure which tool or way of building is best, a step may first run a quick trial that only measures the options, before anything is chosen. Each step is a small round, so a step that did not work out can be thrown away; the answer How do I decide to keep or throw away a step's result? tells more.
A very different idea can be its own project. A new project gets its own vault, and one vault holds one project; the answer How do I start my project over? shows how to ask for a new one.
Codex, OpenAI's AI for writing code, can also start in a separate copy of the project, a Git worktree, if you start it with its --worktree setting; OpenAI describes it as Start in a new managed Git worktree. (https://learn.chatgpt.com/docs/developer-commands?surface=cli, read 13 November 2026).
GilbApp has no control for branches or trials. GilbApp's chat reaches a folder on your computer only when Claude Code, Anthropic's AI that you run in Terminal, the window where you type commands, is connected to it and a code folder is switched on (Choose a code folder, then Code in); otherwise code kept there needs Claude Code in Terminal.
This answer is written for a computer screen.
Source: Standards: Rule_Code_git-workflow (RuleGitworkBranchStrategy, RuleGitlandPatchId: land or park, RuleGitlandLandingIsShipping: work that must not go live yet does not land), Proc_v_i_c_GitWorkflow, Proc_v_i_c_Handback (hand back with an address on the person's computer), Kai-Zen.ValueDeliveryStepRules (NoPrebaked: a spike only measures; Small), Kai-Zen.VTTRules.Act, Kai-Zen.ProjectRules.Vault, Kai-Zen.GoLive. OpenAI, read 13 November 2026: https://learn.chatgpt.com/docs/developer-commands?surface=cli (--worktree). GilbApp 49b1ae53 (https://gilb.com/app/version.json, read 13 November 2026): no branch or trial control in src. Live help pages, sentences shared: Will I understand what the AI built, and can I learn to code along the way?; How do I change the product while a project runs?; Which technology will my app be built with? (a quick trial that only measures); How do I start my project over?.
Checked against GilbApp d529620.