# how a change travels

what happens between typing and everyone seeing it

what happens between pressing send and everyone seeing it, when the runner serves the app (on your laptop saving is the release, so only the first few steps apply). click through it first:

_(on the web page there's a little interactive piece here, `apps/docs/playground/how-a-change-travels.tsx`, that visitors can change by typing into the box)_

## 1. it waits its turn

each version has one queue, and while a request waits its mark in the box is a sparse dither

## 2. you watch it happen

with `app.dev` set, whoever asked gets reloaded onto a hot-reloading copy when the agent starts and sees every save as it happens, while everyone else keeps the built app. in a [sandbox](/sandboxes) there's nothing to watch, it all arrives at the end

## 3. it gets committed

the change becomes one commit on that version's branch, unless it touched files that person can't or `memberCheck` refuses it, in which case it's taken back out here

## 4. it gets built

into a fresh folder, installed, built and started on a free port, then up to 90 seconds to answer at `/` (or `app.health`). one build at a time

## 5. if it doesn't build

the agent gets the error and fixes the build without dropping what was asked, while the box says "It didn't build. Fixing it (try 1)." each fix is a commit and it gets three tries (`repairs`)

fixes are held to the same `memberPaths` and `memberCheck` as the change. if one breaks them, or three tries don't work, every commit gets reverted and the box says nothing changed, and nobody else ever saw it. in [push mode](/on-vercel) the reverts get pushed too

## 6. it gets swapped in

new page loads get the new build, but open pages keep talking to the copy that served them (fetches included) so nothing breaks mid-swap, and the old copy stops after two minutes. whoever asked gets reloaded, unless they're typing another request, then the box says "your change is ready" with a link

## undo

it reverts the change's commits (fixes included) with new ones and builds and swaps like any change. it never overwrites later work, so if the same lines changed since it tells you and does nothing, and if another change is running it asks you to wait

## stop

anything waiting or working can be stopped and keeps none of its edits, and anything past 15 minutes gets stopped for you
