Repository navigation
fix(browser): 0.13 pick of #39267, reinstall the engine by itself after an update - #39476
Conversation
UX Review (Opus 5.5) — ⏭️ skippedRevision |
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Nothing blocks: this is a faithful 0.13 pick of #39267, the one hand-ported hunk keeps the same repair semantics, and nothing is taken away. [DESIGN-REVIEWED] 58ad666 Description read[DESCRIPTION-READ] 1744fba2f7a01291a73b1fc99562ad36ffadc6ffa35be0d7c1681b2aa1a666fd That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
First Principles Review (Opus 5.5) — ✅ PASSPremise-level review of First-Principles-Verdict: PASS This is a straight release pick of #39267. It finishes the startup auto-install that already ships by covering an interpreter removed later, so no new product shape needs a decision. Notes
What this change shipsInventory (6 items) — 5 justifiedIntent: after an update deletes the venv's interpreter, 0.13 users get the browser engine reinstalled without clicking Install. This is a FIX.
[FIRST-PRINCIPLES-REVIEWED] 58ad666 Description read[DESCRIPTION-READ] 0d7b8f7fd0fab658716935e3bc0c7fa9354ed37af649d22eceb6af3ce54dcba8 That sha256 names the PR description this verdict read. Recompute it with |
Opus 5.5 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
Problem / Motivation
Goal: 0.13 users get the browser engine reinstalled by itself after an update, without clicking Install.
This is the 0.13 pick of #39267, the user-reported sibling of #39265 (which reached 0.13 through #39387). After every update, Settings > Browser showed Install with no reason, and the agent's browser tool said browsing is not set up.
Why it matters
Anyone on a packaged release that keeps each version in its own directory loses the browser after an update until they click Install. 0.13 is the release where that experience should be fixed, and #39265's fallback fix is already on it.
Not a goal
run_browser_oprefactor on main); it is a feature, not a prerequisite.What changed (motivation → approach → change)
git cherry-pick -x c8ff0adbof #39267 onto release/0.13.0. Every file applied cleanly except one hunk insrc/kiro_crew/dashboard/handlers/browser_ops.py. On main that hunk sits inrun_browser_op, which #39022 added; release/0.13.0 still has the route-levelapi_browser_op. The hunk is hand-ported to that shape: it reads the dashboard state fromrequest.app.get("state")and answers withweb.json_response, which is the form #39267 had before main's refactor. The repair logic, thebrowser_repairinganswer and the tests are the same as on main.repair_browser_harnessand the startup re-check (browser_harness_status.py)browser_repairing(browser_ops.py)Backwards compatibility
Compatible: only a home whose install broke after startup behaves differently, and that home could not browse before.
Removes nothing: no key, route or field is removed or narrowed.
Tests
release/* gets no backend test lanes in CI, so the related files ran locally on this branch, single process (
-n0): the five files #39267 touches or guards (123 passed), then everytest/test_browser*.pyplustest/test_mcp_browser_tool.pyin two sequential batches (865 and 841 passed, 1 skipped).Proof: not provable -- other: a pick of #39267, whose Proof line on main was PROVEN at head c435961
Manual verification
N/A — same change as #39267 on main; unit coverage drives the dangling-link state.
Real-machine verification
N/A -- a pick; the base behaviour was checked on a packaged release for #39267 and a packaged 0.13 build of this branch is not available from this setup.
Related Issues
Part of #39254
Sibling sweep
Siblings: none -- this is a pick of one main fix; #39267's own sweep covered the browser handlers.
Pattern harvest
Not generalizable: a release pick of one fix whose pattern harvest is on #39267.
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...); PR Hygiene does not count commits