Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

Deploying DiffusionGemma-Jev (djev) just got a lot easier. You can now spin up a Jev API-compatible endpoint on Google Cloud Run using a single command. Performance is solid: ~35-60 ms for single step latency and batch@32 is ~100-123 requests/sec. It's a straightforward way to experiment without needing your own... show more

Google Gemma

101,753 subscribers

627,643 görüntüleme • 3 gün önce •via X (Twitter)

Eğitim Bilim & Teknoloji

Anya Rossi• Live Now

Private livecam show

31 Yorum

Google Gemma profil fotoğrafı

Google Gemma3 gün önce

Credits to @mmastrac and @dylayed. Original post:

Jonathan Ouyang profil fotoğrafı

Jonathan Ouyang3 gün önce

@bodonoghue85 Fastest bookmark of my life

Viren Khandal profil fotoğrafı

Viren Khandal3 gün önce

jev on blackwell in the big 2026 🥀 what are we doing

ORC KILLER profil fotoğrafı

ORC KILLER3 gün önce

but why ? jev is cheaper than $3/h and way better at it

Everlier profil fotoğrafı

Everlier3 gün önce

Infinite Jev unlocked

hey profil fotoğrafı

hey3 gün önce

Put some pressure on Gemini team so you guys can distill for Gemma 5 soon 😌

iMuffin profil fotoğrafı

iMuffin3 gün önce

this is exactly, what i asked for. thanks!

Vincent Myshinkye profil fotoğrafı

Vincent Myshinkye3 gün önce

This is the kind of deployment UX that makes experimentation actually accessible. Spin it up when you need it, pay while it runs, and let it disappear when you’re done. 🔥

Ibrahima Sarr profil fotoğrafı

Ibrahima Sarr3 gün önce

When I was seeing Jev explanation I was asking myself, isn't what DiffusionGemma already doing. Is it the similar, is it that Jev just has more hype?

Red Wizard 🔮 (e/acc) profil fotoğrafı

Red Wizard 🔮 (e/acc)3 gün önce

Coming to the Gemini API/AI Studio?

Sadnan profil fotoğrafı

Sadnan3 gün önce

lmao, didnt see this coming

The AI Therapist profil fotoğrafı

The AI Therapist3 gün önce

Single-ste latency is the real flex. 35ms means you can feel the stream before your coffee cools, smooth workflow vibes that actually respect a mom’s attention span. Efficient code looks good on everyone. 😊

TensorQuay profil fotoğrafı

TensorQuay2 gün önce

One practical limit in the repo: the Cloud Run recipe is set to one GPU instance and 32 concurrent requests. The 100–123 req/s figure is a warm batch result; it says little about the wait a new caller sees when that GPU is busy.

pysolin profil fotoğrafı

pysolin3 gün önce

google's like you want ML, we got ML

𓂀♎︎𓂀 profil fotoğrafı

𓂀♎︎𓂀2 gün önce

Oh ok Google.

Bruno B. Sant' Anna profil fotoğrafı

Bruno B. Sant' Anna3 gün önce

Interesting! How does this compare to running similar models on other serverless platforms like AWS Lambda or Azure Functions in terms of cost and cold start times?

Kyle Kelley profil fotoğrafı

Kyle Kelley3 gün önce

@mmastrac you mad lad

John Rood profil fotoğrafı

John Rood3 gün önce

Don't add --cpu-boost by reflex here. The repo reports 73-75s cold starts with it versus 47.5s without it on the 20-vCPU GPU setup.

Jhon Dennis profil fotoğrafı

Jhon Dennis2 gün önce

一条命令就能把实验跑起来这种少折腾的升级最有用普通人不用先学一堆黑话

刘朝 Zhao Liu profil fotoğrafı

刘朝 Zhao Liu3 gün önce

The interesting part is the deployment contract: Jev-compatible API, scale-to-zero, and a single Cloud Run command. The next useful artifact is a cold-start and tail-latency trace under real bursty traffic, because “$0 when idle” matters only when wake-up cost stays predictable.

Y11 profil fotoğrafı

Y112 gün önce

@grok 这个有什么业务意义呢？

Karios profil fotoğrafı

Karios3 gün önce

Gemini 4 pro gelene kadar tüm yan görevleri yapıyorlar

gab profil fotoğrafı

gab2 gün önce

OMG GEMMA I LOVE YOU

Fajar M Reza profil fotoğrafı

Fajar M Reza3 gün önce

Single-command deployment is the kind of boring improvement engineers quietly celebrate.

Hidde profil fotoğrafı

Hidde3 gün önce

how smart is this though?

extracsw profil fotoğrafı

extracsw3 gün önce

Local?

Noble Savage profil fotoğrafı

Noble Savage2 gün önce

AI is getting so advance its going backwards to 2017. 😂

🇺🇸🏴‍☠️ profil fotoğrafı

🇺🇸🏴‍☠️3 gün önce

Heh heh

Jigs profil fotoğrafı

Jigs2 gün önce

Need to check if laya is better or djev? 🤔

Chase McDougall profil fotoğrafı

Chase McDougall3 gün önce

Is there a blueprint like this for an openai compatible version? Can already get structured output that way. Jev format just seems like nerfing Gemma

Sonath profil fotoğrafı

Sonath3 gün önce

google made deploying its diffusiongemma image model a single cloud run command, $3 an hour and zero when idle. the gpu shortage is just a pricing strategy now.

Benzer Videolar

Claude Code just got a lot easier to use 🙌 Just updated You can now install agents, commands, MCPs, and templates with a single command. Click on any card and it gives you the exact line to run. Everything is pulled from GitHub, the site runs on GitHub Pages, and downloads are logged with GitHub Actions.

Claude Code just got a lot easier to use 🙌 Just updated You can now install agents, commands, MCPs, and templates with a single command. Click on any card and it gives you the exact line to run. Everything is pulled from GitHub, the site runs on GitHub Pages, and downloads are logged with GitHub Actions.

Daniel San

135,292 görüntüleme • 1 yıl önce

If you didn't feel the ongoing revolution, here is my second project I built with jev. Your software is drastically outdated. It contains a lot of instructions your CPU executes one by one. Why if we can simply ask Jev for the next instructions to execute Introducing Jevassembler! It is a new approach to execute something on CPU. You don't need to wait for code to be written, you don't need to compile anything and YOU DON'T NEED CODE. You just give it a task and Jev predicts the next instruction to execute. In runtime. who needs compilers if you have AI

If you didn't feel the ongoing revolution, here is my second project I built with jev. Your software is drastically outdated. It contains a lot of instructions your CPU executes one by one. Why if we can simply ask Jev for the next instructions to execute Introducing Jevassembler! It is a new approach to execute something on CPU. You don't need to wait for code to be written, you don't need to compile anything and YOU DON'T NEED CODE. You just give it a task and Jev predicts the next instruction to execute. In runtime. who needs compilers if you have AI

Dmitriy Kovalenko

222,422 görüntüleme • 6 gün önce

Jev has been blowing up lately. If you've got the Jev API but don't know how to play around with it yet, you can just copy this checklist. 1. jev-ultrafast A high-speed browser Agent built with Browser Use. Jev only judges "what to do, which element to click" at each step, and only calls the small model when typing is needed. Searching for a flight on Google Flights takes about 7 seconds. 2. fast-jev-compaction Context compression for Claude Code. Before each tool call, have Jev judge if there's anything still useful; delete the useless stuff, and keep the original text without rewriting it. 3. json-render Vercel Labs' generative UI framework. In experiments, Jev doesn't write JSON token by token; it just handles selecting components, properties, and layouts. 4. typesafe-mcp Best for people who just got the API. Plug Jev into Claude Code, Claude Desktop, Codex, and Pi, and do Choice / Score / Noul anytime. 5. jev-mcp Ready-made Agent judgment toolkit: fact-checking, content screening, semantic ranking, classification, and information extraction. 6. SemDecide Turn Jev into a command-line tool. Directly classify, score, and filter in the Shell—great for hooking up to crawlers, CI, and data pipelines. 7. jev-codex-router First have Jev judge how hard this round of programming tasks is, then decide the model tier, reasoning depth, and speed mode. 8. Winnow Context garbage collection for Claude Code. When Read / Bash / Grep spits out a ton of stuff, Jev first judges which parts are really relevant to the current task. 9. jev-review Before code review, run it through Jev first to pick out high-risk changes, then hand them off to a pricier big model or a human. Comes with a local dashboard. 10. Blink Use Jev as a code repository navigator. At each directory level, judge which files are most relevant to the current issue, then keep digging down. Copy these complete Jev blueprints - then read full Jev setup below ↓ ↓

Jev has been blowing up lately. If you've got the Jev API but don't know how to play around with it yet, you can just copy this checklist. 1. jev-ultrafast A high-speed browser Agent built with Browser Use. Jev only judges "what to do, which element to click" at each step, and only calls the small model when typing is needed. Searching for a flight on Google Flights takes about 7 seconds. 2. fast-jev-compaction Context compression for Claude Code. Before each tool call, have Jev judge if there's anything still useful; delete the useless stuff, and keep the original text without rewriting it. 3. json-render Vercel Labs' generative UI framework. In experiments, Jev doesn't write JSON token by token; it just handles selecting components, properties, and layouts. 4. typesafe-mcp Best for people who just got the API. Plug Jev into Claude Code, Claude Desktop, Codex, and Pi, and do Choice / Score / Noul anytime. 5. jev-mcp Ready-made Agent judgment toolkit: fact-checking, content screening, semantic ranking, classification, and information extraction. 6. SemDecide Turn Jev into a command-line tool. Directly classify, score, and filter in the Shell—great for hooking up to crawlers, CI, and data pipelines. 7. jev-codex-router First have Jev judge how hard this round of programming tasks is, then decide the model tier, reasoning depth, and speed mode. 8. Winnow Context garbage collection for Claude Code. When Read / Bash / Grep spits out a ton of stuff, Jev first judges which parts are really relevant to the current task. 9. jev-review Before code review, run it through Jev first to pick out high-risk changes, then hand them off to a pricier big model or a human. Comes with a local dashboard. 10. Blink Use Jev as a code repository navigator. At each directory level, judge which files are most relevant to the current issue, then keep digging down. Copy these complete Jev blueprints - then read full Jev setup below ↓ ↓

rody

194,422 görüntüleme • 4 gün önce

sharing an easy way to test DJev (Diffusion Gemma Jev), the next evolution of the incredible jev concept and fully open sourced (model, code, api...) imagine jev but it also has: - native image-input support - native image as options!! - real-time video streaming input - as fast as jev (not with images, 600ms) - same price as jev, but can get even cheaper - using Diffusion Gemma adapted - we are seeing on-par performance but happy to have external validation! It is a research preview made for fun, so don't expect stability and the awesome scaling as jev team has delivered! this was a weekend project :) have fun!

sharing an easy way to test DJev (Diffusion Gemma Jev), the next evolution of the incredible jev concept and fully open sourced (model, code, api...) imagine jev but it also has: - native image-input support - native image as options!! - real-time video streaming input - as fast as jev (not with images, 600ms) - same price as jev, but can get even cheaper - using Diffusion Gemma adapted - we are seeing on-par performance but happy to have external validation! It is a research preview made for fun, so don't expect stability and the awesome scaling as jev team has delivered! this was a weekend project :) have fun!

David Villalón

40,204 görüntüleme • 6 gün önce

The open-source local version of Laya crushes Jev in response speed! On the left is Laya, a local 421M open-source decision model. On the right is Jev 1.13.0, running through a cloud API. Same Snake game, same typed decisions, and the same 30-second free run: - Laya: Score 46, Length 52, 86.5 decisions/sec - Jev: Score 1, Length 7, 3.2 decisions/sec - In a real test on an M5 Pro, median latency was 15.3ms locally versus 298.1ms in the cloud, so nearly 20x faster. Laya uses around 1GB of memory, responds in milliseconds, and doesn’t depend on a network connection. While Jev waits for a cloud round-trip at every step, Laya makes each decision instantly on-device.

The open-source local version of Laya crushes Jev in response speed! On the left is Laya, a local 421M open-source decision model. On the right is Jev 1.13.0, running through a cloud API. Same Snake game, same typed decisions, and the same 30-second free run: - Laya: Score 46, Length 52, 86.5 decisions/sec - Jev: Score 1, Length 7, 3.2 decisions/sec - In a real test on an M5 Pro, median latency was 15.3ms locally versus 298.1ms in the cloud, so nearly 20x faster. Laya uses around 1GB of memory, responds in milliseconds, and doesn’t depend on a network connection. While Jev waits for a cloud round-trip at every step, Laya makes each decision instantly on-device.

Simplifying AI

24,406 görüntüleme • 4 gün önce

Jev is cool. So is it's OSS companion, Laya. The Latest Cool Thing In AI™ tends to get a lot of hype, sometimes without everyone even understanding it. So... what is this thing? Jev is an AI model that consumes input and produces output VERY differently than chat, claude, grok. The input is two things: 1) Text state to assess. Email, html, code, whatever. 2) A set of questions which will be asked about the attached state. The canonical example from TypeSafe's docs is to identify the urgency of a support ticket. We pass the model the customer text + a single noul question "is this urgent?". Jev returns a full set of JSON. This JSON is not generated with token-by-token autoregression. Jev is not trained to produce sequences of text tokens, rather to answer questions, and guarantees well-formed responses. In the example below, we see it produces a 0.99 probability (on a 0-1.0 scale) that the answer is "yes." Jev supports exactly three types of questions (seconds example in video): a) Noul: 0–1 probability that the answer to a yes/no question is "yes." b) Choice: Ask question with pre-defined set of answers. Jev chooses the best and assigns probabilities to each. c) Score: Ask question with pre-defined scale of answers. Jev produces a position on the scale. Jev computes answers for all questions in parallel, making responses super fast even for many questions in a single request. This might seem like a narrow set of capabilities, but in the right contexts leads to incredible potential. It also makes for a useful API / primitive for programming, since the outputs are... *ahem*... type-safe and predictable in structure. Jev is not going to replace LLMs for writing your code, auto-generating your docs, or being at the core of an agent harness. But Jev IS incredibly cool, and will be used to build a lot of amazing tech. Hope this helps.

Jev is cool. So is it's OSS companion, Laya. The Latest Cool Thing In AI™ tends to get a lot of hype, sometimes without everyone even understanding it. So... what is this thing? Jev is an AI model that consumes input and produces output VERY differently than chat, claude, grok. The input is two things: 1) Text state to assess. Email, html, code, whatever. 2) A set of questions which will be asked about the attached state. The canonical example from TypeSafe's docs is to identify the urgency of a support ticket. We pass the model the customer text + a single noul question "is this urgent?". Jev returns a full set of JSON. This JSON is not generated with token-by-token autoregression. Jev is not trained to produce sequences of text tokens, rather to answer questions, and guarantees well-formed responses. In the example below, we see it produces a 0.99 probability (on a 0-1.0 scale) that the answer is "yes." Jev supports exactly three types of questions (seconds example in video): a) Noul: 0–1 probability that the answer to a yes/no question is "yes." b) Choice: Ask question with pre-defined set of answers. Jev chooses the best and assigns probabilities to each. c) Score: Ask question with pre-defined scale of answers. Jev produces a position on the scale. Jev computes answers for all questions in parallel, making responses super fast even for many questions in a single request. This might seem like a narrow set of capabilities, but in the right contexts leads to incredible potential. It also makes for a useful API / primitive for programming, since the outputs are... ahem... type-safe and predictable in structure. Jev is not going to replace LLMs for writing your code, auto-generating your docs, or being at the core of an agent harness. But Jev IS incredibly cool, and will be used to build a lot of amazing tech. Hope this helps.

Ben Dicken

40,810 görüntüleme • 6 gün önce

This is literally the easiest way to build an AI agent. Zero code. You only need to run a couple of commands. (I've said this before, but Google ADK is my favorite way to build code-first agents.) Here is what you need to do: 1. Open your terminal and create an empty folder 2. Run `uv init` inside the folder (if you don't have uv installed, you are really missing out!) 3. Install the google-adk library using the following command: `uv add google-adk`. 4. At this point, you can use the ask to create your agent with a single command: `uv run adk create --type=config my_agent`. This will ask you a couple of questions, including your GEMINI_API_KEY (you can create one online). 5. The command above will create a my_agent/root_agent.yaml file. Open it and add the following two lines at the end of the file so your agent can use Google to search for stuff: tools: - name: google_search 6. You have everything you need now. Run the adk web interface and start playing with your agent: `uv run adk web` That's it! Literally zero code. The agent works off the YAML configuration file.

This is literally the easiest way to build an AI agent. Zero code. You only need to run a couple of commands. (I've said this before, but Google ADK is my favorite way to build code-first agents.) Here is what you need to do: 1. Open your terminal and create an empty folder 2. Run `uv init` inside the folder (if you don't have uv installed, you are really missing out!) 3. Install the google-adk library using the following command: `uv add google-adk`. 4. At this point, you can use the ask to create your agent with a single command: `uv run adk create --type=config my_agent`. This will ask you a couple of questions, including your GEMINI_API_KEY (you can create one online). 5. The command above will create a my_agent/root_agent.yaml file. Open it and add the following two lines at the end of the file so your agent can use Google to search for stuff: tools: - name: google_search 6. You have everything you need now. Run the adk web interface and start playing with your agent: `uv run adk web` That's it! Literally zero code. The agent works off the YAML configuration file.

Santiago

140,922 görüntüleme • 9 ay önce

Finally, an OpenRouter for agent harnesses! (including System One by Jev) Devs just open-sourced a plug-and-play infrastructure layer that lets you run any harness under a single interface, like: - Codex - Hermes - Claude code - DeepSeek Harness - System One, powered by Jev - And 9 more agent harnesses This means you can bring Jev into the same product that already uses Codex, Claude Code, or another supported harness, without writing another implementation for sessions, streaming, files, cancellation, and failure handling. Here's the repo: (don't forget to star it ⭐ ) The harnesses run locally, and the Unified Harness Protocol (UHP) defines the common task interface with an OpenAI Responses-compatible API. If you want to dive deeper, my recent article explains why model routing is not the same as harness routing, and what it takes to support multiple harnesses. It also covers UHP, the full local setup, a working API call, and how sessions and files work. Read it below.

Finally, an OpenRouter for agent harnesses! (including System One by Jev) Devs just open-sourced a plug-and-play infrastructure layer that lets you run any harness under a single interface, like: - Codex - Hermes - Claude code - DeepSeek Harness - System One, powered by Jev - And 9 more agent harnesses This means you can bring Jev into the same product that already uses Codex, Claude Code, or another supported harness, without writing another implementation for sessions, streaming, files, cancellation, and failure handling. Here's the repo: (don't forget to star it ⭐ ) The harnesses run locally, and the Unified Harness Protocol (UHP) defines the common task interface with an OpenAI Responses-compatible API. If you want to dive deeper, my recent article explains why model routing is not the same as harness routing, and what it takes to support multiple harnesses. It also covers UHP, the full local setup, a working API call, and how sessions and files work. Read it below.

Akshay 🚀

350,572 görüntüleme • 4 gün önce

Today, we’re excited to announce and launch Reflex Cloud on Product Hunt! Reflex is an open-source framework for building and deploying data and AI web apps in pure Python. Frontend and Backend in Pure Python: No JavaScript required! With Reflex Cloud, you can now deploy, manage, and scale your Python apps with just a single command! If you're a Python developer, an upvote or a share would mean a lot to us :)💪❤️

Today, we’re excited to announce and launch Reflex Cloud on Product Hunt! Reflex is an open-source framework for building and deploying data and AI web apps in pure Python. Frontend and Backend in Pure Python: No JavaScript required! With Reflex Cloud, you can now deploy, manage, and scale your Python apps with just a single command! If you're a Python developer, an upvote or a share would mean a lot to us :)💪❤️

Reflex

55,100 görüntüleme • 1 yıl önce

I got a rubik's cube to solve itself with TypeSafe AI 's Jev and it solves it like a person does, 94 moves, not the 22 move optimal solution. Jev isn't an LLM, it just answers one question in ~250ms with a probability. so I put the beginner method in code (the one you'd learn on youtube: white cross, corners, middle layer, yellow layer) and at every step Jev just looks at the cube and picks which case it's in. code checks every pick. ~4 seconds of model time total. video is slowed down so you can read it!

I got a rubik's cube to solve itself with TypeSafe AI 's Jev and it solves it like a person does, 94 moves, not the 22 move optimal solution. Jev isn't an LLM, it just answers one question in ~250ms with a probability. so I put the beginner method in code (the one you'd learn on youtube: white cross, corners, middle layer, yellow layer) and at every step Jev just looks at the cube and picks which case it's in. code checks every pick. ~4 seconds of model time total. video is slowed down so you can read it!

Paolo Rosson

207,238 görüntüleme • 8 gün önce

DigitalOcean Managed Agents is now in public preview. Run Claude Code, Codex, or your own LangGraph agent in a runtime environment that pauses when idle. Put its tools behind one governed endpoint, and pick from 75+ open and proprietary models. One cloud, one bill. Prompts to get started available in the blog:

DigitalOcean Managed Agents is now in public preview. Run Claude Code, Codex, or your own LangGraph agent in a runtime environment that pauses when idle. Put its tools behind one governed endpoint, and pick from 75+ open and proprietary models. One cloud, one bill. Prompts to get started available in the blog:

DigitalOcean

3,808,957 görüntüleme • 3 gün önce

GLM 5.3 Flash vs Hybrid (GLM 5.3 Flash + Jev) on a turn-based strategy game (Halite 2) The hybrid approach is 13x faster, 56% of the pure GLM 5.3 Flash API cost, and gains a slight edge in performance. In the hybrid approach: -GLM 5.3 Flash handles strategic judgment of which planets matter, who expands, who fights, when to re-plan. -Jev handles the ship-by-ship execution. GLM 5.3 Flash alone defeats Jev alone 82% of the time. This is obviously just a single example and some of the first things I've tried to make use of Jev as an augmentation to an LLM. Could potentially make even more gains in cost, speed, and performance, but using what I've figured out here, I am compelled to try some ideas with robotics next.

GLM 5.3 Flash vs Hybrid (GLM 5.3 Flash + Jev) on a turn-based strategy game (Halite 2) The hybrid approach is 13x faster, 56% of the pure GLM 5.3 Flash API cost, and gains a slight edge in performance. In the hybrid approach: -GLM 5.3 Flash handles strategic judgment of which planets matter, who expands, who fights, when to re-plan. -Jev handles the ship-by-ship execution. GLM 5.3 Flash alone defeats Jev alone 82% of the time. This is obviously just a single example and some of the first things I've tried to make use of Jev as an augmentation to an LLM. Could potentially make even more gains in cost, speed, and performance, but using what I've figured out here, I am compelled to try some ideas with robotics next.

Harrison Kinsley

53,159 görüntüleme • 5 gün önce

Jev by TypeSafe AI is now on the Venice API, in beta. It answers, it doesn't write. Send it your app's state and typed questions. Get back a typed answer your code can branch on: a probability, a chosen option, or a score on your rubric. No JSON to coax out of a chat model.

Jev by TypeSafe AI is now on the Venice API, in beta. It answers, it doesn't write. Send it your app's state and typed questions. Get back a typed answer your code can branch on: a probability, a chosen option, or a score on your rubric. No JSON to coax out of a chat model.

Venice

536,864 görüntüleme • 7 gün önce

UCONN HC Dan Hurley - Building a System/Identity - "Our system is how hard we play. How hard we get after people every single possession at both ends of the court & on the backboard." - "The number one thing you got to understand if you want to have a program that can sustainably be successful and have a chance to win every single night... It's hard to coach that way because it's fu**ing exhausting. To coach every single possession, every single day and when the losing team runs the line because every single drill we do there is a winner & a loser, when they get this close and miss that line, you better be there to call them out and make the whole team now run with them." - "If you want to start the game 6-0, like I start most games just because my team is ready to go because we go so hard every day."

UCONN HC Dan Hurley - Building a System/Identity - "Our system is how hard we play. How hard we get after people every single possession at both ends of the court & on the backboard." - "The number one thing you got to understand if you want to have a program that can sustainably be successful and have a chance to win every single night... It's hard to coach that way because it's fu**ing exhausting. To coach every single possession, every single day and when the losing team runs the line because every single drill we do there is a winner & a loser, when they get this close and miss that line, you better be there to call them out and make the whole team now run with them." - "If you want to start the game 6-0, like I start most games just because my team is ready to go because we go so hard every day."

James Light

162,675 görüntüleme • 5 ay önce

Jev builds the MOST POWERFUL trading agents and someone JUST open sourced jev-trader, a fully working 24/7 trading bot with Jev along with COMPLETE low latency CODEBASE WHAT THIS MEANS FOR YOU - you no longer have to build a trading bot with Jev from scratch, you just clone this and make it yours here is how you make your own Jev trading bot with this repo: 1. clone it and run three commands, it boots straight into dry run mode with real book data, real decisions, and simulated fills so you can watch it think with zero capital 2. drop in your Jev API key and the model starts answering buy or sell on every block with calibrated probabilities in 81 milliseconds 3. swap the book reader for your own venue, the model interface is clean so any order book that returns bids and asks plugs straight in 4. tune the decision cadence and horizon, ask the model every N blocks about the move over the next M, so you control how aggressive the engine trades 5. the hot loop already fits one block with exactly two round trips, one to read the book, one to send the order, nothing else on the path, this is the institutional latency discipline most retail bots never reach 6. plug in the live server and every block, every decision, every fill streams to a public dashboard so you watch your engine run the whole point is this repo hands you HARDEST part for FREE - > the low latency engine the COMPLETE breakdown of how i turned this into hedge fund grade HFT trading system is in my article below:

Jev builds the MOST POWERFUL trading agents and someone JUST open sourced jev-trader, a fully working 24/7 trading bot with Jev along with COMPLETE low latency CODEBASE WHAT THIS MEANS FOR YOU - you no longer have to build a trading bot with Jev from scratch, you just clone this and make it yours here is how you make your own Jev trading bot with this repo: 1. clone it and run three commands, it boots straight into dry run mode with real book data, real decisions, and simulated fills so you can watch it think with zero capital 2. drop in your Jev API key and the model starts answering buy or sell on every block with calibrated probabilities in 81 milliseconds 3. swap the book reader for your own venue, the model interface is clean so any order book that returns bids and asks plugs straight in 4. tune the decision cadence and horizon, ask the model every N blocks about the move over the next M, so you control how aggressive the engine trades 5. the hot loop already fits one block with exactly two round trips, one to read the book, one to send the order, nothing else on the path, this is the institutional latency discipline most retail bots never reach 6. plug in the live server and every block, every decision, every fill streams to a public dashboard so you watch your engine run the whole point is this repo hands you HARDEST part for FREE - > the low latency engine the COMPLETE breakdown of how i turned this into hedge fund grade HFT trading system is in my article below:

Roan

119,605 görüntüleme • 5 gün önce

Trying Gemini today It feels like Google is trying to scare customers into NOT using it with legal popups literally every step of the way Admittedly it's gotten better and now supports CURL requests without all the Google libraries to install But still no OpenAI-compatible queries yet Took 9 clicks to get an API key, and the legal popups are just way too crazy If Logan Kilpatrick can just get all the lawyers of his back, it could be great

Trying Gemini today It feels like Google is trying to scare customers into NOT using it with legal popups literally every step of the way Admittedly it's gotten better and now supports CURL requests without all the Google libraries to install But still no OpenAI-compatible queries yet Took 9 clicks to get an API key, and the legal popups are just way too crazy If Logan Kilpatrick can just get all the lawyers of his back, it could be great

@levelsio

413,444 görüntüleme • 1 yıl önce

If you are confused about why 𝗝𝗲𝘃 is being called the "Internet" moment for the AI industry. This is 100% worth your time. In fact, you should watch it: It tells LLMs what to do next, in milliseconds & at almost zero cost. If you set it up correctly, you will have the AI engineer’s setup for 2028. How to set up & use Jev (to actually get the 100x): 1. Join the waitlist; it's fairly quick: typesafe .ai. 2. Then go to Claude Code or Codex. 3. Choose Opus 5-Low or Sol-Low. 4. Copy and paste this prompt: "[claude or codex] plugin marketplace add typesafe-ai/skills [claude or codex] plugin install typesafe@typesafe-ai" 5. When you type /typesafe, the skill shows up. 6. Paste your API key once and click "Allow" 7. Start with $5 in free credit. It's hard to spend more. ----- Now, here are the 3 ways to actually use Jev: 1. Jev for Linkedin I have 38,000 connections & invitations on LinkedIn. I have a new company to launch. I need to find a couple of hundred people to message. to do while saving time: > Export your LinkedIn connections and invitations. > Connect Claude to GitHub, Vercel & Apify. > Create an Apify API key to enrich your data. > Go to LinkedIn Settings → Data privacy. > Get a copy. LinkedIn will email you a ZIP file. > Open the file & find the Connections CSVs. > Upload the files to Jev. > Use Jev to classify your contacts. > Review the shortlist. 2. Jev for Gmail To go through all of my Gmail contacts and email the right people. > Go to Google Contacts. Open Other contacts. > Select all contacts. Export them. > Upload the file to Claude Code or Codex. > Use Jev to sort them into: Keep, Review, Remove and Review everything before removing anything. 3. You got lost in Claude Code, GitHub, Vercel, Apify, Jev, Typesafe. I feel you. It is overwhelming. That’s why I included the entire copy-and-paste prompt for each use case in the newsletter: A 45-second TL;DR by Matija Sosic.

If you are confused about why 𝗝𝗲𝘃 is being called the "Internet" moment for the AI industry. This is 100% worth your time. In fact, you should watch it: It tells LLMs what to do next, in milliseconds & at almost zero cost. If you set it up correctly, you will have the AI engineer’s setup for 2028. How to set up & use Jev (to actually get the 100x): 1. Join the waitlist; it's fairly quick: typesafe .ai. 2. Then go to Claude Code or Codex. 3. Choose Opus 5-Low or Sol-Low. 4. Copy and paste this prompt: "[claude or codex] plugin marketplace add typesafe-ai/skills [claude or codex] plugin install typesafe@typesafe-ai" 5. When you type /typesafe, the skill shows up. 6. Paste your API key once and click "Allow" 7. Start with $5 in free credit. It's hard to spend more. ----- Now, here are the 3 ways to actually use Jev: 1. Jev for Linkedin I have 38,000 connections & invitations on LinkedIn. I have a new company to launch. I need to find a couple of hundred people to message. to do while saving time: > Export your LinkedIn connections and invitations. > Connect Claude to GitHub, Vercel & Apify. > Create an Apify API key to enrich your data. > Go to LinkedIn Settings → Data privacy. > Get a copy. LinkedIn will email you a ZIP file. > Open the file & find the Connections CSVs. > Upload the files to Jev. > Use Jev to classify your contacts. > Review the shortlist. 2. Jev for Gmail To go through all of my Gmail contacts and email the right people. > Go to Google Contacts. Open Other contacts. > Select all contacts. Export them. > Upload the file to Claude Code or Codex. > Use Jev to sort them into: Keep, Review, Remove and Review everything before removing anything. 3. You got lost in Claude Code, GitHub, Vercel, Apify, Jev, Typesafe. I feel you. It is overwhelming. That’s why I included the entire copy-and-paste prompt for each use case in the newsletter: A 45-second TL;DR by Matija Sosic.

Ruben Hassid

169,385 görüntüleme • 4 gün önce

fun weekend project: AutoJev. i was curious to see if i could train a competitive Jev-like model completely autonomously with a swarm of agents using our internal system. turns out you can get quite far! some details: - gave the swarm a devbox with an h200 gpu - the swarm is a mix of astra and fable; used sol and luna for synthetic data and filtering; ran for 20 hours - spent $3.1k in total ($1.9k on agents, $1.2k on data) - used qwen3.8-27b as the backbone. it underperforms Jev initially, but after training it is competitive/better, and it also supports 260k context and multimodal input - the agents tried RL, but it hasn't worked out so far, so they fell back to SFT on high-quality synthetic data - both accuracy and calibration are better - jev-compatible api, playground, and inference. on an h200 it gets around 120ms p95. that will be higher under contention, but still quite fast for an unoptimized version code: model: going to let it run longer, and will also bring up inference so folks can try it out.

fun weekend project: AutoJev. i was curious to see if i could train a competitive Jev-like model completely autonomously with a swarm of agents using our internal system. turns out you can get quite far! some details: - gave the swarm a devbox with an h200 gpu - the swarm is a mix of astra and fable; used sol and luna for synthetic data and filtering; ran for 20 hours - spent $3.1k in total ($1.9k on agents, $1.2k on data) - used qwen3.8-27b as the backbone. it underperforms Jev initially, but after training it is competitive/better, and it also supports 260k context and multimodal input - the agents tried RL, but it hasn't worked out so far, so they fell back to SFT on high-quality synthetic data - both accuracy and calibration are better - jev-compatible api, playground, and inference. on an h200 it gets around 120ms p95. that will be higher under contention, but still quite fast for an unoptimized version code: model: going to let it run longer, and will also bring up inference so folks can try it out.

Denis Yarats

27,046 görüntüleme • 3 gün önce

Jev is a new model from the co-inventor of ChatGPT that can use computer tools in realtime right now it's playing Minecraft on its own computer in the cloud on Orgo this is what it looks like with just one Jev, but imagine: what about a thousand? or what about a billion of Jevs? each working together on their own computers in the cloud, discovering new science, running experiments, and designing new drugs 24/7. this is going to be bigger than ChatGPT

Jev is a new model from the co-inventor of ChatGPT that can use computer tools in realtime right now it's playing Minecraft on its own computer in the cloud on Orgo this is what it looks like with just one Jev, but imagine: what about a thousand? or what about a billion of Jevs? each working together on their own computers in the cloud, discovering new science, running experiments, and designing new drugs 24/7. this is going to be bigger than ChatGPT

Nick Vasilescu

16,613 görüntüleme • 8 gün önce