Describe a module. Watch it get built, checked and previewed.
Write a brief in business terms. The sandbox takes it through a specification you approve, a build by your coding agent behind the platform gates, and a live preview, all on your machine.
MIT licensed. Runs on your machine.From a brief to a running module in four steps.
The sandbox waits for you where it matters. Nothing is built before you approve the specification, and nothing leaves the session before the gates pass.
- 01
Brief
Describe the module in business terms: what it records, who uses it, what needs approval. A planner names the modules it touches and the first specialist.
Screenshot coming soon - 02
Specification you approve
The brief becomes a module specification: data, screens, permissions and endpoints. You read it, edit it and approve it. A later change asks for approval again.
Screenshot coming soon - 03
Build with gates
Your coding agent writes the module in an isolated workspace. Every turn runs the gates (types, tests and security checks) and shows the full diff.
Screenshot coming soon - 04
Live preview
The draft runs inside the real application shell, on its own throwaway database, with real permissions and no access to your data. Ask for changes or deliver it as code.
Screenshot coming soon
Your machine, your agent, your model.
The sandbox brings the workspace, the gates and the preview. You bring the rest.
Node 24 and pnpm 11
And Git. The launcher generates and installs the workspace, with a local embedded database, so there is no server to set up.
Your coding agent or a model key
Claude Code or Codex CLI, signed in the way you already use them, or an API key for the model you prefer. The sandbox ships no model of its own.
It runs on your machine
The sandbox, the workspace and its data stay local. Nothing leaves your machine except the calls to the model you chose.
One command to start.
npx @flowdular/sandboxIt creates or finds a Flowdular workspace, starts the app and serves the sandbox at http://127.0.0.1:4320.