Skip to content

docs: add model suitability guidance#325

Closed
honor2030 wants to merge 1 commit intobrowser-use:mainfrom
honor2030:docs/model-suitability
Closed

docs: add model suitability guidance#325
honor2030 wants to merge 1 commit intobrowser-use:mainfrom
honor2030:docs/model-suitability

Conversation

@honor2030
Copy link
Copy Markdown

@honor2030 honor2030 commented May 8, 2026

Summary

  • Add a short "Choosing a model" section to the README
  • Clarify that browser-harness does not yet maintain a definitive supported-model list
  • Document model capabilities that matter for browser-harness: skill following, helper editing, retrying from errors, screenshot/page-state use, and context retention

Test Plan

  • git diff --check
  • PYTHONDONTWRITEBYTECODE=1 python -m pytest -q -p no:cacheprovider tests → 94 passed
  • python -m build → sdist and wheel built successfully

Refs #235


Summary by cubic

Adds a "Choosing a model" section to the README with clear suitability guidance for browser-harness. It notes there’s no definitive supported-model list and summarizes required capabilities (follow skills, edit helpers, retry on errors, use screenshots/page state, retain context), with tips for smaller/self-hosted models and a link to benchmarks in #235.

Written for commit f2f1f9c. Summary will update on new commits.

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

@Alezander9 Alezander9 closed this May 9, 2026
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