F1 through F12 produced no bytes at all. `functional_key` in `src/terminal/input.rs` is the one place a named key becomes an escape sequence, and it knew the cursor and editing keys and nothing else; the `key_char` fallback below it cannot help, because a function key arrives with no character, and `text_key_code` gives up the moment a key name is longer than one character. Both encoders funnel through that function, so the kitty path was equally blank. This was never a Windows or a PowerShell problem — it was every platform, every shell — but it shows up first on Windows because PSReadLine keeps CharacterSearch on F3, HistorySearch on F8 and ClearHistory on Alt+F7, so the missing keys are part of the shell's ordinary editing surface rather than something exotic. The table is `xterm-256color`'s, since that is what we advertise in `$TERM`: `kf1`..`kf4` are the SS3 letters, `kf5`..`kf12` the numbered tilde forms whose numbering starts at 15 and skips both 16 and 22. Modified, they take the same `CSI 1;<mods>` and `CSI <n>;<mods>` shapes the cursor keys already use, which reproduces `kf13` onwards exactly — `kf13` is Shift+F1, `kf25` is Ctrl+F1. DECCKM is deliberately not consulted: unlike `kcuu1`, `kf1` is SS3 under both `smkx` and `rmkx`. It stops at F12 on purpose. In the entry we advertise there is no capability left for a thirteenth key — `kf13` and up are already the modified forms of F1..F8 — so sending the VT220 `\E[25~` for a physical F13 would hand ncurses a sequence its own table reads back as Shift+F1. Silence is the more honest answer, and F13+ keys are close to nonexistent on the keyboards this bug was filed from. Encoding alone would not have reached the shell, because two things upstream were eating the keys first. The inline prompt editor had no arm for a named key it does not bind, so F8 fell out of the bottom of `handle_editor_key` and died on a `cx.notify()`; it now takes the same route an unknown Ctrl chord takes, handing the line to the shell before sending the key, which is what PSReadLine's history and character searches need in order to act on it. And Find Next / Previous sit on F3 and Shift+F3 off macOS, where gpui matches the binding before the pane's key handler ever runs; with no find bar open there is no match to step to, so those listeners now give the keystroke back the way `EditorSave` gives back Ctrl+S. F11 keeps fullscreen. It is the chord Windows Terminal, GNOME Terminal and konsole all use, no shell binds it, the modified forms still reach the PTY, and it is one line of config away from being retired — but it is now a stated choice with a test standing on it rather than an accident. The reporter's second clause is explained rather than fixed: `prompt_editor` is a real gate, and turning it off could not help while the bytes did not exist, which is exactly what they saw. Claude-Session: https://claude.ai/code/session_01UUyWQXzcBAoBzaSX8pc7nU
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