Grok 4.5 is #1 at processing real-world invoices
At Ramp, we tested models on 150k bills submitted by actual businesses, scoring them on whether they predicted every correction a human would make
Grok achieved the highest perfect-extraction rate, beating similarly priced models Gemini Flash 3.6, GPT 5.6 Terra, and Sonnet 5.
This is a demanding long-context reasoning task. The model must infer patterns across 100K+ tokens of prior invoices, business memories, and human corrections, then apply them to new bills. The goal: zero-click accounts payable, with invoices processed correctly without human intervention.
alkadaemon retweeted
For my first post, I’m sharing a letter @NVIDIA signed on why open models matter.
AI will transform every industry, power every company, and be built by every country.
Open models strengthen safety and cybersecurity, accelerate innovation and diffusion, and enable sovereignty.
The world needs both frontier closed models and frontier open models.
images.nvidia.com/pdf/Open-W…
alkadaemon retweeted
Ever since I started SharpEmu, I dreamed of seeing the Demon's Souls logo appear on screen.
Today, it finally happened.
There's still a long road ahead, but this is a milestone I'll never forget.
Every emulator starts with a single frame.
Still a work in progress.
alkadaemon retweeted
agent-browser supports this natively
agent-browser network har start
# agent browses, clicks around
agent-browser network har stop
Also now a skill:
agent-browser skills get derive-client
used a trick @jlongster came up with
agents can control browsers but you can also ask it to record network requests into a HAR file
then it can derive a client for any website which is more efficient than browser controlling it every time
made it build a quick uber eats cli
alkadaemon retweeted
The best thing about Kimis's success is that it represents everything Anthropic hates.
alkadaemon retweeted
actually an insane thing for openai’s head of strategy to publicly say
Some observations on Kimi:
1. It's a very good model! I don't think its performance can be explained away by distillation or anything like that. In agentic coding sessions, it seems pretty much on par with the best public models of Q1 2026. In my fairly limited use, it also seemed very token hungry. It's not obvious to me that this model is actually that cheap to run.
2. I am personally surprised the Chinese state continues to allow the open sourcing of models this good, given potential risks. To be clear, I *myself* might be fine with models presenting this level of marginal risk being open weight, but I am surprised that China is fine with it. I suspect the reason they are is 75% explained by strategic blindness/lack of AGI-pilledness (the CCP is very Yann Lecun-y in its views of AI). The other 25% or so is their lack of compute for customer inference (making China's open-weight strategy an unintended byproduct of US export controls) and the normal Chinese strategy of aggressive exports. For the companies, as opposed to the government, the decision to open source is partially ideological and partially because they are behind, and they know that very few people would pay for sub-frontier models from China.
3. Open-weight models are inherently decelerationist, and I'm continually surprised to see the so-called "accelerationists" so excited about open-weight models. I suspect the reason they are is that they know open-weight models are effectively ungovernable, and they simply like the overall cloak of ungovernability open-weight models create over the whole of AI. It's not a bad strategy; it reminds me of James Scott's recounting of the hill people in "the art of not being governed." Still, in the end, open-weight models deter further AI capex.
4. One probable outcome of an open-weight-model-dominant world is full AI communism, which is precisely what China proposes: rather than a market product, AI is a "public good" which will ultimately be provided by the state as a kind of "digital public infrastructure." This future strikes me as a dystopian hellscape, but I've never met an open-weight models advocate who doesn't ultimately concede this is where things end. You'd be surprised how many 'accelerationists' lobbied me, while I was in government, to support an eleven or twelve-figure federally funded data center so that startups could train models at a subsidy and then give them away for free. There was no other way for AI to progress, they said. Perhaps this is the logical end state of things. Nonetheless, I find myself surprised to see supposed accelerationists excited about such an outcome. I think many of them just don't know what they're doing. Many accelerationists do not view the creation and serving of frontier models as a legitimate business.
5. I would guess that the Trump Administration will at some point realize that their best strategy here would be to create large amounts of regulatory risk around the use of open-weight Chinese models. You don't need to "ban open source" (one of the dumber motifs of AI policy discussion). You just need to direct every agency to issue soft law that creates FUD. "A Federal Reserve Advisory Bulletin found that there may be backdoors in Chinese AI models." It needn't be that well justified. You just create enough regulatory risk that every regulated enterprise backs off. You probably don't want to create so much regulatory risk that you scare off the hyperscalers from serving Chinese models; this will just drive startups to sketchier providers. There's a happy middle ground here. I'd assume they will do some version of this.
6. It's probably true that open-weight models of this capability make the world a bit more dangerous, but not so much more that you'll really notice. At some point the models will be capable enough that you will notice. "A nonliving, invisible, dangerous, and infinitely self-replicating agent escaped from a Chinese lab," you say? Color me shocked.
alkadaemon retweeted
Replying to @ChiefEngineerCE @BarefootStudent
NY Fed data (recent grads 22-27): CS 7.0% unemployment, Computer Engineering 7.8% — among the highest.
H-1B visas are overwhelmingly for computer-related occupations (~65% of approvals) and engineering roles. Major tech/consulting firms sponsor heavily for software devs and IT specialists.
The fields with elevated new-grad joblessness are the same ones drawing most H-1B workers. This points to experience/skill mismatches, post-layoff caution on juniors, and continued employer preference for sponsored foreign talent in specialty positions.
alkadaemon retweeted
Grok Build is now open source
We've open-sourced Grok Build and have reset usage limits for all users.
Open sourcing Grok Build allows anyone to support making a reliable and robust harness. Check out our code, including the Git repo for the Grok Build CLI.
x.ai/open-source
alkadaemon retweeted
this would have been a whole startup not too long ago
alkadaemon retweeted

Doc Strangelove@DocStrangelove2Jul 15
United States
United StatesConnected via United States App StoreAccount-level information, not a live location or per-post device.
You can’t not show the whole scene man.
alkadaemon retweeted
Software hiring has become absurd.
At work, you’re expected to use AI to offload manual coding and move faster.
Then, to get your next contract, you’re asked to code from memory with no assistance.
Pass the interview - and you’re expected to use AI again.
It has never been this broken.
alkadaemon retweeted
A coder getting AI is like a farmer getting a tractor and saying "oh wow, look how fast it tills my small plot! Now what used to take all day takes 30 minutes. I can relax for the rest of the day".
What a tractor actually does is help the farmer till LARGER plots. It still takes all day - but you achieve more.
Any farmer still tilling small plots will be out of business.
alkadaemon retweeted
I still refuse to believe "Mohammed Hijab" is a real name. It would be like if I named myself "Hiroshima Nagasaki".
alkadaemon retweeted
Dominicans are the Argentinians of the Caribbean, but there is only one problem though. Take a wild guess as to what that it is. 🤔
Your Android app got faster in our recent SDKs without a single code change:
◆ ~40% faster cold starts
◆ ~33% faster first render
That is the new Kotlin compiler plugin doing the work while you ship features.
See what shipped:
expo.dev/changelog/sdk-56




































