l0ng-ai 4140214c9f fix(daemon): a phone keeps updating on a pane with a long history (#1105)
* fix(daemon): credit a replay back, so a phone keeps updating on a long pane

An observer was charged for the whole replay ring when it subscribed, but
the writer only credited Output, Image and ClipboardWrite back, never the
Snapshot frames the replay is made of. The charge stayed for good. A full
ring (8 MiB) is the observer's whole budget, so the first byte of live
output pruned it, and with the refusal sender still holding the channel
open nothing told the gateway: the phone showed the screen it opened on
and never updated until the pane was reopened.

Charging and crediting now share one measure, gated_len, and the replay
reports what it queued. A controller's gate starts at its replay too, set
under the state lock instead of reset after it.

* fix(daemon): room for a full replay, and an observer dropped is let go

Crediting the replay was not enough on a busy pane. The observer budget
was exactly RING_CAP, so while a full ring's replay was still being
written, one byte of live output pushed the gate past it and the observer
was dropped. With a 1 ms ticker in the pane this happened on every open.
The budget is now two rings: the replay, and as much again of live output.

A dropped observer also went silent. stream_observer kept a clone of the
channel's sender for refusals, so dropping the pane's sender never closed
the stream; the client sat on a connection nothing would be sent down
again, and a lease it held was never released. Refusals now go through the
pane (tell_observer), the pane holds the only sender, and a dropped
observer is sent a last Error saying why before its stream ends. The phone
reads that Error as a reason to reconnect.
2026-10-07 21:32:49 +08:00

tty7

tty7

A terminal workbench: persistent sessions, remote work, agents.

Pure Rust · GPU rendering on Zed's gpui · VT core from Alacritty


CI Version Platforms License Discord

English · 简体中文


One-minute tour of tty7: agents across repos, one agent driving another through the CLI, the prompt editor, diffs, dragging panes, and sessions that survive quitting the app

▶ Watch in full quality

Why

A background server owns your shells and panes — not the window. Everything below follows from that.

  • Performance — ~2× the throughput of Alacritty, Ghostty, or Kitty (benchmarks)
  • Persistent sessions — quit the app and your shells keep running; after a reboot, layout, screen, and supported agent conversations come back. No tmux
  • Agent-aware — Claude Code, Codex & co.: status, notifications, and git context for every repo at once
  • Scriptable by agents — one agent opens a pane for another, hands off a task, waits, and reads the result, with or without the GUI running
  • Editor-grade input — suggestions, completion, highlighting, history search, with no plugin to install
  • Remote development — files, repos, panes, and git data stay on the remote machine, over a native SSH stack

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

Agent-aware per-pane detection (28 CLIs) · status dot · notifications · branch + diff · tray icon when input is needed · resume after reboot · reopen any past session from Search Everywhere · one-key launch · tab sidebar grouped by repository, with pinned groups
CLI + Skills bundled tty7 CLI · agent skill · run streams a command and exits with its code · split · send · wait --until free · capture
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 Search Everywhere · ⌘ F scrollback search · hibernate a tab to free its memory · IME
Side panel ⌘ J · process tree and listening ports · file tree · changes and diffs · find in files · GitHub issues and pull requests, read-only, signed in through gh
Shell integration injected when a pane starts, nothing to install · prompt marks · working directory · exit codes · command-finished notifications · zsh, bash, fish, PowerShell, WSL, remote panes
Remote workspaces remote files, repos, changes, diffs, worktrees, tabs, and panes · reconnect from any client and continue where you left off
SSH native russh stack: profiles with keychain secrets · SFTP panel · port forwarding · jump hosts · one-time, unprivileged tty7-server install

Supported agents

Detection is free: brand avatar, branch + diff, tab title. Status takes one click under Settings → Integrations to install that agent's hook, and brings the status dot, notifications, the tray icon, tty7 wait, and resume after a reboot. Fork needs both — the agent's own fork command, and the hook that tells tty7 which session to fork. Past sessions are read from the agent's own history files and listed in Search Everywhere, where ⏎ resumes one.

The full support matrix, all twenty-eight
Agent Detected Status · resume Fork Past sessions
Claude Code ✓ ✓ ✓ ✓
Codex ✓ ✓ ✓ ✓
TraeCode ✓ ✓ ✓
Grok ✓ ✓ ✓
OpenCode ✓ ✓ ✓ ✓
Oh My Pi ✓ ✓ ✓ ✓
Prime Agent ✓ ✓ ✓
Droid ✓ ✓ ✓ ✓
Qwen Code ✓ ✓ ✓ ✓
Goose ✓ ✓ ✓
Qoder CLI ✓ ✓ ✓ ✓
Qoder CN CLI ✓ ✓ ✓ ✓
CodeBuddy ✓ ✓ ✓ ✓
Gemini ✓ ✓ ✓
Copilot ✓ ✓ ✓
Kimi Code ✓ ✓ ✓
Pi ✓ ✓ ✓
Crush ✓ ✓
Antigravity ✓ ✓
Cursor ✓ ✓ ✓
Empryo ✓ ✓
Muse Code ✓ ✓
jcode ✓ ✓
Aider ✓
Amp ✓
Auggie ✓
Hermes ✓
Vibe ✓

None of them are wrapped or proxied — the agent you start is the agent you get, in a normal PTY, with its own interface. An agent launched through a wrapper script can be mapped to one by name with agent_commands in config.json. Every agent on your PATH is also a row in Search Everywhere (Agent: Claude Code, …) that opens it in a new tab, and the New Tab menu names the ones you have actually run. agent_launch sets the command line it starts with.

Documentation

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/.


S
Description
A terminal workbench in pure Rust: shells, persistent sessions, SSH, coding agents. GPU-rendered on Zed's gpui, VT core from Alacritty.
Readme Apache-2.0
48 MiB
Languages
Rust 97.4%
TypeScript 1.4%
Shell 0.4%
CSS 0.4%
PowerShell 0.2%
Other 0.1%