MyJackfruit

Help
Browse topics · For developers

For developers

← For developers

How do I publish my app from the terminal?

Short answer

Get connector 0.5.13 or newer, build your folder, try the publish command with --dry-run, run it without, and open the address.

Before you start

A GilbPlatform account, Node.js 18 or newer, and the connector set up through ▸ CONNECT AI in GilbApp, so it is signed in.

Words used here (3)
GilbPlatform
GilbPlatform is the service that keeps people's and organisations' data in vaults, each at its own web address.
GilbApp
GilbApp is the app, opened in a web browser at https://gilb.com/app, where you open, fill and share your vaults.
project
A project is work to bring about a change you want, such as a new app or a better way of doing something.
Steps
  1. Get the newest connector.

    In Terminal, the window where you type commands, paste the line under step 1 of ▸ CONNECT AI in GilbApp and press Return:
    curl -fsSL 'https://gilb.com/app/gilb-connector.mjs' -o ~/.gilb-connector.mjs

    More about this

    The connector is GilbPlatform's small program on your computer; the line puts it at ~/.gilb-connector.mjs, and it runs on Node.js, the program that runs JavaScript on your computer, version 18 or newer. These lines are for macOS and Linux, where ~ is your home folder; this answer has not been checked on Windows. Publishing needs connector 0.5.13 or newer; on 13 November 2026 GilbApp gives 0.6.1. The answer How do I update Claude Code and the connector? shows how to see which one you have.

  2. Build your app into one folder.

    Build it the way your project does, into one folder of plain files, such as dist, with index.html at its top.

    More about this

    If your app signs people in, first choose how long they stay signed in and give it a button to sign out; the answer How do I choose how long people stay signed in to my app? shows how. The folder may hold at most 2000 files and 5 MB in all. A symlink, a link to another file, is refused; a .DS_Store file is left out. Only these kinds of file are taken: html, css, js, mjs, json, map, txt, xml, webmanifest, svg, png, jpg, jpeg, gif, webp, avif, ico, woff, woff2, ttf, otf, mp3, mp4, webm and pdf. A file or folder named _headers, _redirects, _worker.js, _routes.json or functions is refused: no code of yours runs on a server there. A file that looks like it holds a secret key, such as a Stripe key or a private key block, is refused.

  3. Try the publish command with --dry-run.

    Run this line in Terminal, with your folder in place of <built folder> and the name you want in place of <name>:
    node ~/.gilb-connector.mjs publish --dir <built folder> --name <name> --dry-run

    More about this

    It sends nothing over the network. It checks the name and the folder on your computer, prints dry-run (no network call), then the name, the address https://<name>.pages.dev, the kind, the number of files and the bytes, and each file it skipped. The name may use only small letters a to z, digits and hyphens, 3 to 40 characters, with no hyphen at the start or end and no two in a row. The dry run does not check the kinds of file, the secret scan, reserved names or whether the name is free: those come when you publish.

  4. Run the publish command.

    Run the same line without --dry-run; for a website that signs no one in, add --kind website:
    node ~/.gilb-connector.mjs publish --dir <built folder> --name <name>

    More about this

    The kind is app unless you add --kind website. Only an app's address may sign people in and read and write their vaults; a website's cannot. A name keeps its kind: an app cannot later become a website. The command signs in with the connector's own sign-in, your AI acting for you; --as me signs in as this computer instead, if it was added to your account, and --profile <name> picks another of the connector's sign-ins on this computer. For an app, the connector makes a key and keeps it in ~/.gilb-connector/publish/<name>.jwk; keep that file. Published again from another computer, the app gets a new key there, which takes the old key's place. The site is yours, also when your AI publishes it.

  5. Open the address it prints.

    When the site is live, the command prints https://<name>.pages.dev and then t:SiteStateLive; open that address in your browser.

    More about this

    An app's address may sign people in on its own: no request to the platform owner is needed. If the command prints anything else, nothing was put live; the answer Why was my publish refused, and what do I do? tells what each refusal means. If the site does not open after it was published, write to [email protected] with the address and what the command printed.

Deeper

Also asked:

What is the connector, and which version do I need? The connector is the small GilbPlatform program on your computer, ~/.gilb-connector.mjs, that lets Claude Code reach your vaults and publishes your app. Publishing needs connector 0.5.13 or newer; on 14 November 2026 GilbApp gives 0.6.1.

Can I publish from a build pipeline, such as GitHub Actions? This help shows no way: publishing runs the connector signed in as you or as your connected AI, and an app's own token is refused with An app cannot publish for its user. If you need it, write to [email protected].

Publishing puts your built app or website on the internet at https://<name>.pages.dev, an address of its own, where <name> is the name you give it, and anyone can open it. pages.dev is an address service run by Cloudflare, a web company. Only pages.dev addresses are offered; an address of your own is not. The name must be free on all of pages.dev, not only on GilbPlatform, and some names are kept back, such as names GilbPlatform uses and well-known brands.

Each person can have 2 sites. Publishing a site you already hold again works and uses no new site: that is how you put a changed version live. The answers How many sites can I have, and how do I get more? and How do I update my app after it is live? tell more.

What a published site may do. GilbPlatform serves every site with fixed rules that you cannot change: its pages may fetch data only from their own address and from GilbPlatform's own addresses, https://*.gilb.com; scripts come only from the site's own files, so a script written inside a page does not run; pictures come only from those places or from data: and blob: addresses. The site gets no camera, microphone or location, and no other site can show it inside its own page. So a published site cannot call an outside service, such as a payment service, from the browser.

The command ends with an exit code, a number a script can read: 0 when the site is live or the dry run is done, 2 when it refused on your computer, 3 when GilbPlatform refused, 4 when the upload service refused, and 5 when the network failed.

If you build with an AI that works under GilbPlatform's standards, connected through the connector, its standards tell it to ask before it publishes and then to run these steps for you; the answer What happens when my AI asks if my app should go live? tells more. The answer How do I put my app or website live on the internet? is the same way in plain words.

This answer is written for a computer screen.

Source: Connector 0.6.1, served at https://gilb.com/app/gilb-connector.mjs, read 13 November 2026: line 12 (Node 18 or newer), :3570-3571 (2000 files, 5 MiB), :3576-3582 (usage: publish --dir --name [--kind app|website] [--dry-run] [--as ai|me] [--profile]; --kind defaults to app; --dry-run checks and lists what would be sent, and does not call the network), :3697-3706 (name: 3 to 40, a to z, digits, hyphens, no hyphen at the ends or two in a row), :3714-3790 (symlink refused, .DS_Store skipped, index.html at the root), :3797-3809 and :3900-3922 (the app key kept in the connector's folder as publish/<name>.jwk, mode 0600), :4091-4100 (dry-run output), :4199-4267 (publish: an app key for kind app, ticket, upload, prints the address and t:SiteStateLive), :4270-4306 (exit codes 0, 2, 3, 4, 5). GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): src/publish/site-name.ts:12-13, :16, :29, :45-64 (name rules, reserved and brand names), :68 (the one address); src/publish/ticket.ts:20, :31 (2000 files, 5 MB); src/publish/records.ts:256 (2 sites per person), :390 (a name keeps its kind); src/routes/publish.ts:460-485 (only an app's origin is registered and approved; a website's admittedOrigin is null); src/publish/admission.ts:1-37 (a re-publish with a different key replaces the old approval); workers/publish-ingest/src/checks.ts:11-21 (file kinds; _headers, _redirects, _worker.js, _routes.json, functions), :30-40 and :155-158 (secret-looking files refused), :165-172 (the headers every site gets: script-src 'self'; img-src 'self' data: blob: https://*.gilb.com; connect-src 'self' https://*.gilb.com; Permissions-Policy camera=(), microphone=(), geolocation=(); X-Frame-Options DENY; frame-ancestors 'none'). Standards read from GilbPlatform on 13 November 2026: Proc_v_i_c_PublishPagesDev (connector 0.5.13 or later from step 1 of Connect AI; steps 4-9; the app's key in the connector's folder; the platform admits the origin on its own), Standard Rule_Code_deployment (RuleDeployPagesDev: only pages.dev; the name free across all of Cloudflare; 2 sites). GilbApp 49b1ae53 (https://gilb.com/app/version.json, read 13 November 2026): src/components/VaultAccessManager.tsx (▸ Connect AI, shown in capitals). Live help pages, sentences shared: How do I put my app or website live on the internet?; How do I update my app after it is live?; How many sites can I have, and how do I get more?; How do I update Claude Code and the connector? https://gilb.com/app/gilb-connector.mjs CONNECTOR_VERSION 0.6.1 (read 14 November 2026); the live answer How do I update Claude Code and the connector?

Checked against GilbApp d529620.