posts · 2026-07-18

This guide walks you through setting up a spare Mac as a dedicated environment for Claude Code with full computer-use access. The author recommends wiping the machine, creating a fresh local account without an Apple ID, enabling SSH, and configuring passwordless sudo. You can then control it from your main Mac or phone via the Claude app. Compared to running in a container, this setup lets Claude directly control macOS-native apps like Unity and keeps network requests isolated. The post assumes two Macs on the same Wi-Fi but doesn't specify hardware requirements.

Kimi K3 tops AfterQuery's SpreadsheetBench 2 leaderboard, beating Claude Fable 5. The post is blocked by Reddit, so no scores, methodology, or model details are disclosed. Only the title is confirmed—worth noting, but hold off on excitement until the benchmark details surface.

ChatGPT has launched a chat history search feature, letting users search through nearly 4 years of their own conversations. The post doesn't disclose whether the search supports fuzzy matching, time filters, or cross-session references, but the title confirms this is a long-requested basic feature. I'd take it with a grain of salt: being able to find a message doesn't mean understanding the context—actual experience still needs to be tested after launch.

HKUST will present at ICML'26 that MoE routing is fragile to repeated tokens. Duplicate inputs cause the router to overload a single expert, breaking load balance and slowing inference. The post doesn't disclose exact experiment setup or datasets, but highlights an easily overlooked engineering pitfall in MoE.

In 1988, Scottish hi-fi company Linn built the Rekursiv chip: hardware-enforced memory type and bounds checking, on-chip garbage collection, and a single persistent object store spanning RAM and disk. The prototype ended up in a canal after the economics killed it. ARM's CHERI now ships similar ideas in production silicon, and the cost equation has flipped. The post doesn't disclose when or where exactly the machine was dumped.

Neil Rimer, co-founder of top VC firm Index Ventures, said at a tech festival in Athens that the massive wealth AI is creating in Silicon Valley will have to be redistributed—voluntarily or involuntarily. He hopes tech leaders take the lead. Index reportedly netted ~$9B last year from exits including Figma's IPO and Google's Wiz acquisition. Rimer stepped back from day-to-day investing in 2021 and now lives mostly in Athens.

Index Ventures co-founder Neil Rimer said at a tech festival in Athens that the massive wealth AI is creating in Silicon Valley will have to be redistributed, voluntarily or involuntarily. He hopes it's voluntary and that tech leaders can lead the way. Rimer has stepped back from day-to-day investing, but Index has raised roughly $15 billion since founding; last year's exits alone—Figma's IPO and Google's acquisition of Wiz—netted about $9 billion. The post doesn't spell out how or to whom the redistribution should happen.

Author Dave Eggers writes in the FT that AI-generated novels are 'gullible and ridiculous' and no one will read them. He argues AI lacks human emotional depth and lived experience to write stories worth reading. The post doesn't name specific AI models or provide experimental data, but Eggers is a prominent novelist voicing a common literary skepticism toward AI writing.

Dave Rahardja argues that when an OSS project becomes too big to fail, its leadership behaves like a monopoly. The fix: break it into interoperable components using standard protocols, just like UNIX. The post doesn't name specific projects to split or how to enforce this, but makes a sharp point—monopoly may be a human organizing trait, not just a capitalist one.

On July 13, the Washington Post reported—citing a single anonymous source—that the US government and AI industry are discussing an open-model release framework that could use the capabilities of China's leading open models as a baseline. If a US model does not exceed that line, its release process might be streamlined. No draft policy or White House confirmation exists; the post doesn't spell out whether 'capability' means cybersecurity, coding, or composite benchmarks. This thread extends a longer logic: from 2022 chip controls, to a 2025 attempt to classify closed-weight models under export rules (later rescinded), to June 2026 when Anthropic cut off global access to Fable 5 and Mythos 5 under a government directive and OpenAI restricted GPT-5.6 to a few vetted partners for ~13 days. Chips, cloud compute, weights, and APIs are four channels through which the same capability reaches users; when a model slips past one gate, policy moves downstream. Future policy may weigh two lines: a danger-capability line assessing cyber or bio risk, and a global-availability line asking whether equivalent capability has already spread irreversibly via open weights.

Claude Code, Codex, and Cursor are converging as coding agents, but the cloud platforms that turn them into production services diverge from the very first step. Koyeb asks you to deploy a Service first—it manages runtime, you manage business state. Cloudflare asks you to assign a fixed Agent ID—messages and local state follow that ID. Vercel asks you to define a task as a sequence of steps—it records progress and supports pause-and-resume. These starting points determine how each platform recovers state after a process ends: Koyeb restarts compute instances, Cloudflare retrieves object state by Agent ID, and Vercel recovers steps and files via Workflow run ID and Sandbox ID. The post recommends asking what your product centers on—long-running programs, many long-lived objects with local state, or tasks that wait hours before continuing—before choosing a platform.