Skip to content

Comments

Fix DevTunnel warning flash on Settings page load#190

Merged
PureWeen merged 1 commit intomainfrom
fix/devtunnel-warning-flash
Feb 23, 2026
Merged

Fix DevTunnel warning flash on Settings page load#190
PureWeen merged 1 commit intomainfrom
fix/devtunnel-warning-flash

Conversation

@jfversluis
Copy link
Collaborator

Problem

When navigating to Settings, a warning banner saying devtunnel CLI not found flashes briefly before the async CLI detection completes. This is confusing — it looks like something is broken.

Root Cause

Fix

  • Changed devTunnelAvailable from bool to bool? (null = unknown/checking)
  • Added a third state in the template: when null, show a spinner with "Checking for devtunnel CLI…"
  • Warning only shows after detection confirms false
  • Added .tunnel-checking CSS class for the loading state

2 files changed, 19 additions, 3 deletions.

The devTunnelAvailable field was bool (false by default), causing the
'CLI not found' warning to flash immediately before the async check
completed. Changed to bool? (null = checking) and show a spinner
with 'Checking for devtunnel CLI…' while detection runs.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@PureWeen PureWeen merged commit 9ca7260 into main Feb 23, 2026
@PureWeen PureWeen deleted the fix/devtunnel-warning-flash branch February 23, 2026 15:58
PureWeen added a commit that referenced this pull request Feb 23, 2026
## Summary

Two changes to improve the Squad-based PR review workflow.

### How to use

1. Click **+** in the sidebar → select **PR Review Squad** from "📂 From
Repo"
2. Click the **orchestrator** session
3. Send: `Review PRs #194, #193, #191, #192, #190`
4. The orchestrator assigns 1 PR per worker, each worker dispatches 5
sub-agents across different models, and the orchestrator produces a
summary table with verdicts

The mode is automatically set to **Orchestrator** via `mode:
orchestrator` in `team.md` — no manual mode selection needed.

### Example output

The orchestrator produces a summary table like:

| PR | Verdict | Key Issues |
|----|---------|------------|
| #194 | ⚠️ Needs changes | cursor:pointer without click handler,
brittle test regex |
| #193 | ⚠️ Needs changes | Incomplete state sync → infinite unthrottled
renders |
| #191 | ✅ Ready to merge | Clean — concerns were pre-existing patterns
|
| #192 | ⚠️ Needs changes | GC-finalization test unreliable, flaky IP
test |
| #190 | ⚠️ Needs changes | Tests don't guard actual regression |

Each worker's detailed report includes only issues flagged by 2+ models
(consensus filter), with file:line references and severity ratings.

---

### 1. Restructure PR Review Squad for multi-model consensus

Replaces 5 specialized reviewers (bug-hunter, security-analyst, etc.)
with 5 generic reviewers that each independently perform a full
multi-model consensus review.

Each worker:
1. Fetches the PR diff via `gh pr diff` / `gh pr view`
2. Dispatches 5 parallel sub-agent reviews across different models:
   - 2× `claude-opus-4.6` (deep bug analysis + architecture review)
   - 1× `claude-sonnet-4.6` (correctness + edge cases)
   - 1× `gemini-3-pro-preview` (security focus)
   - 1× `gpt-5.3-codex` (code quality + logic errors)
3. Synthesizes findings using a consensus filter (2+ models must flag an
issue)
4. Produces a severity-ranked report with file:line references and a
verdict

### 2. Support `mode:` field in team.md

`SquadDiscovery` now reads an optional `mode:` line from `team.md` to
set the multi-agent mode automatically. Previously hardcoded to
`OrchestratorReflect`.

Supported values: `broadcast`, `sequential`, `orchestrator`,
`orchestrator-reflect`

```markdown
# My Team
mode: orchestrator
```

### Tests
- 6 new tests for `ParseMode` covering all modes + case insensitivity +
default behavior
- All tests pass

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.

2 participants