All discussions

Model Buzz · Decision model

Jev

Recent community conversations about using Jev.

8 selected discussionsReviewed Nov 3, 2026
Community
Month
Latest discussions1–8 of 8 threads · Latest first
LINUX DO分区:开发调优Creator workflow report

Cooking-game creator compares Jev decisions with fast chat-model actions

ChefJeff’s creator describes a cooking prototype where a person and an AI share tasks. The AI reads structured kitchen state and chooses from legal actions, rather than interpreting the screen. In a small trial, the creator says Jev and other decision models were usable, but preferred DeepSeek V4.1 Flash with thinking disabled to reduce latency.

Show discussion detailsHide discussion details

In the repliesNo human replies were visible in the opened launch thread. The linked repository describes a beta with three levels and user-supplied model access; its default 200-call limit caps requests, not the dollar cost of a round.

This is a creator’s project promotion and early comparison, not an independent ranking. The current README documents checks with Jev and DeepSeek; other model routes are not all verified. No gameplay or latency test was reproduced for this summary.

Original October 21 at 12:07 UTC; original and linked README read October 23. The current repository permits a consented server proxy for Jev, alongside direct browser-to-provider routes.

Hacker NewsHacker NewsDecision-model evaluation

Jev experiment prompts discussion of wording sensitivity and human escalation

Zach Landes shared a trolley-problem experiment in which Jev selected among supplied choices rather than generating a chat response. Changing the wording and the order of consequences could change its selection. His linked write-up recommends evaluating decisions on real task data and explicitly cautions against sweeping AI-safety conclusions. The exercise tests hypothetical choices; it does not demonstrate a model's intentions or behavior in a deployed system.

Show discussion detailsHide discussion details

In the repliestomrod argued for keeping human help available when automated systems make consequential decisions. jagged-chisel replied that removing escalation paths was a problem before modern AI. Their discussion shifts the practical question from a model's answer to whether a person can challenge a bad decision.

The author distinguishes shared wording variants from independent tests. The experiment does not establish probability calibration or production reliability; exact hosted Jev revision is not established here.

HN story posted October 15 at 16:24:52 UTC, confirmed by its official API. Linked study dated October 14; human comments 50108895 and 50110121 checked October 16.

Hacker NewsHacker NewsEvaluation report

Jev evaluation pairs cheap claim checks with weaker legal results

Connor Frank published an evaluation comparing TypeSafe's Jev 1.13.0—a fixed-choice probability decision model rather than a conversational LLM—against 11 API systems using identical inputs and native structured outputs. On a 400-item SEC filing claim-verification task across 48 companies, Jev tied GPT-6 Astra, GPT-6.1 Sol and GPT-6 Luna at 97.5% accuracy (390/400) at approximately $0.02 per 1,000 cases. Across a 396-question LegalBench slice, Jev ranked last of all 12 systems with a class-balanced accuracy of 73.0% (trailing Haiku 4.5 at 73.2%), with other evaluated systems showing statistically significant raw accuracy leads after comparison correction. In confidence-calibration router tests, Jev automated 95% of queries but exceeded the 1.0% error budget with a 1.6% realized error rate.

Show discussion detailsHide discussion details

In the repliesThe HN API returned no comments at the snapshot; no reply-based assessment was available.

Vals reports these measurements; TechReadly did not reproduce them. LegalBench covered 12 public subtasks rather than the full benchmark, with possible training contamination. Latency tests used one residential machine and unequal concurrency. The HN submitter’s affiliation with Vals is unconfirmed.

HN submission 49984418 links Connor Frank’s October 6 Vals evaluation at https://www.vals.ai/blogs/independent-evaluation-of-jev. Jev returns fixed-choice probabilities; the findings do not establish general chatbot or legal-workflow superiority.

Hacker NewsHacker NewsDeveloper report

Developer Shares Jeff Local Decision-Model Tradeoffs

Creator firelex, who states they are unaffiliated with TypeSafe, shared Jeff, a suite of small local classification models featuring a Jev-compatible API. In tests not independently verified, firelex said fine-tuning for voice navigation raised held-out command accuracy from 32% to 96% at roughly 40 ms per decision. The creator cautioned that Jeff exhibits weaker multistep reasoning than Jev and noted benchmark comparisons used different test samples.

Show discussion detailsHide discussion details

In the repliesDiscussing routing alternatives, commenter nico described pairing embeddings with logistic classifiers for narrow tasks, noting reduced accuracy on reasoning-sensitive inputs. When derefr asked how to classify inputs needing complex reasoning without incurring latency penalties, nico responded that routing approaches remain experimental.

Jeff is an independent project and not an official TypeSafe release or direct equivalent to Jev.

Creator report and named replies; measurements and comparisons were not independently reproduced. In a follow-up, firelex disclosed receiving a DGX Spark from NVIDIA at GTC 2025 and later buying a second unit.

Hacker NewsShow HNWorkflow report

Decide CLI wraps Jev for shell-based triage and structured decisions

Decide creator vsekhar presented a command-line tool for putting Jev decisions into shell scripts. Their examples route support tickets, assess urgency and check for spam. The author describes fixed-choice, yes/no and ordered-level questions, confidence thresholds with fallbacks, JSON output, and exit codes that distinguish decisions from uncertainty or errors. Access requires a TypeSafe or OpenRouter API key.

Show discussion detailsHide discussion details

In the repliesH4kken said they use Jev to sort items in their own app, Greer, and see repetitive software tasks as a better fit than everyday personal requests, for which they prefer general LLMs. This was experience with Jev in Greer, not a test of Decide.

The author’s configuration uses jev-latest rather than a fixed version. Claimed speed and cost advantages were not independently measured.

Creator-led Show HN post and one substantive reply; both participants disclosed their project involvement.

Redditr/CloudFlareIntegration report

Developer Reports Jev Latency and Integration Traps on Workers AI

Reddit user oh_jaimito reported testing TypeSafe's `typesafe/jev` through Cloudflare's REST API, observing about 1.2 seconds for the first cold call and 340–480 ms afterward. The author said an unfunded request returned error 2021 and described account-specific AI Gateway top-up requirements. They also found answers nested under `result.result.answers` and advised gating `choice` decisions on the top probability rather than the rescaled confidence value. In their own tests, high-confidence outputs were useful while middle-band results were unreliable. The author said Jev beat an existing GPT prompt on hand-labeled client-sorting and news-triage tasks, but supplied no dataset size, baseline prompt, thresholds or result table.

Show discussion detailsHide discussion details

In the repliesOne commenter reported using Jev for issue triage inside a Cloudflare Worker and said it was performing well within a narrow scope. The commenter provided no logs, thresholds, error rate or sample size.

Cloudflare documents `typesafe/jev` as a third-party structured evaluation model with a 32,000-token context window and Noul, Choice and Score questions. The user's billing and performance observations remain setup-specific.

Personal reports from one r/CloudFlare thread reviewed September 23, 2026. Cloudflare documentation confirms model availability and response concepts, not the user's latency, funding experience or comparison with GPT.

Redditr/AIToolsPerformanceHands-on

OpenRouter Jev Gate Exposes an Unsafe Fallback Failure

Reddit user PoppaBear1950 reported wiring `typesafe/jev-1.13` into a Hermes gate for coding tasks. On one machine on September 20, the author measured 239–430 ms latency and $0.000013–$0.000027 per invocation. They found the working route at `POST /api/alpha/decisions`; standard chat and v1 decision routes and the `typesafe/jev-latest` alias failed in their tests. Different `choice` and `noul` response shapes also caused a nested probability lookup to treat valid scalar answers as zero. More seriously, an exception handler returned the first choice after API failures, reportedly classifying a large authentication refactor as a direct shell task and a failed command as complete. The author changed the gate to emit `unavailable`, apply risk-dependent policy defaults and expose whether a verdict came from the model or fallback logic.

Show discussion detailsHide discussion details

In the repliesNo substantive user replies, independent replications or threshold discussions were visible when reviewed.

The results cover one OpenRouter integration on one machine. Route availability, model identifiers, latency and per-call cost may change and do not constitute an OpenRouter SLA.

Single-user r/AIToolsPerformance report reviewed September 23, 2026. The post includes concrete request and failure examples, but no independent replication.

Redditr/ArtificialInteligenceDiscussion

Jev Prefilter Claims Draw Debate Over Cost and Novelty

Reddit user Babayaga1664 described two Jev prefilter workloads without publishing benchmark data. In one, long context previously went directly to an LLM to detect a concern and explain it; the author said Jev reduced the initial decision from 3–6 seconds to milliseconds and limited later LLM calls to flagged cases. In another, point-by-point yes/no checks against legislation reportedly shortened the context sent downstream. The post supplied no exact latency log, threshold, false-negative rate, evaluation set or Jev version, so the results remain personal workflow claims.

Show discussion detailsHide discussion details

In the repliesCommenters disputed the “revolutionary” framing, describing Jev as a fast classifier or oracle and suggesting it as a control layer rather than a new form of intelligence. One commenter warned that changing message history can invalidate cached context, meaning an extra decision call may increase cost in some pipelines. Another said Astra handled Jev-related experiments adequately, contrary to the author's criticism of frontier models.

TypeSafe describes Jev as returning typed probabilistic decisions instead of generated strings. The thread debates practical placement and novelty; it does not independently validate the provider's performance claims.

Personal reports and disagreement from one r/ArtificialInteligence thread reviewed September 23, 2026. No shared code, evaluation set or reproducible cost comparison was visible.

Selected and reviewed Nov 3, 2026. Summaries reflect individual posts and replies, not a community-wide verdict.