The command-line UI is a bit confusing

With the web UI largely making the console UI redundant, it's a little odd that running tilt up gives you two UIs. And it's not entirely intuitive that "exiting tilt" doesn't tear your resources down and that tearing your resources down with tilt down doesn't exit tilt. So it might make sense to decouple the two in some way.

Looking at how docker-compose works, it provides both stop/start and create/teardown commands, maybe that pattern could be nice here. Or some flag to daemonize, i.e. tilt up -d which runs tilt, daemonizes, and you interact through web UI only. Then a tilt stop to kill the daemonized tilt?

Start at the tilt up and tilt down command entry points and compare the console and web UI behavior described in the issue. Review the docker-compose stop/start and create/teardown pattern as a possible reference. Done should mean the command and lifecycle behavior is clearly decoupled, including how a daemonized process is stopped.