DeepSeek v4.1 flash on OpenCode pretty good A developer tool called shev, distributed as the npm package @noorslvt/shev, turns a single pasted message into one JSON decision containing an actionable string, a take_action boolean and a confidence integer constrained to the range [34, 100], running on either DeepSeek over the network or a small ternary MLX model locally. The tool records each decision to responses.json as response1, response2 and so on, and exposes those records to other models over MCP; it installs via a curl script, npm, or cargo, and the author warns that the unscoped npm name shev belongs to an unrelated project. A simple Jev-like decision maker. Without the hype. Hand it one whole message — an email, a ticket, a review, a doc, whatever you pasted out of the support queue — and tell it what you want done with it. It hands back one decision, as JSON: { "actionable": "Reply to Sam and cc finance about the overdue March invoice.", "take action": true, "confidence": 95, "generated response": "Hi Sam, ... the reply, written out " } That's the whole thing. No agents. No orchestration. No prompt engineering. No five-hundred-token preamble to memorise. One message in, one decision out, in a file you can just read. - Whole message, judged once. It doesn't chop the thing into paragraphs and it doesn't go line by line. One message, one decision. - You say what you want. It asks before it answers, and what you want done is what drives the reply it writes. - The answer has a shape. actionable a string , take action a boolean , confidence an integer, always in 34, 100 . No tuple you have to guess at. - Runs on your Mac if you want. DeepSeek over the network, or a small ternary MLX model sitting right there on the machine. Switch whenever. - It writes it all down. Decisions pile up in responses.json as response1 , response2 , … and other models can read them over MCP. One line, copy-pasteable: curl -fsSL https://raw.githubusercontent.com/aditauqir/shev/main/install.sh | bash Then type shev . The installer uses a user bin directory already on PATH where possible. Otherwise it adds a small, removable PATH block to your shell profile; open a new terminal and type shev —no manual shell edits needed. Prefer npm? npm install -g @noorslvt/shev shev This installs the package @noorslvt/shev , with the terminal commands shev and shev-cli . The unscoped npm registry name shev belongs to an unrelated project; do not use npm install -g shev for this tool. You can also install straight from the repo without the registry: npm install -g git+https://github.com/aditauqir/shev.git Both installers prefer a matching prebuilt release and otherwise build with Rust installing the minimal Rust toolchain if necessary . npm runs a postinstall step that fetches the right binary or builds it; macOS/Linux are supported by the npm launcher, and Windows users can use WSL. Recent npm releases gate install scripts. If your install is skipped, shev tells you what to run; you can also fix it up front: if npm blocked the install scripts: npm approve-scripts @noorslvt/shev or: npm rebuild -g @noorslvt/shev --foreground-scripts Got Rust already? Same thing, just as short: cargo install --git https://github.com/aditauqir/shev For full cleanup, whether installed with curl or npm, close other running shev sessions first: shev --uninstall --dry-run preview paths; delete nothing shev --uninstall confirm before removal or: shev --uninstall --yes This removes registered shev binaries, its saved keys/config, local model data, tracked chat records, unchanged tracked shev MCP registrations, and the exact PATH blocks added by its installer. A full npm-backed uninstall also runs npm's package removal. Modified binaries/profile blocks, externally managed weights, host recovery backups, unrelated host settings, non-chat metadata in export files, source checkouts, and shared tools/caches Rust, Node, uv, Codex, OpenCode are not deleted. You can also remove the npm package directly: npm uninstall -g @noorslvt/shev This removes the npm package and its binaries. Modern npm does not execute uninstall hooks , so it cannot also remove persistent settings/models/history or external MCP registrations. Use shev --uninstall for full cleanup; it handles the npm package removal too. Persistent npm data deliberately lives outside the package so a normal npm upgrade does not erase private keys, history, or model downloads. No background uninstall watchers or npm overrides are installed. - Best for local use: Apple Silicon — M1 or newer, 16 GB of RAM and up . - 8 GB will fit the local model too, but it's tight. - Everything else: runs anywhere with a DeepSeek API key. No Mac required.