Small decisions. Interesting possibilities.Submit contentSubmit
Pi Interactive Shell preview

Pi Interactive Shell

An interactive terminal extension that can use Jev to select useful output from captured command logs.

Added to Jevfast

How it uses Jev

The semantic supervisor sends a structured terminal observation to Jev with Noul checks for configured conditions and a Choice for visible attention state. When an action registry is present, it also asks per-action safety questions and a bounded action Choice; application thresholds gate action execution.

What Jev decides

Classify terminal stateExample answers · not a recorded Jev response · Source ↗
Question 1 · attention
YOUR APP
INSTRUCTION

Choose the primary visible state using only explicit current evidence. Choose “other” when the text is generic or ambiguous and contains no explicit request, completed outcome, active work, or exhausted blocker.

STATE

A bounded terminal observation: task/watch context when configured, session fields, viewport, recent output, and recent action IDs.

JEV · CHOICE
  1. working
  2. waiting_input
  3. waiting_approval
  4. presenting_result
  5. blocked
  6. other

App workflow

  1. Capture terminal state

    Build an observation from the session, viewport, recent output, and recent action IDs.

  2. Ask for semantic judgments

    Request configured Noul checks and an attention Choice; include per-action readiness and action-choice questions only when a registry is available.

  3. Validate and route answers

    Parse the typed response and map attention, watches, and action answers into supervisor decisions.

  4. Gate or report action

    Apply confidence, probability, readiness, and session policy checks before a registered action; otherwise observe, notify, stop, or wait.

Why it is interesting

Terminal text is explicitly treated as untrusted data, while action IDs and permissions come from a pre-authorized registry rather than model-generated commands.