SSimon Meng@meng_shengyu𝕏 A Chinese team open-sourced a remake of Jev in Shanghai, reportedly above 9B parameters and beating the original. StartLux-Decision focuses on picking the best reply from given options, avoiding lengthy drafts from large models.
FfreeCodeCamp.org@freeCodeCamp𝕏 In this freeCodeCamp tutorial, learn to build an AI-assisted customer support system with Next.js and Jev, covering ticket intake, AI triage, human review, and privacy-safe handling of feedback scattered across inboxes, forms, and social media.
FfreeCodeCamp.org@freeCodeCamp𝕏 Learn how to build an AI-assisted support system with Next.js and Jev to handle feedback scattered across inboxes, forms, and social media. Covers ticket intake, AI triage, human review, and privacy safety.
GGreg Glazewski@Greg_GL_87𝕏 A user on X complains that after running out of tokens, they can't top up Jev due to the spam check, and they '@' TypeSafe AI for help.
The post shows how a free Jev lab lets AI read a ticket state and answer three typed questions in one call: urgency, owning team, and action timeframe—a clean blueprint for agent builders.
WWinston B.@DoDataThings𝕏 Jev makes ~38K turn-level forecasts across 2,029 calls using only structured inputs — turns, tool calls, workflow stages, and timing — at a 118 ms median, without touching caller names, addresses, or health data.
Jev doesn't write; it reads a situation and returns a number. For example, 100 support emails were sorted in 1.4 seconds, with a bigger model as backup, 96 were correct for about 7 cents.
FFaiz Hadiyan@faizhadiyanx𝕏 Jev acted as a receptionist, handling 2,029 real phone calls with a median response time of just 118 ms. It enables 24/7 customer service that never gets tired or moody, ideal for phone-heavy businesses.
NNike_Zoldyck@Nitin_wysiwyg𝕏 User reports being unable to add credits for JEV on TypeSafe AI even after adding card and billing address, plus Cloudflare blocking their LAN IP, requiring cookie deletion to log in, and overall site bugginess.
NNitesh Sharma 🛠️@nitesh_s11𝕏 Compared Jev and Claude Opus 5 on 3,080 support tickets. Sending only Jev's low-confidence answers to Opus yields 84.0% accuracy while still being 3.5x cheaper than Opus alone. Discusses three deployment strategies: Opus for everything, Jev for everything, or Jev first and Opus when unsure.
A user shares wiring Jev 1.13.0 (TypeSafe, System One) into their support desk: state in, typed questions in, decisions out, automating calls previously done by hand.
When asked where the ticket belongs, Jev returned billing at 0.84. When the question was changed to where the root cause could be fixed, the same ticket was classified as engineering. This shows how question phrasing affects Jev's analysis.