ib-apps dev notices a tunnel that closed while your computer slept, and opens a new one
When the dev server runs on your computer, the CLI now checks every half minute, and as soon as the computer wakes, that its tunnel still reaches it. Before, a quick tunnel whose connection died during sleep stayed in charge: the heartbeats resumed the moment the computer woke and kept pointing the environment at an address that answered nothing, so the app's development address refused to connect and Logs filled with 503s until ib-apps dev was restarted by hand. Now the environment is handed back to the hosted dev server at once, a new tunnel opens and next dev restarts behind it, which takes about as long as a restart did. A tunnel of your own (--url) is served again once it answers.
The tunnel is asked from the outside, as the router asks it: Cloudflare answering that it can't reach the tunnel, or not answering at all, counts as closed; a computer with no network isn't mistaken for one, and the check is made again before anything is done. A tunnel client that stops on its own is handled the same way, where before it only said to restart.
CLI 0.10.1. Update with npm install -g @inferencebureau/apps.
More in Run the dev server on your computer.