Chau7 is a terminal emulator. It sees everything you type and everything your tools output. We take that seriously, even if we don't take our naming conventions seriously.
Do not open a public issue. Instead:
- Use the in-app bug reporter (Option+Cmd+I). Reports are submitted via HTTPS through the issue-intake Cloudflare Worker to a private GitHub repository that only maintainers can access. You choose which diagnostic sections to include before anything is sent. See the in-app privacy page and PRIVACY.md for the full data flow.
- Or open a private security advisory on GitHub.
We acknowledge reports within 48 hours. Critical fixes ship within 7 days. We'll credit you in the release notes unless you prefer otherwise.
Here's everything security-relevant, with no hand-waving:
Terminal I/O: Every keystroke, every command output, every escape sequence. The terminal buffer lives in memory and optionally in scrollback restore files on disk at ~/.chau7/.
API Proxy (chau7-proxy): A local Go binary that intercepts AI API calls over TLS for analytics. Your API keys pass through to the original provider (Anthropic, OpenAI, etc.). Keys are never stored, never logged, never transmitted anywhere else. The proxy is opt-in and runs on localhost:18080. You can disable it in Settings.
MCP Server: 30+ tools exposed over a Unix socket at ~/.chau7/mcp.sock, permissions 0600 (owner-only). Any process running as your user can connect. The tools can read terminal output, send input, manage tabs, and query history. This is powerful by design.
Remote IPC: The remote bridge listens on ~/Library/Application Support/Chau7/remote.sock with socket permissions 0600 inside an owner-only (0700) directory. This keeps other local users from reading or writing remote bridge frames.
Bug Reports: Submitted via HTTPS through the issue-intake Cloudflare Worker (services/chau7-issues/src/worker.js) to a private GitHub repository that only maintainers can access. No data leaves your machine until you hit Submit. All diagnostic sections are off by default — you choose what to include. The in-app privacy page (issue_privacy.rs) lists every third-party involved. See also PRIVACY.md.
Shell Integration: OSC 7/133 escape sequences for working directory and command detection. Shell history access for frecency commands. Git status queries via git rev-parse.
Relay (services/chau7-relay): Cloudflare Worker for remote control, separate from the issue-intake Worker. Rate-limited and authenticated via scoped HMAC tokens. WebSocket frames are end-to-end encrypted and not persistently stored. REST pending snapshots are server-readable and retained for four hours; APNs registrations expire thirty days after registration or sooner on explicit revocation/provider rejection. Replay entries survive through the final accepted token second. Transactional alarms and expiry checks remove old records; legacy records are adopted on activation. See the relay README for explicit deletion and rollout limitations.
Telemetry: Per-run token counts, cost, tool calls. All stored locally in SQLite at ~/.chau7/telemetry/. Nothing leaves your machine unless you explicitly submit a bug report with diagnostic data attached.
- Phone home. No analytics, no crash reporting, no usage tracking. Unless you submit a bug report.
- Store API keys. The proxy forwards them. It does not save them.
- Run in the background after you quit. No daemons, no LaunchAgents (unless you configure start-at-login).
- Send terminal output without opt-in remote control or a diagnostic report you explicitly submit.
Security fixes ship for the latest release only. We're a small team (well, a small person). If you're running an old version, update first, then report.