Jev chooses operations and targets from structured page actions. Separate text helpers supply typed values, and a multimodal pilot tracks progress. Input constraints are prompts, not deterministic guarantees. Hosted models receive page context and recent actions; local Laya decisions are optional, but other hosted components retain separate data flows.
How you can use it
Write browser-test steps in a text file, including the intended clicks and values to enter, then start a session and load that file from the terminal. Use a practice page first. Jev selects actions and targets; separate text and vision models handle typing assistance and progress checks.
Review what was entered and the resulting page rather than trusting instructions to enforce exact text. Hosted Jev is the default; local Laya decisions are also documented, so an OpenRouter key is not required for every decision path. Hosted components can receive page text, element details and recent action history.