← Content: text, pictures and languages in my app
Who writes the text in my app, and can I change it myself?
Short answer
Agent.Coder writes it from your plan; to change it, tell Kai-Zen the new words, and the app is published again after your go.
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
Also asked:
Can I change the text myself without asking my AI? You can edit the words in the code files on your computer, but a wrong character can stop the app, and the live app changes only when your AI builds and publishes it again. GilbApp has no screen that edits your app's words.
Who writes it. The words on your app's screens, such as headings, button names and messages, are part of its code. Agent.Coder, the agent that writes your app's code, writes them as it builds each part, from what you told Kai-Zen, the planning agent. Where you have your own words, such as your shop's description or your opening hours, give them to Kai-Zen in the chat, and say they must be used as written.
Changing it with your AI. Tell Kai-Zen in your own words what you want changed. Kai-Zen shapes the change with you and asks for your go once. After your go, Agent.Coder builds only that change, has it checked, and publishes the app again under the same name. The answer How do I update my app after it is live? tells more.
Changing it yourself. The words sit in the code files in your project's folder on your computer, and you can open them in a text editor. But they sit among code, a wrong character can stop the app from working, and the live app changes only when it is built and published again, which your AI does. So asking your AI is the safer way. GilbApp has no screen that edits your app's words. GilbApp's chat reaches a folder on your computer only when Claude Code is connected and you choose a code folder (Choose a code folder, then Code in); even then, ask your AI to make the change.
Words you change often, such as prices or opening hours, can be kept elsewhere, for example: your AI coder can build your app to read them from records in a vault of yours, which you then change in GilbApp. Your app already reads its look this way, from a style sheet kept in a vault each time it starts. Everyone who opens your app must be able to read those records, so keep only public words there; see How do I make a vault public? Ask Kai-Zen whether this suits your app.
For words in more than one language, see Can my app be in more than one language?
This answer is written for a computer screen.
Source: Standards: Agent.Coder (builds the parts of the plan; Kai-Zen.Cycle), Agent.Coder.AskGoLive and Proc_v_i_c_PublishPagesDev (build the static folder, then publish; publishing a site you already hold again always works). Live help pages, sentences shared: How do I update my app after it is live? (tell Kai-Zen, one go, Agent.Coder builds only that change and publishes again under the same name); Who decides how my app looks? (the app reads its look from a style sheet in a vault each time it starts; anyone can read it); Where does all the code go, and can I get a copy of it? (project folder; a code folder is reached only with Claude Code connected); How do I make a vault public?. GilbApp 49b1ae53 (https://gilb.com/app/version.json, read 13 November 2026): no control in src that edits an app's code or text.
Checked against GilbApp d529620.