Загрузка видео...

Не удалось загрузить видео

На главную

Top 12 agentic use cases for Jev: (bookmark this) Jev handles semantic decisions that ordinary code cannot express reliably. It returns typed answers and probabilities, while code continues to cover the workflow. Here are 12 practical use cases for Jev: 1. Browser next action > Convert the current DOM...

25,216 просмотров • 14 дней назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Jev dropped and people immediately started doing stupid sh*t with it people gave this thing trading bots, browsers, Doom, drones, dinosaurs and tax forms and basically said: “you decide.” here’s what happened: > jev-trader Jev gets a new Monad block every ~300ms and decides whether to place a live limit order. no essay. just the decision. 1,911 stars ▸ ⁠ > jev-ultrafast a browser agent where Jev decides every click. the text model only wakes up when something actually needs to be written. 16,758 stars ▸ ⁠ > jev-doom-agent someone compiled actual Chocolate Doom to WebAssembly and let Jev make the tactical decisions every frame. yes. Doom. ▸ ⁠ > jev-t-rex-runner remember that stupid Chrome dinosaur? now Jev plays it. jump → duck → run → repeat ▸ ⁠ > typesafe-chess Jev went against a real chess search engine. two games. colors swapped. the search engine won both — and overruled Jev’s first instinct on roughly half the moves. ▸ ⁠ > jev-drone camera → Jev → drone. a simulated quadrotor has to clear five stations while Jev looks at the situation twice a second and decides what happens next. ▸ ⁠ > tax-doc-classifier then someone gave it IRS forms. 261 documents. 100% strict accuracy. roughly $0.001/page. ▸ ⁠ > killmyidea this one is evil lol tell it your startup idea. Jev looks at it from different angles and gives you: KILL / FIX / SHIP ▸ ⁠ > jev-curate throw huge Parquet / JSONL datasets at it. Jev judges 1,500+ rows/sec and keeps only the stuff that passes your rules. ▸ ⁠ > pg-jev and now it’s inside PostgreSQL. ask questions about your own tables in plain English → get the decision back. ▸ ⁠ and this is the weird part: none of these need Jev to write you a beautiful paragraph. they need it to look at a situation and pick: BUY / WAIT CLICK A / CLICK B JUMP / DUCK KILL / FIX / SHIP KEEP / DROP that’s basically the whole Jev idea. LLMs think and write. Jev decides. code does. full setup + my three-question Jev test below

kiosa

67,916 просмотров • 1 месяц назад

This is absolutely f*cking insane. you can put a $0.042-per-million-token model in front of Claude and let it decide what Claude ever has to see. that's Jev signal routing, and the trick is stupidly simple: Jev takes the first look at everything. Claude only gets the hard cases. instead of: data -> Claude -> tokens burnt $ it's: data -> Jev -> only the unsure ones -> Claude and here's the part people miss. every Jev answer comes with a probability. that's your router: -> Jev is sure? its answer is final -> Jev hesitates? the case goes up to Claude set the cutoff once, by testing on your own data, not by guessing. 3 repos that already do the routing for you: -> duckdb-jev: route your data. Jev labels every row straight from SQL, up to 1,000 calls in one request -> quicksilver: route your files. Jev checks all 187 files in parallel and Claude gets the 4 that matter. ~2.4k tokens instead of ~26k -> jev-router: route your models. before every message Jev decides simple or hard and sends it to the fast model or the strong one. works with your normal Claude login where this pays off right away: -> support tickets -> your inbox -> lead lists -> messy spreadsheets -> comment moderation on a public benchmark Jev labeled 1,000 rows for $0.015. Claude charged $0.80 for the same job. faster. cheaper. way fewer tokens burned. Jev sorts the mail so the genius only opens what matters. Claude thinks. Jev routes. code does the job.

kiosa

11,388 просмотров • 22 дней назад

jev + sonnet 5.5 is f**king insane. my entire workflow got 4x faster after adding these 6 lines to CLAUDE.md. [with jev connected, paste this👇] 1. Before you start a Claude worker, ask Jev once to select a host-approved profile with one or two sessions. The profile must specify each session’s model and effort level. If Jev makes no selection, use the host default. 2. The host must check Jev’s selection. The host must set the model and effort before each session starts. Keep these settings fixed during the session. The host controls permissions and approvals. 3. Use Sonnet 5.5 at medium effort for clear coding tasks. Use higher effort for complex reasoning or JSON tasks. Use a second Claude only for independent research or a review that the user requested. 4. Give the second Claude the task, applicable files, limits, and completion requirements. Return its findings and evidence to the lead. 5. Complete the requested work. Ask the user only when you cannot continue without input or before an action that needs approval. Do not add features, tests, files, documentation, refactors, or review rounds that the user did not request. When the work is complete and checked, stop. Report the result. 6. Before you report completion, run a test, build, type check, or command that checks the code change. If no check can run, identify the missing check. Explain why it cannot run. same task. two timers. watch the difference.

Avid

177,825 просмотров • 1 месяц назад

Jev + SERV is actually insane. We already showed you can increase Jev's performance with SERV Reasoning. Now we're taking it further, bringing Jev-powered Decision nodes into Graph Sharding with the upcoming SERV v3. Here's a breakdown of how it works: Jev is a decision-making model. Given a task and a set of options, it predicts which path is more likely. Think of the octopus that predicted World Cup results. Jev does that for your business, except it's not luck. It weighs every option and tells you how sure it is. It does this by assigning probabilities to outcomes. It doesn't generate text on its own, so you can't expect it to create a new outcome for you. But that's also what enables it to be lightning fast and dirt cheap. For example, in customer service you can ask Jev how to triage an incoming query and route it to the correct department. It can only select from the list of departments you provide it. This also means it can't hallucinate a new outcome outside the options it's given, which makes it incredibly interesting for OpenServ. In Graph Sharding, we take a single system prompt and break it down into multiple LLM steps with deterministic input and output shapes. Some of these steps require an LLM to produce new output, while others are simply decision routers that determine the next possible path. Traditionally, LLMs are slow and expensive. Breaking a single prompt into multiple steps increases accuracy and reliability by a ton, but it also introduces latency. Jev takes on those decision nodes, which are the backbone of a business process and therefore SERV graphs, and makes them super consistent and lightning fast, lowering the overall cost and latency of graph execution. SERV Reasoning on its own is a great force multiplier for Jev because, like all other models, it works by interpreting input instructions. The clearer those instructions are, the better the model performs. That's where SERV Reasoning comes into play. Just like amplifying any other model, we also amplify the accuracy and consistency of Jev's responses. And now we're bringing Jev-powered Decision nodes into Graph Sharding with SERV v3.

Armagan Amcalar

366,601 просмотров • 1 месяц назад

Jev + Muse is the first AI agent system that actually automate 100% of my life 99% of people pay 200x more for slower AI agents - while 1% run this 2030 setup just 5 min and setup is ready: prompt → Muse → Jev decision → Muse execution → result step 1 → create your Jev API key (typesafe website) step 2 → clone and install the complete router from Github below python3 -m venv .venv && .venv/bin/pip install -r requirements.txt && cp config.example.yaml config.yaml step 3 → export the key before running anything: export TYPESAFE_API_KEY='YOUR_KEY' add the same export to ~/.zshrc or ~/.bashrc if you want it to survive a new terminal session step 4 → give your agent skill/jev-decision-layer.SKILL.md and connect it to src/router.py + recipes/ , raw Jev returns probabilities - the router converts them into executable actions step 5 → test the entire chain, not the raw Jev API: .venv/bin/python -m src.cli '{"goal":"what is 2+2?","kind":"chat"}' the final JSON should contain action, reason, mode, jev_used and confidence details step 6 → keep mode: shadow for 20–50 real decisions: the agent works normally while Jev’s routes are logged and checked; promote only reliable question packs step 7 → switch to mode: active with hard confidence gates: ≥0.80 act automatically, 0.50–0.79 advisory only, <0.50 escalate to the human the result: Jev + Muse is a system that decides what to do, what to skip and when to bring in - I’ve tested it across my daily workflows, and it’s the best setup I’ve found for automating routine Take the exact stack I built, run it yourself from the repo - then read the full Jev architecture behind it ↓

codila

97,018 просмотров • 1 месяц назад

THIS IS A PURE F*CKING GOLDMINE the best REA trick almost nobody runs yet. The idea: REA takes the app apart, Jev keeps only what's proven, and a fresh Opus 5.5 rebuilds the feature from that alone. Nothing gets copied and no guess makes it into the code, because the builder never sees the original, only the spec Jev signed off on. You just connect REA like this: npx rea-agents setup here's the split: → REA reads the feature down to the binary and writes every rule into SPEC.md → Jev checks each rule against REA's evidence and sends back anything unproven → a fresh Opus 5.5 session gets only SPEC.md and rebuilds the feature → Haiku 5.5 runs the tests against 3 intentionally broken versions Opus only shows up at three moments: → rebuilding from the approved spec → the checks Jev marks as unclear → signing off before anything ships REA reads. Jev judges. Opus rebuilds. That's the clean-room rule in one line: the model that saw the original never writes the code, and the model that writes the code never sees the original. the full tree > REA reads the app and writes SPEC.md with evidence for every rule > Jev approves or returns each rule > Opus 5.5 rebuilds from the approved SPEC.md in a fresh session > Haiku 5.5 runs the tests and the 3 broken versions > Jev routes unclear checks back to Opus > /goal keeps going until all 3 broken versions fail paste the tree and this prompt into Claude Code ↓ "Set up a clean-room rebuild around this tree: 1. Use REA to investigate [FEATURE] in [APP]. Write every behavior and rule into SPEC.md, each with the evidence REA found. 2. Send each rule to Jev. Any rule without evidence goes back to REA. 3. Start a fresh session with only SPEC.md. Rebuild the feature on Opus 5.5 without opening the original. 4. Write tests on Haiku 5.5 plus 3 intentionally broken versions. Use /goal until the rebuild passes and all 3 broken versions fail. Show me SPEC.md first. Nothing gets built until I say go." ↳ save it, it'll come in handy.

Archive

59,706 просмотров • 1 месяц назад