From 418ebbf9605357741e2fbc74dffb873326fb727d Mon Sep 17 00:00:00 2001 From: l0ng-ai <24760907+l0ng-ai@users.noreply.github.com> Date: Sun, 16 Aug 2026 10:10:11 +0800 Subject: [PATCH] docs: the front page promised shells that survive a reboot MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit README, both languages, and the docs index said that after rebooting the machine your shells are still running. They are not, and the project's own agent documentation says so plainly: When the server goes away — a reboot, a crash, a deliberate restart — the shells go with it. Panes that were running an agent relaunch the conversation on restore. That is the accurate version, and it is what I measured: killing the GUI leaves the server and every pane alive, and restarting the server takes panes from two to zero while the workspaces survive. So quitting the app really does keep shells running — the front page was right about that half — and a reboot rebuilds the layout around fresh shells with agent conversations resumed. The headline is no weaker for being true; "resumes your agent conversations after a reboot" is the thing that is hard to build, and it is the thing that actually happens. Left alone, because they were already exact: "a pane lost to a reboot relaunches the conversation", prompt history that "carries across sessions and reboots" (it is on disk), and "session resume after a reboot". --- README.md | 2 +- README.zh-CN.md | 2 +- docs/index.mdx | 7 ++++--- 3 files changed, 6 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 0ea6a2a3..1bb9c10e 100644 --- a/README.md +++ b/README.md @@ -27,7 +27,7 @@ ## Why - **Performance** — ~2× the throughput of Alacritty, Ghostty, or Kitty ([benchmarks](#benchmarks)) -- **Persistent sessions** — quit or reboot; your shells and supported agent sessions keep running, no tmux +- **Persistent sessions** — quit the app and your shells keep running; after a reboot the layout comes back and supported agent conversations resume, no tmux - **Editor-grade input** — suggestions, completion, highlighting, history search - **Remote development** — files, repos, panes, and git data stay on the remote machine - **Native SSH** — profiles, SFTP, port forwarding, and jump hosts diff --git a/README.zh-CN.md b/README.zh-CN.md index bb075519..dd12663b 100644 --- a/README.zh-CN.md +++ b/README.zh-CN.md @@ -27,7 +27,7 @@ ## 为什么 - **性能** —— 吞吐约为 Alacritty、Ghostty、Kitty 的 2 倍（[基准测试](#基准测试)） -- **持久会话** —— 退出应用、重启机器后，shell 和已支持的 agent 会话照样运行；无需 tmux +- **持久会话** —— 退出应用后 shell 照样运行；重启机器后布局恢复、已支持的 agent 会话续上；无需 tmux - **编辑器级输入** —— 建议、补全、语法高亮、历史搜索 - **远程开发** —— 文件、仓库、pane 和 git 信息都留在远端机器上 - **原生 SSH** —— profile、SFTP、端口转发和跳板机 diff --git a/docs/index.mdx b/docs/index.mdx index d70cc602..916d463b 100644 --- a/docs/index.mdx +++ b/docs/index.mdx @@ -9,9 +9,10 @@ mode: "wide" tty7 showing a sidebar of agent sessions across several repositories -tty7 is a terminal you can leave running. Close the window, reboot the machine, -walk to a different laptop — the shells you started are still there, and so are -the coding agents you left working in them. +tty7 is a terminal you can leave running. Close the window and the shells you +started are still running, untouched. Reboot the machine and the layout is +rebuilt around fresh shells, with the coding agents you left working picking +their conversations up where they were. It is written in Rust, renders on the GPU through Zed's [gpui](https://github.com/zed-industries/zed), and parses VT with Alacritty's