Skip to content

fix(tui): keep team navigation responsive during first worker open - #1951

Merged
santoshkumarradha merged 3 commits into
devfrom
fix/team-tab-clicks
Oct 26, 2026
Merged

santoshkumarradha merged 3 commits into
devfrom
fix/team-tab-clicks

Conversation

@santoshkumarradha

@santoshkumarradha santoshkumarradha commented Oct 26, 2026 •

Copy link
Copy Markdown
Member

A team strip can show workers whose conversations this window has not opened yet. Clicking one called the opening factory inside the UI input handler, so slow engine setup also blocked later tab clicks and typing. Already-open tabs were fast, which hid the defect in warm navigation checks.

Open independent cold conversations through the existing asynchronous opening path. Validate the team overlay after opening completes, preserving the originating manager and worker strip. Canceled results release their connection without selecting an outdated target. Held chats switch immediately; legacy shared connections retain their existing swap contract.

Validation drove actual TUI mouse clicks in a team created by a real manager starting two workers. All 72 model receipts use OpenRouter deepseek/deepseek-v4.1-flash; navigation made zero model calls.

  • Before: with the disposable engine paused for 2.168 seconds after a first worker click, the next manager click and typed probe remained invisible until the engine resumed.
  • After, on final source: the manager click and typed probe appear in 43.9 ms while the engine is still paused. Resuming does not steal selection or the draft.
  • The canceled worker opens later in 36.5 ms. An uncanceled delayed open shows feedback, then its actual history 30.6 ms after engine resume. Worker → manager → same worker before resume selects the latest worker in 44.1 ms after resume, without a lock error.
  • Entering the team cold from another chat through AI Teams or the Teams dropdown takes 33.8/31.9 ms and retains its manager and both workers. Sixteen normal manager/worker clicks take 12–39 ms, median 21 ms. Screen response is measured separately from engine wait and model latency.

Focused checks, make test-quick, and make pr-ready pass. All eight final TUI shards pass on their first run in 94 seconds. Independent Standards and Spec reviews have no outstanding findings. GitHub checks are pending.

Actual terminal captures remain local because direct PR attachment upload is unavailable.

@santoshkumarradha
santoshkumarradha marked this pull request as ready for review October 26, 2026 04:36
@santoshkumarradha
santoshkumarradha merged commit ed8bf75 into dev Oct 26, 2026
6 checks passed
@santoshkumarradha
santoshkumarradha deleted the fix/team-tab-clicks branch October 26, 2026 04:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant