wisp GitHub

Guideswisp Cloud

Publish an app your agent built

Ask Claude Code or Codex for a demo, then send a link: Publish puts it on your wisp Grid while your laptop sleeps.

wisp guidesUpdated · 2 min read
wisp’s My Stuff page: the pricing page demo, marked Public, with Launch

To share a demo your agent built, you usually need hosting: a Vercel or Netlify project, a build, a domain. In wisp, the agent saves the app to My Stuff, and Publish puts it on your wisp Grid at a link anyone can open, no sign-in. Or just ask the agent to publish it.

Try wisp CloudFree during the preview

The manual way

npm i -g vercel
cd /tmp/pricing-demo
vercel login
vercel --prod

That’s an account, a project per demo, and a deploy each time the agent changes it.

With wisp

  1. Sign in to a grid. Use your cloud wisp at grid.trywisp.dev, or sign wisp on your computer in to it from Settings → Cloud.
  2. Have the agent build it. Build a pricing page demo with a monthly/yearly toggle and save it to my stuff. The agent writes a static app (HTML, JS, CSS) and saves the folder; its card in the reply has Launch to try it inside wisp.
  3. Publish. On the app’s ⋯ menu, or its bar while it runs: Publish to grid.trywisp.dev. Or ask: publish it. The link is copied, and the card shows Public.

The link looks like https://pricing-demo--app--you.grid.trywisp.dev/. Anyone with the link opens it without signing in, while your computer or cloud wisp sleeps. Published apps are kept out of search engines.

Change it, keep the link

@Pricing page demo make yearly the default: the agent saves a new version in place, and Update public link puts it at the same address. Unpublish takes it down, as does removing the app from My Stuff. Your grid account page lists everything you published, with Unpublish.

On your own grid

wisp Grid is MIT and in the repo. On your own server, grid.json’s "sites" sets the limits; by default 50 MB per app, 20 apps per person and 10 MB of data per app. See self-host wisp Grid.

Questions

Does whoever opens the link need a wisp account?

No. A published app opens for anyone with the link, without signing in.

Does my computer need to stay on?

No. The app’s files go up to the grid, which serves them while your computer or cloud wisp sleeps.

Can I publish a Next.js or server app?

Not as it is. Published apps are static files (HTML, JS, CSS), optionally with a SQLite database the grid keeps. Build a static export first.

How do I take an app down?

Unpublish on the app in My Stuff, remove it from My Stuff, or Unpublish on your grid account page.

Try it with the lid shut

Sign in with GitHub and give your own cloud wisp a task. Or run wisp on your own computers: same app, MIT.

Try wisp Cloud

or run it on your own computers

macOS · Linux and Windows in beta · Node 20+ · MIT

Runs Claude Code, Codex, Cursor CLI, opencode, Antigravity CLI, Grok Build and Copilot CLI