Top Repos· Jev-Based· Demo· Last updated

brnyxx / jev-ra

“Browser use for coding agents, 3-5x faster than browser-use. MCP server + CLI; TypeSafe Jev decides every step in 300 ms.”

Jev-Based rank #163In Demo #35

TL;DR

brnyxx/jev-ra showed up as Jev / System One related work: Runnable demo or product experiment that uses Jev as a decision layer.

The author describes it as: “Browser use for coding agents, 3-5x faster than browser-use. MCP server + CLI; TypeSafe Jev decides every step in 300 ms.” That is their claim, not a bench this site ran.

Who it’s for

What’s inside

Top-level entries on GitHub at generation time: .github, .gitignore, .pre-commit-config.yaml, AGENTS.md, CHANGELOG.md, CODE_OF_CONDUCT.md, CONTRIBUTING.md, LICENSE, README.md, SECURITY.md, SUPPORT.md, THIRD_PARTY_NOTICES.md, assets, corpus. Read those before you trust a one-line install.

How to use

  1. Clone and follow the author’s Python toolchain. Do not invent a package name.
git clone https://github.com/brnyxx/jev-ra.git
cd jev-ra
  1. If the project calls hosted Jev, you still need a TypeSafe console key or a documented gateway.
  2. Send a complete state and typed questions. Code owns control flow after the probabilities.

Hosted Jev still looks like a function call — wrapper or not:

{
  model: "jev-1.13.0",
  state: { source: "brnyxx/jev-ra", brief: "..." },
  questions: {
    gate: { type: "noul", instructions: "Should we act on this state?" },
    route: { type: "choice", instructions: "Pick one next system.", criteria: ["code", "review", "human"] },
  },
}

Try this

One typed action per frame

Using brnyxx/jev-ra, send Jev a text brief of the current screen and ask for Choice{click, type, wait, give_up}. Do not ask Jev for coordinates or screenshots — it is text-only.

Schema-safe ≠ correct

On a case brnyxx/jev-ra gets wrong, write down the schema-legal answer it returned and the human label. Do not “fix” it by asking Jev to generate an explanation.

FAQ

Does this replace the TypeSafe SDK?

Only if the author implemented a full client. Most harnesses still call the vendor SDK or raw HTTP.

Are the star chips live?

Star, fork, and watcher chips refresh from the public GitHub API via a scheduled job. The prose on this page is editorial.

Sources

Public repository metadata and TypeSafe documentation. No private claims.