Small decisions. Interesting possibilities.Submit contentSubmit

How it uses Jev

Jev repeatedly selects a bounded operation from results observed in the user's real Chrome session, such as searching, opening a specific post/profile, reading comments, or finishing. The socai CLI executes the selected command; its result is returned for the next Jev decision.

What Jev decides

Illustrative routing requestExample answers · not a recorded Jev response · Source ↗
Question 1 · route
YOUR APP
INSTRUCTION

Choose the one supported workflow that should execute this request. Honor the explicit platform if present; choose unsupported for requests outside read-only social search.

STATE

Request: “Find handmade art on social platforms.” Requested platform: auto. Supported workflows: read-only search on Instagram, TikTok, and LinkedIn (default capabilities).

JEV · CHOICE
  1. instagram_search
  2. tiktok_search
  3. linkedin_search
  4. unsupported

App workflow

  1. Translate the research goal

    The run prepares platform and operation candidates from the goal and current browser state.

  2. Choose an operation

    Jev selects a permitted search, profile/post opening, comment read, explicitly requested TikTok media download, inspection, or finish action.

  3. Execute and observe

    socai runs the chosen CLI command in Chrome and returns a result summary; attempted operations are removed from later candidate sets.

  4. Compile a report

    The run stores choices, commands, observed summaries, and source links, then produces evidence-linked cards, tables, or a report with partial-result status when blocked.

Why it is interesting

The loop grounds later choices in captured results and restricts Jev to offered CLI operations and observed or user-provided targets; unsupported, malformed, and low-confidence choices do not execute.