noback

Optional: you don't need it, create_app asks for approval by itself the first time you publish. Asks the person for approval without publishing anything (agent is your name, like "Claude Code"). Returns url, code, pollKey and message. Take the person to url yourself: open it in their browser if you can (open on macOS, xdg-open on Linux, start on Windows, or navigate there if you have a browser); if you can't, show them the link in one line in the language of the conversation. Then call connect_status with pollKey and carry on by yourself as soon as it's approved, without asking the person to type anything. Never put pollKey in an app.

Waits (up to 20 seconds) for the person to approve the request that create_app, update_app or connect started, and answers as soon as they do. Returns status: pending (call it again), slow_down (wait a few seconds, then call it again), approved (with token and kind: account or anonymous), denied or expired. The token comes only once: right away call create_app or update_app again with credential: token, and keep sending it on every publish. Never show it to the person or put it in an app.

Publishes a new app from html or zipBase64. The first time you publish, the person approves you once in their browser, with or without a noback account; nothing is needed before. Without credential it doesn't publish: it returns status approval_needed, connect (url, code, pollKey) and next. Then, by yourself: open connect.url in the person's browser (open on macOS, xdg-open on Linux, start on Windows, or navigate there if you have a browser), or if you can't, show them that link in one line in the language of the conversation; call connect_status with pollKey (it waits until they approve; call it again while it says pending); as soon as it says approved, call this tool again with the same content and credential: token. Don't ask the person to type anything. Same checks as validate_app. Once published it returns appId, version, openUrl, message and warnings: tell the person message in the language of the conversation. Keep appId for update_app; don't create another app for changes.

Returns noback's guide for writing apps (in English, as Markdown in markdown): how to make a single-file HTML app whose data is saved and shared (localStorage, window.storage or app.db), what works inside noback and what doesn't, packages, limits and how to publish. Read it once before writing or changing an app for noback. Read-only.

Publishes a new version of an app you published, with the same checks as create_app. Send the credential you got from connect_status (or the editKey of an app published before approvals existed). The first time you publish, the person approves you once in their browser, with or without a noback account; nothing is needed before. Without credential it doesn't publish: it returns status approval_needed, connect (url, code, pollKey) and next. Then, by yourself: open connect.url in the person's browser (open on macOS, xdg-open on Linux, start on Windows, or navigate there if you have a browser), or if you can't, show them that link in one line in the language of the conversation; call connect_status with pollKey (it waits until they approve; call it again while it says pending); as soon as it says approved, call this tool again with the same content and credential: token. Don't ask the person to type anything. The data and the link stay as long as you keep the same app.db collections and fields and the same localStorage keys. Returns openUrl, version, message and warnings.

Checks an app (html or zipBase64) against noback's rules, with the limits of an app without an account, without publishing anything or running its code. Use it before create_app or update_app. Returns { ok, errors, warnings }; each item has a code, a message and a fix. Fix every error before publishing; warnings are suggestions and the app works anyway. Without an account, the app can reach the internet only through the services on noback's list. If warnings include NO_APP_DB with certain: true, the app loses what people enter when the page reloads: save it in localStorage (the warning's prompt says what to change) before publishing. If warnings include STATIC_LIST, the content is written by hand in the page: offer to make it editable from the page, with only the owner writing (the warning's prompt says what to ask for). Read-only.