Question 1

Will this take over my agent loop or switch my model?

Accepted Answer

No. It reads agent state, consults Jev or local rules, and calls pi.setThinkingLevel(). It does not switch models, modify code or take over the agent loop. A manual level change puts it into manual-override, which stays silent until the next task starts.

Question 2

What happens if the Jev endpoint is down or I never configured one?

Accepted Answer

It prompts once, then keeps working on local rules: low for document tasks, medium for implementation, debugging and tests, high for architecture and optimization. The status bar shows which source is in play, with jev:medium(rules) or jev:medium(fallback) when the model is not answering.

Question 3

How do I stop it flip-flopping the level mid-task?

Accepted Answer

Several brakes are built in: at most one level per adjustment, at most two upgrades and two downgrades per task, a stability window before any downgrade, a cooldown on Jev calls and a manual override. A fresh reasoning failure can bypass the cooldown, since that is the case you want caught quickly.

Question 4

How much of this is verified, and against what?

Accepted Answer

The repo ships offline unit and integration tests plus a live suite behind JEV_LIVE=1, a two-probe ping and a 3-seed A/B benchmark, with results and charts in its validation document. Every decision is also written to JSONL. The main caveat is that task typing is keyword-based, not learned.

Question 5

How do I install it into pi?

Accepted Answer

Register the repository in pi's ~/.pi/agent/settings.json under the extensions array, or load it for a single session with pi -e ./index.ts. The router then only reads agent state and calls pi.setThinkingLevel(), without switching models or modifying code.

Question 6

What thinking levels can it pick, and where does the key come from?

Accepted Answer

It chooses between low, medium, high and xhigh. The API key is resolved in order from config.apiKey, then JEV_API_KEY, then the cc-switch credential store, and without an endpoint or model it prompts once and falls back to local rules.

Question 7

What commands does it add?

Accepted Answer

/thinking-router toggles automatic routing, /thinking-router status shows the current level, source, counts and log path, /thinking-router test makes one real Jev call, /thinking-router set changes a config value, and /thinking-router log shows the last five decisions.

Pi Thinking Router Jev

Highlights

Questions about this entry

More Jev resources like this

From the Jev community