On Windows and Linux a fullscreen window has no caption. The platform asks what is under the pointer through `WM_NCHITTEST`, gpui answers from the window control hitboxes the frame registered, and fullscreen clears `WS_CAPTION` — there is nothing left to answer with. Measured on a fullscreen tty7: `GetWindowLong` reports `WS_CAPTION` clear, and every point along the top of the window comes back `HTCLIENT`, where the same window a moment earlier answered `HTCAPTION`, `HTMINBUTTON` and `HTCLOSE`. The bar was drawn anyway. `WindowControls` renders minimize, maximize and close whenever the target is not macOS, without asking whether the window is fullscreen, so all three sat there taking hover styling — gpui's own dispatch reaches them fine — and doing nothing at all when clicked. Dragging the bar did nothing either. So on those two the bar goes. It is the app's own chrome there: a caption to move the window by and the controls at its end, none of which a fullscreen window has. Drawing chrome that cannot work is worse than drawing none. Not on macOS, and the reason is not that the bug is milder there — it is that the premise does not hold at all. `WindowControls` draws none of the three on macOS; the ones that go dead elsewhere are the system's traffic lights, and the system hides them itself. What that bar does in fullscreen is hold the band the system reserves: the traffic lights land on it when the menu bar is revealed, and so does the translucent strip drawn under the menu bar. Take the bar away and that strip lands on the terminal and covers its first row instead — measured, and the difference is exactly `TITLE_BAR_HEIGHT`. Fullscreen belongs to the system on macOS, and the bar is part of how the system dresses the window rather than something broken. Nothing on the bar becomes unreachable where it goes. Its controls are actions first, dispatched from the window's root rather than from the bar, and each has a chord or a seat in the palette, which has one; `what_the_title_bar_offers_is_reachable_without_it` is that in a test. Worth noting for anyone reading it: `ToggleTabSidebar` ships with no chord, so in fullscreen the palette is how it is reached. Entering says how to leave, because entering is the instant the bar disappears — so only where it does, and only through the action: a window that starts fullscreen because the setting says so is not a surprise anybody needs explaining, and `startup_mode` is untouched by the toggle either way. The chord comes from the keymap rather than from a string, so it reads `F11` or whatever it was rebound to. The notice carries an id, which is what keeps a held-down `F11` to one notice rather than a column of identical ones: pushing under an id already on screen replaces that one. Leaving through the action takes it back as well. Leaving some other way lets it time out instead — a second or two of a stale notice, which is not worth a per-frame watch on a state that lies: `toggle_fullscreen` is spawned onto the executor on every backend, so `is_fullscreen` still reports the old value when the action returns, and a render-time test for "not fullscreen now" can take the notice back before it has been seen. Verified on Windows 11 26200, and on macOS 26.5.2 by a second pair of hands: the macOS half of this is the reason the change is not applied there. Linux is reasoned about rather than measured — it draws its own chrome the way Windows does, and the same `WM_NCHITTEST`-shaped question is answered through gpui's window control hitboxes.
tty7
A terminal workbench: persistent sessions, remote work, agents.
Pure Rust · GPU rendering on Zed's gpui · VT core from Alacritty
English · 简体中文
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 or reboot; your shells and supported agent sessions keep running, 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
- Git beside the terminal — source control, diffs, and worktrees without leaving the window
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 (20 CLIs) · status dot · notifications · branch + diff · tray icon when input is needed · resume after reboot · tab sidebar grouped by repository |
| 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 palette · ⌘ F scrollback search · ⌘ J panel with process tree and listening ports · 13 themes, your own YAML, iTerm2 import · IME |
| 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 |
| Git | panel follows the focused pane · stage, commit, amend, branch, push, stash · side-by-side or unified diffs · commit graph with cherry-pick, revert, and reset · a new worktree opens its own tab |
Supported agents
Detection is free: brand avatar, branch + diff, tab title.
Status takes one click under Settings → Agents 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.
The full support matrix, all twenty
| Agent | Detected | Status · resume | Fork |
|---|---|---|---|
| Claude Code | ✓ | ✓ | ✓ |
| Codex | ✓ | ✓ | ✓ |
| TraeCode | ✓ | ✓ | ✓ |
| Grok | ✓ | ✓ | ✓ |
| OpenCode | ✓ | ✓ | ✓ |
| Oh My Pi | ✓ | ✓ | ✓ |
| Droid | ✓ | ✓ | ✓ |
| Qwen Code | ✓ | ✓ | ✓ |
| Goose | ✓ | ✓ | ✓ |
| Gemini | ✓ | ✓ | |
| Copilot | ✓ | ✓ | |
| Kimi Code | ✓ | ✓ | |
| Pi | ✓ | ✓ | |
| Aider | ✓ | ||
| Amp | ✓ | ||
| Cursor | ✓ | ||
| Auggie | ✓ | ||
| Hermes | ✓ | ||
| Vibe | ✓ | ||
| Antigravity | ✓ |
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.
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/.
Built on gpui and alacritty_terminal · Apache-2.0 · Discord · Changelog