napStar on GitHub

Describe an app. Then go take a nap.

It'll be running by the time you're back — written in a live sandbox you can watch.

Every app is built in its own sandbox, and only you can open it.

You describe it. nap builds it. You wake up to it running.

One turn, start to finish. Everything below happens on a machine that is yours for the length of the project.

  1. 01

    Say it in one sentence

    No stack to choose, no repo to clone, no template to pick. A sentence is the whole setup.

  2. 02

    Then nod off

    It works in a sandbox of its own — reading, writing, running commands, fixing what it broke.

  3. 03

    Wake up to it running

    The preview updates as it goes, so what you come back to is the app, not a diff to review.

It keeps its head while you don't.

The parts that make walking away from a half-built app a reasonable thing to do.

  • A room of its own

    Every project gets its own machine, with its own filesystem and its own git history. Nothing it does can reach anything else, and only you can open its preview.

  • It talks in its sleep

    The transcript is a live event log, not a spinner: every command, every file it touched, every result, in the order it happened.

  • It remembers where you dozed off

    Close the tab and the sandbox is committed and snapshotted. Open it again and you are back where you were.

  • Shake it awake

    Stop a turn mid-thought. What it finished is kept, and the sandbox is left consistent.

  • No sleepwalking

    A real file tree, and the real files behind it. You can read every line it wrote.

Right then. Nap.

A sentence is the whole setup. Everything after that happens in the sandbox.