DONE is a suggestion to check
The README describes withholding DONE when the independent goal Noul is below 50%, instead of trusting the operation label alone.
Inspect the supporting source ↗REPOSITORY ANALYSIS
JevBrowserExt
A Manifest V3 Chrome port of jev-ultrafast: Jev picks the operation and DOM element in one request per step; a small chat model fills TYPE_TEXT.
E2 · source reviewedPublic material or source evidence was reviewed. A fixed-version source review requires checking a pinned revision; this is not a reproduction, performance endorsement, or safety guarantee.
- Stars
- 21
- Forks
- 2
- License
- MIT
- Last commit
- 2026-09-22
What Jev does here
Chooses CLICK, TYPE_TEXT, SELECT, SCROLL_DOWN, SCROLL_UP, PRESS_ENTER, WAIT, DONE, or BLOCKED and the matching DOM target in one request; PRESS_ENTER is a separate key control. Separate yes/no checks cover goal completion and a stuck loop.
Runs in the user’s own tabs without screenshots, and keeps the action, target, and typed string inspectable.
Fixed-version documentation and implementation material were inspected on 2026-10-24. The recorded task suite is author-reported and was not rerun here. Extension permissions and transmitted page data require separate review.
What task does this project fit?
Run bounded browser actions inside a Chrome extension rather than a separate automation browser.
Material analysed：
From input to action
- A content script observes actionable DOM elements; a background worker sends their table and recent history.
- Jev chooses operation and target; a separate model supplies TYPE_TEXT text.
- Independent goal/stuck checks and local freshness guards can withhold a proposed action.
Implementation details that matter
Failures reveal separate observer and model problems
The documented suite includes an occluded-card observer bug and an arXiv decision error even with links present. Adding context cannot repair every kind of failure.
Inspect the supporting source ↗When to choose it
Consider it when working in your own Chrome tabs matters. Use a dedicated test profile and inspect traces before enabling tasks with consequential actions.
How to inspect it yourself
Compare the README’s operation/target flow with the TypeSafe provider body. Trace PRESS_ENTER separately from TYPE_TEXT; confirm that “typed text” does not imply a submit action.
Limits of this review
- The recorded task suite is author-reported and was not rerun here.
- Extension permissions and transmitted page data require separate review.