runs and edits your live production code
stardance runs the app you actually ship, and the agent edits the real files in your repo. on its own git branch, so main stays yours until you say so.
stardance is a desktop app for building with ai coding agents on your real codebase. leave a comment on any element and claude code or grok build changes the actual files, on its own git branch.
requires your own subscription to claude code or grok build. it's not included with stardance.
your app, running. in the middle of the window, not a screenshot.an agent on its own branch. you see it work, then review the diff.
design surface and source of truth are the same thing: the app you run. nothing to rebuild, nothing to translate back.
agents edit files in your git repo on their own branch. normal commits, normal diffs, normal merges.
node or python backends are auto-detected and run beside the frontend, so changes are tested against the whole stack.
six things stardance does in one window, so you stop hopping between a browser, a terminal, a git client and a design tool.
stardance runs the app you actually ship, and the agent edits the real files in your repo. on its own git branch, so main stays yours until you say so.
click anything in the running app and leave a note. the comment is the spec: the agent knows which element you meant.
one agent per git branch, all working in parallel. when they finish, the ai helps resolve merge conflicts.
branches, commits, merges and pushes without leaving the window. every agent change is a real, reviewable commit.
set up the processes your project needs, each with a real terminal. node or python backends are auto-detected and run next to the frontend.
describe a new screen and it shows up as a prototype next to your running app. check it at phone, tablet and desktop sizes before you commit to it.
node or python (django, fastapi, flask) backends start next to your frontend, each with its own real terminal.
export your running app as a single .html file. clients comment in any browser and their notes come back as pins.
when parallel branches collide, an agent works the conflict out and shows its steps.
flip the live preview between device sizes to see how your app really lays out.
work with claude code or grok build, choosing the model per request.
open any file in a proper code editor right beside the live app when you want to take the wheel.
a parent and child branch tree with rebase, merge and optional push to github.
push the branch to your own github remote when you are ready. your repo, your history.
keep your agent. stardance gives it eyes on the running app instead of a wall of diffs.
point at what's wrong and say what you want. the code changes underneath, in a repo you own.
ship faster on your own product: parallel agents on separate branches while you keep building.
polish the real interface instead of a mockup, then prototype the next idea next to it.
send clients a review file, collect their comments as pins, and turn them into branches.
a desktop app for building with ai coding agents on your real codebase. you run your app inside it, click any element to leave a comment, and claude code or grok build edits the actual code on its own git branch, with your backend running in the same place.
a subscription to a supported ai coding cli: claude code or grok build. it is required and it is not included with stardance. stardance drives the cli you already pay for.
you also need a project on your machine (or one from github) to point it at.
you can sign up for the free beta right now. it doesn't cost anything to get on the list, and we'll email you about the beta. remember that your own claude code or grok build subscription is separate.
you do. stardance edits your real repo, on its own git branch, as normal commits. there is no proprietary format and nothing to export back out. review the diff, merge it, or throw the branch away.
stardance runs your frontend and auto-detects node or python backends (django, fastapi and flask included), starting them next to the frontend with a real terminal each. if your setup is different you can configure the processes by hand.
the design surface is your actual running app, not a mockup or a copy of it. you point at the real thing, an agent changes the real code on a branch, and several agents can work at once on separate branches. there's nothing to copy back into your repo.
every change lands on its own git branch, never straight on main, and shows up as a diff you can read. you decide what merges.
drop your email and we'll let you know about the beta. tell us what you build with and we'll keep that in mind.