正在加载视频...

视频加载失败

加载此视频时出现问题。这可能是由于临时网络问题，或视频可能不可用。

computer use with openai's decisions api might be the next big thing. i built arc-cua - a fast computer use layer powered by decision models. >no screenshot + LLM call after each action. >supports jev & decisions api. open source. link below.

shiv

1,550 subscribers

14,990 次观看 • 2 天前 •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

computer use on mac just got a lot faster. i built arc-driver - a lean & powerful computer-use driver for macos. >faster than cua-driver on most tasks. up to 8x on some. >plug it into your coding agents with a single command. open source. link below.

computer use on mac just got a lot faster. i built arc-driver - a lean & powerful computer-use driver for macos. >faster than cua-driver on most tasks. up to 8x on some. >plug it into your coding agents with a single command. open source. link below.

shiv

40,564 次观看 • 5 天前

we built blazing fast computer/browser use with Jev + Stagehand. this task cost $0.001 and executed at near instant speed (in a remote browser btw) the loop: observe the page, send a11y tree as state + actions as questions, Jev decides the next action, then Stagehand executes it.

we built blazing fast computer/browser use with Jev + Stagehand. this task cost $0.001 and executed at near instant speed (in a remote browser btw) the loop: observe the page, send a11y tree as state + actions as questions, Jev decides the next action, then Stagehand executes it.

Kyle Jeong

71,304 次观看 • 23 天前

I explored a further possibility with local models: Qwen3.6 35B A3B + NVIDIA LocateAnything-3B as a local Computer Use agent (proof of concept). In the demo, I asked it to switch my Mac to light mode. It did. Then back to dark. Did that too — finding the right toggle in System Settings, clicking it, and verifying the change itself. It's fully screenshot-based, so no Accessibility API needed. If it's on screen, the agent can see it and act on it. This runs entirely on your own hardware — private, local, built from two small open models.

I explored a further possibility with local models: Qwen3.6 35B A3B + NVIDIA LocateAnything-3B as a local Computer Use agent (proof of concept). In the demo, I asked it to switch my Mac to light mode. It did. Then back to dark. Did that too — finding the right toggle in System Settings, clicking it, and verifying the change itself. It's fully screenshot-based, so no Accessibility API needed. If it's on screen, the agent can see it and act on it. This runs entirely on your own hardware — private, local, built from two small open models.

stevibe

44,283 次观看 • 4 个月前

Opus 5.5 + GrokBot + Jev... I can't believe that I build it I packed the best of AI into ONE agent - now 99% of people’s AI agents look dumb, slow, and expensive Try here (free): prompt → GrokBot → Jev chooses LLM → Claude / GPT working on GrokBot's computer 24/7 → result → Jev sends only the tasks Grok is weak at to Opus or GPT → Jev picks the best model for each task - for example, Claude for motion design and Codex for web design → runs on the ChatGPT and Claude subscriptions you already pay for (API also work) → works on GrokBot computer while you keep chatting → checks every result against the goal before you see it → GrokBot gets smarter and cheaper at the same time → And plenty more features in a bot everyone will call "obvious" by 2030 Try Jevopus, thank me later - then read the article on the full Jev architecture ↓

Opus 5.5 + GrokBot + Jev... I can't believe that I build it I packed the best of AI into ONE agent - now 99% of people’s AI agents look dumb, slow, and expensive Try here (free): prompt → GrokBot → Jev chooses LLM → Claude / GPT working on GrokBot's computer 24/7 → result → Jev sends only the tasks Grok is weak at to Opus or GPT → Jev picks the best model for each task - for example, Claude for motion design and Codex for web design → runs on the ChatGPT and Claude subscriptions you already pay for (API also work) → works on GrokBot computer while you keep chatting → checks every result against the goal before you see it → GrokBot gets smarter and cheaper at the same time → And plenty more features in a bot everyone will call "obvious" by 2030 Try Jevopus, thank me later - then read the article on the full Jev architecture ↓

codila

272,469 次观看 • 12 天前

Jev + GrokBot is the best AI agent system I’ve built in my life It just made my setup CHEAPER and FASTER than what 95% of people are running... setup takes literally 7 minutes: prompt → GrokBot → Jev decision → GrokBot execution → result step 1 → open TypeSafe AI , create API key (keep it off chat paste) step 2 → tell Grok Bot: store TYPESAFE_API_KEY in the secure field step 3 → prompt Grok Bot: install typesafe-sdk on Agent Computer + smoke system_one (Choice) step 4 → tell Grok Bot: build the usage lab (router, dry-run, config, logs) - or clone Github below step 5 → add skill jev-usage-router: before browser / research / retry / extra bot → call the router, honor action step 6 → stay shadow first, read logs, then active when you trust it - kill switch: bypass jev or enabled: false step 7 → flip active: GrokBot obeys route - Jev decides - GrokBot executes - humans control irreversible actions the result: Jev + GrokBot the best and fastest agent running directly on your computer rn, I’ve already tested it on routine tasks - and the results are genuinely incredible You can come up with endless ways to use Jev + GrokBot - but the most important thing is to install it as soon as possible Copy this 2028 setup, explore my repo below - then read the full Jev deep dive ↓

Jev + GrokBot is the best AI agent system I’ve built in my life It just made my setup CHEAPER and FASTER than what 95% of people are running... setup takes literally 7 minutes: prompt → GrokBot → Jev decision → GrokBot execution → result step 1 → open TypeSafe AI , create API key (keep it off chat paste) step 2 → tell Grok Bot: store TYPESAFE_API_KEY in the secure field step 3 → prompt Grok Bot: install typesafe-sdk on Agent Computer + smoke system_one (Choice) step 4 → tell Grok Bot: build the usage lab (router, dry-run, config, logs) - or clone Github below step 5 → add skill jev-usage-router: before browser / research / retry / extra bot → call the router, honor action step 6 → stay shadow first, read logs, then active when you trust it - kill switch: bypass jev or enabled: false step 7 → flip active: GrokBot obeys route - Jev decides - GrokBot executes - humans control irreversible actions the result: Jev + GrokBot the best and fastest agent running directly on your computer rn, I’ve already tested it on routine tasks - and the results are genuinely incredible You can come up with endless ways to use Jev + GrokBot - but the most important thing is to install it as soon as possible Copy this 2028 setup, explore my repo below - then read the full Jev deep dive ↓

codila

384,277 次观看 • 21 天前

What is the best video editing agent for short form social? Does it actually work? We watched professional video editors, step by step, as they built short-form social reels in Adobe Premiere Pro. Today we're open-sourcing this preview dataset on Hugging Face, to make AI agents better at editing videos. The data set is 234 annotated steps across 4 computer-use trajectories. Editors narrated their reasoning aloud as they worked, so every step pairs a screenshot with the expert's own thought, a structured action, and executable grounding: >a Premiere MCP tool call, keyboard shortcut, menu path, or coordinate click. >The format follows the AgentNet trajectory schema, extended with a Premiere action taxonomy and multi-path execution. ***That makes it directly usable for computer-use agent SFT, reasoning mid-training, tool-use and function calling, and benchmarking agents against a human expert baseline. Enjoy!

What is the best video editing agent for short form social? Does it actually work? We watched professional video editors, step by step, as they built short-form social reels in Adobe Premiere Pro. Today we're open-sourcing this preview dataset on Hugging Face, to make AI agents better at editing videos. The data set is 234 annotated steps across 4 computer-use trajectories. Editors narrated their reasoning aloud as they worked, so every step pairs a screenshot with the expert's own thought, a structured action, and executable grounding: >a Premiere MCP tool call, keyboard shortcut, menu path, or coordinate click. >The format follows the AgentNet trajectory schema, extended with a Premiere action taxonomy and multi-path execution. ***That makes it directly usable for computer-use agent SFT, reasoning mid-training, tool-use and function calling, and benchmarking agents against a human expert baseline. Enjoy!

ben

40,192 次观看 • 2 个月前

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 state into a bounded action such as click, type, or stop. Code executes only valid operation-target pairs. There are already several open-source Jev web agents. 2. Context compaction > Decide which events from a long agent trace should remain. The selected text stays verbatim instead of being replaced with a generated summary. 3. Skill and context loading > Compare the current user turn against the available skills. Load only the instructions needed for that turn instead of filling the context window with every skill. 4. Typed tool-call compilation > Map a natural-language request to a function and fill its typed arguments. Each argument is evaluated separately before code allows execution. 5. Citation verification > Check whether a quoted passage exists and whether the surrounding evidence supports the claim. The output can be supported, unsupported, or contradicted. 6. Extraction verification > Run a cheap extractor first, then use Jev to verify questionable fields. Clean records stay on the fast path while uncertain ones reach a reasoning model. 7. Agent trace evaluation > Turn raw trajectories into queryable labels such as progress and repetition. This avoids asking another LLM to write a full review of every run. 8. Semantic regression tests > Replay a trace suite against a new agent build. Semantic checks can then pass or block prompt, model, tool, and policy changes in CI. 9. Jevgrep code search > Search a codebase by what the code does rather than its exact words. Jev scores candidate snippets and returns the most relevant code first. 10. Entity alignment > Compare two candidate records and decide whether to merge, review, or keep them separate. Candidate generation remains deterministic while Jev handles semantic identity. 11. Retrieval reranking > Let embeddings retrieve a broad candidate set, then use Jev to reorder passages by relevance. The generation model receives the most useful evidence first. 12. Memory promotion gate > Capture a completed agent trace, then judge whether its corrections contain a reusable lesson. Trace-backed lessons can be promoted while task-specific noise is discarded. If you want to see the final pattern in practice, it is already implemented in the Beacon open-source project. Beacon captures full sessions across Claude Code, Codex, Cursor, OpenCode, and 20+ agent harnesses, and then Jev identifies which workflows and corrections are worth learning from, so that a lesson discovered by one agent can become available to the others. GitHub repo: (don’t forget to star it ⭐) If you want to dive deeper, I also wrote about a similar mechanism in a hands-on guide. It covers building a Jev-style decision path with open models, entirely locally. Read it below.

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 state into a bounded action such as click, type, or stop. Code executes only valid operation-target pairs. There are already several open-source Jev web agents. 2. Context compaction > Decide which events from a long agent trace should remain. The selected text stays verbatim instead of being replaced with a generated summary. 3. Skill and context loading > Compare the current user turn against the available skills. Load only the instructions needed for that turn instead of filling the context window with every skill. 4. Typed tool-call compilation > Map a natural-language request to a function and fill its typed arguments. Each argument is evaluated separately before code allows execution. 5. Citation verification > Check whether a quoted passage exists and whether the surrounding evidence supports the claim. The output can be supported, unsupported, or contradicted. 6. Extraction verification > Run a cheap extractor first, then use Jev to verify questionable fields. Clean records stay on the fast path while uncertain ones reach a reasoning model. 7. Agent trace evaluation > Turn raw trajectories into queryable labels such as progress and repetition. This avoids asking another LLM to write a full review of every run. 8. Semantic regression tests > Replay a trace suite against a new agent build. Semantic checks can then pass or block prompt, model, tool, and policy changes in CI. 9. Jevgrep code search > Search a codebase by what the code does rather than its exact words. Jev scores candidate snippets and returns the most relevant code first. 10. Entity alignment > Compare two candidate records and decide whether to merge, review, or keep them separate. Candidate generation remains deterministic while Jev handles semantic identity. 11. Retrieval reranking > Let embeddings retrieve a broad candidate set, then use Jev to reorder passages by relevance. The generation model receives the most useful evidence first. 12. Memory promotion gate > Capture a completed agent trace, then judge whether its corrections contain a reusable lesson. Trace-backed lessons can be promoted while task-specific noise is discarded. If you want to see the final pattern in practice, it is already implemented in the Beacon open-source project. Beacon captures full sessions across Claude Code, Codex, Cursor, OpenCode, and 20+ agent harnesses, and then Jev identifies which workflows and corrections are worth learning from, so that a lesson discovered by one agent can become available to the others. GitHub repo: (don’t forget to star it ⭐) If you want to dive deeper, I also wrote about a similar mechanism in a hands-on guide. It covers building a Jev-style decision path with open models, entirely locally. Read it below.

Avi Chawla

128,229 次观看 • 13 天前

Introducing: OpenGranola 🔥 I built an open source meeting copilot for macOS. It transcribes both sides of your call on-device, searches your own notes in real time, and hands you talking points right when the conversation needs them. No audio leaves your Mac. Point it at a folder of markdown files, pick any LLM through OpenRouter (Claude, GPT-4o, Gemini, Llama), and it just works. It's invisible to screen share too — nobody knows you have it. The whole thing is open source. Link below

Introducing: OpenGranola 🔥 I built an open source meeting copilot for macOS. It transcribes both sides of your call on-device, searches your own notes in real time, and hands you talking points right when the conversation needs them. No audio leaves your Mac. Point it at a folder of markdown files, pick any LLM through OpenRouter (Claude, GPT-4o, Gemini, Llama), and it just works. It's invisible to screen share too — nobody knows you have it. The whole thing is open source. Link below

yazin

293,571 次观看 • 6 个月前

You can now use Jev right inside Claude Code 🤯 It's called jev-model-router, an early access mod built on Claude Code's new function hooks. Before every turn, it checks in with Jev and asks: > how mechanical the task is > how much reasoning it needs > whether it's risky Then it routes: → it'll move up to a stronger model on weak evidence, and only drops to a cheaper one when it's confident the task is simple → every decision gets logged in your transcript → if the call fails, your request runs untouched Setup: 1. copy the install command: npx claude-code-templates@latest --mod productivity/jev-model-router 2. paste it inside Claude Code 3. run claude with CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 set 4. accept the trust prompt on first launch Link: Also works with no api key, it just falls back to a built-in classifier with no confidence score. For real jev routing, add your typesafeApiKey or gatewayApiKey to ~/.claude/settings.json. Follow me for more AI workflows and tutorials.

You can now use Jev right inside Claude Code 🤯 It's called jev-model-router, an early access mod built on Claude Code's new function hooks. Before every turn, it checks in with Jev and asks: > how mechanical the task is > how much reasoning it needs > whether it's risky Then it routes: → it'll move up to a stronger model on weak evidence, and only drops to a cheaper one when it's confident the task is simple → every decision gets logged in your transcript → if the call fails, your request runs untouched Setup: 1. copy the install command: npx claude-code-templates@latest --mod productivity/jev-model-router 2. paste it inside Claude Code 3. run claude with CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 set 4. accept the trust prompt on first launch Link: Also works with no api key, it just falls back to a built-in classifier with no confidence score. For real jev routing, add your typesafeApiKey or gatewayApiKey to ~/.claude/settings.json. Follow me for more AI workflows and tutorials.

Alvaro Cintas

43,331 次观看 • 19 天前

Sign in with ChatGPT is available for all OSS tools - Every single one of them. This has massive benefits! Here I have Blender running locally with a Chat interface on it powered by Sign in with ChatGPT. It has its own super-lightweight custom built harness that speaks to the Blender MCP and has Computer Use. I can package this up as a binary and send it to a colleague who can click open, Sign in with ChatGPT and just get to the good bits. They’ll never have to switch tools. Yay? Blender Artists - INACTIVE

Sign in with ChatGPT is available for all OSS tools - Every single one of them. This has massive benefits! Here I have Blender running locally with a Chat interface on it powered by Sign in with ChatGPT. It has its own super-lightweight custom built harness that speaks to the Blender MCP and has Computer Use. I can package this up as a binary and send it to a colleague who can click open, Sign in with ChatGPT and just get to the good bits. They’ll never have to switch tools. Yay? Blender Artists - INACTIVE

Vignesh

11,233 次观看 • 7 天前

Found a great production use case for Jev. I used Jev to organize ~2.3K AI research papers. The total cost was $0.14, and it took about 83 seconds. The process: The papers already had old tags, which I ran through a previous open model (DeepSeek V4 Flash). However, I wasn't confident in the classifications, and I didn't want to spend more on tokens unless I spent time tuning it into a good LLM classifier via few-shot (more expensive). Too tedious, too costly, and unsustainable. Luckily for us, we now have Jev to help us with organizing papers better. So Jev first went through all the papers and retagged them. It agreed with 75% of the previous tags. Jev found about 579 high-confidence topic changes. I evaluated reliability by manually labeling 30 disagreements and accepted all of them. I was astonished by Jev's classification capabilities. We applied and verified all changes in production. I'm much more satisfied with the classifications, but I think there is still room for improvement. Check out the papers here: I will experiment with Jev more. The takeaway is that pipelines can be significantly improved by carefully combining System One and System Two models. Jev clearly unlocks more interesting ways to organize papers and offer a more useful discovery layer for research papers. More updates on that soon.

Found a great production use case for Jev. I used Jev to organize ~2.3K AI research papers. The total cost was $0.14, and it took about 83 seconds. The process: The papers already had old tags, which I ran through a previous open model (DeepSeek V4 Flash). However, I wasn't confident in the classifications, and I didn't want to spend more on tokens unless I spent time tuning it into a good LLM classifier via few-shot (more expensive). Too tedious, too costly, and unsustainable. Luckily for us, we now have Jev to help us with organizing papers better. So Jev first went through all the papers and retagged them. It agreed with 75% of the previous tags. Jev found about 579 high-confidence topic changes. I evaluated reliability by manually labeling 30 disagreements and accepted all of them. I was astonished by Jev's classification capabilities. We applied and verified all changes in production. I'm much more satisfied with the classifications, but I think there is still room for improvement. Check out the papers here: I will experiment with Jev more. The takeaway is that pipelines can be significantly improved by carefully combining System One and System Two models. Jev clearly unlocks more interesting ways to organize papers and offer a more useful discovery layer for research papers. More updates on that soon.

elvis

15,427 次观看 • 19 天前

We are entering an extremely exciting era for open-weight models. Kimi K2.6 now feels like a top agentic model. I took it for a spin via Fireworks AI fast inference APIs. Kimi K2.6 has impressive agentic capabilities, design skills, and the ability to synthesize large amounts of information. I built a little Skill that produces survey papers on any AI research topic you want. (see example in the clip) You can use the skill to tell your agent to generate a survey on whatever topic and watch it go to work. The artifact was fully generated by Kimi.ai's Kimi K2.6. It's cheap and fast. Next step for me is to explore ways to continue integrating the capabilities of these models on use cases like automating my LLM knowledge bases and augmenting my agent memory capabilities. Stay tuned for more.

We are entering an extremely exciting era for open-weight models. Kimi K2.6 now feels like a top agentic model. I took it for a spin via Fireworks AI fast inference APIs. Kimi K2.6 has impressive agentic capabilities, design skills, and the ability to synthesize large amounts of information. I built a little Skill that produces survey papers on any AI research topic you want. (see example in the clip) You can use the skill to tell your agent to generate a survey on whatever topic and watch it go to work. The artifact was fully generated by Kimi.ai's Kimi K2.6. It's cheap and fast. Next step for me is to explore ways to continue integrating the capabilities of these models on use cases like automating my LLM knowledge bases and augmenting my agent memory capabilities. Stay tuned for more.

elvis

47,678 次观看 • 5 个月前

Jev + GrokBot is the best GTM system I've ever built It just made my GTM x200 CHEAPER and x400 FASTER than what 95% of teams are running... setup takes literally 9 minutes: prompt → GrokBot → Jev routes every candidate → GrokBot opens only survivors → campaign step 1 → open TypeSafe AI, create API key (keep it off chat paste) step 2 → tell GrokBot: store TYPESAFE_API_KEY in the secure field step 3 → prompt GrokBot: install typesafe-sdk on Agent Computer + smoke system_one (Choice) step 4 → point it at a target: "read end to end, pull positioning, ICP, every proof point. no copy yet" step 5 → add skill gtm-router: every candidate from X / LinkedIn / YouTube gets 6 typed questions → CHEAP SKIP / OPEN FULL / FLAG KOL step 6 → let Jev rank hook archetypes by viral rate, not by how often people post them - this is where the whole playbook comes from step 7 → GrokBot assembles the KOL shortlist and the 7-day plan - you stay in control of anything irreversible the result: → 3,412 candidates, X, LinkedIn and YouTube. → 15.7 seconds. $0.41. → me doing the same reading: 6h 12m. 8 grok bots brief it, Jev decides, GrokBot executes. no fine-tuning, no embeddings, no vector db - 6 typed questions and a schema. Setup your GrokBot JEV GTM today, then read the article below to learn how to build an agent team with JEV.

Jev + GrokBot is the best GTM system I've ever built It just made my GTM x200 CHEAPER and x400 FASTER than what 95% of teams are running... setup takes literally 9 minutes: prompt → GrokBot → Jev routes every candidate → GrokBot opens only survivors → campaign step 1 → open TypeSafe AI, create API key (keep it off chat paste) step 2 → tell GrokBot: store TYPESAFE_API_KEY in the secure field step 3 → prompt GrokBot: install typesafe-sdk on Agent Computer + smoke system_one (Choice) step 4 → point it at a target: "read end to end, pull positioning, ICP, every proof point. no copy yet" step 5 → add skill gtm-router: every candidate from X / LinkedIn / YouTube gets 6 typed questions → CHEAP SKIP / OPEN FULL / FLAG KOL step 6 → let Jev rank hook archetypes by viral rate, not by how often people post them - this is where the whole playbook comes from step 7 → GrokBot assembles the KOL shortlist and the 7-day plan - you stay in control of anything irreversible the result: → 3,412 candidates, X, LinkedIn and YouTube. → 15.7 seconds. $0.41. → me doing the same reading: 6h 12m. 8 grok bots brief it, Jev decides, GrokBot executes. no fine-tuning, no embeddings, no vector db - 6 typed questions and a schema. Setup your GrokBot JEV GTM today, then read the article below to learn how to build an agent team with JEV.

Movez

86,466 次观看 • 20 天前

$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 ↓$

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

95,371 次观看 • 18 天前

this is pure f*cking treasure. my ai bill last month: claude max 20x ............ $200 chatgpt pro ............... $200 supergrok heavy ........... $300 total ..................... $700 then i went through github and found 5 repos that eat the boring half of that bill on my own machine rizzo-flow ................ 833 stars the open local take on typesafe's jev. a 4.4gb model on llama.cpp answers yes / no / pick one / score with a probability on every answer, and you point your api at localhost by changing one url llm2jev ................... 391 stars turns qwen3.5-4b into a jev-style decision model. 48ms p50 in their own benchmark, against 652ms for the real jev fast-browser-use .......... 202 stars a browser agent that runs 100% local on qwen3.5-9b and plugs into claude code and codex as a skill. opens the right wikipedia article in about 4 seconds, zero cloud calls deepseekgui ............... 84 stars a desktop workbench on deepseek harness with git, a built-in browser and memory. you pay deepseek per token instead of a flat $200 a month oriveo .................... 25 stars one app for openai, anthropic, gemini, grok, deepseek and 10 more providers, plus ollama on your own gpu. your keys, no subscription, no account claude still writes my hardest code. the yes or no calls, the browser clicking and the everyday chatting moved to my gpu and my own api keys, and the receipt stopped looking like rent repos in the comments

this is pure f*cking treasure. my ai bill last month: claude max 20x ............ $200 chatgpt pro ............... $200 supergrok heavy ........... $300 total ..................... $700 then i went through github and found 5 repos that eat the boring half of that bill on my own machine rizzo-flow ................ 833 stars the open local take on typesafe's jev. a 4.4gb model on llama.cpp answers yes / no / pick one / score with a probability on every answer, and you point your api at localhost by changing one url llm2jev ................... 391 stars turns qwen3.5-4b into a jev-style decision model. 48ms p50 in their own benchmark, against 652ms for the real jev fast-browser-use .......... 202 stars a browser agent that runs 100% local on qwen3.5-9b and plugs into claude code and codex as a skill. opens the right wikipedia article in about 4 seconds, zero cloud calls deepseekgui ............... 84 stars a desktop workbench on deepseek harness with git, a built-in browser and memory. you pay deepseek per token instead of a flat $200 a month oriveo .................... 25 stars one app for openai, anthropic, gemini, grok, deepseek and 10 more providers, plus ollama on your own gpu. your keys, no subscription, no account claude still writes my hardest code. the yes or no calls, the browser clicking and the everyday chatting moved to my gpu and my own api keys, and the receipt stopped looking like rent repos in the comments

starmex

73,538 次观看 • 4 天前

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.

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

365,108 次观看 • 17 天前

Here's what The Browser Company's AI eng & ML teams are working on for Dia right now: (This is a pitch to come work for us; info at end) 🤖 COMPUTER USE – we've built our own bespoke APIs on top of Chromium to optimize latency, accuracy, and cost of computer-using agents. Demo attached. Big breakthroughs here in recent weeks. 🛡️ ON-DEVICE MODELS – we've built our own custom infra to run everything from encoder-only models to full LLMs on device. It's cross-platform, supports LoRa adapters, and optimized for the GPU. This system preserves privacy and enables fast inference times. 🧠 MEMORY – with your permission, Dia automatically tailors your AI experiences to you, personally, based on the tabs you open while browsing normally every day. We're also bringing vertical memory to specific features. ♻️ DATA FLYWHEELS – our Fall/Winter P0 is to double-down on training custom models based on implicit signals from daily use of Dia. Dia should get smarter and more useful the more people use it. Whether via RL, auto-generated prompts, or otherwise. If this work sounds interesting to you please visit our jobs page or email careers@thebrowser.company. Hiring nearly every related role -- from ML engineers to people prototyping with AI and context/prompt writers -- everyone encouraged to apply!!

Here's what The Browser Company's AI eng & ML teams are working on for Dia right now: (This is a pitch to come work for us; info at end) 🤖 COMPUTER USE – we've built our own bespoke APIs on top of Chromium to optimize latency, accuracy, and cost of computer-using agents. Demo attached. Big breakthroughs here in recent weeks. 🛡️ ON-DEVICE MODELS – we've built our own custom infra to run everything from encoder-only models to full LLMs on device. It's cross-platform, supports LoRa adapters, and optimized for the GPU. This system preserves privacy and enables fast inference times. 🧠 MEMORY – with your permission, Dia automatically tailors your AI experiences to you, personally, based on the tabs you open while browsing normally every day. We're also bringing vertical memory to specific features. ♻️ DATA FLYWHEELS – our Fall/Winter P0 is to double-down on training custom models based on implicit signals from daily use of Dia. Dia should get smarter and more useful the more people use it. Whether via RL, auto-generated prompts, or otherwise. If this work sounds interesting to you please visit our jobs page or email [email protected]. Hiring nearly every related role -- from ML engineers to people prototyping with AI and context/prompt writers -- everyone encouraged to apply!!

Josh Miller

68,240 次观看 • 1 年前

Inviting early testers and contributors to Project Devika - The open-source alternative to Devin. 👩‍💻 As of now, Devika is far from the capabilities of Devin... but we'll eventually get there. So I am calling the open-source community to join forces! ❤️ Features: - 12 Agentic models that can interact with each other in a feedback loop to understand, browse, research, code, document, and make decisions according to the user's query to complete a project. - Supports Claude 3, GPT-4, GPT-3.5, and Local LLMs via ollama. - Devika can run the code she writes and fix/patch the code herself if she encounters any errors without user intervention. - Devika can deploy static websites she creates on Netlify. (Experimental) - And much more... Will be doing an official launch after intensive testing and bug fixes. 🙌 I've created a Discord server for the early testers and contributors. If you're interested in joining the team, reply to this tweet and I will DM you the invite link. #buildinpublic

Inviting early testers and contributors to Project Devika - The open-source alternative to Devin. 👩‍💻 As of now, Devika is far from the capabilities of Devin... but we'll eventually get there. So I am calling the open-source community to join forces! ❤️ Features: - 12 Agentic models that can interact with each other in a feedback loop to understand, browse, research, code, document, and make decisions according to the user's query to complete a project. - Supports Claude 3, GPT-4, GPT-3.5, and Local LLMs via ollama. - Devika can run the code she writes and fix/patch the code herself if she encounters any errors without user intervention. - Devika can deploy static websites she creates on Netlify. (Experimental) - And much more... Will be doing an official launch after intensive testing and bug fixes. 🙌 I've created a Discord server for the early testers and contributors. If you're interested in joining the team, reply to this tweet and I will DM you the invite link. #buildinpublic

mufeed vh

155,153 次观看 • 2 年前

OpenCode Go is now wired into Codex!! The pricing is insane. $10 gets you 10,000 DeepSeek requests every 5 hours (no weekly limits). I converted that into DeepSeek API dollars because I thought I was reading it wrong, and the same 5 hours of usage would run somewhere between $10 and $30 depending on how big your context gets. So one afternoon of use already covers the whole sub. It comes with Kimi K3 as well. Both sit in the picker next to my other models now. Next time we hit a limit in the middle of a loop, we can grab it and keep going.

OpenCode Go is now wired into Codex!! The pricing is insane. $10 gets you 10,000 DeepSeek requests every 5 hours (no weekly limits). I converted that into DeepSeek API dollars because I thought I was reading it wrong, and the same 5 hours of usage would run somewhere between $10 and $30 depending on how big your context gets. So one afternoon of use already covers the whole sub. It comes with Kimi K3 as well. Both sit in the picker next to my other models now. Next time we hit a limit in the middle of a loop, we can grab it and keep going.

Ziwen

435,072 次观看 • 2 个月前

Hiring managers: you’re spending 15 hours screening resumes, squinting at buzzwords, and still wondering if you missed the best candidate. Perplexity Computer does it in 4 minutes. What I asked: “Screen these 200 resumes against this job description, rank the top 10, and explain your reasoning for each. Prioritize must-haves, flag deal-breakers, and show me exactly where in each resume you found the evidence.” What I got: → Ranked list with match scores tied to the JD requirements → Clear, specific reasons each candidate made the cut (skills, scope, impact) → Red flags called out with receipts (job-hopping, missing core tools, inflated claims) → A side-by-side comparison table of the top 5 across every key competency → Short, tailored interview questions for each candidate—built from their actual projects and gaps → A quick “why not” summary for the next 10 so you can sanity-check the cutoff Real outputs. Cited data. No guesswork. Just faster, cleaner decisions.

Hiring managers: you’re spending 15 hours screening resumes, squinting at buzzwords, and still wondering if you missed the best candidate. Perplexity Computer does it in 4 minutes. What I asked: “Screen these 200 resumes against this job description, rank the top 10, and explain your reasoning for each. Prioritize must-haves, flag deal-breakers, and show me exactly where in each resume you found the evidence.” What I got: → Ranked list with match scores tied to the JD requirements → Clear, specific reasons each candidate made the cut (skills, scope, impact) → Red flags called out with receipts (job-hopping, missing core tools, inflated claims) → A side-by-side comparison table of the top 5 across every key competency → Short, tailored interview questions for each candidate—built from their actual projects and gaps → A quick “why not” summary for the next 10 so you can sanity-check the cutoff Real outputs. Cited data. No guesswork. Just faster, cleaner decisions.

Leonardo

29,673 次观看 • 6 个月前