What has actually shipped

Showing 20 of 20 items.

1. 18 Sept 2026Release

   In four days of frantic activity, the model itself has not moved once

   The SDKs have shipped, four gateways have picked it up, and the docs have been edited continuously — but jev-1.13.0 is still the only published version. No point releases. jev-preview remains a no-op alias pointing at the same weights, and TypeSafe's docs say so outright. There is no changelog page anywhere on typesafe.ai, and no GA announcement. If you are deciding whether to build on this, the contrast between the ecosystem's pace and the model's stillness is the thing to weigh.

   TypeSafe models page ↗
2. 18 Sept 2026ReleaseTypeSafe

   Python SDK 0.7.0 swaps its serialiser; the JavaScript SDK has not moved since launch

   typesafe-sdk 0.7.0 landed with a breaking change — serialisation moves from msgspec to pydantic — and adds response_model on system_one. That is the Python SDK's second release since launch. @typesafe-ai/sdk is still on 0.6.0 from launch day. If you are on JavaScript, expect to be a step behind. Both SDKs quietly existed before launch: the first public releases were 11 and 12 September.

   Python SDK changelog ↗JS SDK changelog ↗
3. 18 Sept 2026Availability

   Jev reaches OpenRouter and Cloudflare AI Gateway

   OpenRouter lists it in beta as typesafe/jev-latest and typesafe/jev-1.13, plus a pinned typesafe/jev-1.13-20260917 — the only dated model artefact that exists anywhere. Cloudflare's catalogue entry is typesafe/jev. Two cautions: this is Cloudflare AI Gateway, not Workers AI, which does not carry it; and Cloudflare's own page is undated, so 18 September is a "documented by" date rather than a go-live. Both list 32K context — the figure from TypeSafe's Primitives page, not the 64K on its Models page.

   OpenRouter ↗Cloudflare model page ↗Our reference →
4. 18 Sept 2026Benchmark

   First independent calibration study returns a split verdict

   A pre-registered community study across 8,576 responses found Jev calibrated on CLINC150 (ECE 0.0204) and systematically overconfident on Banking77 (ECE 0.0936). A separate check found that on rows where Jev reported confidence of 0.9 or higher, it was only 72.2% accurate. TypeSafe has still published no calibration metric of its own, so these are the only numbers that exist.

   ASSAY-001 ↗Confidence-bucket check ↗Our writeup →
5. 18 Sept 2026Community

   The question everyone is actually asking: is it just a BERT?

   The dominant framing on r/LocalLLaMA is that Jev is encoder-style classification rediscovered — "like people finally rediscovering the use of LMs before autoregressive sampling… like the good old BERT." The mechanism explanation that circulated most: "they just split the fields and process them in parallel. No diffusion, just batching and running through prefill only… That's why their 'output tokens' are 'free'." That is speculation — TypeSafe has published no architecture — but it is the misconception most readers will arrive with, and the founder himself answered "exactly right!" when a commenter called it a zero-shot classifier.

   r/LocalLLaMA ↗Our answer →
6. 18 Sept 2026Benchmark

   Someone actually measured the run-to-run variance

   The most useful number anyone has published, and it is a small one. A developer scoring code segments reported that identical calls varied by up to ±0.04 — "It's not deterministic. It's stochastic" — while still separating the cases cleanly: "it consistently flagged the segment with an error >0.95 and segments without an error ≤0.10." Their verdict is the honest middle ground between the marketing and the dismissals: "It's not exactly 'cold fusion' but it is useful." Do not write logic that depends on exact equality of a probability.

   r/LocalLLaMA ↗Shipping checklist →
7. 18 Sept 2026Community

   A note on reading Jev's apparent popularity

   At least seven Jev-related subreddits were created at or just after launch, several of them posting the same single-author material to near-zero audiences within minutes of each other. Treat subreddit counts and post volume as noise. The organic discussion is happening in a handful of places — r/LocalLLaMA above all — and GitHub star counts are the far more reliable signal. Notably, r/MachineLearning has not engaged with the launch at all, and r/LocalLLaMA's first thread landed a full day late.

   r/LocalLLaMA — first thread, 16 Sep ↗
8. 18 Sept 2026Community

   SDK issues pin down the hard limits

   An open issue against the JavaScript SDK documents the real API ceilings, quoted from the server's own rejections: "Too many choices. Must have at most 255 choices." and "Too many score levels. Must have at most 10 levels." It also reports that noul() called with no arguments serialises to a shape the API rejects with a 400 — and that the SDK's own test suite asserts the broken shape. Separately, state: null type-checks but returns 422 Field required.

   typesafe-sdk-js issue #6 ↗
9. 17 Sept 2026Dispute

   Analysts name the two costs the launch post leaves out

   The first substantive named-analyst commentary on the launch, and both points are ones a developer feels immediately. Stephanie Walter of HyperFrame Research on the engineering burden: developers "have to specify questions, possible outputs, thresholds, and escalation paths in advance for that part of the workflow, which could be a significant task." Paul Chada of Doozer AI on the audit gap: "A probability can show how confident a model was in a decision, but it does not explain why the model made that decision. That distinction could matter when enterprises need to explain or defend automated decisions to regulators or auditors."

   InfoWorld ↗When not to use Jev →
10. 17 Sept 2026Integration

    LangChain ships langchain-typesafe

    LangChain published a launch-partner integration with a TypeSafeClassifier and two experimental middlewares: ModelRouterMiddleware, which uses Jev to pick which model handles an agent run, and AutoModeMiddleware, which screens tool calls before they execute. Their framing is the useful part — the dangerous-action classifier every coding harness ships has been locked inside closed-source harnesses until now. Note the experimental namespace.

    LangChain blog ↗Our tutorial →
11. 17 Sept 2026ReleaseTypeSafe

    TypeSafe publishes a jaggedness page for jev-1.13

    TypeSafe added a documentation page listing nine failure modes of its own model — literal reading, arithmetic, date comparison, indirection, context rot, adversarial content, contradictory criteria, broken structural invariants, and generation. It is more candid than most model launches manage, and it includes a published counter-example where the same question asked as a Noul and as a Choice disagrees flatly.

    docs.typesafe.ai ↗Our walkthrough →
12. 17 Sept 2026Community

    The quickstart's documented answer does not reproduce

    A developer reported that TypeSafe's own Python quickstart returns billing at 0.67 rather than the documented technical — consistently, across 100 runs. The issue was still open at the time of writing. Whatever the cause, the lesson generalises: the documented output of an example is not a test result.

    typesafe-sdk-python issue #2 ↗
13. 17 Sept 2026Dispute

    A prior-art claim, and a rebuttal in the same thread

    A researcher posted that he had built the same architecture a year earlier, with an arXiv paper and open weights, and that a frontier lab had now shipped it as a breakthrough without a paper, open weights or a dataset. It drew a large thread — and a substantive rebuttal: another commenter argued the earlier work is "essentially a sequential PPO policy" while Jev is more general. He later walked the accusation back himself: "It was never stolen work. Just the architecture similarities." Both halves belong together.

    r/LocalLLaMA ↗arXiv 2503.23303 ↗
14. 16 Sept 2026Availability

    Vercel AI Gateway adds Jev as typesafe-ai/jev

    The first gateway to carry it, the day after launch, alongside an @ai-sdk/typesafe-ai provider package. Requires AI SDK 7.0.105 or newer and its experimental evaluate surface — Jev is a decisions endpoint, not a chat completion, so it does not slot into normal model-list tooling. It has shipped four point releases in about 36 hours, which tells you how new the integration is.

    Vercel changelog ↗
15. 16 Sept 2026Community

    Every top community repo now out-stars every official one

    Four days in, the largest Jev project is browser-use/jev-ultrafast at roughly 4,800 stars, followed by a Claude Code compaction plugin at ~2,750 and the SemIf reimplementation at ~1,500. TypeSafe's own most-starred repo is its agent-skills package at around 200 — and it has not been touched since before launch. Read that as genuine developer pull rather than as a judgement on the company; it is the clearest signal in a launch where post volume has been a poor one.

    browser-use/jev-ultrafast ↗fast-jev-compaction ↗
16. 16 Sept 2026Community

    Open reimplementations start appearing within a day

    The first open attempts to reproduce the interface landed on 16 September — reading logits directly from an open-weights model instead of generating JSON. One of them was posted while still named OpenJev; it was renamed to SemIf on 18 September, hours after reaching the Hacker News front page, bundling the rename with an independence notice and a trademark disclaimer. No cease-and-desist or contact from TypeSafe is documented anywhere — the sequence is suggestive, the cause is not on the record. It is the clearest evidence that the mechanism is not exotic; whether the calibration training reproduces as easily is a separate and much harder question.

    r/LocalLLaMA ↗Why it matters →
17. 16 Sept 2026Dispute

    “Frontier model” and “can't hallucinate” both take fire on Hacker News

    The launch thread ran to roughly 1,900 points and 490 comments, with the title edited within the hour to drop the multiplier claims. The sharpest objection: a type guarantee is not correctness, and an approval for an unauthorised action still satisfies the schema. Almeida conceded the point directly — "that's right, but because these models are probabilistic, it's also possible to be confidently wrong."

    Hacker News ↗Our analysis →
18. 16 Sept 2026Community

    The Register leads with the Doom demo — and the caveat

    Coverage focused on Jev playing Doom at roughly ten decisions a second for about $7 an hour. The caveat that matters: the model is fed structured game state as text, not pixels — enemy coordinates and distances — so, as one commenter put it, it is effectively looking through walls. TypeSafe's own note concedes a non-AI bot would play better; the demo is about latency, not skill.

    The Register ↗Our tutorial →
19. 15 Sept 2026LaunchTypeSafe

    TypeSafe AI exits stealth with Jev and a $40M seed

    TypeSafe AI, founded 2024 by Diogo Almeida (ex-OpenAI, InstructGPT), Erik Gafni and Sasha Sheng, came out of stealth with Jev — the first "System One" model, trained with a method they call Reinforcement Learning for Calibrated Decisions. The $40M seed was led by DCVC and announced in the company's own press release. Pricing: $0.042 per million input tokens, output free. A valuation around $200M has been reported secondhand, but traces to a single source we could not read — treat it as unconfirmed.

    TypeSafe launch post ↗DCVC ↗
20. 15 Sept 2026ReleaseTypeSafe

    Official Python and JavaScript SDKs published

    @typesafe-ai/sdk landed on npm on launch day (Node 20+), and typesafe-sdk on PyPI (Python 3.10+). Both read TYPESAFE_API_KEY from the environment and default to jev-latest, which currently resolves to jev-1.13.0. The Python package has since moved ahead of the JavaScript one on version.

    npm ↗PyPI ↗