Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Launching Jev on Command Code for free today. Jev x Command Code is super interesting. You can only use Jev in headless mode or Provider API. Also open sourced a mod "cmd-mod-jev-nudge" Use Jev for free to keep your agent running as long as the there's more work to do.

32,437 görüntüleme • 2 gün önce •via X (Twitter)

33 Yorum

Ahmad Awais profil fotoğrafı
Ahmad Awais2 gün önce

Here's the open sourced mod for continuation nudge, have at it. mix and remix. got the prompt from @willcb: 'Would a gentle nudge help the agent advance useful work within the user’s existing request right now?'

Command Code profil fotoğrafı
Command Code2 gün önce

Welcome Jev!! 🐐

Blogangster profil fotoğrafı
Blogangster2 gün önce

I still don’t understand its usecase

Ahmad Awais profil fotoğrafı
Ahmad Awais2 gün önce

have you watched the video?

Maedah Batool profil fotoğrafı
Maedah Batool2 gün önce

It's Jev time in Command Code.

Ahmad Awais profil fotoğrafı
Ahmad Awais2 gün önce

🤘

satvik profil fotoğrafı
satvik2 gün önce

wow

Ahmad Awais profil fotoğrafı
Ahmad Awais2 gün önce

🤘

Aziz Emre OZTURK profil fotoğrafı
Aziz Emre OZTURK2 gün önce

You're awesome, @MrAhmadAwais feature is going to give Command Code a huge advantage...

Ahmad Awais profil fotoğrafı
Ahmad Awais1 gün önce

Let's go, GOAT! 🐐

Gulagi profil fotoğrafı
Gulagi2 gün önce

So good

Ahmad Awais profil fotoğrafı
Ahmad Awais2 gün önce

Let's go! 👊

Hafeez Al-Haqq profil fotoğrafı
Hafeez Al-Haqq2 gün önce

Hey Jevis

Rick A.F. profil fotoğrafı
Rick A.F.2 gün önce

What’s your best Jev use case internally? Would love to see how a pro uses it

Ahmad Awais profil fotoğrafı
Ahmad Awais2 gün önce

Have you read this? Taste is quite similar to Jev.

Avik profil fotoğrafı
Avik2 gün önce

Nice. But too bad that there is no proper ADE support for command code. People are forced to use the API instead of the actual harness because of this

Ahmad Awais profil fotoğrafı
Ahmad Awais2 gün önce

you're misinformed. check out @CommandCodeAI Desktop

Leonardo profil fotoğrafı
Leonardo2 gün önce

Even paying for the GOAT plan I only have 200 reqs/day? 😓

Ahmad Awais profil fotoğrafı
Ahmad Awais2 gün önce

free limits are 200/day and the upstream has no GPU capacity so we can't really sell more either. looking into it.

Leonardo profil fotoğrafı
Leonardo2 gün önce

I don’t mind being charged in my goat plan 😆

Ahmad Awais profil fotoğrafı
Ahmad Awais2 gün önce

i know. let us get the capacity for it. @AhmadBilalDev

Leonardo profil fotoğrafı
Leonardo2 gün önce

@AhmadBilalDev

安叫兽|Bird🕊️ 🔶 BNB profil fotoğrafı
安叫兽|Bird🕊️ 🔶 BNB2 gün önce

让代理别忙一半就停,这个小模组还挺对症

Ayzap profil fotoğrafı
Ayzap2 gün önce

I tried using JEV in CommandCode on the Go plan, but it doesn’t work there. It would be really nice if JEV could also be supported on the Go plan.

Ahmad Awais profil fotoğrafı
Ahmad Awais1 gün önce

Upgrade to GOAT. $1 isn't a serious plan.

Joey Kudish profil fotoğrafı
Joey Kudish2 gün önce

Limited time or staying free? 😳

Ahmad Awais profil fotoğrafı
Ahmad Awais2 gün önce

few days, it's pretty cheap otherwise too.

Joey Kudish profil fotoğrafı
Joey Kudish2 gün önce

Yeah very cheap!

$SOLANA profil fotoğrafı
$SOLANA2 gün önce

Final phases usually make leaderboards more interesting to watch because rankings can change quickly. BingX has three separate categories here, which gives the results more context.

Gargeya profil fotoğrafı
Gargeya2 gün önce

It's a great demo and that's a great example. I think you can also try to incorporate or create a mod that can help people switch models or their effort based on the complexity of the task. Even while it's working, like during the single run.

Ahmad Awais profil fotoğrafı
Ahmad Awais2 gün önce

you can ask, @CommandCodeAI it can build mods for you.

Gargeya profil fotoğrafı
Gargeya2 gün önce

@CommandCodeAI Oh is it! okay thank you so much I'll do that, I'm testing.

unfair.so intern profil fotoğrafı
unfair.so intern2 gün önce

headless agents are great, pair them with tinyfish monitor so they only run when something actually changes

Benzer Videolar

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

Jev has been exploding in popularity recently. If you already have access to the Jev API but aren’t sure how to start experimenting with it, just copy this checklist: 1. agent-desktop Desktop automation. Read the system's accessibility tree, judge which button, menu, or input field to click next. 2. typesafe-mario Have Jev play Super Mario. No screenshots—just read the structured state in the emulator's RAM, then decide to run, jump, or dodge. 3. jev-drone Use Jev to control a drone. The underlying flight control still handles stability and safety; Jev just does higher-level judgments like climbing, braking, and navigating obstacles. 4. OneVOneJev 1v1 FPS in the browser. Every decision tick, judge movement, view angle, aiming, firing, and jumping. 5. jev-trader High-frequency market making on Monad testnet. Jev judges the next buy or sell based on spreads and trade direction, with model latency around 81ms. 6. Prism Doesn't directly have Jev place orders. It judges states like toxic flow, market pressure, mean reversion, etc., then hands off to the original strategy. 7. neo4jev Stuff Jev into a knowledge graph. At each node, judge the most worthwhile edge to take next, then follow it all the way. 8. jev-curate Use Jev to screen training data. For JSONL / Parquet, first judge quality, relevance, and risk, then decide which ones go into the next training round. 9. Canny Prevents Coding Agents from stubbornly claiming they're done. Look at tool outputs, code diffs, and test results, then judge if the completion claim is reliable. 10. killmyidea Input a startup idea, and Jev scores it from multiple angles, finally giving you KILL, FIX, or SHIP. Copy these complete Jev blueprints - then read full Jev setup below ↓ ↓

rody

334,032 görüntüleme • 3 gün ö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.

Ruben Hassid

167,306 görüntüleme • 4 gün önce

Another insane Jev use case! Jev is making it dramatically cheaper to evaluate what actually happened inside an agent run. And finally, someone open-sourced a self-improving memory layer that can put that signal to work across agent harnesses: - Claude Code - Codex - Cursor - OpenCode, and 20+ more Beacon by Asymptote Labs continuously captures your agent history across harnesses and uses Jev to identify which runs are actually worth learning from. It then turns the highest-signal workflows, corrections, and debugging patterns into reusable skills. GitHub repo: (don’t forget to star it ⭐ ) Beacon preserves the complete session history. But preserving a run and learning from it are two different things. Most coding-agent sessions contain routine exploration, failed commands, and fixes that only apply to one task. The trace can remain available for inspection without turning every detail into guidance for future agents. Jev scores each run for evidence, reuse potential, and human correction signals. An application policy then decides whether to promote, review, or discard it. The recording shows this in action. Claude receives a coding task, modifies the implementation, and runs the tests. I then provide an edge-case correction, so Claude updates the code and adds regression coverage. Beacon automatically captures the complete session. Jev evaluates whether the correction contains a reusable engineering lesson. Once approved, that lesson becomes available to other coding agents working on the project. Since it works across harnesses: - Claude Code sessions can teach Codex. - Cursor debugging can improve OpenCode. So a problem solved by one agent should not need to be learned from scratch by another. If you want to dive deeper into Jev, I also wrote a hands-on guide to building this Jev-style decision path with open models, entirely locally. Read it below.

Avi Chawla

285,761 görüntüleme • 4 gün önce

Another insane Jev use case! Jev makes it incredibly cheap to evaluate and classify agent runs at scale. And finally, someone open-sourced a self-improving memory layer that can put that capability to work across agent harnesses. It turns your agent sessions into a compounding knowledge layer, where every successful run can make future agents smarter across: - Codex - Claude Code - Cursor - OpenCode and 20+ more Beacon by Asymptote Labs continuously builds a shared history across your agent harnesses and uses Jev to identify the runs worth learning from. It then turns the best workflows, corrections, and debugging patterns into reusable skills. GitHub repo: (don’t forget to star it ⭐) Most agent runs are messy. They contain exploration, failed commands, dead ends, and one-off fixes that should never become permanent memory. So Beacon preserves the full session history, while Jev helps decide what should be promoted, reviewed, or discarded. The recording below shows this in action. Beacon found 579 sessions across 5 coding-agent harnesses and normalized them into one consistent history. From there, Jev surfaces the lessons worth keeping and makes them available across your agent stack. - A pattern learned in Cursor can carry into OpenCode. - A lesson from Claude Code can improve the next Codex run. Every successful run adds to the shared knowledge layer, making future agents smarter. If you want to dive deeper into Jev, I also wrote a breakdown of how it works. The article is quoted below.

Akshay 🚀

113,866 görüntüleme • 2 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.

Ben Dicken

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