Weird but true: without crypto, the current AI boom would not have been possible.
Today's data center buildout would've been impossible without Bitcoin miners spending a decade building the knowhow around power, sites, and scale in remote locations.
Nvidia could not moved beyond gaming to specialized compute without crypto mining as the bridge.
And the biggest neoclouds are almost all ex-crypto talent: @CoreWeave, @CrusoeAI, @togethercompute, @nscale, etc.
this article will be out of date in 6 months, and the reason why is in the second paragraph:
> We wanted off VMs because giving every user an always-on machine with attached disk was too expensive to scale. The hard part is that coding agents assume Linux.
if you were a betting person, would you bet that either:
a) someone will figure out a way to deliver full-VM semantics at a fraction of the cost, allowing coding agents to continue to assume Linux
or b) everyone will converge on a cloudflare stack that requires rewriting everything into javascript?
you can guess where I am, Linux isn't going anywhere. *especially* because it's:
- portable across providers
- users can build different price vs. performance vs. security options themselves
- it works with 100% of the existing software out there
there are *already* more interesting ways to fix costs in VMs, like Archil's serverless sandboxes which don't charge you at all during the "inference" part of the step
what would happen to costs when we intelligently decide on the server-side, for each bash invocation, whether it needs real Linux or just-bash? this stuff is going to become 1000x cheaper
We audited SWE-Bench Pro, one of the most widely used AI coding benchmarks, and found it no longer reliably measures frontier coding capability.
We find 30% of SWE-Bench Pro tasks to be broken, and are retracting our previous recommendation that the research community use it as a leading coding eval.
https://t.co/wDdSEjBe4F
A Brown professor gave his students a take-home midterm exam. After suspecting many cheated using AI, he made the final in-person. The orange dots are the midterm scores and the gray dots are the final scores. Looks like all but 3 cheated on the midterm.
Announcing our $130M Series A to build the Open Superintelligence Stack
Led by Radical Ventures, with NVIDIA, Intel Capital, Dell Capital, and existing investors
Train, deploy, and continuously improve your own models using our stack.
Own your intelligence.
I burned $13,836 worth of Claude Code tokens in June.
The same work on open models: $3,106.
That's $10,730 left on the table — one month, one laptop.
So I built the instrument that shows you the gap. Open source, 100% local. Launching today 🧵
✨ I think I've been coding almost solely on my VPS with Claude Code for almost a year now
All I can say it's just fantastic:
- no need to keep laptop open ever
- no laptop battery drain
- can switch to phone or any other device you like whenever you want to continue (like when you're outside)
- it just keeps going all night while you sleep (esp with /goal)
- you can start hacky projects from scratch and go live in seconds because you're already on the server which is great to ship things and get it used by people fast (not stuck on your local laptop webserver)
- it just feels like living in the future
I used to code on my laptop, test locally, then push to GitHub, then it auto pulled and deploy to production, that'd take me ~1 minute to get a new feature out
But then when I bought a new Mac Book Pro a few years ago I was too lazy to install a local Nginx environment, so I just started pushing to prod and everything went fine, and I sped up deploying to about 3 seconds from laptop to server, which people called me crazy for too
But now with Claude Code on my VPS in the last year, it just live edits on my production server, which sounds like it should go wrong but it just doesn't, it's very careful and only twice in 12 months messed up which meant my site didn't load for 10 seconds which is OK
If I wasn't working solo, like at a big company, I' think I'd recommend the same workflow but with a staging server, so it wouldn't touch production, for safety and regulatory reasons etc. but for me it's fine
I agree with @theo completely, it's clear to me this is where it's going, also seeing @karpathy with Claude moving to the cloud (via Slack etc), I think AI "agents" and AI coding will operate on servers / from the cloud first
P.S. I have 3-2-1 backups, multiple on-site and off-site backups which you should also even if you wouldn't code with AI, safety first!
Talked with a few folks inside of AI labs (OpenAI, Anthropic) about what they think of the future of software engineering.
The “closer” to shipping production code engineers are, the less they believe software engineering will be “solved” fully by AI. The opposite true as well
I think the deeper shift is that a lot of AI work is going to become factory style work.
Humans and agents will sit on shared pipelines that produce outcomes: software, operations, support, research, sales, content, and eventually better agents. As these workflows become more repeatable and commoditized, the winning companies will not just be the ones with better models. They will be the ones with better systems of record.
You need to know: how did this pipeline perform over time? How much revenue did it generate? What did it cost? Which decisions improved it? Who approved the work? What artifacts changed? What customers, payments, and operations were affected?
That needs to be legible in one system.
Slack can be a useful communication layer. But it was not designed to track persistent agentic work, pipeline economics, approvals, provenance, artifacts, and optimization loops.
This is why I’m much more bullish on vertical integration. The future is not just agents in chat. It is humans and agents working together inside systems that understand the work end to end.
This is a new paradigm for interacting with Claude that is significantly more "inline" with all the other human activity org-wide. Once you do all of the under the hood engineering work to make this "just work" (e.g. across tools, integrations, compute environments, memory, security, etc.), Claude basically joins the team in a seamless way - you can talk to it as you would talk to a person and it can help with a very large variety of workloads.
Imo this is the 3rd major redesign of LLM UIUX. The first paradigm was that the LLM is a website you go to, the second was that it is an app you download to your computer. This third one is that it is a self-contained, persistent, asynchronous entity with org-wide tools and context, working alongside teams of humans. It really takes a while to wrap your head around it, but it works and it is awesome.
Prediction: Slack driven coding agents are going to be a transitional phase.
The long term winner will be vertically integrated software designed around the new reality of human/agent collaboration. Existing tools were built for a different operating model, and they’ll get absorbed by systems that understand the right abstraction for coauthored work.
Introducing Claude Tag, a new way for teams to work with Claude.
In Slack, Claude joins as a team member with access to the channels and tools you choose. Tag Claude in and delegate tasks to it while you focus on other work.
it remains super odd to me that none of the existing agent frameworks, Mastra, Flue, or now Eve seem to do anything about getting context into the agent?
every team that i talk to who are designing agents at-scale need to figure out how to get the enterprise data *to* the agent, which requires carefully planning ETL, evaluating how well the agent performs with different data formats, running things like map-reduce
and yet, every one of the agent frameworks just... leaves this to user with no opinion on it?
maybe you can only do this part with a fully-owned storage layer, idk
Unreal Engine 5.8 ships today with experimental MCP server support:
Your sources, your pipeline and your workflow—simply configure the MCP plugin and connect to any agent. Get familiar with the MCP server and the PCG Primitive Plugin today and see what teams can build together: https://t.co/cDITLWWv2F
Monday: Darkbloom goes live on OpenRouter.
Every OpenRouter user gets a free trial of private inference, powered by idle Macs around the world.
And for providers -- next week we're launching an Alpha Rewards Program: earn up to $40 guaranteed just for running a node. Limited time while we're in alpha. Breakdown in the replies.
The network is ready for it. Since our Public Alpha two weeks ago: Gemma 4 is now multimodal, SSD caching has made time-to-first-token much faster, and load tests show we can sustain millions of tokens per second -- with more upgrades landing before launch.
If you run a node: turn it on. Demand arrives Monday.
If you have a Mac: darkbloom(.)dev → one install command and you're earning.
The world's sleeping compute is waking up.
We've been thinking a lot at Stripe about the Coasean lens on AI:
- The obvious near-term effect is reduced transaction costs within companies: shared context, systems of record, aligned incentives etc.
- But inter-company transaction costs also reduce sharply: agents are great at discovery, make it trivially easy to integrate; make contracting much more straightforward; agent-to-agent commerce.
- On net, we think second effect bigger in medium term: fewer people per firm, more output per firm, just more firms, and more coordination happening through market-like mechanisms
BREAKING: Apple is scared of vibe coding
they removed Anything from the App Store so we moved app building to iMessage
good luck removing this one, Apple