Telemetry
QuickTTY does not include analytics or advertising SDKs. The application does not add product telemetry to terminal sessions.
Standard macOS and network services used by processes outside QuickTTY may have their own policies.
Update checks
When QuickTTY checks for application updates, Sparkle requests a GitHub-hosted feed:
- The stable channel uses the public GitHub latest release feed.
- The beta channel uses the versioned feed tracked in the QuickTTY GitHub repository.
Downloading an update retrieves the corresponding immutable GitHub Release artifact. Those requests are subject to GitHub’s infrastructure and policies.
Terminal activity
QuickTTY starts shells and other commands selected by the user. Their terminal output, file access, subprocesses, and network activity belong to those processes and depend on the commands, tools, remote hosts, and configuration the user chooses.
QuickTTY does not promise network isolation for terminal processes. For example, ssh, package managers, development servers, and coding agents can make network connections as part of their normal operation.
Agent integrations
QuickTTY can display standard OSC 9;4 terminal progress. Pi can emit these sequences through its own setting. Claude Code and Codex examples are bundled with QuickTTY, but their hooks are installed only when the user manually merges them into an agent configuration.
QuickTTY does not automatically install, overwrite, or update agent hooks. The bundled helper does not inspect prompt, transcript, hook stdin, or environment secrets.
Local files
QuickTTY uses these user-local paths:
~/.config/quicktty/config— user-authored QuickTTY and terminal configuration.~/.config/quicktty/.ghostty-effective-config— generated effective Ghostty configuration.~/Library/Application Support/QuickTTY/state.json— workspace descriptions, tabs, split layout, working directories, startup command descriptions, focus, and normal window frame.
Saved state describes a workspace; it does not preserve live shell processes. On restore, every saved pane starts a fresh shell in its saved working directory. A saved custom startup command is never run automatically.