Skip to content

fix: agent self-recovery when 0 browsers connected (issue #40) - #51

Open
iAstro wants to merge 1 commit into
Tencent:mainfrom
iAstro:fix/issue-40-no-browser-recovery
Open

fix: agent self-recovery when 0 browsers connected (issue #40)#51
iAstro wants to merge 1 commit into
Tencent:mainfrom
iAstro:fix/issue-40-no-browser-recovery

Conversation

@iAstro

@iAstro iAstro commented Jul 31, 2026

Copy link
Copy Markdown
  • Add 0-browser recovery protocol in SKILL.md: agent should self-detect and self-launch browsers before falling back to user interaction
  • Update NoBrowserConnected error hint in render_error.rs with detailed ACTION and FALLBACK branches for different agent capabilities
  • Update NO_BROWSER_HINT in status.rs and doctor.rs with consistent two-case FALLBACK
  • Clarify that BrowserSkill never launches browsers itself

- Add 0-browser recovery protocol in SKILL.md: agent should self-detect and
  self-launch browsers before falling back to user interaction
- Update NoBrowserConnected error hint in render_error.rs with detailed
  ACTION and FALLBACK branches for different agent capabilities
- Update NO_BROWSER_HINT in status.rs and doctor.rs with consistent
  two-case FALLBACK (can detect vs cannot detect)
- Clarify that BrowserSkill never launches browsers itself — browser
  launch is always the agent's responsibility via shell commands
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