Get back to your session.
Start with what you can see. A browser disconnect, an offline host and an exited process need different fixes. Check before restarting anything.
On this page
The page says offline
Check that the host computer is awake, online and still running the process. The CLI and browser retry temporary connection failures automatically.
On the host, use the local session list. A stale app row is not proof that a process is still alive.
shell list- Check local process and relay state separately.
shell attach <ID>- If the local session is alive, inspect it without relying on the browser. Detach with Ctrl-X, then D.
The terminal is blank or looks wrong
Wait for the reconnect snapshot, then try reopening the view. If you selected Refstream, switch back to xterm.js. Check whether the running host predates your installed CLI.
Installing an update does not restart hosts. Save work and arrange a safe restart if a host update is needed. Never kill all sessions to fix one view.
The password no longer works
Use the complete link, including its #salt= fragment, and the current password. Password rotation changes both the salt and password and disconnects old viewers.
If the app has a sealed copy, unlock your personal vault. Otherwise recover the password on the host.
shell password <ID>- Print the active password locally. Do not put it in a bug report.
You cannot type
Check whether the session was created read-only or another person currently holds input. A read-only session requires a new interactive share if its owner wants typing enabled.
For MCP, check the grant scope, expiry and host version. MCP setup explains the additional input requirements.
A command exits before you get a link
Very short tasks may finish during startup. The CLI reports their exit status instead of printing a dead link. Try a longer-running process or start a fresh shell.
shell- Start an interactive shell to test the share path.
What survives a disconnect
The process runs on your computer. A temporary browser or network failure does not intentionally stop it. Current hosts keep bounded screen state and restore the screen when viewers return.
An ordinary disconnected share can recover its link for 12 hours. A known task exit closes the ordinary share. A persistent identity can be reused, but it is not a process checkpoint.
High output and nested terminals
Display queues are bounded. When output outruns the connection or renderer, stale display work may be replaced by a fresh screen snapshot rather than an unlimited transcript.
Current snapshot handling suppresses replies to old terminal queries. It is designed for full-screen programs, tmux and nested terminal use, but a specific application can still expose a compatibility bug.
Report a useful bug
Use Report in the shared terminal, or send feedback. No account is required. Signed-in users can choose to send without their account or email; anonymous reports cannot receive replies. Terminal text, passwords and sharing links are not attached automatically.
Include your CLI version, operating system, browser, renderer and a small reproduction that contains no private work. Say whether the problem happens locally, in a browser, or only after reconnecting. Remove share links, passwords, tokens and raw terminal logs before sending feedback or opening an issue.