Skip to content

feat(browser-fast): add read-only Jev MCP adapter - #20

Open
makoto075 wants to merge 1 commit into
edinetdb:mainfrom
makoto075:feat/browser-fast-phase1
Open

makoto075 wants to merge 1 commit into
edinetdb:mainfrom
makoto075:feat/browser-fast-phase1

Conversation

@makoto075

Copy link
Copy Markdown

Summary

Add browser-fast, a local stdio MCP adapter around pinned Jev Ultrafast for bounded, read-only browser navigation and query tasks.

Phase 1 focuses on safe browser automation with explicit policy enforcement, independent verification, and redacted traces.

What this adds

  • local browser_fast_run MCP tool
  • pinned Jev Ultrafast upstream revision
  • URL and DNS safety checks
  • same-site/domain boundary enforcement
  • read-only action policy
  • bounded step budget
  • fresh-observation verification
  • screenshot-free redacted JSON traces
  • Browser Harness integration
  • strict JSON Schema text-helper output
  • safe text-helper failure classification
  • OpenRouter require_parameters for supported structured output endpoints only

Safety boundaries

Phase 1 explicitly blocks:

  • authentication/login flows
  • password / OTP / MFA / API key input
  • financial transactions
  • buy/sell/order/payment actions
  • email/message sending
  • publishing/posting/comments
  • uploads
  • deletion
  • account changes
  • arbitrary model-generated JavaScript
  • model-generated selectors

Jev DONE alone is not treated as success. Final success requires an independent verifier against a fresh browser observation.

Validation

  • ruff: PASS
  • pytest: 108 passed
  • live Wikipedia smoke: 3 / 3 verified
  • Browser Harness doctor: PASS
  • environment check: PASS
  • upstream Jev source modified: no
  • lock drift: no
  • secrets committed: no
  • traces committed: no

Reliability note

An earlier live validation observed an intermittent text-helper MODEL_ERROR with 2 / 3 verified runs.

The text-helper boundary was subsequently hardened with strict JSON Schema output and safe failure classification. The final acceptance run completed 3 / 3 verified.

This does not claim that intermittent provider-side failures are impossible; failures remain fail-closed and are now safely classifiable without logging raw model content.

Known Phase 1 limitations

Unsupported in this phase include:

  • Shadow DOM
  • iframe/frame interaction
  • canvas interaction
  • uploads
  • popup tabs
  • nested scrolling
  • arbitrary keyboard widgets
  • screenshot/vision fallback
  • auth flows
  • transactions
  • TradingView-specific behavior

Scope

This PR intentionally contains only:

  • .gitignore entries needed for browser-fast
  • mcp/browser-fast/**

No unrelated RC2/RC3 integration changes are included.

@makoto075

Copy link
Copy Markdown
Author

Hi, the GitHub Actions workflow for this PR is awaiting maintainer approval. Could a maintainer please review and approve the workflow run when convenient?

Local validation passed: ruff, all 108 pytest tests, and the final Wikipedia live smoke test (3/3 verified). The upstream CI run is still pending approval.

Thank you for your time!

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.

1 participant