click your running app. ai agents edit the real code.

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.

the loop

point at it. say it. watch it change.

my-shop10100%Live appExportReading×3The hero now uses the new photo grid,and the cart badge updates live.1. button.order-now“make this pill-shaped and purple”Reading×2Refining design×1Updated Button.tsx: fully rounded, brandpurple, committed on feat/button.Working 0:14 · 412 tokensDone in 0:41Ready to mergefeat/button↑1Button.tsx+3−1MergeRebaseDescribe a change, or ask for a new design…feat/buttonOpus Highorder nowbutton.order-nowbutton.order-nowmake this pill-shaped and purpleTest caseFlagStageSend

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.

real code. real app. no mockup in between.

01

the app is the canvas

design surface and source of truth are the same thing: the app you run. nothing to rebuild, nothing to translate back.

02

the repo is yours

agents edit files in your git repo on their own branch. normal commits, normal diffs, normal merges.

03

the backend is there too

node or python backends are auto-detected and run beside the frontend, so changes are tested against the whole stack.

what it does

ai, code and design, side by side.

six things stardance does in one window, so you stop hopping between a browser, a terminal, a git client and a design tool.

runningLive appstartHero.tsx1export function Hero() {2 return (3 <button− className="btn"+ className="btn-pill"5 >start</button>6 );7}feat/hero↑1
01

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.

get startedbutton.get-startedbutton.get-startedmake this the brand purpleand add a soft glowTest caseFlagStageSendWorking 0:06 · 1,204 tokens
02

comment directly on elements

click anything in the running app and leave a note. the comment is the spec: the agent knows which element you meant.

3003Active30Pending03Pill-shaped order buttonfeat/order-button2 helpersReading Button.tsxChecking hover statesFix cart total roundingfix/cart-totalAdd footer linksfeat/footer3 branches ready for review
03

orchestrate multiple agents at a time

one agent per git branch, all working in parallel. when they finish, the ai helps resolve merge conflicts.

BRANCHESmainfeat/order-buttonfix/cart-totalfeat/footer↑0 ↓0↑2 ↓0↑0 ↓03↑1 ↓0↑4 ↓1ActionsActionsActionsMerged feat/order-button into main2 commits · no conflictsCommitRebaseMergeNew branchPush
04

manage your git from in the app

branches, commits, merges and pushes without leaving the window. every agent change is a real, reviewable commit.

ENVIRONMENTSdefaultAUTOstagingTermLog12:01:03frontend> next dev -p 300012:01:03frontend▲ Ready on :300012:01:04backenduvicorn api:app --rel…12:01:04backendApplication startup c…12:01:05databasepostgres ready on :54…12:01:05iveyenvironment “default”…›Type a command for Frontend…TERMINALSFrontendBackendDatabasepid 4812
05

configure your environment

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.

checkout.html100%a checkout screen with saved cardsproto/checkoutOpus High
06

prototype designs

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.

and more

...and the small things that add up.

node and python backends, auto-detected

node or python (django, fastapi, flask) backends start next to your frontend, each with its own real terminal.

client review file

export your running app as a single .html file. clients comment in any browser and their notes come back as pins.

ai resolves merge conflicts

when parallel branches collide, an agent works the conflict out and shows its steps.

phone, tablet and desktop previews

flip the live preview between device sizes to see how your app really lays out.

pick your agent

work with claude code or grok build, choosing the model per request.

a real source editor

open any file in a proper code editor right beside the live app when you want to take the wheel.

branch manager

a parent and child branch tree with rebase, merge and optional push to github.

export your branch

push the branch to your own github remote when you are ready. your repo, your history.

stardance was built using stardance.

  • built from the inside. the app you're signing up for was developed from inside itself, commenting on its own interface and letting agents change its own code on branches.
  • the product is the proof. the same comment-then-branch loop you see above is how stardance itself gets made.
  • follow the build on x at @Hkahn033.
who it's for

if you build with agents, this is your window.

developers on claude code, cursor or grok build

keep your agent. stardance gives it eyes on the running app instead of a wall of diffs.

vibe coders

point at what's wrong and say what you want. the code changes underneath, in a repo you own.

indie hackers

ship faster on your own product: parallel agents on separate branches while you keep building.

designers who code

polish the real interface instead of a mockup, then prototype the next idea next to it.

freelancers and agencies

send clients a review file, collect their comments as pins, and turn them into branches.

faq

questions, answered.

not here? ask on x: @Hkahn033.

what is stardance?

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.

what do i need to use it?

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.

is it free?

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.

who owns the code?

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.

does it work with my stack?

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.

how is it different from other ai coding tools?

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.

can i trust what the agent changes?

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.

free beta

sign up for the free beta. start building.

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.

  • you need a claude code or grok build subscription. it is required and not included with stardance.
  • your code stays in your repo, on branches you control.
what do you build with? (optional)

requires your own subscription to a supported ai coding cli: claude code or grok build. it's not included with stardance.

we only use your details to contact you about stardance. privacy