Several other DSH-plus-Jev plugins appeared within days of the Jev launch. Why this one?

The README's own comparison says the difference is narrow and deliberate. This one is single-file plain ESM with no TypeScript toolchain, so copy and run; it reuses the DSH credential seam instead of demanding an env var or a plaintext key in the patch; and it retries with the short backoff the provider recommends for 429 and 529. The alternatives it lists cover ground this one skips on purpose, including mixing several questions into one state and dual transport through the official API and the Vercel AI Gateway.

Do I have to configure a key, or will it pick up what DSH already has?

Probably not. Resolution order is the plugin's own apiKey config first, then the TYPESAFE_API_KEY environment variable, then refs.TYPESAFE_AI_API_KEY in ~/.dsh/.credentials.yaml. That third path is the same credential seam DSH already uses for providers, so if you have configured TypeSafe there the plugin finds it with no extra setup and without putting plaintext anywhere. Model, timeoutMs and baseUrl live in a config.json under the DSH home plugins directory or in the cordis patch config block.

I hand-wired this plugin into my profile before the bundle existed. What happens on upgrade?

Your profile will refuse to start. Registering the same id in two places, once by your manual insert and once by the bundle, produces a duplicate loader entry id error and the whole profile fails to boot. The fix is to comment out or delete the manual entry and let dsh plugin add do the wiring. There is a second upgrade trap: host plugins are assembled at process start, so changes only take effect after restarting DSH.

Can the agent ask several questions in one call?

No, and the signature makes that visible. The tool takes a single state and a single question with an optional type, so options and levels belong to that one question. The README says as much in its comparison section: for multi-question states, dual gateways or advanced routing, use one of the other integrations it lists. The tests cover request construction for all three types, the validation error paths, and response parsing for the three answer shapes, all offline with no network calls.

What is the jev_decide tool signature?

It takes state and question as required, an optional type of noul, choice, or score, options for choice, levels for score, optional yes and no criteria for noul, and an optional model that defaults to jev-latest.

What are the required option and level counts?

A choice question needs at least two options and a score question needs at least two levels, ordered from low to high. Noul needs neither and returns a probability.

What does a jev_decide call return?

An object with model, type, answer, and usage, plus confidence and probabilities for choice and score. Noul returns the probability of yes as its answer.

CommunityJev Practices & Patterns

Dsh Jev Decide

A DSH plugin, published to npm, that registers one agent tool, jev_decide, so a coding agent can ask TypeSafe's Jev a typed question and get a calibrated probability instead of guessing from intuition.

See highlights

Open github.com

Stars: 4
Language: JavaScript
License: MIT
Published by: Community
Author: nanami-0713
Last verified: Oct 2026

nanami-0713/dsh-jev-decide

User repository on GitHub

View on GitHub

DSH plugin: register TypeSafe Jev (System One decision model) as an agent tool — jev_decide returns calibrated probabilities (noul/choice/score) for routing/triage/guardrail judgments, no text generation. 把 TypeSafe Jev 决策模型注册为 DSH agent 工具

Forks: 2
Last pushed: Updated Sep 2026

Repo stats from the GitHub API, cached Oct 2026.

About this project

把 TypeSafe Jev（"System One" 决策模型）接入 DSH：注册一个 agent 工具 jevdecide，让 agent 在需要"快而准的判断"时调用 Jev，而不是让对话模型凭感觉猜。. 插件配置的 apiKey（cordis patch config 或数据目录 config.json）. 数据目录 $DSHHOME/plugins/dsh-jev-decide/config.json（或 cordis patch 的 config:）：. v0.1.2 起包内自带 dsh.bundle（根目录 cordis.patch.yml）：dsh plugin add 会自动把插件装配进 profile，无需手写任何接线；纯 npm install 仍只装包不装配。. 发版即自动发布：git tag vX.Y.Z && git push --tags → GitHub Actions 以 OIDC 免 token 发布（带 provenance 签名），无需任何长期 npm 凭据。.

Quoted from the project's README. Read the full README.

Tagscommunity awesomejev catalog-import

Works forJev for Classification Jev for Routing Jev for Ranking Jev for Moderation

Used inJev for Software & DevTools

Languages: JavaScript

Highlights

Three question types in one tool: noul yes/no probability, choice with a full distribution, and score over ordered levels.
Zero build step, single-file plain ESM; the repo notes it consumes only defineTool from the host package.
Reuses the DSH credential seam at ~/.dsh/.credentials.yaml, so an existing TypeSafe key needs no duplication.
Ships its own dsh.bundle, so dsh plugin add wires it into a profile with no hand-written patch entry.

Watch out

The host does not inject its bundled dsh-tools into a plugin's module resolution chain, so a link: or local-path install needs npm install run inside the plugin directory to materialize the peer, and the semver prerelease match only selects the 0.1.0-rc.x tuple, which the author considers expected. The bundle arrived in 0.1.2, so anyone who hand-wired an insert on 0.1.1 will hit duplicate loader entry id and an unbootable profile unless they remove the manual entry first. The README also carries an ecosystem scan of four other DSH-plus-Jev integrations and is explicit that this one deliberately does only the tool registration, so multi-question calls and dual transports are not its job. Pricing and rate limits quoted there are provider-side figures that move with the model version, which is itself pinned in the default at a moving alias. Copy reviewed against the repository README on 2026-10-04, not from running it.

Questions about this entry

Short answers drawn from the linked project or page.

More Jev resources like this

jevshield

Framework-agnostic guard layer that puts Jev in front of an agent's tool calls: a Choice risk tier, a Noul destructiveness check and a Score blast radius decide allow, deny or ask.