MyJackfruit

Help
Browse topics · Keeping it running

Keeping it running

← Keeping it running

Does my app need looking after when nobody changes it?

Short answer

GilbPlatform's code does not change its files until you publish again, but nothing promises it keeps working after GilbPlatform changes; check it now and then.

Before you start

Words used here (1)
GilbPlatform
GilbPlatform is the service that keeps people's and organisations' data in vaults, each at its own web address.
Deeper

Also asked:

Does my live app get security updates, and who does them? Nobody updates your live app's code by itself: only you, through your AI, can put a new version live. When it works on your app, Agent.Coder checks its packages for known security holes; a fix goes live only with your yes.

What stays the same. Your app is live at https://<name>.pages.dev, where <name> is the name given to your site. pages.dev is an address service run by Cloudflare, a web company. As far as GilbPlatform's code shows, nothing changes its files until you publish again; nothing published promises that. Cloudflare says: "Every time you deploy an asset to Pages, the asset remains cached on the Cloudflare CDN until your next deployment." (https://developers.cloudflare.com/pages/configuration/serving-pages/, read 13 November 2026). There, to deploy means to publish, an asset is one of your app's files, and the CDN is Cloudflare's network of computers that hands out those files. A new version goes live only when it is published again, and your AI may not put it live without your yes. Your live app keeps running at its address if your computer breaks: it is published, not served from your computer.

What can still change. Your app's data and sign-in come from GilbPlatform, so they work only while GilbPlatform answers; the answer What happens to my app if a connected service stops working? says more. GilbPlatform itself is changed by its makers. MyJackfruit, the public brand at myjackfruit.com, says in its Terms that features may change, and the service may be unavailable at times; it is given as it is, without promises about availability (https://myjackfruit.com/terms/, read 13 November 2026). If early access or the service ends, MyJackfruit gives at least 30 days' notice to export your data (https://myjackfruit.com/terms/). Nothing published promises that your app keeps working after a GilbPlatform change. If something stops working after a GilbPlatform change, write to [email protected].

Security updates. Your app may be built from your own code and from ready-made parts that other people wrote, called packages. Nobody updates your live app's code by itself: only you, through your AI, can put a new version live at its address. Your AI updates it when you ask, or when it works on your app. The rules of Agent.Coder, the agent that writes your app's code, say:
- Before it proposes a change to the code, it runs npm audit, a check for known security holes in the packages, and fixes the serious ones first. If a serious hole has no fix yet, it tells you the risk in plain words.
- When it makes a new copy of your code on GitHub, a website where programmers keep and share code, it switches on Dependabot, a GitHub tool that proposes package updates every week. GitHub calls them automated pull requests that keep your dependencies updated (https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates, read 13 November 2026); a pull request is a proposed change to the code. Agent.Coder's rules tell it to review those proposals and not let them pile up: it merges a small update when the checks pass, and for a big version change it first reads what changed and tests it by hand. It does this when it works on your project.
None of this changes your live app until the new version is published, with your yes. The answer Do I need a GitHub account? tells about the GitHub copy.

What you could do. This is advice, not a rule. You could open your app now and then and do what a new person would do; read what your users tell you; and, from time to time, ask your AI to check your app's packages for security holes and update them, then check the new version and say yes to putting it live. If you can, publish updates from the same computer. The answers How do I know if my live app stops working, and see the errors my users get?, How often should I update my app? and How do I update my app after it is live? tell more.

This answer is written for a computer screen.

Source: Cloudflare, https://developers.cloudflare.com/pages/configuration/serving-pages/ (read 13 November 2026): a deployed asset stays cached until the next deployment. GitHub, https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates (read 13 November 2026). MyJackfruit Terms, https://myjackfruit.com/terms/ (last updated 11 November 2026, read 13 November 2026). Standards read from GilbPlatform on 13 November 2026: Proc_v_DependencyManagement (npm audit before every PR, critical or high fixed first; no fix yet: tell the person the risk in plain language; Dependabot weekly in a new repo; Agent.Coder reviews and merges its PRs), Agent.Coder (Contextual: dependency-update PRs; AskGoLive: never publish without the person's yes), Kai-Zen.GoLive. GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): src/routes/publish.ts:390 (only the account that holds a site name can publish to it). Live help pages, sentences shared: What happens to my app if a connected service stops working?; What are the early access terms? (30 days' notice); Is my code safe if my computer breaks? (runs if the computer breaks); How do I update my app after it is live?; Do I need a GitHub account?

Checked against GilbApp d529620.