feat(opencode): add killswitch indicators to TUI sidebar

[iceteaSA]

Dependencies: Requires #35 (killswitch) and #37 (TUI sidebar) to be merged first.

Adds killswitch awareness to the TUI sidebar widget:

• Red dot for killed accounts, green for active
• Quota/refresh backoff state display
• Kill summary section showing which accounts are blocked
• writeSidebarState() computes killswitch policy for all accounts

Files:

• packages/opencode/src/sidebar-state.ts — adds killed, backoff fields
• packages/opencode/src/tui.tsx — killed indicator, kill status section
• packages/opencode/src/index.ts — killswitch-aware sidebar state

---

Summary by cubic

Adds killswitch status to the TUI sidebar and wires it to a shared QuotaManager for real-time quota and backoff with persisted state and cross-process dedupe. Also writes a sidebar state file and exposes the TUI module so the UI can render without extra fetches.

• New Features
  • Enforces killswitch thresholds: blocks killed accounts, returns Retry-After based on earliest reset, eager initial quota refresh, and skip-main routing if killed.
  • Sidebar: per-account status dot (green/red), kill summary, and quota/refresh backoff indicators with “retry at” timestamps.
  • QuotaManager: unified cache for main + fallbacks with inflight dedupe, exponential backoff, request-count-based refresh, persisted main quota/backoff, and cross-process file-lock dedup.
  • writeSidebarState() computes killswitch/quota/backoff for main and fallbacks and persists it for the TUI.
  • Adds /claude-killswitch command to view, enable/disable, and set per-account thresholds.
  • Exposes the TUI via @cortexkit/opencode-anthropic-auth ./tui export and copies tui.tsx at build.

^{Written for commit 583586a. Summary will update on new commits. Review in cubic}

[cubic-dev-ai]

2 issues found across 16 files

<sub>Tip: cubic can generate docs of your entire codebase and keep them up to date. Try it here.

Fix all with cubic | Re-trigger cubic</sub>

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​opentui/​core@​0.2.15
	solid-js@​1.9.13
	@​opentui/​solid@​0.2.15

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: ? → npm/@opentui/solid@0.2.15 → npm/entities@6.0.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@6.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report