The dev server runs on your computer
For team owners and admins, ib-apps dev now runs next dev on your own machine over a mirror of your folder, with the environment's variables, and points the app's development address, its actions, the app proxy and its jobs at it through a tunnel started for you. Your own debugger and tools, no sandbox wake, and no dev server hours used. Ctrl-C hands the environment back to the hosted dev server, and so does closing the laptop, within a minute.
The CLI keeps the mirror in .ib/local (never synced) and takes the generated files from the server, so what runs locally is what the hosted dev server would run. A heartbeat every five seconds keeps the environment pointed at your computer. Pass --url for a tunnel of your own and --port for another port (3000 moves on to the next free one when busy). It reveals the environment's variables, so it takes a team owner or admin, and each start is in the audit log; a member's ib-apps dev syncs with the hosted dev server as before, as does --hosted, and --local insists on your computer rather than falling back.
Both modes print the address to open the app at, and the hosted dev server stays awake while ib-apps dev is connected instead of sleeping between visits.
More in Run the dev server on your computer.