No keys in the chat. No claims we can't back.

This connection can upload your app’s source or import it from a public GitHub repository, download your app’s code into a new folder on your computer when the agent runs there, get the link that opens your app in Tofu’s builder, which you open yourself, run the safety check, deploy it — its build runs any migration step it has — once you have a hosting plan, save and remove your app’s public settings — an address, a feature flag, a key meant to be public — when the agent runs on your computer, but never a hidden value, which you type yourself in Keys & settings, create the app’s managed database, on its own or in the same call as a deploy, which Tofu runs and pays for as part of your plan, read the app’s build and runtime diagnostics, restore a previous deployment, connect, verify, release or withdraw the authorization for a domain you already own, read domain quotes and prepare a dashboard link for you to review a fresh price, agreements and payment when the agent runs on your computer — it cannot place an order or submit payment, read the stored status of domains you bought through Tofu and ask the registrar to send its confirmation email again to the registrant, without seeing your owner details or changing renewal settings, read and add DNS records on a domain you bought through Tofu, and delete one of yours — never its mail (MX) or verification (TXT) records, which stay with you, read your app’s own traffic — the first read for an app that has no counter yet issues its key — and turn that counter on or off, read whether your app is answering its visitors, and turn Tofu’s emails about it on or off, change how your app’s users sign in and how its sign-in email is sent, see who has an account in your app, add a person by email or remove one — which signs them out — choose whether anyone can sign up or only the people you add, and make the app private — only people with a link can open it — or open to everyone again, send a short message to up to ten of your app’s users, from your app’s own email address, get an invite link that lets one person into your private app — you hand the link out yourself, and the first person who opens it gets in for up to 30 days — list the links you made and turn one off again, choose who can open your app — anyone with the link, only people you list by email, or anyone with a code you share, which puts a sign-in page in front of the whole app — add or remove those people, make a new code, sign everyone out, and keep exact paths open for services like webhooks, connect your app to your own Stripe account when the agent runs on your computer — you install Tofu’s app on Stripe’s own page — then create payment links there, pass their payment events to the app or disconnect it, with the money going straight to you and nothing in its reach that moves money out of your account, set up email your app sends from its own address, pause it, give it a new key or remove it, when the agent runs on your computer — Tofu writes the app’s sending key into its settings, and nothing is sent until the app sends email itself, connect your app to Tofu AI or disconnect it, when the agent runs on your computer — Tofu makes the app its own key, which spends your account’s AI balance up to a monthly limit you can change, and writes it into the app’s settings without the agent ever seeing it, see your sandboxes and choose what model each one’s agent runs on — Tofu AI, which spends your account’s AI balance, or your own endpoint — and which agent its chat talks to, putting your own API key into that sandbox, when the agent runs on your computer, make your sandboxes, wake them, put them to sleep or delete them — which ends everything in one for good — and run commands in them and talk to their agents, which spends each one’s model budget, when the agent runs on your computer, make a new token for your own code to call a sandbox with, when the agent runs on your computer — it stops the token made before, the connection receives it (Tofu’s own tool on your computer keeps it in a private file, never in the chat), and it keeps working after you remove the connection, make a private test copy of one of your server apps to try a change on, put the version you tested there on the live app, or remove the copy and its database for good, when the agent runs on your computer — the copy takes test payments only, restore an archived database into a new one Tofu runs and pays for as part of your plan, and hand you a short-lived link to download its archive, keep a database Tofu warned you about from being archived for going unused, list your database’s daily backups and ask a person at Tofu to put it back to one, which loses what was saved after it, see which of your app’s database setup steps are done, choose whether Tofu runs them for an app, and mark one as done so it never runs, when the agent runs on your computer, delete an app — which also deletes its managed database, permanently, and the delete itself keeps no copy (a copy Tofu already holds of a running database, such as the archive it was restored from, is untouched) — or just its database; the source you uploaded is kept until you ask Tofu to erase it, send Tofu’s team a problem report you approved word for word, with your app’s status attached, sign in to Tofu, read the account’s id and email address, report the plan and the account’s GitHub state, and turn automatic updates off.