Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

introducing OpenBench v1, an open framework for measuring AI performance and efficiency for your codebase and use case. Companies are realizing that you can't simply tokenmaxx, and are frantically looking for better ways to use and measure AI use and efficiency. One approach is evidenced by the rise in...

124,431 görüntüleme • 3 ay önce •via X (Twitter)

67 Yorum

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

open :)

Filip profil fotoğrafı
Filip3 ay önce

okay so the takeaway is that cursors harness is the best for solving tasks overall but it outputs most tokens? and pi isnt as great for % of solved tasks but the output tokens per solved task is much lower making it the cheapest overall?

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

yes Cursor has done well for the two models I got to test it with, one is their own model. They don't have ease to test with Deepseek, Kimi, etc. so i can't say across the board but definitely impressed by their harness. Pi has always done best in token efficiency and latency. It actually regressed from gpt 5.5 to 5.6 in correctness, wouldn't attribute to the harness just yet. I'm bullish on Pi coming back

Filip profil fotoğrafı
Filip3 ay önce

hmm interesting.. i wonder what pi does differently to get such token efficiency.. system prompts or harness instructions itself?

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

@filip_a__ most minimal is probably every aspect: system prompt, tools, etc. claude also removed 80% of its system prompt according to @trq212

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

one thing to call out: for correctness especially I need to add more difficult long horizon tasks. But I think the best way to judge these right now are through trends. Few trends I've seen repeated through the different updates: > Cursor harness performs well in correctness > Pi and claude have been efficient in token spend + latency > Codex likes to token maxx, I've even tested ablations myself (codex variants) and see opportunity to make the harness more efficient

stridell profil fotoğrafı
stridell3 ay önce

pi keeps winning

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

yes bullish Pi

Chase profil fotoğrafı
Chase3 ay önce

love this! not enough content out there that shows perf difference for the same model across different harnesses

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

appreciate it!

Sydney Runkle profil fotoğrafı
Sydney Runkle3 ay önce

how does deepagents stack up?

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

let me add to the list

Sezan profil fotoğrafı
Sezan3 ay önce

@thsottiaux we need to fix codex bro...It was my personal observation as well coz i also got better results using 5.6 with claude code...but we have benchmark now...look at the solve rate and token efficiency for 5.6 on other harness

Auro profil fotoğrafı
Auro3 ay önce

Very cool benchmark and I'm excited to learn more! Will you be expanding to more harnesses?

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

yes! any specific ones you're intersted in? Right now I'm adding: - omp harness - aider harness - Inkling @thinkymachines - Laguna @poolsideai

Auro profil fotoğrafı
Auro3 ay önce

@thinkymachines @poolsideai Droid and copilot are the two that come to mind! OpenCode v1 vs OpenCode v2 is also interesting to me

Divanshu Chauhan profil fotoğrafı
Divanshu Chauhan3 ay önce

@mattlam_ @thinkymachines @poolsideai I'd love to see droid as well

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

@Aurokinn @thinkymachines @poolsideai let me see what I can do, I am curious about OpenCode v2, not sure how @thdxr thinks it'll be diff, i havent read up it too much yet. Also I pay for these out of pocket and am fun employed rn, so will try my best but these subs + api keys add up 😂

Auro profil fotoğrafı
Auro3 ay önce

@Divkix @thinkymachines @poolsideai @thdxr totally get that! if I can help run some evals for you let me know I have a variety of subs for my cross-harness tooling if you're comfortable with cliproxyapi I believe you can bring your codex sub to copilot + droid, and amp natively supports codex oauth

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

@Divkix @thinkymachines @poolsideai @thdxr oh sick ye thats how i got gpt5.6 on claude, but i don't want to mess with claude oauth on other harnesses, cause apparently you can get banned

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

@Divkix @thinkymachines @poolsideai @thdxr actually the best part about OpenBench is that it's open, if you're curious and willing, try to run this on your machine and compare results :)

MisterCh0c profil fotoğrafı
MisterCh0c3 ay önce

Try tura with sol!

Thomas Silva profil fotoğrafı
Thomas Silva3 ay önce

Why are the stats in this video different from the dashboard? e.g. for 5.6 sol the video shows cursor as the least efficient but then the site says it is the most efficient

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

good catch fixing, dashboard is wrong

Yash Gogri profil fotoğrafı
Yash Gogri3 ay önce

This is sick!

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

appreciate it Yash

rehen profil fotoğrafı
rehen3 ay önce

OpenBench measures production reality.

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

@rehensina yessir!

Jorge profil fotoğrafı
Jorge3 ay önce

most relevant for me, for gpt 5.6: pi • 35K tokens • 72.7% opencode • 90K tokens • 80% grok build • 142K tokens • 82.2% codex • 157K tokens • 72.7% lmao 😂

Arrow profil fotoğrafı
Arrow3 ay önce

where is glm

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

ye I should've included in video, but i did benchmark previously, results should be in repo, but TLDR GLM is very good for day to day tasks and very efficient

FloppyBlahaj🦈 profil fotoğrafı
FloppyBlahaj🦈3 ay önce

That’s really sick!

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

appreciate it!

VibecodePro profil fotoğrafı
VibecodePro3 ay önce

Kilo cli?

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

can take a look

Vadims profil fotoğrafı
Vadims3 ay önce

There seems to be a mistake in the total token calculation for the Grok build: cache-read tokens are included for it but not for the others. I would also recheck the Cursor build, as it ended up with only 73 uncached input tokens.

Artificial Guy / João Vitor A. profil fotoğrafı
Artificial Guy / João Vitor A.3 ay önce

Amazing thanks

Jabol aso profil fotoğrafı
Jabol aso3 ay önce

Great direction — cost-per-token alone hides real efficiency. Worth also tracking task success rate and latency variance, not just tokens/$, since a cheaper model that needs 3x retries often costs more in wall-clock time. Will you support custom eval harnesses?

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

agreed! Right now i'm latency and success rate, didn't have latency in the video but it's up on the repo. Also for tokens I do track input/output/cache splits! One caveat is for cursor/cli they're based on what the cli reports to me, the rest of the harnesses let me use a proxy that aggregates their token spend from providers.

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

good catch, fixing the token solve, dashboard is wrong there. Med wall on dashboard was comparing all Cursor solves, but video was only latency for all problems that all harnesses solved. My bad, can look confusing, can make more clear.

Furkan Ceyran profil fotoğrafı
Furkan Ceyran3 ay önce

No worries, anyone taking a quick look can figure it out anyway, so those are pretty minor issues. You’ve genuinely filled a real need here, thanks for making this benchmark. It’s exactly what I was looking for :)

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

appreciate it! will continue to improve on it, and open to feedback

Centraly profil fotoğrafı
Centraly3 ay önce

ofc, benchmark showing pi as best harness, hover the profile -> pi developer, completely unbiased opinion

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

i use all the coding harnesses. I built pi-gui because I think it's a product missing in the market. You can also view the results and try running yourself, they're all open haha

逍遥醍醐仙TIHU profil fotoğrafı
逍遥醍醐仙TIHU3 ay önce

Well done! People always benchmark the models, fewer do this to the harness

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

appreciate it!

Vitor de Lucca 🇧🇷 🏳️‍🌈 profil fotoğrafı
Vitor de Lucca 🇧🇷 🏳️‍🌈3 ay önce

Try reasonix with deepseek

Sayem profil fotoğrafı
Sayem3 ay önce

interesting

RayBytes profil fotoğrafı
RayBytes3 ay önce

That Claude vs Codex token difference is crazy. Any idea why there’s such a stark difference?

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

claude killed 80% of its system prompt supposedly recenlty, think it's made a big help, and look at Pi it's minimal and does well

Saswata profil fotoğrafı
Saswata3 ay önce

this is the new open router

KYDNO profil fotoğrafı
KYDNO3 ay önce

been waiting for a harness bench for a while, go work at Artificial Analysis!

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

same surprised I didn't see one, so decided to build one haha

buildwithjay profil fotoğrafı
buildwithjay3 ay önce

OpenBench feels like the part every AI team eventually needs. not another model leaderboard, just proof of which one is cheap on your own repo.

Sebastian Buzdugan profil fotoğrafı
Sebastian Buzdugan3 ay önce

openbench needs drift tracking because static eval sets go stale fast in real codebases

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

good idea I'll take a look!

MI COWI profil fotoğrafı
MI COWI3 ay önce

does it differentiate cached tokens?

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

yes! I have a proxy that sit in front and differentiates tokens reported back from providers. Unfortunately some providers like @cognition Devin and @cursor_ai are more closed, and those I take wtv their cli reports back.

Milkman Dan profil fotoğrafı
Milkman Dan3 ay önce

Explains a few things, like why it seems like most of the "5.6 is killing my tokens" complaints are coming from Codex users.

itsaflecha profil fotoğrafı
itsaflecha3 ay önce

good stuff.

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

appreciate it

Marco Lee profil fotoğrafı
Marco Lee3 ay önce

It’s Pi cheaper than the other harness?

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

yes from my exp

erik@try.works profil fotoğrafı

Let me integrate this with role-model

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

yes please! lmk how it goes

Hi9841 profil fotoğrafı
Hi98413 ay önce

Change the name to HarnessBench

Matthew Lam profil fotoğrafı
Matthew Lam3 ay önce

thinking about it lol

Benzer Videolar

Insane Grok Grok Bot upgrade! Finally, you can connect Grok Bot to different agent harnesses and run tasks through their native runtimes. Devs just open-sourced HarnessRouter, the infrastructure layer that lets Grok Bot run tasks across: - Codex - Hermes - Claude Code - DeepSeek Harness - System One, powered by Jev - Pi, and 20 more GitHub repo: (don’t forget to star it ⭐) With HarnessRouter, each external specialist gets to use its own harness, model, tools, skills, and agent loop while Grok coordinates the project from one conversation. I tested this by asking Grok Bot to turn a support-ticket CSV into an interactive dashboard. Grok Bot assigned the analysis to DeepSeek Harness with Claude Sonnet 5.5, passed the output to Codex with GPT-5.5, and checked the finished dashboard in its browser. This differs from simply creating more Bots. These workers are not additional Grok Bots, and Grok Bot itself does not switch harnesses. Instead, it remains the coordinator while the delegated tasks run inside separate HarnessRouter sessions with the harness of your choice. So for another task, you can use Claude Code, Hermes, Pi, etc., without requiring a separate integration for task execution, sessions, streaming, and generated files. HarnessRouter standardizes all those operations through the Unified Harness Protocol (UHP). UHP handles sessions, streaming, files, cancellation, and failures through the same interface, regardless of which harness runs the task. I shared the GitHub repo above. And if you want to dive deeper into Grok Bot, I wrote about it in full in a masterclass, including the shared computer, memory, skills, routines, and the macOS setup. Read it below.

Avi Chawla

137,148 görüntüleme • 14 gün önce

We’re launching Optima. Now anyone can create a custom benchmark for their use case, leveraging Artificial Analysis’ leading research and platform Building and running benchmarks is difficult. We have distilled Artificial Analysis’ research and experience developing benchmarks into Optima, a new platform for benchmarking models on your own workloads and comparing performance, speed and cost efficiency. Optima allows you to find the best model for your task, or an equally performant alternative to your current setup at 10x lower cost or time per task. We’ve integrated Artificial Analysis' research and experience in benchmarks across the Optima workflow: ➤ Build benchmarks based on your own data and use cases: There are three ways to build a benchmark with Optima. Upload an existing evaluation dataset from your own files or Hugging Face, or import agent traces from platforms including Arize AI, Braintrust and langfuse.com. Install the Optima skill to build a benchmark using context from your coding environment and previous sessions. Or simply describe your use case and provide example inputs and outputs, and Optima will build the benchmark for you ➤ Run across the latest models: Run the same benchmark across leading models in a single click, and keep your leaderboard up to date as soon as new models are released ➤ Bring Artificial Analysis grading to your own benchmark: Evaluate responses against objective rubric criteria or using the same pairwise judging approach used for Artificial Analysis benchmarks including GDPval-AA and AA-Briefcase. For pairwise judging, select your preferred responses from a sample and Optima uses those preferences to rank models across your test set ➤ Compare performance, cost and time efficiency: Optima measures more than model performance. Cost per Task and Time per Task are tracked alongside benchmark scores, with category-level results and support for custom metrics, allowing you to compare the tradeoffs between models for your specific use case Ahead of launch, here are examples questions our beta testers answered with Optima: ➤ Which model can save me 10x the cost without a meaningful decrease in quality for my finance & accounting agent? ➤ Which model best matches the writing style of lawyers for my legal agent? ➤ Which model can best identify different elements in my custom image dataset? Optima is available today. Build your own benchmark at

Artificial Analysis

133,823 görüntüleme • 2 ay önce

Harness Engineering 2.0 is here! We benchmark models all the time but the harness running the model can dramatically improve the result, cost, and execution time too. And finally, devs just open-sourced Harness Arena, where you can test the same task across multiple harness and model combinations side by side. You provide one task and then run it across several model x harness configs that you want to test. Every config receives the same prompt, files, tools, skills, and evaluation checks. Harness Arena then returns: - total cost - execution time - whether the task passed - files and artifacts produced If you want to try it yourself, it is implemented within the open-source HarnessRouter project. Here's the repo: (don't forget to star it ⭐ ) HarnessRouter is 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 25 more agent harnesses In Harness Arena, the cheapest run does not automatically win. A config must complete the task correctly first. Cost and execution time are compared only among the configurations that pass. Here's the result from one Harness Arena test: - Hermes + GPT-5.2: 5/5 successful runs using 0.47 credits - Claude Code + Opus 4.8: 3/5 successful runs using 223 credits That is around 474x difference in credits, while the more expensive configuration also failed two runs. You can keep the model fixed to measure how much the harness changes the result. Or vary both to find the best harness and model pairing for that task. This helps answer practical questions such as: - Should this task run on Codex or Claude? - Can a cheaper config still pass every check? - Which setup is best to handle this workload? Once you find the best config, you can run future tasks through it using the same Unified Harness Protocol (UHP) interface for sessions, streaming, files, artifacts, cancellation, and failures. So you are no longer choosing an agent stack based only on a model leaderboard. Instead, you can benchmark the complete runtime on the task your product actually needs to solve. To dive deeper, my co-founder wrote an article explaining why model routing is different from harness routing, how UHP works, and what supporting multiple agent runtimes involves. It also covers the local setup, a working request, and how sessions and files move through the system. Read it below.

Avi Chawla

30,563 görüntüleme • 3 gün önce

Introducing *Switch*: a *harness framework* for *decision models* like Jev I looked for this the other day and was surprised to not find anything like it You obviously cannot use a decision model like an LLM in a coding agent harness like Pi, because Jev cannot generate tool calls But what if there was a framework that "generated the tool calls" for it programmatically, and Jev only had to pick out of that finite set of choices That is what switch does. You pick a "domain" to implement the decision model in, and it provides a core API to define your state, and the functions that will derive decision model questions out of that state. Chess is a domain, as well as being a rubric judge for evals It basically standardizes what I imagine a lot of people are already vibe-coding, to an abstract interface: calling a decision-model API through multiple steps, i.e. an agent loop over finite choices Because of the finiteness of the output of a decision model, you cannot have a general pure decision model harness. Instead, you need to implement specific ones that generate the choices programmatically (or have an LLM generate the choices, but I find the former more interesting) A primary use case I have for this is use as a judge in an eval. For example, At the end of a task run that involves a bunch of documents, most people currently follow this approach: extract text out of PDF/docx/md files, and dump them right into the context But what if the visual formatting of the output is a judging criterion? Then you have to dump an image of every page in the input state. But what if you have 200 pages, and your question does not need looking at all of them? What if Jev could navigate through the haystack and find the info it needs? I have noticed that Jev is not so good at chess nor being a Decision-Model-as-a-Judge. It sucks at chess, and it does not perform well enough to replace GPT 6.1 Sol as a judge in the domain I am working for But switch is not only for Jev! It is for any decision model including the ones supported by the pi-ai package So once you can generate enough data with a better model, you should be able to pick an open source one and fine-tune it on your use case to perform better! And the model should be trained in a harness like switch's to be especially performant and cost-efficient I wanted to get this out because I find the idea very exciting, at least for benchmarking. Jev is currently not there, but decision models obviously will be there at some point, and we can take them there! There are also a lot of potential gains from picking a specific domain, and creating a looping agent that does a job for 100x cheaper! Let me know if you have any ideas, I am quite keen to try this on new domains! Repo:

Onur Solmaz

106,096 görüntüleme • 9 gün önce