Sessions, PTYs and buffers live only in memory, so restarting the service ends every session. This is a deliberate boundary: WebMux uses no database, does not detach into a separate daemon and does not interoperate with tmux. Only explicitly registered state files (repository list, launch configurations, preferences and so on; see the
persistence list (Chinese)) survive a restart. The exception is
hybrid sessions (Chinese): WebMux records which agent session they map to, so after a restart you can resume them from the “Resumable” group on the home screen; the agent itself keeps the conversation.