51 links
> We tasked Opus 4.6 using agent teams to build a C Compiler, and then (mostly) walked away.
> Parametric 3D printable magnetic separation contactless key switch and stabilizers (OpenSCAD files).
> This approach has become standard practice — Claude Code now automatically searches for markdown versions of websites, and other tools like Codex have followed suit. Yet despite its importance, few websites have implemented this technique. Here’s how to be one of them.
> A simulated bash environment with an in-memory virtual filesystem, written in TypeScript.
> amla-sandbox is a WASM sandbox with capability enforcement. Agents can only call tools you explicitly provide, with constraints you define. Sandboxed virtual filesystem. No network. No shell escape.
Lets a coding agent run commands in a different VM
> Use a (gitignored) file for interactive scripting. Instead of entering a command directly into the terminal, write it to a file first, and then run the file. For me, I type stuff into make.ts and then run ./make.ts in my terminal (Ok, I need one Up Enter for that).
> Agents mirror local style. Your codebase is the prompt. If you're using a state-of-the-art agent, and you don't like the code it generates, don't correct the agent. Instead, improve the code it learned from.
> A modern, component-based language for building reactive web apps. Type-safe. Fast. WASM-powered.
> A simple, lean issue tracker CLI designed for AI-assisted development. Track tasks across sessions with context preservation.
[L]ike many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words.
> When you're using [a coding agent] to clean up your codebase and improve code health, it's sort of like using a pressure washer. You can use it to clean your steps but you wouldn't use it to clean a painting.
I think this is fiction?
> On January 21, 2026, @fredwilson challenged @seth: AI can write code, but it can't affect the physical world.
> This is our response. Real corn, grown from seed to harvest, with every decision made by Claude Code.
(Not real yet, though. They just started.)
> Gas Town is just Gas Town. It started with Mad Max theming, but none of it is super strong. None of the roles are proper names from the series, and I’m bringing in theming from other sources as well [...]
> In its purest form, Ralph is a Bash loop.
> The repeat-test library is my attempt to come up with a nicer API for writing property tests in TypeScript.
> Cross-platform shell tools for Deno and Node.js inspired by zx.
ssh sends lots of "chaff" packets
> Combining the three ideas, I now have a deno script, called box, that provides a multiplexed interface for running ad-hoc code on ad-hoc clusters.
> A Rust port of Steve Yegge's beads, frozen at the "classic" SQLite + JSONL architecture [...]
A PDS browser, pointed to my own PDS.
> In differential spec analysis, you write multiple implementations from a spec and then compare their behavior. It is most powerful when paired with fuzzing, but as we’ll see, it even works without fuzzing.
> Beans is an issue tracker for you, your team, and your coding agents. Instead of tracking tasks in a separate application, Beans stores them right alongside your code. You can use the beans CLI to interact with your tasks, but more importantly, so can your favorite coding agent!
> I am sorry but I've somehow been turned into a superfan of exe.dev, Shelley (their coding agent), and Claude Opus 4.5. I'm going to gush a bit. After ...
> [exe.dev co-founder here] If you are curious, we have a clone command coming soon for sub-section creation of a new VM out of an existing VM. This i...
> [...] Now I have a full-time driver. I’m in the back seat, giving directions when asked, or perhaps browsing the Internet if the driver doesn’t need any help. I do look in now and then to make sure we’re going in the right direction. [...]
> How we learned to stop worrying and love writeable root filesystems.
> With the rise of LSPs, query-based compilers have emerged as a new architecture. That architecture is much more similar and also different to Signals than I initial assumed them to be.
> We developed a multipurpose secret-using service called the Tokenizer.
> We apply a transparency log to a centralized keyserver step-by-step, in less than 500 lines, with privacy protections, anti-poisoning, and witness cosigning.