Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

I have been testing “OpenAI” o3 mini-high. The exposure of the “reasoning” on this model in my tests seem to not be the full reasoning, but a shifted and edited and tunicated version of what we would expect from a full exposure of the reasoning engine. See the video...

74,506 Aufrufe • vor 1 Jahr •via X (Twitter)

11 Kommentare

Profilbild von Vikram Arora
Vikram Aroravor 1 Jahr

An actual review.

Profilbild von Brian Roemmele
Brian Roemmelevor 1 Jahr

Vikram, yes, I broke down and had to do it. Be careful I may start doing video reviews!!! Smash that like button and subscribe. Just practicing.

Profilbild von The Information
The Informationvor 1 Jahr

OpenAI is betting on a little-known startup to stay ahead of Elon Musk in the supercomputer race.

Profilbild von Ken Cornia
Ken Corniavor 1 Jahr

Your tests of OpenAI & DeepSeek outputs & reasoning insights are interesting, as open source DeepSeek out performs closed source OpenAI & it cost them far less to do it Makes one wonder about OpenAI's allegations that their tech was obtained in an unauthorized manner by DeepSeek

Profilbild von EMILY
EMILYvor 1 Jahr

DeepSeek is totally crushing it

Profilbild von Ed
Edvor 1 Jahr

Deepseek r1 has so much personality eh

Profilbild von RicBezos
RicBezosvor 1 Jahr

You really don't like it Brian, do you?

Profilbild von Brian Roemmele
Brian Roemmelevor 1 Jahr

Does it show? “OpenAI” can fix this and the image they made for themselves.

Profilbild von volar yu
volar yuvor 1 Jahr

it's high because it's always high? am wondering what I should try it on, and curious about the limits of a 20$ sub on it

Profilbild von 🍓 Ada
🍓 Adavor 1 Jahr

naming models is an art form, brian. it's like naming a new species—gotta keep it quirky. as for the reasoning, maybe the model's just trying to keep us on our toes. let's see where this 'mini-high' takes us.

Profilbild von Brian Kelly
Brian Kellyvor 1 Jahr

Thank you @BrianRoemmele for real AI news and analysis ! Let’s build !

Ähnliche Videos

I have been testing DeepSeek-V4-Pro with the Pi coding agent. I am mindblown by how well it works out of the box. A few notes: I spent a few hours building an LLM wiki with an agent powered entirely by DeepSeek-V4-Pro on Fireworks inference. This is the first time I feel like there is an open-weight model that can reason at the level of Claude and Codex. And it does this in a cost-effective way with support for 1M context length. To be clear, I am using DeepSeek-V4-Pro inside of Pi without any special configuration. It works out of the box. It's exciting that there is a model that can just be plugged into a basic harness like Pi, and it just works. I've never seen that before. Most models require lots of configuration and setup. DeepSeek's DeepSeek-V4-Pro is clearly good at agentic coding (probably the best from the open-weight models), but the model is also great on knowledge-intensive tasks where reasoning matters. The agent pulled agentic engineering best practices from different company docs (Anthropic, OpenAI, Google, Stripe, Meta, Modal, DeepSeek, Mistral, Cohere), searched and digested Reddit and HN threads, summarized arxiv papers, and surfaced trending GitHub repos. Then it distilled everything into actionable tips across categories. I love the Wiki it built. The quality is really good. Here is a snapshot of what the wiki looks like: DeepSeek-V4-Pro handled the task without breaking stride. Multi-step research queries, code generation for scaffolding, context-heavy reasoning across disparate sources. For coding specifically, this is the first open-weight model that genuinely feels like a Codex or Claude Code experience. It compares in capability and actual multi-turn agentic work. What made the loop feel so responsive was Fireworks' inference speed (the fastest in the market) and the fact that they actually validate models at the systems level before shipping. No corrupted reasoning traces. Just fast, reliable iteration. The hybrid CSA and HCA attention design cuts KV cache to just 10% and inference FLOPs by nearly 4x at 1M-token context. This is what makes the agent loop actually fast and cheap enough to run in practice. For devs who've been watching open-weight models close the gap but haven't found one that actually delivers in practice, this is the closest I've seen. Try it here:

elvis

60,091 Aufrufe • vor 4 Monaten

Cerebras inference is very fast. So fast that it changes how we think about configuring our LLMs for voice agent use cases. Kimi K2.6 is a 1T parameter reasoning model that Cerebras serves at 650 - 1,000 tokens per second (end-to-end throughput), with time to first token metrics as low as 150ms (latency). These numbers are two to three times faster than other similarly capable models. The biggest lever we get from this kind of speed is that we can use the model in reasoning mode, and still have excellent "time to first non-thinking token." This solves a big pain point we have in 2026 for voice agent use cases. Almost all recent innovation in post-training has focused on making models good at reasoning ("test time compute"). This is great, but it makes the user-facing model latency much, much slower. Which is a problem for conversational voice agents. We can run Kimi K2.6 with reasoning turned on, and get responses faster than other models produce with reasoning disabled. On my 30-turn voice agent benchmark, Kimi K2.6 with reasoning enabled ties GPT 5.1 and Haiku 4.5 with reasoning disabled, and is still about 200ms seconds faster! On my primary task agent benchmark, Kimi K2.6 is now the #2 model. It ranks just behind Gemini 3.5 Flash in "high" reasoning mode, and tied with GLM 5, Sonnet 4.6, and GPT 5.4 with reasoning set to "low." But Kimi K2.6 completes each turn in the agent loop in under 500ms. The other four models are all at least 3x slower. (Models only qualify for this benchmark if they can complete task turns at a P50 <4s.) A couple of other things that this speed buys us, for production voice agents: - Tool calls happen fast enough that we don't have to work around tool call latency in our pipeline design. - We can prompt the model to output structured data at the beginning of a response, followed by plain text for voice generation. This opens up possibilities like asking the model to do complex classification/generation tasks that influence the rest of the pipeline. For example, the model could create a detailed style prompt for a steerable TTS model, for each individual conversation turn. And, of course, you can use Kimi K2.6 with reasoning turned off. Cerebras calls this "instant" mode. Here's a video of a Cerebras Kimi K2.6 voice agent with voice-to-voice response time, measured at the client, under 500ms. This is the true response latency as perceived by the user, including all network and audio codec overhead, transcription and turn detection, Kimi K2.6 token generation, and voice generation. 500ms is, effectively, instant. So the Cerebras naming for this mode is a propos. :-)

kwindla

40,593 Aufrufe • vor 3 Monaten

Algorithms and the Affections John Piper (Nov. 2025): “If you had thought that your essence of humanness in the image of God was your reasoning capacity, over an ape or a porpoise, you’re in trouble. Because, guess what? ChatGPT is smarter than you are and more creative than you are in expressing things in language that is good. It can write prayers better than you can, and it can reason through hard problems better than you can. Therefore, there are people who are going to forsake the faith because they thought to be a human in the image of God was to be a reasoning person over against the animals, and they discovered a machine can do it better than they can. Crisis of faith. This to me is no crisis because of my Christian Hedonism. I do not think that my reasoning capacities are my essence. I think the soul’s capacity to delight in God is my essence. The soul’s capacity to enjoy God. No machine will ever enjoy, period. It will have the language of enjoyment. You can tell it to write a poem of enjoyment and it will use the language. That machine is not enjoying *her*. It’s not. It never will. Only human beings created in the image of God can enjoy God. Therefore, enjoyment matters. I mean, affections are who we are ultimately. The end of history, the end of creation, is not going to be merely rational creatures thinking rightly about God, little computers. It’s going to be people who are so perceptive spiritually of the glories of God that they are full of affections that are appropriate for those glories and can give expression to them. That’s what eternity will be.” Source: Sovereign Grace Churches, Pastors Conference PreCon (November 2025)

Tony Reinke

151,773 Aufrufe • vor 8 Monaten

HERMES AGENT VS OPENCLAW. a local ai onboarding flow test. a 3.9gb bonsai served on localhost, both agents upstream and latest, i point each one at the endpoint and watch which one even finds it. > hermes opens a provider menu, thirty plus options, local servers sitting right there next to the cloud ones, i hand it 127.0.0.1:8899, it verifies the endpoint, one model visible, auto-detects the model by name, bonsai-27b-q1_0, reads the context length straight off the server, saves it, and starts reasoning and firing real tool calls on my local model. no key. no friction. > openclaw has no menu. it goes hunting for a codex login, an openai key, finds none because there are none, prints no models available three times, defaults to openai/gpt-5.5, a cloud model it cannot reach, and dead ends on run auth login --provider openai. read that back. it asked me for an openai key. to run a model already running on my own machine. it never once looked at localhost. to be fair, openclaw can run local if you hand wire endpoint yourself. what it will not do is find the model already sitting on your box. hermes agent found it in one line. now the part i owe you. the auto-detect that just won, the model name read, the .gguf strip, the context length probe off the server, that is my code, it is in hermes agent main right now, authorship preserved, #2051 and #4218. the wizard fix that stops an agent from silently routing you to someone else's creds, the exact trap openclaw still falls into, mine too, #4210. i contribute to hermes agent, i told you that going in. one agent is built to talk to whatever you are running, the other is built to talk to a cloud api, so one found my model and ran it and the other asked me to log into openai. onboarding flow of both, mapped, below.

Sudo su

23,816 Aufrufe • vor 1 Monat