Follow T3's server config live in the TUI

[krishhgg]

The TUI now follows T3's server configuration live, so provider and model changes reach its chips and open menus. Reconnects keep the last configuration until a fresh snapshot arrives. Servers that refuse the subscription retain the existing menu-time reads.

Parent PR #21 has merged. This PR targets master. It also removes the walkthrough requirement at the user's request.

Verification

Sol reviewed and ran these at 15af96bfbdacfccb57e21e7021f4e75ba5f70e1f:

• git diff --check e15c522..15af96b: passed.

• cargo fmt --all -- --check: passed.

• cargo clippy --locked --all-targets -- -D warnings: passed.

• cargo test --locked: all 293 passed, comprising 274 library, 2 main, 9 CLI and 8 fake-server tests.

• macOS: SUCCESS

• Linux build (unsupported): SUCCESS

The new tests exercise the actual RPC client against fake WebSockets and the full App against an offline client. They cover exact empty subscription payloads, cursor-free fresh snapshots, backoff reset, cancellation during connect/retry/stream, request-scoped legacy refusals, preservation of the shared shell watch, live menu/chip changes, selection identity, draft preservation, late unary results and fallback reads. No real T3 server, Keychain or user settings were used. Greptile reviewed the same commit, gave it 5/5 and found no actionable issues.

Decision log

What I noticed

The TUI refreshed provider data at startup and when a menu opened. Provider notices need live configuration even with no menu open.

How I confirmed it

The pinned nightly f570bd21663f56ce94c41829d3b7d72886e25a34 defines subscribeServerConfig with an empty payload, version-1 snapshots and field replacement events. Its client reducer keeps unrelated fields when a delta arrives. The new fake-server and App tests confirm the corresponding Rust behavior.

Options

Use the shared RPC connection with a snapshot-based config watcher. Keep shell and thread subscriptions sequence-based. Preserve unary server.getConfig reads for servers that refuse the config subscription. Polling and a new connection for config were unnecessary.

What review changed

Sol found a formatter difference and requested WebSocket and App coverage. Claude fixed formatting and wrote six WebSocket tests and seven App tests, in addition to the three reducer tests. The compatibility question was checked against T3's request-scoped unknown-method test and refusal frames. Those refusals stop only the config watch and trigger unary fallback. Formatting, Clippy and all tests now pass. Greptile's final review found no actionable issues.

Known limits

This adds no provider banner, setup action, theme subscription or usage-limit action. Configuration survives transient reconnects until a new snapshot. A connection-wide protocol defect still retries as other watchers do; it is not treated as an unknown-method refusal. Compatibility testing uses fake frames and the pinned T3 contract, not a live legacy server. This PR changes no TUI layout and has no new visual captures. The first-ten audit's CI, Greptile context and unrelated CLI output gaps are separate maintenance work.

Confidence Score: 5/5

The PR appears safe to merge; no actionable issues were found.

Summary

The TUI follows T3’s server config over the existing shared WebSocket.

• The TUI follows T3’s provider and model changes while it stays open.
• Pull requests now use a short description and a five-part decision log.

No actionable issues were found. The diff’s whitespace check passed; this review did not run the test suite.

krishhgg explicitly leaves provider banners, setup actions, theme changes and usage-limit actions out of scope. Connection-wide defects still retry. Live legacy-server testing, new visual captures and unrelated maintenance work are also documented limits.

krishhgg explicitly documents preserving the draft when its provider disappears while its chip shows the thread’s model. krishhgg also explicitly requested removing the walkthrough requirement.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Shared RPC connection] --> B[Config subscription]
  B --> C[Snapshot or field change]
  C --> D[Update held config and revision]
  D --> E[Refresh chips and open menus]
  B --> F[Connection drops]
  F --> G[Keep config and retry]
  G --> B
  B --> H[Request refused]
  H --> I[Read config when menus open]
  J[Unary config answer] --> K{Revision still matches?}
  K -->|Yes| D
  K -->|No| L[Ignore old answer]

Loading

_{Reviews (1) · Last reviewed commit: "docs: record the live server config in t..." · Reviewed by Greptile}