MyJackfruit

Help
Browse topics · Last checks before going live (Testing)

Last checks before going live (Testing)

← Back to How do I update my app after it is live?

How do I check my app once it is live?

Short answer

Open its address, do what the change was for as a user would, and tell Kai-Zen what is wrong until you approve.

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

When Kai-Zen asks. When a change goes live, Kai-Zen, the planning agent, asks you to check it live, and fixes what you send back, puts it live again with your yes, and asks again, until you approve. Your AI has already checked that the address opens; what it cannot judge for you is whether the change does what you wanted, where people use it. Your app is live at https://<name>.pages.dev, where <name> is the name given to your site.

What to look at. You could check, in this order:
- The change itself. Open the address and do what the change was for, the way the people your app is for would: the new button, the fixed fault, the new screen.
- What was there before. Use the main things your app does once more, and see that they still work.
- Signing in and out, if your app signs people in: sign in, and press its button to sign out.
- Your phone. Open the address in the web browser on your phone too.

What to send back. Answer Kai-Zen where it asked you. If something is wrong, say where it happened, what you expected, what happened instead, and the exact words of any message on the screen; the answer How do I tell my AI about a fault so it can fix it? shows how. If it does what was agreed but you want it different, say that it is a change; see How do I change the product while a project runs? If everything is right, say so: that is your approval. Kai-Zen then has each goal the step aims at measured, by an agent other than the one that built it; a goal here is a goal for how well your app must do something. An agent is your AI following one written procedure, its standing instructions, for one kind of work.

The way a new user sees it. You are already signed in and know the app. Open the address in a private window, a separate browser window meant for browsing without your usual saved information; Google says Chrome's Incognito window doesn’t automatically sign you into your Google Account or other websites (https://support.google.com/chrome/answer/95464, read 13 November 2026), which we have not tried with a live app: in Chrome, choose More, then New Incognito window; in Safari on a Mac, choose File and then New Private Window. To check sign-in as someone else, sign in there with a second e-mail address you can open; each address makes its own account, and an account made this way stays until you ask for it to be deleted: GilbApp has no delete button for an account, and the answer How do I delete my account? shows the e-mail to write. The answer How do I test my app the way a new user would, on other phones and browsers? tells more.

If you still see the old version, or the page does not open, see My live site does not open, shows a blank page or an old version. What now?

Should I check again later? Yes, after each update: Kai-Zen asks you again each time a change goes live. A pass on the builder's own computer does not count as working in production, the live system people use; the live check is where it counts. Between updates, GilbApp has no screen that shows your site or tells you when it stops working, so you could open it yourself now and then; the answer How do I know if my live app stops working, and see the errors my users get? tells more. If your site does not open after it was published, write to [email protected] with the address and what your AI showed you.

This answer is written for a computer screen.

Source: Standards read from GilbPlatform on 13 November 2026: Kai-Zen.HumanCheck (Ask: Ask the requester to check it live.; Fix: Fix what they send back, put it live again, and ask again, until they approve.), Kai-Zen.Cycle (Human; Measure: by an agent other than the builder), Proc_v_i_c_PublishPagesDev (step 3: a Sign out button; step 8: check that https://<name>.pages.dev loads), Agent.Coder (Solutions: a pass on your own computer is not production). GilbApp 49b1ae53 (https://gilb.com/app/version.json, read 13 November 2026): no list or state of published sites in src. Google Chrome Help, Browse in Incognito mode (https://support.google.com/chrome/answer/95464, read 13 November 2026). Safari User Guide for Mac, Browse privately (https://support.apple.com/guide/safari/browse-privately-ibrw1069/mac, read 13 November 2026). Live help pages, sentences shared: What should I do in the first week after my app is live?; How does Kai-Zen put a change live?; How do I tell my AI about a fault so it can fix it?; How do I change the product while a project runs?; Who tests my app, and why does my AI write tests?; How do I put my app or website live on the internet?; Which e-mail address should I use, and can I change it later?

Checked against GilbApp d529620.