pdum_aiui

Appearance

@habemus-papadum/create-aiui ​

Scaffold a fresh SolidJS app pre-wired for the aiui loop — a Claude Code session with a custom channel, a shared agent+human browser, and the web intent tool floating over your page.

sh
pnpm create @habemus-papadum/aiui@latest my-app   # or: npm create @habemus-papadum/aiui@latest my-app
cd my-app
pnpm install
npx aiui claude   # terminal 1 — Claude Code with the aiui channel + session browser
pnpm dev       # terminal 2 — the app (Vite + the intent tool)
npx aiui open http://localhost:5173

Use the @latest tag: pnpm create runs through a dlx cache that can otherwise reuse a previously-resolved (older) scaffolder. And if you need a release published within the last day, pin it exactly (…/aiui@0.9.0 my-app) — pnpm's minimum-release-age gate silently holds back very fresh versions, even under @latest. Either way the version matters: the scaffolder pins the app's aiui dependencies to its own release line, so an old scaffolder gives you old @habemus-papadum/* packages.

The scaffolded app opens on a banner that explains itself: the page is alive, arm the ✳ aiui overlay and start talking about the app you want. Its starter content — a Maurer rose driven by two sliders — is scenery built to be rebuilt, but its shape is the frontend-for-agents methodology in miniature:

  • durable roots (src/model/store.ts) — durableSignal() interaction state that survives hot edits;
  • a disposable cell graph + agent tools (src/model/graph.ts) — Observable-style dataflow over the roots, built by hotCellGraph() and rebuilt on every hot edit, with the app's operations exposed as tools;
  • an .envrc (direnv), a .gitignore, a CLAUDE.md with the agent's ground rules, and its own git repo so agent churn is versioned in the sandbox and nowhere else.

Re-running the command on an existing scaffold continues it (tops up node_modules, reprints the loop) — it never overwrites your or the agent's changes. Anything else at the target path is refused.

This is the only starter aiui ships. (An older aiui demo subcommand scaffolded a second, throwaway playground; it was removed in favour of one template that people actually build on.)

Advanced pieces the starter deliberately omits — the modal interaction kit (@habemus-papadum/aiui-viz/modal), Web Worker cells, the Observable Plot and Mosaic bridges — are shown in the repo's demos/gallery reference notebooks.

Development notes ​

  • The template lives in templates/app and ships in the published tarball (files). Dot-files are shipped undotted (gitignore, envrc) because npm strips dot-paths from tarballs; the scaffolder restores them.
  • __APP_NAME__ and __AIUI_VERSION_RANGE__ in the template's package.json are resolved at scaffold time (release builds pin ^X.Y.Z; dev builds fall back to latest).
  • pnpm typecheck checks the template's source too (tsconfig.template.json, resolving @habemus-papadum/* through the workspace) — template code that doesn't compile fails CI here, not in a user's freshly scaffolded app.