AI Digest.

Applied AI Layer Defends Against Vertical Integration Squeeze While Multi-Model Workflows Slash Token Costs

Today's discussions were dominated by fears of frontier labs monopolizing the AI stack, prompting a strong push toward open-source infrastructure and applied context layers. Meanwhile, developers are finding aggressive new ways to cut API costs, utilizing multi-agent workflows and clever image-rendering hacks to bypass text token limits.

Daily Wrap-Up

The AI ecosystem is currently wrestling with a profound identity crisis regarding trust and ownership. Enterprise leaders and developers alike are sounding the alarm on the risks of building atop closed foundation models, fearing that the labs providing their infrastructure might eventually consume their businesses. This anxiety is entirely justified as we watch frontier labs aggressively expand into vertical SaaS applications. The realization is dawning on the community that true AI safety is not about abstract alignment research or government regulation, but rather about an organization's ability to maintain strict sovereignty over its proprietary data, model weights, and compute. As power concentrates at the model layer, the defensive moat for everyday developers is shifting entirely to the application layer, where specialized context engineering and domain-specific workflows remain difficult for large labs to replicate.

Away from the high-level market dynamics, the boots-on-the-ground developer community is undergoing a radical efficiency revolution. Multi-agent orchestration has transitioned from an experimental novelty to a standard operational procedure. Builders are increasingly segmenting their tasks, using cheaper, highly capable models for high-frequency coding tasks while reserving expensive frontier models for architectural planning and final code review. This multi-model approach is being paired with wild, creative hacks to circumvent restrictive API pricing structures. By rethinking how context is fed into these models, developers are achieving massive cost reductions that fundamentally alter the unit economics of software development, pushing us closer to an era of autonomous, long-running agents that can operate for dollars rather than hundreds of dollars.

The infrastructure supporting these local and cloud-based agents is simultaneously maturing, leaning heavily into open-source ecosystems and specialized developer tools. We are seeing a fascinating divergence in hardware strategies, with a renewed appreciation for older, high-memory GPUs augmented by custom kernels, standing in stark contrast to expensive, tightly controlled proprietary ecosystems. This democratization of hardware and software stacks ensures that the future of AI development remains accessible. The most practical takeaway for developers: stop relying on a single frontier model for your entire pipeline and start building multi-step agent workflows that separate planning, execution, and review, while actively auditing your token formatting to drastically reduce your API overhead.

Quick Hits

  • @hardfist_1 shared a deep dive into async programming, pointing to an incredibly thorough article on the subject that cuts through the noise.
  • @mattpocockuk reminded us that "evals on skills are hard" remains the understatement of the year as developers like @steipete struggle to assess agent capabilities properly.
  • @dillon_mulroy shared a video snippet of an essential tool used in every single agent working session, highlighting how integrated these workflows have become.

Enterprise Data Sovereignty and the Battle for the Application Layer

The discourse today was heavily defined by a growing resistance against the monopolistic tendencies of frontier AI labs. David Sacks amplified comments from Palantir CEO Alex Karp, arguing that genuine enterprise AI safety has nothing to do with government regulation and everything to do with data sovereignty. Sacks pointed to the controversy between Anthropic and Figma as a cautionary tale. He noted that frontier labs are systematically dominating the model layer and then using that leverage to capture lucrative verticals, effectively swallowing their own business partners. "Dario has argued that open source models powerful enough to compete with Anthropic are 'dangerous.' But dangerous to whom? Not to enterprises that want to retain control over their data and workflows," Sacks observed.

This sentiment was echoed powerfully by Yann LeCun, highlighted by @jun_song, who warned that the concentration of power in AI is the most significant danger the technology poses. LeCun compared the current landscape to historical attempts to control information, arguing that foundation models are inevitably becoming commoditized infrastructure. This directly informs where the long-term market value will reside. Aaron Levie (@levie) expanded on this, explaining that the battle in AI is ultimately a battle for context. He argued that the applied AI layer provides immense value precisely because it organizes critical knowledge and governs workflows. "This is why the applied AI layer has a lot more value than just being an LLM wrapper," Levie wrote. "The ability to organize the critical knowledge for the work being done... is critical." The consensus is clear: whoever controls the context and application governance wins the enterprise market, regardless of what the underlying model providers do.

Multi-Model Agent Orchestration and Workflow Optimization

As the application layer becomes the primary battleground, developers are refining highly sophisticated, multi-model workflows to maximize efficiency. Mitchell Hashimoto (@mitchellh) detailed a highly effective architecture where a specialized model is used as a planner and judge, while a fast, powerful model acts as the coder. By segmenting the responsibilities, Hashimoto noted that costs drop dramatically. "At API pricing, planning+judge costs are in the ~few dollar range compared to typical $50+ full round trips," he explained, highlighting that GPT 5.5 operates exceptionally fast and cheap even at high intensity. This approach validates the idea that future pipelines won't rely on a single monolithic model but a symphony of specialized agents.

Managing these agents requires entirely new workflows and mental models for software engineers. Matt Van Horn (@mvanhorn) synthesized a guide on agentic coding, explaining that the model is no longer the bottleneck. The true skill lies in discovering your unknowns and mapping them accurately for the agent. He suggests doing a "blindspot pass" where you literally ask the agent to find your blind spots and interview you one question at a time. Furthermore, how developers review this code is shifting. @thdxr noted that instead of painstakingly reading code diffs, they now simply ask the agent for a summary of what changed in each file. Anything weird sticks out immediately, and a few prompts later, the code is exactly where it needs to be.

Hacking Token Economics and Prompt Engineering

As these agent workflows scale, API costs naturally become a massive friction point, leading developers to invent incredibly clever optimizations. @hqmank uncovered a brilliant token hack that drastically reduces the cost of feeding dense context into models that charge images by pixel size rather than text density. By routing context through a proxy that renders it as a PNG image before sending it to the API, the token count plummets. "Before: 92,000 tokens for a dense tool result. After: 4,761 tokens for the same content as a PNG," the user shared. This hack results in a massive 59 to 70 percent reduction in end-to-end billing without sacrificing task completion rates.

Optimizing what goes into the model is just as crucial as how it is formatted. @alxfazio strongly recommended looking into ARC AGI winning harnesses, noting that they clearly illustrate what actually works from first principles versus what is simply overfitted to benchmark maxing. For broader educational foundations, Sean Welleck (@wellecks) announced that all 23 lectures for his CMU Advanced NLP course are now publicly available on YouTube. Complete with slides and code examples, the lectures cover everything from fundamental architectures to scaling and efficiency. This release provides an invaluable resource for developers looking to strengthen their underlying understanding of how these systems process the context they are so desperately trying to optimize.

The Local Hardware Renaissance and Unconventional VRAM Optimization

While cloud infrastructure offers scale, a fierce renaissance is happening in local AI hardware and optimization, driven by developers refusing to pay premium cloud tax. Lucas Tech (@lucastech) posted a stark hardware comparison highlighting the price-to-performance ratios of current options. The analysis showed the RTX 3090 offering unparalleled bang for the buck at 24GB of GDDR6X memory running at 930GB/s for roughly $1,500, easily outperforming significantly more expensive enterprise alternatives in raw speed, even if it lacks the memory pool of a DGX Spark or an RTX 6000.

Eric Hartford (@QuixiAI) aggressively championed this perspective, dismantling the myths that older hardware cannot run modern formats. He noted that while companies push new proprietary formats, you can run almost anything on anything if you have the right kernel. "@nvidia's vast conspiracy to suppress this knowledge is over. Buy 3090s y'all! better yet 2 and an nvlink," Hartford declared, pointing out that older AMD cards are also incredibly smart buys right now. The hardware limits are being broken on the software side as well. Sakura Yuki (@sakurayukiai) highlighted a mathematical breakthrough in reinforcement learning training that drops optimizer VRAM usage by a staggering 97 percent. By freezing 35 of 36 layers on a Qwen3-8B model and training just Layer 18, researchers recovered 107 percent of the full-parameter GRPO gains. This proves that high-level reasoning is heavily concentrated in specific middle layers, opening the door for massive local training efficiency.

Secure Agent Sandboxing and Cloud Infrastructure

Running these complex workflows requires a robust infrastructure that can handle secure, unconstrained execution without putting the host machine at risk. Guillermo Rauch (@rauchg) highlighted a major update to Vercel Sandbox, which now supports FUSE-based filesystems and unconstrained Docker containers. "MicroVMs are the gift that keeps on giving. Instant boots, unconstrained runtimes," Rauch noted. This allows developers to mount S3 buckets and share state across sandboxes seamlessly. Providing a robust, isolated environment is critical for letting agents execute code safely.

For developers operating across multiple machines and preferring a decentralized approach, @0xSero introduced Parcels. This tool solves the issue of cloud agents for users with Tailscale networks and multiple desktops. Parcels packages your current work, transfers it to a designated machine on your Tailscale network, and runs it within a tmux session. This allows developers to step away from their screens while long-running agentic tasks continue to execute in the background. To manage the repetitive loops required in testing these environments, @MatthewBerman noted that Loopy now allows developers to save their agent loops locally for easy reuse, further streamlining the iterative process of harness engineering.

Specialized AI Models and the Developer Ecosystem Pivot

The mainstream models are dominating headlines, but highly specialized open-source models are solving incredibly complex, niche problems. Mert Unsal (@mertunsal2020) released Leanstral 1.5, a model achieving state-of-the-art performance on graduate algebra benchmarks. @MiaAI_lab expressed excitement over the model's ability to handle long-range coding tasks and theorem proofs that previously required hours of human labor. In the open-text domain, @EricStrate_ noted that Qwen3.6-35B-A3B is currently the reigning champion for overall quality and reasoning in local use cases, proving that the open-source community is successfully competing with, or at least closely trailing, massive closed labs across various modalities. Thomas Wolf (@Thom_Wolf) even showcased a fully open-source, real-time speech-to-speech demo built in collaboration with Cerebras, proving that open infrastructure can handle instantaneous, high-demand tasks.

This thriving open ecosystem is actively shaping the broader developer tooling market, perhaps most notably in programming languages. Robert Scoble (@Scrobilizer) pointed out that Nvidia's LPU team is going all-in on Rust to build the future of low-latency inference. This represents a massive vote of confidence for Rust and reshuffles the hierarchy of developer platforms. Meanwhile, UI and privacy tooling are also benefiting from this applied AI wave. MengTo (@MengTo) highlighted Toolcraft, a free, open-source starter kit that uses AI to help developers build bespoke creative tools, saving massive amounts of UI development time. Taking privacy directly into their own hands, developer SHL0MS open-sourced UNBROKER, a Hermes Agent skill highlighted by @gospaceport. This tool runs locally to autonomously find and file data removal requests with hundreds of data brokers, completely bypassing paid services like DeleteMe and ensuring personal data never leaves the user's machine.

Sources

D
David Sacks @DavidSacks ·
Legacy Media types are calling this Alex Karp interview a “crash-out” so that’s your first clue that he is actually saying something extremely insightful. He is articulating what real “AI safety” looks like in the enterprise. Not abstract alignment research or certification by a government-run DMV for AI. Real AI safety for businesses is the ability to control their own data, model weights, and compute — so a frontier lab can’t hoover up their proprietary knowledge and turn it into their next product. As Karp explains, technical customers want “control over their compute, their models, their data stack, and their alpha. They want to know they own the means of production, and it’s not being transferred to someone else.” Don’t think that can happen? Just look at Figma. According to The Information, Anthropic “blindsided” its then-business partner with the launch of Claude Design. Figma’s founder said Anthropic had not been “consistently honest” with them. Anthropic’s chief product officer had even served on Figma’s board until three days before the launch of Claude Design. Figma’s stock has fallen sharply this year while Anthropic’s valuation has surged. This isn’t an isolated example. Anthropic has launched Claude Science, Claude Security, Claude Legal, and of course Claude Code — each expanding into categories previously served by companies building on top of their models. The pattern is consistent: watch where value is being created, then move in directly. Dominate the model layer, then use that position to capture the most lucrative verticals. Dario has argued that open source models powerful enough to compete with Anthropic are “dangerous.” But dangerous to whom? Not to enterprises that want to retain control over their data and workflows. Dangerous to a business model that benefits from customers having few real alternatives at the model layer. As Karp exposes, true enterprise safety isn’t trusting that a lab’s future roadmap won’t include your business. It’s retaining the ability to choose — at the model layer — who gets to see and use your alpha.
P PalantirTech @PalantirTech

Palantir CEO Alex Karp on what customers actually want, the real business of frontier labs, and the importance of open source models: “What the technical customers want is control over their compute, their models, their data stack, and their alpha. They want to know they own the means of production, and it's not being transferred to someone else.” "Who owns the data? Are the prompts secure? Is this being transferred to you?" "If it was so valuable, and I can make you a billion dollars, wouldn't I say I'll make you a billion dollars and I want 30%? Why are they charging for tokens if it's so valuable?"

M
Mitchell Hashimoto @mitchellh ·
I'm having a lot success using Fable xhigh as a planner/architect, using GPT 5.5 xhigh (subscription) as a coder, then Fable xhigh again as a judge. At API pricing, planning+judge costs are in the ~few dollar range compared to typical $50+ full round trips. I've seen some others using dumber/cheaper coders, but GPT 5.5 even at xhigh compared to Fable 5 is very cheap and very fast. And GPT 5.5 is just... really good. Still been less than 24hrs since the re-release so the longevity of this approach is unclear, but its been working really well.
S
Sakura Yuki @sakurayukiai ·
A 97% drop in optimizer VRAM during RL training sounds like a stunt, but the math is so clean. Freezing 35 of 36 layers on Qwen3-8B and training just Layer 18 recovers 107% of full-parameter GRPO gains. Reasoning is purely a middle-layer story??
E
Eric @EricStrate_ ·
@ivanfioravanti Qwen3.6-35B-A3B is my champion for quality, reasoning and my use cases.
T
Thomas Wolf @Thom_Wolf ·
Most people should probably update their priors on the state of open-source speech-to-speech. It's honestly kind of mind-blowing. We teamed up with @cerebras to build a fully open-source realtime voice demo (models + code) to show what's possible today. Demo : https://t.co/UCciOXSteq Blog: https://t.co/rsULsWWKlO Go test it, fork it, tweak it, and impress your friends. video is raw, no cut, no speed-up, first take
J
Jun Song @jun_song ·
Great message from @ylecun.
Y ylecun @ylecun

Exactly. I've been disseminating a similar message for years. The concentration of power in AI and the desire for control is by far the biggest danger of AI. It could lead to a few private companies and/or countries being in control of access to information, access to knowledge, and access to the tools of economic expansion. It's a kind of medieval obscurantism akin to the Ottoman empire banning the use of the printing press for 200 years, in part to keep control of the dogma, but also to protect the corporation of the calligraphers and scribes. Relevant historical bits about the Internet: 1. It took a deliberate decision by Al Gore and Bill Clinton to open up access of what was then ARPAnet to commercial entities and to the public, against the desires of the entrenched telecom industry. During a public roundtable about the "information superhighway" in 1993, the CEO of AT&T told Gore and Clinton "leave it to us". Gore said no. 2. In the late 1980s, setting up an Internet presence required buying proprietary hardware with proprietary OS and software stack from Sun Microsystems, HP, IBM, or Dell. By the 2000s, all of this was wiped out by commodity hardware, Linux, Apache, and an entirely free/open software stack. This migration to open platforms was the result of market forces. Infrastructure wants to be open. Foundation models are becoming an infrastructure and will inevitably become commoditized. Long term, the money is in the application layer, which is what I, Arthur Mensch, Alex Karp, and others have been saying.

M
Meng To @MengTo ·
As someone who's built a lot of ui controls, this saves so much time for creating well-crafted sliders, color pickers, drop-downs and infinite canvases. Can't believe it's free and open-source.
A alex_barashkov @alex_barashkov

Forget trying to design everything in Figma. You can build your own design tools with AI. Introducing Toolcraft - a starter kit and UI library for building beautiful creative apps. It's free and available for you today. npx @​pixel-point/toolcraft create Use it to build apps to stylize images, create WebGL shaders, Three.js scenes, animations, photo editing tools, or whatever else needs a canvas and controls. Toolcraft gives you the full architecture in a single solution. It comes with: - plenty of UI components: sliders, pickers, timelines, curves, and more - built-in canvas, export, and toolbar setup - AI instructions to help the agent deliver a great result to you With Toolcraft, you don’t need an extensive prompt. Just explain what type of visuals you want to build, attach references, and wait. It’s been a game changer for our design process. Watch the full video on our YouTube channel with all the details and examples.

M
Matthew Berman @MatthewBerman ·
Loopy - New Feature! Loopy can now save your loops (locally) so you can reuse them later easily. Find and create the best agent loops with Loopy! https://t.co/V3QFCbs9e7
A
alex fazio @alxfazio ·
if you’re into harness engineering, i strongly recommend looking into arc agi winning harnesses. they clearly illustrate what works from first principles, what is bs, and why a lot of current harness design is overfitted to benchmarkmaxx
D
Dillon Mulroy @dillon_mulroy ·
i use this every single session i work with agents https://t.co/mXpAaovd7H
G
Guillermo Rauch @rauchg ·
This is so powerful. ▲ Sandbox can now run 𝚍𝚘𝚌𝚔𝚎𝚛 and 𝚏𝚞𝚜𝚎, unconstrained. MicroVMs are the gift that keeps on giving. Instant boots, unconstrained runtimes. Very happy we bet on it as the foundation for 🌊 Fluid compute. S3-backed filesystem for agents in 10LOC ↓
V vercel_dev @vercel_dev

Sandbox now supports FUSE-based filesystems. ▪︎ Mount S3 buckets and network filesystems ▪︎ Run CLI tools against remote sources ▪︎ Share state across Sandboxes https://t.co/mTlXIfHeXB

M
Matt Van Horn @mvanhorn ·
TL;DR ELI5 of @trq212's new article: Claude isn't the bottleneck anymore. The stuff you forgot to tell it is. Your prompt is a map. The codebase is the actual road. Every pothole you didn't mention, Claude fills with its best guess, and the more work you hand it, the more it has to guess. The skill of agentic coding is shrinking that gap. 🗺️ Your unknowns come in four flavors: what you said, what you know you haven't decided, what's so obvious you never wrote it down, and what you never considered at all 🔦 Starting unfamiliar work? Do a blindspot pass: literally ask Claude to find your unknown unknowns and teach you to prompt better 🎨 Know it when you see it? Prototype first. 4 wildly different HTML mockups is cheaper than one wired-up wrong guess 🎤 Let Claude interview you, one question at a time, starting with answers that would change the architecture 📁 Can't describe what you want? Point at a reference. Source code beats screenshots, even in another language 📋 Ask for a plan that leads with what you're most likely to change: data models, interfaces, UX 📝 During the build: an implementation-notes.md that logs every deviation from the plan 🧪 After: make Claude quiz you on the change. Only merge when you pass Every brainstorm, interview, prototype, and reference is a cheap way to find out what you didn't know before it gets expensive to fix.
T trq212 @trq212

A Field Guide to Fable: Finding Your Unknowns

A
Aaron Levie @levie ·
The battle in AI is shaping up to be a battle for context. Everything in AI is about making sure that agents are effective as possible. That effectiveness comes down to whether the agent has the right domain expertise, access to the right context and tools to work with, and are involved in workflow in a way that users can easily interact with, review its work, and incorporate it into the rest of the process. As a consequence, the platforms that are able to capture and leverage the best and most context within their agents —and be able to pick the right models for the task- will be the place where agents do their best work. You can just look at coding agents, legal agents, or support agents as examples of what this looks like at scale. This is why the applied AI layer has a lot more value than just being an LLM wrapper. The ability to organize the critical knowledge for the work being done, and maintain this knowledge in a governed way where only the right people and agents have access, and the ability to improve the context for agents more and more over time, is critical. Over time, this layer will be able to route work between a variety of models, leveraging frontier intelligence for planning and orchestration and review, and a mix of lower cost models (open or closed) for the large volume of work between these tasks. The applied layer is also in a good position to train and develop its own models as well that are purpose built for their domains. Never good to bet against the bitter lesson, but equally taking a near frontier base model and post training it for just one type of domain work can -in many cases- lower costs or deliver better performance for certain tasks. Finally, this applied layer is also where most of the change management of the workflow will need to occur. This is why FDEs are so important at the applied layer, because this is the point where the customer needs to have specific business problem solved by a particular vendor. Whichever companies can solve that completely in an end-to-end fashion will have the greatest moats. As each day goes on, we’re learning more about what the likely long term market dynamics will look like in AI.
M
Matt Pocock @mattpocockuk ·
"Evals on skills are hard" is the understatement of the year
S steipete @steipete

@MichaelArnaldi @EffectTS_ @ZachWarunek Start with a skill that distills the most important things latest gen agents don't get right with Effect and you're 80% there. Evals on skills are hard.

D
Digital Spaceport @gospaceport ·
Interesting new Hermes skill
S SHL0MS @SHL0MS

i'm open sourcing UNBROKER: a tool that finds where your personal info is exposed by data brokers and files the removals for you it runs as a skill in Hermes Agent _________ your data is everywhere; hundreds of brokers publish your name, current and old addresses, phone, email, birthday, even your relatives. anyone can find where you live in about ten seconds CCPA, CPRA, GDPR, and a growing number of state laws say a broker has to delete your data if you ask. there's just no easy bulk button. every broker has a different process and many make it intentionally difficult to exercise your right to delete this is the entire business model for companies like DeleteMe, Incogni, EasyOptOuts; they charge you monthly (DeleteMe is $330/yr for a Family plan) to file removals that you can submit yourself for free, and then you're giving a new company the exact data you want to erase so i built one you just run for free. your data never even has to leave your machine if you run a local model _________ how it works: first it builds search vectors from everything: every name, alias, email, phone, and address you've had (brokers might index you under a maiden name or a house you left in 2014, so the naive "current name + current city" approach can miss profiles). then it fans out parallel sub-agents across the broker list, which refreshes from a maintained public source automation is tiered. when it can handle a broker end to end with your settings, it drives a browser through the opt-out form, sends the email, and opens the confirmation link itself. soft CAPTCHAs clear on their own with a real browser. anything only a human can finish comes back to you as a short list at the end the email side doesn't need a stored password and can send opt-outs and open verification links through your own logged-in webmail. you can also wire up SMTP, or keep it manual and just send the drafts it writes it tailors every request to your jurisdiction, filing under the framework that applies where you live: CCPA and CPRA in California, GDPR in the EU and UK, a general right-to-delete request everywhere else. if you're in California it also uses the state's DROP portal, a single request that covers 500+ registered brokers at once it holds as little of your data as it can, and keeps it local. dossiers are encrypted at rest if you want, opaque ids keep your real name out of every filename and log, and nothing leaves your machine unless you opt in brokers sometimes relist you eventually or new ones find your data, so every case is tracked in a ledger and can be re-scanned on a cron schedule so if your data pops back up it files the removal again https://t.co/2jfQxBYZkW

S
Sean Welleck @wellecks ·
All 23 lectures for my CMU Advanced NLP course are now on YouTube. The slides and 20 code examples are also publicly available. - YouTube: https://t.co/PV5FMA47La - Course Page (Slides, Schedule): https://t.co/2C7JNAC9eY - Code: https://t.co/mz6i7tcoMh The lectures are grouped into 7 themes: fundamentals, architectures, learning & inference, modeling, evaluation, RL & agents, and scaling & efficiency. Check them out if you’re looking for an introduction or refresher on the fundamentals of LLMs, key ideas from recent NLP research, or are just curious to learn more.
M
Mia @MiaAI_lab ·
This almost seems too good to be true... 🤔 What caught my attention the most — 𝐋𝐞𝐚𝐧𝐬𝐭𝐫𝐚𝐥-𝟏.𝟓-𝟏𝟏𝟗𝐁-𝐀𝟔𝐁 promises: - Ask Leanstral to do any coding task for you, such as prove a given theorem or fix some code in your project. - Leanstral is capable of doing very long range tasks which requires hours of work. Don’t hesitate to let it work away at a problem. Looking forward to test it out on my DGX Spark
M mertunsal2020 @mertunsal2020

Today, we are releasing Le Chaton L∃∀N, aka Leanstral 1.5. It achieves SOTA performance on graduate algebra benchmarks FATE-H and FATE-X and improves Pareto Frontier on PutnamBench, solving 587/672 problems with a x10 cheaper budget. 🧵 https://t.co/ySGMr2oqg5

L
Lucas Tech @lucastech ·
Atlas 300l is 96GB (2x48GB) LPDDR4x @ ~408GB/s 150W $1.5k DGX Spark is 128GB LPDDR5x @ 273GB/s 140-240W $4k RTX3090 is 24GB GDDR6X @ 930GB/s 350W $1.5k RTX6000 is 96GB GDDR6 @ 1,792GB/s 300W $13.5k that's the best bang for the buck by a long margin, but it's slow for a GPU
S sudoingX @sudoingX

for everyone asking for a buy button: listings like this have been sitting on chinese b2b markets for months. huawei atlas 300i duo, the inference card. the listing attributes are chaos, intel chipset? ddr4? b2b sellers gonna b2b, but the card underneath is real. nobody has posted serious tok/s from one yet. that is the gap i intend to fix.

E
Eric Hartford @QuixiAI ·
"none of this was supposed to work" Pfuh! Power to the people! No more "gguf/mlx is for mac, bf16 is for ampere, nvfp4 is for nvidia" nonsense.
Q QuixiAI @QuixiAI

I keep hearing myths spoken as truths. like "metal doesn't support nvfp4" and "3090 doesn't support fp8" False. You can run anything on anything - you just need a kernel. (which is easy now with AI and harnesses) Thanks @mgoin_ for inspiring with @vllm_project Marlin kernels. @nvidia's vast conspiracy to suppress this knowledge is over. Buy 3090s y'all! better yet 2 and an nvlink. 4x amd mi100's (32gb each) with infinity fabric would be a smart move too.

D
dax @thdxr ·
lately after a big change instead of reading the diff i ask the agent for a summary of what it did in each file anything weird sticks out immediately and 1-2 prompts later it's completely as i want it files + functions signatures i need to know, care less about function body
T theo @theo

How much better do the models have to get before you'll stop reading the code?

0
0xSero @0xSero ·
I think I have solved cloud agents for those with tailscale and more than 1 desktop. Parcels packages your work, transfers it over to a machine on your tailscale, and runs it in tmux. That way you can step away from screen. https://t.co/1CFVsE09x3
R
Robert Scoble @Scobleizer ·
Tim O'Reilly @timoreilly used to do these posts about the developer ecosystem. He had a famous book publishing company that published books for programmers (they were the ones with the cute animals on the cover). Every year, he would publish a list of developer platforms and which ones were more popular with developers than others. The fact that Nvidia is going with Rust would, I assume, get him to re-rank the whole frickin' list.
O omarkilani @omarkilani

The LPU team at @nvidia is building the future of low latency inference. We're going all in on Rust. If you're a cracked Rust engineer and love making hardware do things, we want you. https://t.co/EEPoYOWWmh

H
hardfist @hardfist_1 ·
https://t.co/L3WxjgjKIU This is the best article on async I've read so far.
K
Kai @hqmank ·
✅Found a wild token hack that only works properly on Fable 5. Claude charges image tokens by pixel size, not by how much text is in the image. So someone built a proxy that renders your context into PNGs before sending it to the API. Before: 92,000 tokens for a dense tool result After: 4,761 tokens for the same content as a PNG End-to-end bill savings: 59-70%. SWE-bench tasks: same completion rate, half the cost. Link in reply👇