Small decisions. Interesting possibilities.Submit contentSubmit

How it uses Jev

With Jev as the active classifier, the router sends the new request and recent dialogue. Jev returns route, continuation and optional activity decisions. Local policy maps this advice to a Claude model and effort while Claude Code keeps execution and provider traffic.

What Jev decides

Route the coding turnExample answers · not a recorded Jev response · Source ↗
Question 1 · route
YOUR APP
INSTRUCTION

Choose a route based on reasoning depth, uncertainty, constraints and verification difficulty.

STATE

The currentRequest.text and recentDialogue. Activity is included only when activity routing is enabled.

JEV · CHOICE
  1. micro
  2. low
  3. medium
  4. high
  5. uncertain
Question 2 · continuation
YOUR APP
INSTRUCTION

Does this request continue the recent task?

STATE

The currentRequest.text and recentDialogue. Activity is included only when activity routing is enabled.

JEV · NOUL
YesNo
Question 3 · activity
YOUR APP
INSTRUCTION

What must this turn produce? Omitted when activity routing is off.

STATE

The currentRequest.text and recentDialogue. Activity is included only when activity routing is enabled.

JEV · CHOICE
  1. code
  2. debug
  3. explore
  4. plan
  5. review
  6. ops
  7. docs
  8. uncertain

App workflow

  1. Collect context

    The hook gathers the current prompt and recent dialogue for the active classifier.

  2. Classify

    Ask Jev for route and continuation, plus activity when enabled.

  3. Apply policy

    Map the advice to configured model and effort routes; periodically reassess when configured.

  4. Execute

    Claude Code sends provider requests, streams responses, runs tools and reports usage.

Why it is interesting

The router separates required reasoning depth from the work the turn must produce. Local policy can combine those judgments and reassess long-running work without proxying Claude model requests.