termio-sh/termio

The iOS companion is killed by the kernel when a terminal surface is torn down. Two TestFlight crash reports carry the full log, and both are the same: Exception Type: EXC_GUARD (SIGKILL) Exception Subtype: GUARD_TYPE_FD Exception Message: CLOSE on file descriptor 0 Termination Reason: GUARD 0x4000000100000000 Something calls close() on fd 0. iOS guards stdin/stdout/stderr, so the process is killed outright — no exception to catch, no chance to recover. That is why the Mac side sees every companion socket for the phone drop in the same millisecond. Stack The iPad report symbolicates cleanly and pins the path: -[UIView removeFromSuperview] → UITerminalView.didMoveToWindow() UITerminalView+Lifecycle.swift:70 → TerminalSurfaceCoordinator.freeSurface() :361 → TerminalSurfaceCoordinator.tearDownSurface(removingBridgeFrom:) :386 → TerminalSurface.free()

On some Macs the toolbar buttons — the navigator toggle, the sort pull-down, +, and the inspector toggle — draw as bare glyphs with no capsule behind them. On other Macs the same buttons carry the Liquid Glass capsule. Same source, sometimes even the same machine running two builds side by side. Nobody has reproduced this on a machine we control, so this issue is a call for data rather than a diagnosis. If your toolbar buttons have no capsule, please post the output of the two commands below. Screenshots What we know The buttons are plain NSToolbarItems with isBordered = true (Sources/termio/App/App.swift, the .toggleNavigator / .sortProjects / .newTerminal / .toggleInspector cases). The capsule is drawn by AppKit, not by us — we never paint it, and there is no setting that turns it off. AppKit decides that chrome from two numbers: the macOS version the app runs on and the SDK version the binary was linked against. Our own code only branches at runtime (if #available(macOS 26,

The problem Settings ▸ Usage only reads four agents: Claude Code, Codex, Kimi, and Grok. Every other agent termio can launch — cursor-agent, Amp, OpenCode, Antigravity, Hermes, Prime — shows nothing, even when its CLI is installed and logged in. What you'd want instead One UsageProvider per additional agent, so the Usage tab reads its plan limits and token totals the same way it reads the four it already supports. How Usage is wired Sources/termio/Companion/Usage/ is one file per agent. Each provider holds its own credential read, its own plan-limit endpoint, and its own session-log scanner; UsageMonitor knows only the list. Adding an agent is a new file plus one line — not an edit threaded through the fetch and scan paths. protocol UsageProvider: Sendable { var agent: AgentPreset { get } func planLimits(allowKeychain: Bool) async -> PlanLimitReading func tokenUsage(in windows: DateWindows) -> AgentTokenUsage } UsageProvider's protocol extension already gives you th

Problem Qoder CLI is not in the agent roster, so it can be run in a plain terminal but gets none of what termio adds to an agent session: status (working / idle / needs-you / done), notifications, session resume, or transcript reading. Original request 希望 qodercli 支持下呢 — @gaoyanchen, v2ex/t/1232978#5 Scope One bundled manifest, Sources/termio/Resources/agents/qoder.json, alongside the ten that already ship (claude, codex, cursor, amp, grok, opencode, kimi, antigravity, hermes, pi). No app code changes if Qoder's integration surface fits AgentDefinition — the manifest declares launch argv, the hook destination and dialect, resume, and transcript discovery. What has to be established first Does Qoder CLI have a hooks mechanism termio can write into (like Claude Code's settings.json, Amp's plugin drop-in, or Cursor's flat hooks.json)? Without one, status has to fall back to screen classification and the manifest declares no hook integration. Where does it store session

Part of the issue-tracker integration designed in docs/design/issue-tracker-integration.md (M4 of 4). Builds on #99 / #100. Problem Different projects use different trackers — some GitHub Issues, some Linear. The provider architecture (#99) exists precisely so the second tracker is a conformance, not a rewrite. Linear is the first proof of that. Scope Connect: personal API key paste (Connect → open linear.app/settings/api → paste). Linear's OAuth2 requires a client secret, which an open-source app cannot ship; API keys are Linear's blessed path for local tools. Key stored in Keychain alongside the GitHub token. Provider: LinearProvider over the GraphQL API (bare URLSession, hand-written queries) — teams as containers, issues list/detail/comments, and the write set from #100 scoped by capabilities (Linear has no GitHub-style emoji reaction set and no pull requests — the reaction bar and the Issues/PRs kind filter must shrink away). Binding picker: Linear teams cannot be deriv