mirror of
https://github.com/l0ng-ai/tty7.git
synced 2026-09-22 00:02:23 +00:00
l0ng-ai
bdd9a6ccf1
An x86_64 build on Apple Silicon asked for the x86_64 package on every update, because the architecture came from `cfg!(target_arch)` — a compile-time constant that says `x86_64` whether the binary is on an Intel Mac or under translation. So an install that arrived as Intel by any route (a mis-picked download, a migration off an Intel Mac) renewed itself as Intel forever. The updater was the only thing that could have carried it across, and it was the thing holding it back. Nothing said so until macOS began warning that the app "includes a component that will not work with a future release of macOS" (#687). `sysctl.proc_translated` distinguishes the two: 1 under Rosetta, 0 native, absent on Intel, where the question does not arise. An x86_64 build that reads 1 is running on Apple Silicon, so it is offered the arm64 package and migrates on its next update. Safe unasked: the swap is the unzip-and-rename the updater already performs, with no architecture check anywhere in that path, and it runs in a separate process that only moves files. Both packages ship in every release, and a release missing the arm64 zip fails loudly in `select_release_asset_for` rather than falling back to the wrong one. The policy is split from the probing, the way the AppImage answer already is, so it is testable without a Rosetta process. The probe is split in turn into a raw `Option<i32>`: every way of misusing `sysctlbyname` returns non-zero and reads as an ordinary "not translated", which is also the right answer on the untranslated machines the tests run on — so a broken probe would have passed a bool-only assertion while leaving the bug in place. The published arm64 bundle was never at fault: its three Mach-O files are single-architecture arm64, and `bundle-macos.sh` copies only out of the matching target directory.
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