SonicTerm Wiki

简体中文

SonicTerm is a native, GPU-accelerated terminal for macOS, Windows, and Linux. Start with Usage to install it and learn everyday actions.

User guide

• Usage — install, open tabs, split panes, detect file references in terminal messages, and select text
• Terminal Multiplexers — set up tmux, rmux, GNU screen and Zellij so links, paths, keys and the clipboard work
• Configuration — change defaults in ~/.sonicterm/sonicterm.toml, reload, and save
• Keybindings — find a shortcut or write a binding
• Themes — choose or create a color palette
• Logging — find logs, investigate a problem, and prepare a bug report
• Memory — understand resource limits and retained-memory reports

How SonicTerm works

Read Architecture for the map, then From Keypress to Pixel for one A's round trip. Use the references below for a particular subsystem.

• Architecture — system shape and crate boundaries
• From Keypress to Pixel — input, child output, grid, glyph, and pixel
• Runtime Lifecycle — startup, ownership changes, tab transfers, and shutdown
• Terminal IO and VT — PTYs, parser protocols, shell integration, and grid rules
• Rendering Modes — adapter selection and frame pacing
• Rendering and Fonts — typography, atlases, GPU/CPU drawing, and damage
• Platform Integration — AppKit, Win32, X11, and Wayland boundaries
• Architecture Internals — correctness, accounting, and lifetime invariants
• Crate Reference — all 23 crates, their interfaces, and dependencies

Build and contribute

• Packaging — build local packages and inspect their layouts
• Development and Release — the local gate table, coverage evidence, and the index of development pages
• Repository and Toolchain — layout, toolchain, build entry points, code conventions, and native dependencies
• Local Gate — how the gate runner executes each step
• CI and Coverage — pull-request and main CI, gate blind spots, and the workflow supply chain
• Release Process — tag-driven releases, published assets, and resolved-issue provenance
• Wiki Publication — wiki source rules and publication after every merge
• Code Ownership — the platform area of each path, and how agents claim work
• Home — return to this index