Docs

The operating manual for a factory that writes real files.

CodeLoom is a hosted studio: you describe software, Cursor writes a Vite + React + TypeScript app into a project you own, then this host installs, builds, and starts a local preview. These pages are how that loop actually works — not a marketing paraphrase.

Describe

Homepage composer

Build

Staged Cursor agent

Preview

Vite on this host

Export

Zip of the tree

Why this exists

One project is the source of truth.

The working loop

There is no stub fallback. Follow-up messages edit the same workspace the file tree, Monaco, and iframe already show. If preview is already running, the studio reuses it instead of restarting Vite on every tab. Checkpoints let you rewind a bad follow-up.

Studio panes

  • Agent chat
  • File tree
  • Monaco
  • Live iframe

In the product

What you actually get.

Composer

Enter sends. Shift+Enter is a new line. Suggestion chips fill the prompt. Signed-out users keep the idea on this device until sign-in creates the project.

Staged builds

The agent lands a shell, then routes, then screens. You watch stages instead of waiting on a silent job.

Preview

A Vite process on localhost behind a proxy. Restart only when you ask (?restart=1). Home is required on the VPS so npm/node resolve.

Attach a file

Mention @path/to/file in chat so the agent reads that file instead of guessing.

Secrets

Named env-style keys, ciphertext at rest, never pasted into the transcript. Put values in the studio Secrets UI.

Publish

Opt-in card on /community. Templates are separate: they are briefs that start the same Cursor pipeline.

How

A path you can follow without a call.

  1. 01

    Sign up

    Email, Google, or GitHub when those keys are on the host.

  2. 02

    Send a prompt

    Who, job, first screen, what done looks like. Skip the tech shopping list unless you care.

  3. 03

    Wait for preview

    Install + Vite. Open the iframe. Click the empty states.

  4. 04

    Steer, restore, export

    Follow-ups, checkpoints, zip. Billing is /pricing. Usage is /dashboard/usage.

Deep cut

The rest of the page — not a teaser.

Dashboard

/dashboard is the studio home: search, rename, duplicate, export, publish, open. /dashboard/usage is the 14-day chart and monthly cap.

Settings

/settings updates name and password and can delete the account.

Models

CodeLoom is the default. CodeLoom Max is the deeper planner. Both write into the same project files.

Templates

Each card saves a prepared brief and starts a full build — not a static demo.

Admin

/admin is off the public nav. Email allowlist or ADMIN_PASSWORD after sign-in.

Billing

Pro checkout is GET /api/billing/checkout → Whop. The webhook at /api/webhooks/whop sets plan=pro when payment succeeds — register that URL in Whop.

Questions

Ask these before you waste a week.

Is this a mock or a real app?

Real Vite + React + TypeScript files in a project you own. Preview is a running Vite server proxied through the studio iframe.

What happens when I hit the token cap?

The agent stops until the month resets or you upgrade. Pro is $19.99/month via Whop card checkout. The webhook sets your plan to Pro.

Can I take the code?

Yes. Export a zip from the studio. Secrets are not stuffed into the zip as plaintext from the ciphertext store — add env files yourself after export.

Where do files live?

On this host, in a per-project workspace. Export if you want them on your laptop.

Why is preview slow?

First install is npm. After that, reuse should be hundreds of milliseconds. If it hangs, the Vite process likely never started — that was a known host bug and is the thing we fixed.

Can I invite teammates?

Projects are owned by the signed-in account today. Enterprise is the conversation for seats.

Next

Keep going.

Describe it. Watch it become real.

Free is live. Pro is $19.99/month on Whop. The studio, preview, and export are on this host — not a waitlist.