Small decisions. Interesting possibilities.Submit contentSubmit
Surf CLI preview

Surf CLI

A Chrome control CLI with an optional Jev-driven semantic action loop.

Added to Jevfast

How it uses Jev

Surf’s optional semantic browser workflows send a bounded current-page observation and allowed candidate actions to Jev. Jev selects a supplied target or action; Surf applies its own thresholds, validates the browser scope and target, executes the step, then can ask Jev whether the requested outcome is visible.

What Jev decides

Filter page regions for a goalExample answers · not a recorded Jev response · Source ↗
Question 1 · chunk 0
YOUR APP
INSTRUCTION

Is chunk c1 relevant to this goal: change notifications?

STATE

The test evaluation page state about notification settings, with two text chunks: c1 describes notification delivery and c2 billing history; goal is to change notifications.

JEV · CHOICE
  1. relevant
  2. not_relevant

App workflow

  1. Observe the current page

    Collect a bounded, value-filtered page state and candidate controls or evidence.

  2. Choose a supplied target or action

    Ask Jev to select from the provided candidate IDs, including an explicit none option where applicable.

  3. Validate and execute

    Apply decision thresholds and verify the pinned browser scope and unchanged target before carrying out an allowed action.

  4. Check the requested outcome

    Observe the page again and ask Jev to judge whether the requested result is visible; stop on success, uncertainty, or workflow limits.

Why it is interesting

The model chooses only from bounded browser candidates while Surf retains page-change checks, write permissions, step limits, and outcome verification.