mirror of
https://github.com/l0ng-ai/tty7.git
synced 2026-09-22 08:02:24 +00:00
l0ng-ai
23bbe7d400
`TabCreate`, `PaneSplit` and `PaneReplace` each carry a pane the window has already spawned — the shell is running on the machine before the tree is told about it. When the tree refuses one of those, nothing ever takes the pane and the re-pull leaves the window without the tab it was for, so the shell goes on running with nothing referencing it. The log said only that an operation was refused, which is the one thing that does not point at the leak. Reproducible against a running instance: with a window open on a workspace, `tty7 tab new` and `tty7 tab close` back to back. The GUI restores the new tab, finds its pane already hung up, spawns a replacement, and `PaneReplace` is refused because the tab is gone. Four cycles in five leak a shell; leave half a second between the two and none do. Killing the GUI and repeating the loop leaks nothing — the CLI half is correct throughout. Not swept here, and the comment says why: at the point of the refusal the window still holds a view for the pane and only drops it once the re-pull lands, so hanging it up here would kill a pane that is still on screen. The sweep belongs after the pull settles and has to test the whole machine tree rather than this workspace's mirror, since a pane belonging to another workspace on the same host is not this window's to end. That change wants a GUI it can be watched in; this one only makes the leak say its own name, and `tty7 pane ls --all` already points at the recovery. `seeded_pane` is pinned by a test, because the set of requests that name a pane into existence is exactly the set a refusal can strand one from — a new one added without it would leak silently. 2933 tests pass.
tty7
A terminal workbench: persistent sessions, remote work, agents.
Pure Rust · GPU rendering on Zed's gpui · VT core from Alacritty
English · 简体中文
Why
- Performance — ~2× the throughput of Alacritty, Ghostty, or Kitty (benchmarks)
- Persistent sessions — quit or reboot; your shells and supported agent sessions keep running, 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
- Agent-aware — Claude Code, Codex & co.: status, notifications, git context
- CLI + Skills — agents create panes, run commands, and inspect output
Install
Native builds for macOS, Windows, and Linux on Releases:
| macOS | …-macos-arm64.dmg · …-x86_64.dmg |
drag into Applications |
| Windows | …-setup.exe · portable ….zip |
|
| Linux | …-x86_64.AppImage |
chmod +x and run — X11/Wayland libraries bundled |
What's inside
| Editor-grade input | ghost suggestions from history · explained tab completion · syntax highlighting · multi-line editing · click places the caret · ⌃ R fuzzy history |
| Window | tabs & splits · ⌘ P palette · ⌘ F scrollback search · nine themes · IME |
| Agent-aware | per-pane detection (18 CLIs): status dot · notifications · branch + diff · resume after reboot · tray icon when input is needed |
| Remote workspaces | remote files, repos, changes, diffs, worktrees, tabs, and panes · reconnect from any client and continue where you left off |
| CLI + Skills | bundled tty7 CLI · agent skill · pane/workspace control · real PTY commands · output, process, port, and agent status |
| SSH | native russh stack: profiles with keychain secrets · SFTP panel · port forwarding · jump hosts · one-time, unprivileged tty7-server install |
Full documentation lives in docs/ —
keyboard shortcuts ·
config.json ·
CLI reference. The agent-facing CLI interface is also
documented in skills/tty7/SKILL.md.
Install the skill with:
npx skills add l0ng-ai/tty7 # install
npx skills update tty7 # update later
Benchmarks
Same machine, same day, same 155×40 grid — Apple M1 Pro, macOS 26.3.1, five-run averages (2026-07-04):
| tty7 | Alacritty | Ghostty | Kitty | |
|---|---|---|---|---|
Plaintext I/O — 11 MB cat (lower = better) |
95 ms | 239 ms | 179 ms | 185 ms |
| DOOM-fire frame rate (higher = better) | 888 fps | 485 fps | 552 fps | 617 fps |
| Cold-launch memory | 116 MB¹ | 105 MB | 128 MB | 130 MB |
¹ GUI 105 MB + the persistent server 11 MB.
Methodology and one-command reproduction: scripts/bench/.
Built on gpui and alacritty_terminal · Apache-2.0 · Discord · Changelog