mirror of
https://github.com/l0ng-ai/tty7.git
synced 2026-09-22 08:02:24 +00:00
l0ng-ai
212d5110ef
With a repository open, an idle window ran `git status -uall` about 2.6 times a second, forever. Measured on the Linux CI runner: 78 debounce bursts in 30 seconds, from one real change. `notify`'s inotify backend subscribes with `WatchMask::OPEN`, so every `open(2)` under a watched directory is an event. `git status` opens `.git/index`, `.git/HEAD` and `refs/heads/*`, all of which the source control watch covers — so the read that answers "did this repository change" is itself an event saying it may have changed, and the answer schedules the next question. The debounce caps the rate; it cannot break the cycle. `Debounce`'s own doc argued this was structurally impossible, because `GIT_OPTIONAL_LOCKS=0` stops `git status` writing the index back. That covers writes. `IN_OPEN` fires on reads, and no environment variable suppresses it. macOS FSEvents has no equivalent, so this was invisible on the machine it was written on, and every theory that did not involve the kernel was correctly eliminated before this one was found. `is_content_change` drops `Access(Open | Read | Close(Read))` and keeps `Access(Close(Write))`, which is a write finishing rather than a reader. Applied at both watchers: the host watch, and the config hot-reload watch in `main.rs`, which has the same shape — a reload re-reads the file it is watching. The guard is a host conformance case rather than a platform test, because macOS passes it trivially and Linux is where it has to hold. It was verified red on the Linux runner with the filter removed. Its drain waits out the create of the file it asserts about: FSEvents hands that over a beat after the stream opens, and a stale create is indistinguishable here from a read reporting.
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 each platform 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
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