AWS Emulator puts AWS on your laptop, and Apple's Harbor pools Macs for AI

On Wednesday's HN front page, Amazon put AWS on your own machine. AWS Emulator is a local program that answers AWS API calls. You point the AWS CLI or an SDK at it with a few environment variables, and your code runs as usual, with no AWS account and no fee. On Linux it installs as a package. On a Mac or Windows, it runs in Docker.

AI agents wrote all of it, and the team behind it hasn't reviewed the code. One group of agents writes tests and checks each one against real AWS. A second replays them on the emulator and files whatever differs. A third fixes one issue at a time, behind a gate for builds, security and fidelity. So a DynamoDB table with a two-letter name gets the same validation error AWS sends. In the thread, schonfinkel said it looks vibe-coded, and Bnjoroge answered that a bounded job you can check against the real service is exactly where a swarm of agents fits.

$ aws dynamodb create-table --table-name ab …
ValidationException: … length greater than or equal to 3

Don't test security on it. The emulator never denies a request signed with its own key, and it skips S3 bucket policies and KMS key policies, so a call AWS would refuse can succeed here. Each emulator keeps one Region and one account, and holds everything in memory, so a restart gives your tests a clean slate. Usage data goes to AWS unless you turn it off. In the thread, scriptsmith had hoped the official emulator would check permissions better than LocalStack does.

Apple is building a Mac app called Harbor, found by the leaker Aaron Perris. It downloads open-weight models and runs them on Apple silicon, with nothing sent to the cloud. Plug two or more Macs together over Thunderbolt 5 and it pools their unified memory, so you can load a model bigger than any one machine holds. Macs with Thunderbolt 4 can't join. It's in private preview under Claris, the Apple subsidiary behind FileMaker. In the thread, waz0wski pointed out that Exo already clusters Macs this way.

Atuin, the shell history tool, now keeps your coding agent sessions too. From version 18.24, it syncs Claude Code, Codex and OpenCode sessions across your machines, end-to-end encrypted, and you can resume one in a different agent. Start a task in Claude Code on a dev server, and finish it in Codex on your laptop. An MCP server lets agents search your old sessions themselves. Capture is opt-in. In the thread, suis_siva, an Atuin engineer, said it syncs pretty much everything, with no filter for what's worth keeping.

$ atuin resume              # any session, any machine
$ atuin mcp install claude  # agents search old sessions

Your SSH key doesn't have to sit in a file. A Mac can create it inside the Secure Enclave, where it can't be copied out, and ask for Touch ID every time it signs. There are no backups. The key dies with the Mac, so put a second key on every server. In the thread, jwr, who uses YubiKeys, called that required touch a feature: an AI agent can't reach their production servers unless they're there to approve it. I'd use Secretive for this. It's the same enclave with a clearer prompt, and it's where the author ended up.

$ sc_auth create-ctk-identity -l ssh-MacBook -k p-256-ne -t bio
$ export SSH_SK_PROVIDER=/usr/lib/ssh-keychain.dylib

Guido van Rossum announced that Tim Peters died on July 15. Peters wrote the Zen of Python, the poem you get when you type import this. In 2002 he designed Timsort for Python's lists, and Java and Android adopted it. One of his first contributions was persuading Guido that integers and floats should mix in arithmetic. His last post on the Python forum ended: the real world is more complicated than our clean abstractions hope for.