[marius-kilocode]

What Problem This Solves

The Integrated Browser rendered every page with prefers-color-scheme: light, even in a dark IDE. Sites that honor the color scheme, for example GitHub, stayed bright against the editor theme.

Why This Change Was Made

The Playwright context was created without a colorScheme, so it used Playwright's light default. The broker now takes a theme callback from the extension, sets colorScheme on new contexts from vscode.window.activeColorTheme, and exposes retheme() to re-apply the scheme to live pages when the IDE theme changes. High-contrast-light maps to light.

User Impact

Pages in the Integrated Browser follow the IDE theme, so prefers-color-scheme matches dark or light. Switching the IDE theme while the browser is open updates the page without reopening.

Evidence

• bun run typecheck, bun run lint, and bun test tests/unit/browser-broker.test.ts (56 pass).
• Real Chromium probe through the broker: a probe page reported DARK with a dark theme and switched to LIGHT after retheme().
• Manual check in an isolated VS Code instance: the Integrated Browser loaded a probe page in dark and followed the IDE theme when it changed.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (4 files)

• .changeset/browser-ide-theme.md
• packages/kilo-vscode/src/extension.ts
• packages/kilo-vscode/src/services/browser-automation/browser-broker.ts
• packages/kilo-vscode/tests/unit/browser-broker.test.ts

---

_{Reviewed by deepseek-v4.1-flash · Input: 59K · Output: 6K · Cached: 327.3K}

_{Review guidance: REVIEW.md from base branch main}