Don't Blow Your Budget on a GPU—Top-Tier AI Tools Don't Need a Top-Tier Machine
Top-tier AI tools require a maxed-out machine with a flagship GPU? That's the misconception I got asked about most this week, and the one I most want to kill. I'm a hardware guy myself—I've bought and used a 3090, a 4090, all kinds of flagships, and I sold them all recently, because for personal AI work that GPU is close to wasted.
Large-model inference happens in the cloud. What your local machine needs isn't a GPU, it's RAM and CPU cores: they set how many windows you can keep open and how many sub-agents run in the background. This episode covers the buying logic, three machines, the worst traps, and the minimum VPS spec for running CC in the cloud.
It’s been a while since I posted, and a lot of new people added me this week. I was in Shanghai teaching two days of in-person classes to Owl Academy’s 19th cohort, on putting WorkBuddy and Claude Code to work on real jobs. I also dropped into Dedao New Business School’s livestream to talk about building a short-video creator matrix with AI.
The question I got asked most this week: I’m about to start using Claude Code, Codex, and WorkBuddy—what kind of computer should I get to make the most of these tools?
The biggest misconception: top-tier AI means a maxed-out machine
I keep running into one big misconception—that using top-tier AI tools requires a maxed-out machine. Plenty of people spend thirty thousand, even forty or fifty thousand yuan on a MacBook, or on a flagship laptop with a top-end gaming GPU. None of that is necessary.
I’m a hardware guy myself. The 3090, the 4090, the top flagship laptops—I bought them, used them, put them through their paces, and sold every one of them over the past stretch. Hardware prices had climbed, so I even made money on the way out.
I did once think about running a local model on local compute to keep my day-to-day costs down. In practice it doesn’t hold up. Only a handful of video, image, and audio jobs work on local models. One or two discrete GPUs, top-end or not, can’t unlock everything an open-source model can do. And on complex tasks they aren’t remotely close to the closed-source labs’ models, on speed or on quality of result. So if you’re using AI as an individual, don’t waste money on a GPU.
The real logic of speccing an AI machine: money goes to RAM, not the GPU
In a traditional build, the discrete GPU often eats 40% or more of the budget. But if large-model inference never happens locally and runs entirely in the cloud, the one component worth real money is RAM—part of why RAM prices have climbed the most in the current hardware market.
RAM and CPU set how many tasks you can run at once and how many parallel sub-agents you can keep in the background. Take Claude Code: each window you open takes roughly 400–600MB of RAM, and long-context windows take more. The concurrency ceiling is generally thread count minus 2. Since most of the computation happens elsewhere, CPU threads aren’t the pinch point either. Add the resident memory that MCP tools and small local services need, plus Windows’ own footprint, and a comfortable setup starts at 16G.
RAM is expensive right now, so if you can’t get to 32G or 64G in one shot, pick a machine with upgradable memory: run 16G now and add an identical stick later. What matters is capacity, not frequency—lower-frequency, higher-capacity RAM is the better buy.
For the screen I still recommend 4K. It draws more power, but when you’re reading model output across several windows, the sharpness and eye comfort beat 2.5K or 3K. Everything past that is preference—portability, battery life, even looks.
Three machines worth buying
If you’re buying new, there are three good options:
- ThinkBook 16+ Core edition—great value, and it’s the version with replaceable RAM;
- Lenovo Xiaoxin Pro 16 GT;
- Redmi Book Pro 16-inch—better value at the same size, thickness, and weight.
If you want more performance, go with the ThinkBook 16p 2025 edition: high CPU core and thread counts, priced past ten thousand and sometimes up to twenty thousand, but far cheaper than the laptops packing high-end desktop-class GPUs.
On a tight budget and open to used, the Dell XPS 15 9510 is a good pick too. It shipped in a huge number of configurations, so make the seller spell out exactly which one it is—the spread runs from just over three thousand to eight thousand.
The traps that catch people most often
- RAM is the worst thing to buy right now—the prices are brutal, so used is usually the better deal;
- A certain “pride of domestic tech” in-house OS can’t run Node or CC at all;
- Don’t buy the wrong version—the same model number ships as a 2025 and a 2026 edition, with big gaps in RAM and CPU performance and big gaps in price, and some sellers will pass the old one off as the new one;
- Know the difference between RAM and storage—a salesperson may tell you “this has 256G of memory,” but they mean storage, how many files you can keep. That’s not the memory that sets how many programs you can run at once. The difference is enormous.
Putting CC in the cloud: how much VPS do you need
Plenty of people, me included, install CC in the cloud rather than on a local machine. So how do you pick a spec when you buy a VPS? If you’re not trying to run seven or eight windows at once and just need two or three for day-to-day work, two cores and 2G of RAM is enough. The official recommendation is two cores with 4GB. If you want long sessions with headroom, four to eight cores and 16G is best. To be straight with you, I run cloud CC with a wrapper on top, three sessions in parallel on a two-core 2G box, and it holds up fine.
Don’t buy a monster rig just to “play with AI”
Whatever you do, don’t fall for the online pitch: “I’m getting into AI, so I need a maxed-out machine worthy of AI’s high tech.” It doesn’t work that way. We’re using AI, not playing games—you don’t need high clock speeds, you don’t need the newest GPU. You need more RAM and more CPU cores. It’s closer to speccing a server.
When people come asking, I point them at a used Acer Edge 16: 16-inch 4K screen, 16G of RAM, thin and light, right around a kilogram. Claude Code, Codex, day-to-day work—it handles all of it.
Updates should pick up pace from here. See you next episode.
Source: EP0058_audio.mp3 · ASR model gemini-2.5-pro (chunked parallel) · full text of the original recording
[00:00] I’m back, friends. I haven’t posted for a while, and a lot of you asked where I went. So: on July 4th and July 11th I was invited to Shanghai to teach two days of in-person classes to cohort 19 at Owl Academy—hands-on work plus theory on how WorkBuddy and Claude Code get used in real work. Then on the 9th I dropped into the Dedao New Business School livestream to talk about using AI to run a matrix of short-video creator accounts. And over that week
[00:25] a lot of new friends added me. The question I get most, by far, is this: I’m about to start using Claude Code, Codex, WorkBuddy—so what kind of computer should I get to run these new AI tools properly? And I’ve found there’s one huge misconception everybody has: that top-tier AI tools demand a top-spec machine. Plenty of people drop 30,000, even 40,000 or 50,000 yuan on a MacBook, or on a flagship machine with a top-end gaming GPU.
[00:50] It’s completely unnecessary. I’m a hardware guy myself—3090s, 4090s, all those cards, plus the top flagship machines—I bought them, used them, lived with them, and over these past few months I sold every single one. And because hardware prices went up, I actually made money selling them. I did once think about using local compute to run a local model, so I could keep my day-to-day costs way down. But once I actually did it, only a handful of video, image and audio jobs could run on local models.
[01:16] With just one local card—even two discrete cards, even top-tier ones—you can’t get the full capability out of an open-source model. And that’s before we talk about efficiency and results on complex tasks, which are simply not in the same conversation as the closed-source models from the big labs. So really, as an individual using AI tools, there is absolutely, absolutely no reason to waste your money on a graphics card. So today I went and built a web page just to show you what kind of
[01:41] machine spec is the better choice when you’re working with agents. Traditionally, when you build a computer, the discrete GPU eats a big chunk of the budget—usually more than 40%, often higher. But if none of the model inference happens locally and it all runs in the cloud, the thing you should actually spend money on is memory. That’s one of the reasons memory prices have climbed the most in the whole hardware market right now. Memory and CPU determine how many tasks you can run in parallel, how many
[02:06] sub-agents can run in the background. The other thing to think about is screen size and how sharp the screen is, because when you’ve got multiple windows open, reading back what the model says gets uncomfortable fast unless you’ve got a good 16-inch screen or bigger. And last is portability—the more portable, the better the battery, and honestly whether the design is something I like—those are the final tiebreakers. If I take Claude Code as the example, every window you open
[02:32] uses somewhere between 400 and 600 megabytes of memory. Windows with long context can take more. And your parallel ceiling is usually your thread count minus 2, because a lot of the computation isn’t happening locally, CPU threads aren’t that demanding either. When we call MCP tools, or run some small services locally, we also need to carve out extra memory for those always-on apps.
[02:57] Plus Windows itself eats memory. So in an ideal setup you need at least, at the very least, 16 gigs of memory just to hold the system up. And since memory is expensive right now, if you can’t buy 32 gigs or 64 gigs outright, look for a model with upgradeable memory. I’m on 16 gigs now, and later I can buy a matching stick and drop it in to get more out of it. And the thing that matters here is capacity, not clock speed.
[03:22] So you can go buy memory that isn’t especially fast but has high capacity—you get more for your money. On screens, I’d still recommend 4K. It draws a bit more power, but it’s sharper overall and easier on the eyes than a 2.5K or 3K panel. So pulling all of that together, if you’re buying a new machine, these three are decent picks. First, the ThinkBook 16+, the Core version.
[03:47] Good value, and it’s the version where you can swap the memory. Then there’s the Xiaoxin Pro 16 GT. The Redmi Pro 16 gives you better value at the same size, thickness and weight. And if you want more performance, you can go for the ThinkBook 16p 2025 version, because its CPU core and thread count are very high. Of course, that puts the price at over 10,000, even up around 20,000 yuan. But that’s still far, far cheaper than the laptops packing
[04:12] high-end desktop-class GPUs. If your budget is tight and you’re okay buying secondhand, the Dell XPS 15, the 9510, is also a solid pick. It’s one model number, but the configs—Dell has a huge number of configs. When you buy, always pin the seller down on exactly what the spec is. The price spread can be anywhere from 3,000-something to 8,000. So, to sum all of that up. First, memory really is at
[04:37] the worst possible buying point right now—it’s extremely, extremely expensive. So buying secondhand is actually the better deal. Another trap people fall into: a certain much-celebrated domestic brand’s in-house OS can’t run Node or CC. Also, with the models I just recommended—do not buy the wrong version. Same model number, but there’s a 2025 version and a 2026 version, and the memory and CPU performance differ a lot, and so does the price, obviously. Plenty of shady sellers pass the old version off as the new one—they blur the two together and sell them that way.
[05:02] Another thing: some friends can’t really tell the difference between memory and storage. Some unscrupulous salesperson will say, oh, my memory is 256 gigs, blah blah—but what he’s talking about is disk size, how many files you can store. That is not the memory that determines how many programs you can run at once. The difference is enormous. Beyond that, a lot of you, like me, install CC in the cloud rather than on a local machine. So when you buy that VPS,
[05:27] that virtual host, what does the spec need to be? If you’re not running seven or eight windows in parallel and just need two or three for everyday work, honestly the minimum can be a 2-core, 2-gig virtual host. The official recommendation is 2 cores plus 4 gigabytes of memory, but if you want long sessions and some headroom on resources, better to go for 4 to 8 cores and 16 gigs. Though truth be told,
[05:53] I’ve got a shell wrapped around my cloud CC right now, running three of those sessions in parallel on a 2-core, 2-gig box, and it’s not really a problem. Whatever you do, don’t let the marketing online convince you that now that you’re getting into AI you need to buy some beast of a machine, or some maxed-out computer just to be worthy of all this high-tech AI stuff. It doesn’t work like that. Using AI isn’t gaming. You don’t need high clocks, you don’t need the newest GPU. You need more memory and more CPU cores.
[06:18] It’s a little bit like speccing out a server. When friends come to me, I’ll often recommend a secondhand Edge 16—16-inch 4K display, 16 gigs of memory, super thin and light, right around a kilo. And for everyday use, whether it’s Claude Code or Codex, it’s absolutely, absolutely fine. That’s it for today. I should be posting a lot more again soon. See you next time, bye.