NewPi Advisor
Use Jev screening to decide when a Pi coding agent should request a second opinion.
Added to Jevfast
NewHow it uses Jev
When proactive turn gating is enabled, the Pi extension periodically sends its recent conversation to Jev and asks whether an engineering advisor should be consulted before the executor continues. A sufficiently high YES probability triggers a separate advisor consultation; Jev does not perform the consultation or control the executor.
What Jev decides
Illustrative proactive advisor gateExample answers · not a recorded Jev response · Source ↗
Question 1 · should consult
YOUR APP
INSTRUCTION
Should a senior engineering advisor be consulted now, before the executor continues, based on recent_conversation?
STATE
The gate sends state with role=executor and recent_conversation containing the bounded conversation digest. The example describes the source-defined request, not a captured runtime conversation or Jev answer.
JEV · NOUL
YesNo
App workflow
- Check whether the gate is due
At turn end, the extension checks the configured turn interval, active ask_advisor tool, allowed model, session state, and consultation budget.
- Ask Jev about the current turn
When due, it sends the conversation digest and the should_consult Noul question. A failed or missing Jev response does not trigger proactive consultation.
- Consult and deliver advice
A YES probability meeting the configured threshold consumes a call and invokes the advisor. The extension delivers the advisor's text as a steer message and records the consultation.
Why it is interesting
The extension uses a small typed judgment to decide when a more expensive second opinion could change the next step. Its turn counter, model-access checks, call budget, and consultation remain ordinary application logic.