Question 1

How is this different from just picking a reasoning level by hand?

Accepted Answer

The plugin automates the case where you forget, not the case where you cannot decide. DSH reasoning levels are manual, so a chat greeting burns high and a complex refactor goes out at low because nobody adjusted the dial. The README's own example shows the asymmetry: one Jev call per turn costs about 500-800 tokens and one to two seconds. The chip next to the model selector shows the level and confidence, and hovering gives the reason, but it lives only in process memory and disappears on restart.

Question 2

One Jev call per message or per turn?

Accepted Answer

Per turn. Jev is asked once before the first model call of a turn, and every step and every retry inside that turn reuses the cached level, with the rewrite applied to the request config. The interception happens at agent/pre-step to catch the current user message before it enters the log, and the decision result is pushed to the browser through a projection that moves exactly once per turn as a trigger. That is also why the cost stays negligible relative to the tokens saved on a cheap turn.

Question 3

What stops it choosing off for a one-word continue?

Accepted Answer

The context envelope plus exactly one hard rule. Isolated, the word continue would be judged off even if the previous turn was designing a distributed transaction engine, so the plugin summarises the previous turn's facts, the effort used, what the user said, where the assistant got to, the activity counts, whether it finished and any unfinished todos, at roughly 500-800 tokens with no transcript, tool output or code. If Jev says the message continues and the previous work was unfinished, the level is not lowered below the previous one.

Question 4

Where does the API key end up?

Accepted Answer

In DSH's credential service, the same chain used for custom providers under Settings to Models. The settings field for the API key only writes and reports status, and the status contains no field capable of holding the key itself, so it is never transmitted back to the browser. Resolution order is inherited process environment, which is read-only and highest priority, then ~/.dsh/.credentials.yaml at mode 0600, then the launch directory's .env, then ~/.dsh/.env. When a higher layer is occupied the interface says so rather than accepting a save that would have no effect.

Question 5

How do I install the effort selector into DSH?

Accepted Answer

Run dsh plugin --profile web add github:justhalfbit/dsh-plugin-jev-effort-selector, then restart dsh web. The command writes the package into the profile and appends it to dsh.profile.bundles.

Question 6

What confidence threshold and timeout does the plugin default to?

Accepted Answer

A confidence threshold of 0.6, below which it picks the higher of the two most likely levels, and a 5000 ms timeout after which it reuses the level already resolved for the call.

Question 7

Which DSH versions does the plugin support?

Accepted Answer

One release supports both DSH 0.1.5 and 0.1.7, detecting the settings wiring generation automatically at runtime.

Dsh Plugin Jev Effort Selector

Highlights

Questions about this entry

More Jev resources like this

From the Jev community