signaltty documentation

The server owns sessions and processes. GTK and CLI are clients. Start with the current architecture or the development workflow for your task. Research and verification reports retain their original dates and describe the checkout they examined.

Current architecture and product direction

• 01 — Architecture & process model
• 02 — Data model (server/workspace/tab/pane)
• 03 — Lifecycle & attention models
• 04 — PTY lifecycle
• 05 — Terminal backend research
• 06 — GUI toolkit decision (GTK vs Qt)
• 07 — Agent integration strategy
• 08 — IPC schema
• 09 — Persistence & restore
• 10 — Security model
• 11 — Crate layout
• 12 — MVP roadmap & risks
• 13 — Plugins & workflows
• 14 — Product direction (cmux + herdr, t3code visual bar)
• 16 — Visual references (Geist, Linear, Vercel)

Development workflow

• 15 — Agent skills (install + phase routing)
• 17 — Agent development and verification
• 18 — Agent workflow commands and source ownership
• 19 — CI and pull request delivery
• Feature catalog and recorded lifecycle

Architecture decisions

• ADRs

Research

• License provenance and remaining distribution checks, 2026-10-11
• Agent Orchestrator review, 2026-10-12
• Agent-ready repository research, 2026-10-03
• Agent workflow automation research, 2026-10-14
• cmux and Herdr source review, 2026-10-03

Historical verification evidence

• App verification, 2026-09-29
• Native UI refinement verification, 2026-09-29–30
• Workspace visual hierarchy verification, 2026-09-30
• Automatic hook configuration verification, 2026-09-30
• Codex pane runtime verification, 2026-09-30
• Local agent workflow verification, 2026-09-30
• Per-file diff review verification, 2026-10-03