Question 1

Could this let an agent do something my permission system would have blocked?

Accepted Answer

No, and the wording is deliberate: it is not a security boundary. The host sends the candidates it already allows, checks the recommendation against its own registry and permissions, and decides whether to execute. If Jev is disabled, unavailable, invalid or inconclusive, the host's normal path runs instead, and Jev never widens permissions.

Question 2

What does this add to my per-request cost?

Accepted Answer

Nothing until you turn it on. Optional surfaces are disabled by default and enabled by explicit flags such as JEV_SUPERVISION or JEV_BROWSER_FAST_PATH, the default demo provider is deterministic and offline, and the context filter is a deterministic shadow or conservative pass rather than an LLM summarisation. Providers are demo, OpenRouter Decisions or TypeSafe.

Question 3

Does anything actually happen with the recommendation?

Accepted Answer

Not on its own. The host executes and can then attach what happened to the decision under its correlation_id, which is what makes cases replayable offline. Routing stays advisory: jev_model_route recommends a host-declared profile for a future call, and the host is expected to measure outcomes before changing provider or model settings.

Question 4

Is the browser tool ready to depend on?

Accepted Answer

It is labelled experimental and carries its own caveats: reliability is validated against current real-browser fixtures, performance work is still in progress, and no browser speedup claim is made. The host still supplies approval, native execution and recovery, because jev_browser_step only recommends one bounded action and never starts a browser worker.

Question 5

How do I install it, and what does it require?

Accepted Answer

npm install --global jev-layer, then jev install --project /path/to/workspace, jev add generic and jev doctor. It needs Node.js 20 or newer and has no mandatory runtime dependencies; the default demo provider is deterministic and works offline, and jev mcp runs the stdio MCP server directly.

Question 6

Which providers can back the decisions?

Accepted Answer

A deterministic demo provider, OpenRouter Decisions, or TypeSafe. Optional Jev surfaces are disabled by default and fail open: if Jev is disabled, unavailable, invalid or inconclusive, control returns to the host's normal path, and Jev never widens permissions or guesses execution.

Question 7

What optional surfaces exist beyond jev_route?

Accepted Answer

Supervision returns bounded work-state judgments, model routing recommends one host-declared model profile, shadow compaction produces report-only keep/drop candidates, and context filtering reduces stale context. A browser fast-path recommends one bounded action from a host observation; these are enabled explicitly with environment variables such as JEV_SUPERVISION=1.

Jev Layer

About this project

Highlights

Questions about this entry

More Jev resources like this

From the Jev community