MacBook Neo: A carry everywhere laptop for remote AI steering
I’m on a nearby couch during my son’s piano lesson on a Tuesday night. The indigo MacBook Neo is resting on the armrest: quiet, barely warm. Across the internet at my house, heavy (a more powerful Mac) is doing the grunt work: always on, always ready. Earlier today I planned a refactor and kicked it off with Codex working the plan.
On paper, this “entry” level laptop should not be an essential tool in my toolkit.
I do software development, and traditionally that meant I sometimes have to run memory intensive VM’s, simulators, IDEs, and server software. I usually need real headroom: RAM, battery, screen space, enough local capacity to run several things at once without thinking about it. The Neo is not that kind of machine. Apple positioned it for students, first-time Mac buyers, and light workloads. At $499/$599, with an A18 Pro chip and 8GB of RAM, that positioning makes sense.
And yet the Neo is earning a place in my setup anyway.
It is not that you can suddenly do everything with 8GB of memory. It is that the shape of a lot of software development work is changing. More and more of the useful work happening on my machines now can begin somewhere more powerful and continue without me at the keyboard for a while. Agents reading docs, writing code, running tests, and occasionally getting things wrong in ways that need correcting. Those things can be managed with remote access tools. That changes what the laptop I take with me needs to be good at.
In this post:
- Apple told only a part of the story
- A Mac as a remote control for a Mac? what???
- Why the Neo is unusually good at the role
- Making 8GB work without pretending it’s 32GB+
- Apple undersold the interesting part
- What I would want in the next Neo
Apple told only a part of the story MacBook Neo’s potential
For development, a light machine is not usually my category.
That is exactly why the Neo is interesting. If you evaluate it as a primary development machine, the case is weak for power users that run demanding software development applications. If you look at it as a companion machine though, the value becomes more clear. “Can I run all my apps on it?” is mostly the wrong question. A better question is “How might I use this for what it can be really good at?”
The low relative cost also changes how you think about portability. I carry it to more places than I would ever bring a $3,000+ laptop. I use it in a way that rarely stresses its limits, keeps performance snappy, and lets the battery last an absurdly long time.
A Mac as a remote control for a Mac? what???
The MacBook Neo is an ideal remote control for my heavy Mac.
Heavy runs the builds. Heavy runs the long-running daemons, scheduled tasks, the Xcode builds, the parallel test suites, the local LLM’s. Heavy is where agentic work that needs to keep going lives, and where that work gets plenty of horsepower.
The Neo’s job is different: check in, steer, approve, kick off the next thing, human-in-the-loop eval of the results. Use remote access (Screensharing, VNC, SSH) into heavy from anywhere (Tailscale/VPN). Make a quick edit. Review a diff. Nudge an agent back on course. Approve the next step. Schedule the next bit of work and close the lid any time.
The Neo is the machine I carry to steer the work happening on heavy.
Why the Neo is unusually good at the role
Light but sturdy, stays cool. At almost a pound lighter than a Macbook Pro, and given that using this as an AI remote control does not stress machine at all, it is a real ‘lap’top you can put on your lap and not feel the heat of the sun on your knees. It stays fairly cool. It is light enough, but it also feels rock solid with that Aluminim case build quality you expect from an Apple laptop.
Cheap enough that you carry it to more places. There’s a different psychology around a $499/$599 machine than a $3,000 one. The “is it worth the trouble/worry to bring along?” calculation changes. More places feel like a yes. I find myself taking it places without a case and without a charging cord. If it gets broken/stolen/etc it is a small fraction of the cost to replace compared to heavy.
Battery that supports more than a day of intermittent check-ins. Sixteen hours of battery life and using it for steering AI means I’m not hunting for outlets between the couch, the kitchen, and the coffee shop. That said, it charges with any usb-c adapter.
Locally fast enough for the steering stack. Even for some offline scenarios I can be productive by just being a little careful to choose apps that keep the device snappy. Ghostty, Zed, Safari: these run fine.
Making 8GB work without pretending it’s 32GB+
Some things belong on the Neo. Some things belong on heavy.
What fits comfortably:
- Terminal (Ghostty)
- A lightweight editor (Zed)
- Safari with tab discipline (automatic age out of tabs is a config option!)
- Notes, Messages, a handful of support apps
- Web apps for email, calendar, and docs
- Claude Code, Codex, and other CLI based agent control surfaces.
What I pushed over to heavy:
- IDE’s and heavy editors (XCode, VSCode, JetBrains, etc)
- Web and Database servers
- Executing parallel builds and test suites
- memory-heavy resident and background apps
- Electron-heavy apps that have a decent web or native alternative (Slack, Dropbox)
- Chrome
Habits that matter:
- Accept that this machine rewards focus more than sprawl
- Keep fewer browser tabs, fewer apps running
- Quit what you’re not using — on a 32GB+ machine you can get sloppy; on 8GB it sneaks up on you
- Prefer tools that do work and exit over tools that sit in the background being ready
- Prefer tools that compile down to native and avoid cross-platform wrapper layers when possible
Note
The constraints are real. 8GB isn’t generous. If you mind what you’re using and how you use it, for the remote-control use case, you can keep performance snappy.
Apple undersold the interesting part
Apple sold affordability and approachability. The more interesting story is that the Neo fits an AI-era workflow unusually well.
We’re in an early period where computers are increasingly able to do meaningful knowledge work with AI for us while we’re not at our desk. That makes “small, light, always with you, connected” more valuable. The Neo optimizes for exactly that profile. Apple’s framing, “beginner’s Mac” and “entry-level laptop,” doesn’t really capture it. The Neo isn’t just a lesser Mac for light users. For AI power users that set up their tools deliberately, it’s the ideal Mac to act as a remote control surface, and take with you anywhere.
What I would want in the next Neo
It is not all rainbows though. After carrying one around for a month, I have wishes for what would make this an even better go-everywhere laptop.
The reflective/glossy screen is the Neo’s worst feature for a go-anywhere machine. A matte option, please.
Cellular support would further enable the remote-control story. An always-connected Neo that doesn’t need my iPhone hotspot would close the last gap in the “pull it out anywhere, steer heavy, put it away” loop. A laptop-sized antenna would hopefully do better than an iPhone hotspot for locations with more spotty network connectivity.
A more aggressive low-memory mode in macOS would help too. The OS knows this machine has 8GB; more optimizations and options for choosing not to enable certain system features would be welcome. Right now, macOS grabs about 6GB of the 8GB on the machine just to run the operating system, and it starts to swap if you load it past 8GB. If I recall correctly, some Linux systems with GUI’s are closer to 1GB of operating system memory usage. Surely there is some gap to close here.
The rumor mill says the next Neo may get a RAM bump. That would smooth out some rough edges, but the bigger point is not raw power. The point is that the laptop in my bag no longer needs to be the machine that does everything. It needs to be light, cheap enough to bring everywhere, connected, and good at steering work already in motion.
It’s kind of already there, which is what surprised me the most … back on that couch during piano lessons … I kicked off Claude and Codex on some work, and edited this blog entry. When it was time to go, I shut the lid without a second thought, knowing that the agents I kicked off elsewhere would keep working. It was nice.