App Builder And Web Hosting

App Builder lets an agent build a website or app for you, preview it on your machine, and publish it to the web. Describe what you want in Chat, review the result, and publish when it’s ready.

You can build on This Mac, another linked machine, or a Managed Cloud Agent. Where the code lives and where the finished site is hosted are separate choices.

Build an app from Chat

1. Open Chat and ask for the app you want, such as a website, dashboard, game, or clone.
2. Review the plan and approve the App workspace. HivemindOS creates a project folder for this conversation.
3. Watch the app card beside the conversation. It says Building while the agent works, then Running · Open app when the app is ready.
4. Press the preview button to open the app. Keep chatting to change it; later requests edit the same project.

Before an app is marked ready, HivemindOS opens it and tries every control. Buttons that do nothing, or a game that doesn’t actually play, are sent back to the agent to fix. If a build can’t finish, or you press Stop, the card says Needs attention with the reason, and you can ask the agent to continue.

The workspace opens beside the chat with three tabs:

• App — the live preview, with desktop, tablet, and phone widths.
• Code — the project files (read-only; the agent makes edits).
• Console — a shell on the machine that holds the project.

Simple HTML, CSS, JavaScript, and game requests use a plain starter with nothing to install. Framework and full-stack requests use a Next.js starter.

Start from a template

In the composer, open the plus menu, choose Templates, then Websites, and pick a starter. HivemindOS copies it into a project for this conversation, and the agent asks what you’d like to change.

The first website starter is Scroll World, an MIT-licensed landing-page engine that previews without any accounts or outside services.

Where your project can live

Your own machine. Choose a folder on This Mac or another linked machine. Files stay on that machine. You can also adopt an existing static or Next.js folder. The agent can’t pick a folder on its own, and installing packages, starting, and stopping each need your confirmation, so creating files never runs downloaded code by itself. Previews are only reachable from that machine.

A Managed Cloud Agent. The project lives on that agent’s workspace. You can create, list, read, start, stop, and delete projects. Deleting permanently removes the project files. File editing and in-dashboard preview aren’t available for managed projects yet. A managed agent set up before these controls existed must be reconfigured once first. Owning a managed agent doesn’t include hosting; publishing is a separate purchase.

If a linked machine needs an update to run App Builder, Preview updates it and retries automatically.

Share a test build for 60 minutes

Need someone else to see a work in progress? Press Share in the workspace. After you confirm, HivemindOS creates a free Cloudflare preview on a workers.dev address. It expires after 60 minutes unless you claim the temporary Cloudflare account. This needs Wrangler 4.102 or newer.

Treat the claim link like a password: it grants ownership of that account. This preview is not HivemindOS hosting and doesn’t use a HivemindOS address.

Publish with HivemindOS

You can publish from any machine or managed agent to a stable address such as:

https://example-site-a7k2.build.hivemindos.app

Only plans with available capacity are offered. The Dynamic App plan appears only when the dynamic runtime is available, so you can’t be charged for capacity that isn’t there. Prices are set by HivemindOS servers, not the app. Card and x402 top-ups fund the same hosted-credit balance.

• Static sites suit landing pages, portfolios, documentation, and exports. Framework projects publish their out folder; plain HTML projects publish from the project folder. Limit: 1,000 files, 20 MiB total, 5 MiB per file.
• Dynamic apps run server-side code from one bundled dist/worker.mjs file, with their own isolated database and storage.

Versions and rollback

Each hosted app keeps its version history. You can save a new version without changing the live site, deploy a chosen version, or roll back to an earlier one. Publish saves and deploys in one step. In a Git project, each version records the current commit.

Who can open it

Choose private, workspace (only holders of a workspace access token), link (anyone with a revocable link), or public. You can revoke link access by changing the setting.

Site settings file

A local project links to its hosted site through .hivemindos/hosting.json. It holds only the site ID and optional storage names:

{
  "project_id": "site_example",
  "d1": ["DB"],
  "r2": ["BUCKET"]
}

Environment values are stored encrypted by the hosting service. The app can list their names but never read the values back.

Dynamic App allowance

The Dynamic App plan includes, per 30 days: 10 million requests, 250 million reserved CPU-ms, 1 million storage operations, and 1 GiB of runtime storage. Each request counts the full 25ms execution ceiling against the CPU allowance, even if it finishes faster. When requests or CPU run out, the site returns HTTP 429 until the next period. Storage operations are refused once their allowance runs out, and writes stop at the capacity limit without corrupting existing data.

Renewal

• Turn on auto-renew to renew each 30-day period from hosted credits when your balance is enough.
• Manual renewal opens seven days before the period ends. A period is never charged twice.
• A failed renewal gets a seven-day grace period.
• Expired or unpublished releases can be recovered for 30 days, then they’re deleted.
• Changing between Hosted Site and Pro Site uses a full-price extension: the new plan starts now, your remaining time is kept, and one full 30-day period is added. There are no partial refunds.

If activation fails after a charge, your hosted credits are refunded automatically.

Hosted publishing appears only when the hosting service is available. Building and local previews always work without it.

What stays in your control

• Projects can’t reach outside the folder you chose.
• Package installs never run package install scripts.
• Local previews are reachable only from that machine.
• Nothing is installed, started, published, or deleted without your confirmation.
• Published sites are checked on the server before going live, and dynamic apps only get the storage they declared.

Related

• Managed Cloud Agents
• Wallets And Spending Controls
• Agents, Runtimes, And Chat