mirror of
https://github.com/l0ng-ai/tty7.git
synced 2026-09-22 00:02:23 +00:00
l0ng-ai
adfdd398f6
A kitty graphics escape is untrusted input — any program running in a pane can print one — and every bound on that path is deliberate and spelled out, except this one. `to_rgba8` clamps an inflate to `min(declared, MAX_IMAGE_BYTES)` and says why the declared size cannot be trusted on its own; the PNG branch called `image::load_from_memory`, which leaves the ceiling to `Limits::default()`. That default is 512 MiB — a real bound, eight times `MAX_IMAGE_BYTES`, and somebody else's number. A patch release that relaxed it would silently widen what a hostile escape sequence can allocate, and this runs in the GUI process, so an OOM here takes every pane down rather than the pane that asked for the image. The limit is now stated locally at the value the default has today, so behaviour is unchanged and the invariant stops depending on a dependency's opinion. Why the number is not simply `MAX_IMAGE_BYTES`: that bound comes from what a wire frame carries, and a PNG crosses the frame still compressed, so its decoded size is the one thing on this path not already settled. Lowering it would bound this properly but decides how large an image tty7 means to display, which is a product call and not a cleanup — noted in the comment. The PNG branch had no test at all, so the change is covered both ways: a real 2x1 PNG decodes at its own dimensions rather than the escape's `s=`/`v=`, and a 1x1 PNG whose IHDR is rewritten to 0xffff x 0xffff (~17 GB, CRC repaired so the decoder parses it) is refused. Checked out of band that the refusal really is "Memory limit exceeded" and not a malformed-file rejection, so the test cannot pass for the wrong reason. 2936 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