MyJackfruit

Help
Browse topics · Getting ready to publish

Getting ready to publish

← Back to What should I check before I say yes to going live?

What happens when my AI asks if my app should go live?

Checked against GilbApp d529620.

Your AI is told to say it becomes public, the 2-site limit and where to ask for more; it needs your yes to go live.

Deeper

Also asked:

How long should people stay signed in to my app? You choose, from 5 minutes up to 14 days; it is 14 days if you do not choose, and each renewal starts the time again. Shorter is safer when people share a computer or phone; longer means they sign in less often.

My AI never asked if my app should go live. Why? It asks only when it works under GilbPlatform's standards, as an AI coder connected through the connector, and when the last part runs and its checks pass. An AI used outside that setup does not know to ask, and GilbApp has no button that puts an app live.

When it asks. Agent.Coder, the agent that builds apps, is told by its standing instructions to ask when the last part of an app or website built on GilbPlatform runs and its checks pass. An agent is your AI following one written procedure for one kind of work. It asks in the message where it hands the work back to you, and asks if you want the app live now at https://<name>.pages.dev, a web address of its own, where <name> is the name given to your site.

What it tells you in the same question, in short:
- the app becomes public on the internet at that address;
- each person can have 2 sites;
- publishing a site you already hold again does not use a new one;
- for more sites, you write to [email protected].

If you say yes. It puts the app live. If the app signs people in, it first asks how long a person should stay signed in: from 5 minutes up to 14 days, and 14 days if you do not choose; each renewal starts the time again. Shorter is safer when people share a computer or phone; longer means they sign in less often. It does not choose for you. It gives the app a button to sign out, builds the app, puts it live, checks that the address opens and tells you the address. If you want another name in the address, say so in your answer.

If you say no. Nothing goes live. It tells you that the app is not live, and where it runs instead. You can tell it later, in your own words, that you want it live.

The choice is yours: it never publishes without your yes. A yes uses one of your 2 sites, unless it is a site you already hold. If you already hold 2 other sites, publishing is refused; the answer How many sites can I have, and how do I get more? tells what to do.

When it does not ask. Your AI asks only when it works under GilbPlatform's standards: an AI coder, such as Claude Code, Anthropic's AI, connected to GilbPlatform through the connector, the small GilbPlatform program on your computer. An AI used outside that setup does not know to ask. GilbApp has no button that puts an app live.

This answer says what Agent.Coder is told to do. The answer How do I put my app or website live on the internet? walks through the whole way.

This answer is written for a computer screen.

Source: Standards read from GilbPlatform on 13 November 2026: Agent.Coder (AskGoLive: "When the last increment of an app or website built on GilbPlatform runs and its checks pass, ask the person if they want it live now"; the question in the handback message; the four points to say in short; Yes: run Proc_v_i_c_PublishPagesDev; No: say it is not live, and where it runs; never publish without the person's yes; Contextual: read Proc_v_i_c_PublishPagesDev when publishing), Proc_v_i_c_PublishPagesDev (step 1: ask how long, 14 days longest and default, shorter safer on shared devices, longer fewer sign-ins, the AI does not choose; step 2: 300 seconds shortest; step 3: a Sign out button; steps 4-8: build, publish, the address printed, check that it loads), RuleDeployPagesDev (2 sites per person; the limit message). GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): src/publish/records.ts:256, :259, :273-276, :410-416 (2 sites; refusal names [email protected]); src/auth/renewable-sign-in.ts:81, :84 (300 seconds to 14 days). GilbApp 49b1ae53 (https://gilb.com/app/version.json, read 13 November 2026): no publishing control in src. Live help pages: What can I make, and is there something I can't make?; Can my app have its own users who sign in?; How do I make sure I end up with an actual app?