Jev DSH Decision Engine

Not as a native package. The repository ships a DeepSeek Harness plugin installed by local path or a .tgz, plus one iPolloWork import that serves OpenCode, DeepSeek Harness, and Codex Harness from a single install inside Work. It states outright that it does not yet provide standalone native packages for OpenCode or Codex Harness.

No. Jev returns the choice, probabilities, confidence, and usage, and the plugin does not execute the recommended action, switch models, or reroute requests. The host agent keeps planning, explanation, argument construction, and tool execution, and the README notes a recommendation is not execution authorization, so external actions still follow the harness's own permission flow.

It makes a real, slightly billable request. A local status of configured only means the key is present in DSH credentials or Work's plugin authorization store, not that it works, which is why the docs tell you to run the connection test and report the results back before trusting a recommendation.

Each request is capped at 64 questions, 256 KiB up, 1 MiB down, and 20 seconds of total network time, with retries only for 429 and 529 and at most twice. There is no infinite retry, no background learning, and no global request interception, and errors are redacted rather than passing the upstream error body through.

Clone the repo, then run `dsh plugin add /absolute/path/jev-dsh-decision`; a `.tgz` package installs the same way. The plugin uses DSH's native dsh.bundle format and needs no source build. Configure TYPESAFE_API_KEY in DSH's credentials, then restart the running session.

Three tools and one skill: `jev_status` for local state, `jev_check_connection` for a real connection test, and `jev_evaluate` for structured evaluation, plus the `jev-decision` Skill. In iPolloWork the same actions appear as status, check-connection and evaluate through the existing extension interface.

It caps each request at 64 questions, 256 KiB, a 1 MiB response and a 20-second total network timeout, and retries only 429 or 529 errors up to twice. There is no unlimited retry, background learning or global request interception, and upstream error text is desensitized.