- ↔
- →
- November 21, 2026
-
🔗 Register Spill Joy & Curiosity #107 rss
In Werner Herzog's Rogue Film School, he taught his pupils how to pick locks or forge signatures. Herzog says the reason behind that curriculum is that some films can't be made if you don't "have the right criminal energy and the skills ".
(His movie Fitzcarraldo , whose production Wikipedia calls "troubled" only to then mention that a 320-ton steamship had to be pushed over a hill in the Amazon rainforest and that, at the end of filming, the chief of a native tribe told Herzog they could, you know, take care of the problem for him and kill Klaus Kinski, that movie couldn't have been made, in Herzog's words, without "massive forgery".)
Now, that's what Herzog says as to why you need criminal energy and "the skills". My interpretation of the curriculum is different. And yes, I'm going to use my criminal energy here to re- and possibly misinterpret the founding idea behind a school I neither visited nor was involved in.
I think that he's teaching how to pick locks and forge signatures and be rogues because you need to live a life , ideally a full life, in order to make films.
Because if you don't have that, what are you going to make films about? About school? About learning how to make films? No, you have to have something worth sharing, something worth talking about: experiences, ideas, opinions, doubts, delights, heartbreaks, and questions.
And I think it's the same for programming now.
Yes, it's always been the case that programming alone, the typing of code and the construction of computer programs, wasn't enough.
But there was so much typing, and syntax, and libraries, and function signatures, and all that stuff to wrestle with that the ratio was off: for one bit of idea you had to spend ten bits of programming.
Now it's much more balanced and you have to figure out what to do with all the programming you can now accomplish.
So, if I had to build a Rogue Software School, I'd get my students to learn about business, about startups, about marketing, about markets, about the places where software is made and sold; I'd want them to learn about how software is used and why, learn about the trends involved in all of that, learn how to market and sell software.
And I'd also want them to spend time in places where nobody talks or even thinks about software. Work on a construction site, unload trucks, help in a restaurant, work in a bookstore, run a youth soccer club.
Find something that gives you a reason to build software, because programming isn't enough anymore.
Note: This will be the last Joy & Curiosity this year. I'll be back in January. If you want me to come back earlier, tell your friends about this newsletter.
-
Completely forgot to mention this last time: we shipped Boxes! What's a box? It's simply a computer, a VM. You can tell Amp now to deploy something to a box and it'll do it. You can have as many apps as you want running on a box. Apps, daemons, scripts, whatever you want. It's just a computer. There are no containers or other isolation. Agents absolutely love that. I have a tiny box on which I run my newsletter-link collector app, my metronome app to practice drums, a festival store app for my local club, and a bunch of other things. Best of all: on each box there's an agent running. No longer do I have to carefully edit text or other content or data in production. No, I can just point the agent at it via the built-in widget and say "format this nicely" and it'll do it. Jellyware!
-
Bad ideas that aren't bad anymore. Yes, yes, yes, it's what I've been saying, yes, rethink everything, yes, a fundamental constant in a very big equation has changed and you need to rerun the calculations.
-
ADVICE WANTED: "If you could write one essay to every scared new grad and young person in software… What would you tell them?" I'm going to be a judge for this writing contest, which not only means that I'm Very Important and Smart but also that I'm Cool and Sexy and maybe I'll wear a wig like the judges in England (or whatever they're called) when reading submissions. And it also means that I'd love for you to submit an essay. I'm serious. I really am Smar-- no, I mean: submit an essay!
-
Levent Alpoge claims to have proven the Riemann Hypothesis. I can't tell you whether it's a valid claim or not. It's 250 thousand pages long, which is quite the hurdle to declaring you agree or not, but, maybe even more importantly, I also don't know anything about math. What I can tell you is that I recommend you read the first two pages of that PDF. "[…] this time Claude far outpaced me near the finish line. No, Claude flew, and danced, and sparkled near that finish line. I had us on the line of combining two quite different ideas present in a toy setting, one of which was already new and shocking, making very simple one of the shadows of Riemann over which we mathematicians felt most triumph. I guided us to the right situation analogous to that toy setting, and then Claude began to leave me in awe."
-
Joscha Bach: "It still feels to me as if dropping through an event horizon. That is, there is nothing specific about any given moment, but the rate of change and weirdness is constantly speeding up, and we won't ever return to the before times."
-
Scattered thoughts on how doing math feels these days. This was a great read. And, funnily enough, I came across that post a few days before the whole Riemann Hypothesis AI sensation extravaganza.
-
This is absolutely wild: "BREAKING: Rockstar Games says Grand Theft Auto VI sold $3.79 billion in 24 hours, making it the biggest entertainment launch of all time. Pre-sales of the game reached 32.5 million units." It does seem like everyone is talking about GTA VI and I can't help but think that I agree with the people shouting "bring back monoculture!" because it is nice having shared experiences like this.
-
The School by Donald Barthelme. This did something to me. The amount of inspiration you can get from a 4-page PDF, huh?
-
Hillel Wayne on his Least Favorite Example in Software Engineering. Great post. In response to Hillel, Richard Feldman also shared his least favorite example. Examples are important! So, so, so important. In case you haven't read it: Examples are the best documentation.
-
I started reading the first of Knausgard's My Struggle books. It all started with a post I saw a few months ago. It was a picture of a young girl reading the book and the post made the rounds due to (I assume) the dichotomy of a young girl reading a book whose original title in Norwegian is Min Kamp, which is, well, the Norwegian version of Mein Kampf, which is, well, … So I started reading the Wikipedia page, then I read it again and again over the next few weeks and became increasingly fascinated. Finally, right before the flight to London last Sunday, I bought the first volume for two euros and started reading. I was hooked immediately. I'm now halfway through the book and I can't remember the last time I was this into a book (which is also why there are fewer links in this issue). On nearly every page I wonder: how does he do it? How does he remember? How does he weave the events like this? How does he create this sense of suspense when describing a normal afternoon of a teenager? Why is this so insightful? It was a huge bestseller, Wikipedia told me, but I don't know what the general perception of the books is, but to me it feels like great literature. It's very good.
-
Yes: "Theater is simply not a current artform, it's a historic one. To write a "play" is to purposefully engage in anachronism. Current artforms include sigma edits, moodboards, nanofiction, DM dialogues, mass shootings, AI fruit commedia dell'arte, video essays, thirst traps, etc." The last sentence I'm not sure about, at least not entirely.
-
Ben Thompson: Obituaries.
-
I really like these two terms here: everflux software and translucent sources. Everflux software means that "instead of stepping from release to release, months apart, software now evolves continuously." And translucent sources: "Today Claude will happily pick apart any Electron app, and any binary shipped with debug symbols has become a reverse-engineering playground for LLMs. In other words, much so-called closed-source software is now open source in all but name, and keeping code closed makes less and less sense."
-
Henrik Karlsson on learning from DFW: You learn more about writing from close reading than from writing advice. This made me buy a subscription to his Substack. Great writing, great piece, as always by Karlsson. And yet… Something always rubs me the wrong way when someone wants to ascribe specific intentions to the author of a piece of writing, music, art. That's not exactly what Karlsson is doing here, but I couldn't help but think of all the different pieces of Hendrix analysis I read, listened to, or watched over the years. "And then he did this because of… and after that he did so he could…" It all sounds neat and makes you go a-ha! But then you watch an interview with Hendrix and listen to enough of his music and have to come to the conclusion that, well, it's more likely that he didn't think about any of this at all. It just felt right to him.
Want to sign up for Rogue Software School? Here you go:
-
-
🔗 smol-machines/smolvm smolvm v1.36.1 release
Fixed
- A host bound live is trusted at once. In v1.36.0, adding a credential binding for a new host to a running machine (
smolvm machine credentials add) reported success, but the guest did not trust the new host until its file cache expired, so requests failed withcurl: (60) self-signed certificate in certificate chain. The host now hands the guest its new CA bundle directly. Needs the v1.36.1 guest agent; a machine on an older agent keeps the old behavior until it restarts on this one. (#2356)
Added
Runtime::set_credential_bindingsfor embedders: replace a created, stopped or running machine's credential bindings and their values in one call. Values held for a binding that stays are kept; those of a removed binding are dropped. (#2356)machine ls --jsonandmachine status --jsonlistcredentials: each binding's name, variable and hosts. Values are never on the record, so they are never shown. (#2356)
What's Changed
- docs: say that virtiofs DAX is off on arm64 hosts and SMOLVM_MOUNT_DAX does nothing there by @BinSquare in #2087
- Add smolvm docker: one command starts a Docker engine in a managed machine and points docker at it by @BinSquare in #2089
- Share the home directory with the smolvm docker machine at the same path by @BinSquare in #2090
- Resolve host.docker.internal to the host from smolvm docker containers by @BinSquare in #2091
- Fix a port race in the leader-exit test by @BinSquare in #2096
- Remove smolvm docker by @BinSquare in #2095
- Hand supplied credential values to a running embedded machine at once by @BinSquare in #2097
- Pin libkrunfw with UDP kept inside a TSI guest, and test it by @BinSquare in #2099
- Publish ports below 1024 on macOS, add IPv6 loopback to live-forwarded ports, and lift the 64-mapping cap by @BinSquare in #2092
- Return idle guest memory to the host within two minutes and cap new machines at half the host's RAM by @BinSquare in #2094
- Install a root-owned agent-rootfs when root runs install.sh by @rdslw in #2082
- Announce a changed file to the guest once per change by @BinSquare in #2102
- Answer guest DNS from a host cache that coalesces bursts and resends lost queries by @BinSquare in #2098
- Keep every disk chain under the branch depth limit: fold restored checkpoint layers and frozen-source chains by @BinSquare in #2103
- Exec sessions: commands the node owns, resumable after a dropped connection by @BinSquare in #2101
- Let a guest hold tens of thousands of connections on virtio-net and free their host sockets promptly by @BinSquare in #2104
- Scope the usage journal to the test's own thread by @BinSquare in #2106
- Pin libkrun 526be460 and libkrunfw f290c62b, rebuilt for every platform by @BinSquare in #2109
- Build the agent rootfs as non-root on hosts with user namespaces again by @BinSquare in #2107
- Answer a start missing the mediated interceptor with 400, not 500 by @BinSquare in #2108
- Run tests that need a released file lock free at once in their own process by @BinSquare in #2110
- Pin libkrun 9df62257 and libkrunfw 7f4d4950, rebuilt for every platform by @BinSquare in #2113
- Stop resetting virtio-net connections a server closes first by @BinSquare in #2118
- Upgrade rusqlite to 0.41 for the patched bundled SQLite (RUSTSEC-2026-0459) by @BinSquare in #2128
- Keep a host memory reserve VMs cannot take and charge branch children for growth by @BinSquare in #2127
- Ask before stopping a machine on delete, so a refused or declined delete leaves it running by @connorburgess in #2131
- Prepare SmolVM v1.34.1 for release by @BinSquare in #2135
- Bring a soft open-file limit above kern.maxfilesperproc down to the cap on macOS, so the limit raise_nofile_limit reports is the one in force by @connorburgess in #2132
- Leave no data directory behind when exec, status or stop name a machine that does not exist by @connorburgess in #2129
- Warn when --block-private keeps a named host unreachable by @BinSquare in #2146
- Register Rosetta itself as the x86_64 interpreter when the host answers its start-up ioctl by @BinSquare in #2148
- Make a mounted host directory belong to the workload user so a non-root workload can write to it by @BinSquare in #2149
- Record the image platform on the machine so a Rosetta machine can be created from an amd64 image by @BinSquare in #2147
- Bump libkrun so a Rosetta machine runs amd64 programs directly and a macOS machine stops promptly by @BinSquare in #2150
- Keep a cache disk's chain on its shared base when compaction shortens it by @BinSquare in #2145
- Satisfy Rust 1.100's needless_bool lint in connect_in_progress on Windows by @BinSquare in #2154
- Bound branch admission and reported capacity by the VM slice's memory limit, not just host free memory by @BinSquare in #2152
- Stop throttling the VM slice and reclaim it from the pressure guard instead by @BinSquare in #2153
- Release a paused branch child's VM lock so the memory pressure guard can resume it by @BinSquare in #2157
- Keep a restored machine's local image on its storage disk instead of mounting the capturing host's archive by @BinSquare in #2163
- Update quinn-udp to 0.5.16 for RUSTSEC-2026-0538 by @BinSquare in #2165
- Count every symlink with one mode in the agent rootfs digest so a Mac checkpoint restores on Linux by @BinSquare in #2162
- Carry guest traffic in 64 KB frames over the gateway link so downloads use a quarter of the CPU by @BinSquare in #2168
- Pin libkrun 518949b4 and libkrunfw 0fae3853, rebuilt for every platform by @BinSquare in #2169
- Reserve tmpfs for concurrent RAM captures and sweep abandoned checkpoint scratch at serve start by @BinSquare in #2173
- Let a packed image's branch take the deferred checkpoint save and say when the VM died mid-save by @BinSquare in #2174
- Integrate and validate Docker Engine, automatic ports, and nested Rosetta support by @BinSquare in #2172
- Run x86_64 images in containers Docker starts inside a Rosetta machine, keeping their PID by @BinSquare in #2093
- Serve the Docker Engine API from smolvm, every container a machine by @BinSquare in #2114
- Publish the ports a machine starts listening on, with --auto-ports by @BinSquare in #2136
- Give engine containers user-defined networks, so Docker Compose stacks run by @BinSquare in #2115
- Let engine containers reach the Docker socket, so Testcontainers and Dev Containers work by @BinSquare in #2116
- Branch engine containers from a warm base when many of one image run by @BinSquare in #2117
- Publish engine container ports on the address each one names by @BinSquare in #2119
- Give engine containers a volume for each VOLUME their image declares by @BinSquare in #2120
- Move images in and out of the engine: save, load, push, commit, import, export by @BinSquare in #2121
- Run --network container: containers in that container's machine by @BinSquare in #2122
- Give engine networks IPv6 by @BinSquare in #2123
- Run the Docker API on demand with independent workload supervisors by @BinSquare in #2175
- Fix Buildx volume permissions and macOS restart stalls by @BinSquare in #2178
- Improve default macOS shared-volume write performance by @BinSquare in #2179
- engine: speed up macOS Buildx with automatic overlayfs snapshots by @BinSquare in #2181
- Run the guest keep-alive init as root while workloads and execs keep the image user and its supplementary groups. by @BinSquare in #2004
- engine: fix multi-stage Buildx builds containing deleted files by @BinSquare in #2183
- Scrub injected credential values from what a credential host sends back by @BinSquare in #2180
- Re-authorize a restored checkpoint's credential bindings from the CLI, and refuse a start that could not inject them by @BinSquare in #2182
- Sweep a deleted machine's pause-operation lock along with its fork-operation lock by @connorburgess in #2184
- Let machine update set and remove labels, in any machine state by @josmo in #2143
- Leave the Docker Engine API opt-in so installing or upgrading smolvm never switches the user's Docker context by @BinSquare in #2186
- Bump every workspace crate and the nix flake to 1.35.0 by @BinSquare in #2185
- fix(network): retain OS-allocated local TCP listeners by @kumanday in #2112
- Retry a checkpoint part the object store refuses with a transient error by @BinSquare in #2191
- fix(shim): preserve foreground helper exit statuses by @hfiguera in #2190
- Delete the image seed builder when a CLI start is interrupted, and reap builders whose owner exited (#2083) by @rdslw in #2188
- Honor SMOLVM_DATA_DIR and --state-dir on macOS by @BinSquare in #2193
- Map a mounted host directory to the workload user again, not the keep-alive init's root, so a non-root workload can write to it by @josmo in #2189
- Open the Nix flake bump from main and run its required attribution check, so the bump PR can merge by @BinSquare in #2194
- Bind the port forward tests' ports before using them, instead of picking a free port and binding it again later by @BinSquare in #2195
- engine: use an on-demand native Buildx builder by @BinSquare in #2196
- perf(engine): reduce container lifecycle overhead by @BinSquare in #2198
- perf(engine): improve streaming output throughput by @BinSquare in #2200
- perf(engine): bound log tail reads and stream binary payloads by @BinSquare in #2201
- Compile the auto ports test's port helper only on Unix, where its one caller runs by @BinSquare in #2199
- Keep an image's files under /run when a container starts by @BinSquare in #2203
- Leave the Docker context alone when an engine with its own state directory is set up, and remove its registration by name by @BinSquare in #2202
- Stop a workload supervisor on SIGTERM and when its engine state is deleted, whoever holds the warm base lock by @BinSquare in #2204
- Start a display without a host GPU, check the host GPU before a --gpu start, and finish stop and delete around a process the kernel will not let exit by @BinSquare in #2210
- Allow ARM cloud checkpoints to return to macOS by @BinSquare in #2216
- Refuse a staged sync entry whose parent leads outside the mount through a symlink, so a guest cannot delete host files by @BinSquare in #2242
- Serve at most eight workload log connections, closing the oldest, so a guest cannot exhaust host threads by @BinSquare in #2243
- Bump libkrun so a resumed macOS machine releases the memory its guest frees and keeps it out of checkpoints by @BinSquare in #2244
- Trim the guest's disks before a capture, so deleted files leave the checkpoint and the host disk by @BinSquare in #2245
- Forget a host's learned addresses when a running machine's allow list is left with no hosts by @josmo in #2142
- Point exec and cp on a paused machine at resume, not at a start that refuses it by @connorburgess in #2167
- Bump libkrun so restored macOS machines keep later writes in checkpoints and qcow2 discards free host disk space by @BinSquare in #2248
- Preserve local-image machines across export and restore by @Vishv07 in #1980
- Preserve packed network restrictions and apply overrides atomically by @Vishv07 in #2006
- Clone the case-sensitive layers image instead of formatting a new one by @BABTUNA in #1713
- Preserve staged files when an interactive output pipe closes by @connorburgess in #2164
- Diagnose unsupported macOS virtualization without masking other failures by @Bnjoroge1 in #1323
- Allow disk growth before first boot by @BinSquare in #2211
- Expose machine files and harden engine storage workflows by @BinSquare in #2206
- Close failed port-forward tunnels and reap reply readers by @BinSquare in #2214
- Fix Docker container name filtering by @BinSquare in #2225
- Speed up and isolate first-use disk template expansion by @BinSquare in #2229
- Fix Docker networking and persistent VM lifecycle by @BinSquare in #2234
- Serialize overlay remounts so concurrent prepares don't race by @Liamso in #2166
- Fix interactive stream stalls and idle wakeups by @BinSquare in #2250
- Report Docker container resources from guest kernel accounting by @BinSquare in #2228
- Preserve image index digests for Docker image lookup by @BinSquare in #2224
- Hold back the growth already promised to running branch children when admitting a branch by @BinSquare in #2205
- Share local images with managed Kubernetes and recover filesystem notifications by @BinSquare in #2219
- fix(engine): stop polling idle Docker event streams by @BinSquare in #2251
- fix(checkpoint): retain booted rootfs after app updates by @BinSquare in #2253
- Preserve container sessions and discover local apps by @BinSquare in #2254
- Build a restored checkpoint over the most similar tree the node has, not only a recorded ancestor by @BinSquare in #2255
- Clean up disconnected sessions when guest input is blocked by @BinSquare in #2256
- chore(nix): bump flake to 1.35.3 by @github-actions[bot] in #2249
- Add machine credentials refresh, which hands a running machine new credential values from this shell without a restart by @BinSquare in #2257
- Approve the Nix flake bump PR's held checks, so a release's bump can merge by @BinSquare in #2258
- Let the Nix package keep the guest rootfs's links, and build the flake in CI by @BinSquare in #2261
- Bump libkrun so a Windows guest rewrite keeps a file's owner and a share can serve a default owner by @BinSquare in #2262
- Let a host mount name the guest owner of its files (-v HOST:GUEST:uid=N[,gid=N]) by @BinSquare in #2260
- Keep pack and OCI layer extraction from touching anything outside the layer by @BinSquare in #2264
- Reuse a pack's extraction only for the artifact it came from, and key bundled libraries by SHA-256 by @BinSquare in #2266
- Load a pack's own libraries only when they came from the executable running by @BinSquare in #2267
- Serve only the host on the guest agent's vsock listeners by @BinSquare in #2268
- Keep host loopback closed to gateway flows under --block-private by @BinSquare in #2269
- Pin libkrun at the share-confinement fixes by @BinSquare in #2271
- Add on-demand SSH and SFTP for seamless environment access by @BinSquare in #2272
- Preserve image-backed containers across VM pause and resume by @BinSquare in #2274
- Expose checkpoint reader requirements before local offload by @BinSquare in #2277
- Keep pod volume copies private to the VMM and honor read-only volume mounts by @BinSquare in #2270
- Support POSIX ACLs on a machine's ext4 disks by @BinSquare in #2276
- Keep guest root ownership consistent across hosts by @BinSquare in #2279
- Preserve guest permissions when installing the runtime by @BinSquare in #2281
- Preserve PAX filenames and links containing newlines by @BinSquare in #2283
- Relocate checkpoint mounts without losing ownership by @BinSquare in #2284
- chore(nix): bump flake to 1.35.4 by @github-actions[bot] in #2263
- Preserve machine ownership across lifecycle and transfer operations by @BinSquare in #2289
- Preserve workload dependencies during transfers by @BinSquare in #2290
- Unpack image layers whose entries use absolute paths by @BinSquare in #2291
- Keep the vendored tar crate's lockfile out of git by @BinSquare in #2292
- Clear every networking request when machine update turns the network off by @BinSquare in #2307
- Keep artifacts from naming a host directory as their image by @BinSquare in #2302
- Match an IPv4-mapped IPv6 destination against the watchlist as its IPv4 form by @BinSquare in #2305
- Learn allowed addresses only from a successful answer to a plain DNS query by @BinSquare in #2306
- Floor multicast and reserved addresses under the private and strict egress floors by @BinSquare in #2304
- Hold a gateway flow to the full egress policy on the loopback address it reaches by @BinSquare in #2295
- Attach a restored checkpoint's host mounts only where the user names them by @BinSquare in #2301
- Give a pack entry its mode and owner where it landed, never through a link by @BinSquare in #2297
- Refuse a checkpoint disk listed as raw that is a qcow2 image by @BinSquare in #2299
- Attach a packed run's disks as raw instead of trusting their header by @BinSquare in #2293
- Refuse to attach a disk whose qcow2 header names another file by @BinSquare in #2296
- Attach the pod share to the sandbox VM read-only by @BinSquare in #2294
- Refuse a restored checkpoint's egress policy when its own entries reach the host by @BinSquare in #2300
- Preserve sparse disk copies and APFS archive holes by @BinSquare in #2310
- Bind workload previews to image and machine identities by @BinSquare in #2309
- Keep this host's registry logins out of pulls for an artifact-chosen image by @BinSquare in #2303
- Treat a branch or fork request's secret refs as untrusted, like every HTTP request by @BinSquare in #2311
- Refuse symlinks among a pack's or checkpoint's own files, and non-file objects on export by @BinSquare in #2313
- Recover container cleanup across workload transfer cancellation by @BinSquare in #2312
- Check that the bundled guest kernels are built with gcc by @josmo in #2308
- Bring the installer header, default memory text and docs/llms.txt up to date by @NickyHeC in #2273
- Fix the Windows native test build by @BinSquare in #2318
- Pin libkrun so branches are not charged twice for their base's untouched memory by @BinSquare in #2317
- Show a Windows interactive session's output without waiting for a keypress by @BinSquare in #2246
- Allow checkpoint restores to override egress policy by @NickyHeC in #2280
- Refuse API requests that web pages send from origins that are not allowed by @BinSquare in #2319
- Serve a packed machine's published ports without turning on egress by @BinSquare in #2320
- Present the restore's registry token only to registries the server is configured for by @BinSquare in #2321
- Check checkpoint lineage ids and tie restored trees to the checkpoint they came from by @BinSquare in #2322
- Fetch a run's image on the host instead of opening its registry to the workload by @BinSquare in #2323
- Run an init bake under the run's private-range floor and deny rules by @BinSquare in #2324
- Keep a machine's egress interceptor requirement across a checkpoint restore by @BinSquare in #2325
- Share a staged mount's host directory with the guest read-only by @BinSquare in #2326
- Mount a pod share nodev,nosuid so copied device nodes stay inert on the host by @BinSquare in #2331
- Have the boot helper refuse a boot config the launcher did not write by @BinSquare in #2330
- Rotate machine logs without following a link the machine directory's owner planted by @BinSquare in #2332
- Stage each agent rootfs install in a tree of its own by @BinSquare in #2328
- Read a fork disk chain's layer formats from what the host declared by @BinSquare in #2327
- Keep an in-guest pull's registry login in memory, never on the storage disk by @BinSquare in #2329
- Hold a reference's tag and registry host to the characters a registry URL allows by @BinSquare in #2333
- Serve a cached pack only to a caller the registry authorizes for that repository by @BinSquare in #2334
- Give API commands the secrets the machine's record grants, not a stale entry's by @BinSquare in #2335
- Floor the clouds' IPv6 metadata endpoints in every egress mode by @BinSquare in #2336
- Keep a registry's token realm and redirects off the host's own and private addresses by @BinSquare in #2337
- Contain Docker and OCI image archive references by @BinSquare in #2212
- Refuse a tenant image on a private registry, as a tenant registryRef already is by @BinSquare in #2338
- Accept a display WebSocket only from the display's own page by @BinSquare in #2340
- Refuse credential hosts a URL parser reads as an IPv4 address by @BinSquare in #2339
- Run image init without reading the host keyboard by @BinSquare in #2192
- Resume a paused machine on the same host without decoding its artifact by @BinSquare in #2085
- Let a machine whose guest cannot confirm shutdown still be deleted by @BinSquare in #2151
- Restore read-only checkpoint files from cloned cache entries by @BinSquare in #2217
- Name the OS error when a checkpoint or layer entry fails to unpack by @BinSquare in #2068
- Preserve Docker container filesystem lifetime by @BinSquare in #2213
- Follow a machine's shared pack pointer only to a shared extraction by @BinSquare in #2341
- Check a carried agent rootfs's digest before it reaches the store by @BinSquare in #2342
- Adopt only indexed checkpoint objects that hash to their names by @BinSquare in #2344
- Publish a pause's kept-resume record whole, so a resume never reads it half-written by @BinSquare in #2345
- Refuse a launch whose mount source now resolves to a protected path by @BinSquare in #2346
- Hand out a per-VM uid only once no process still runs as it by @BinSquare in #2347
- Keep per-machine ready markers out of the rootfs every guest shares by @BinSquare in #2350
- Revoke the share the host attached for a detached path, not the one the guest names by @BinSquare in #2343
- Walk a machine directory by descriptor when handing it to the VM's uid by @BinSquare in #2348
- Record the disk backings root attaches and report chains that name any other by @BinSquare in #2351
- Add and remove credential bindings on a running machine, with a name-constrained CA of its own for each new host by @BinSquare in #2265
- Reach the host's local services by default on your own computer by @BinSquare in #2352
- Prepare SmolVM v1.36.0 for release by @BinSquare in #2353
- Let embedders change a machine's credential bindings, and fix live trust for a new host by @BinSquare in #2356
New Contributors
- @rdslw made their first contribution in #2082
- @connorburgess made their first contribution in #2131
- @josmo made their first contribution in #2143
- @kumanday made their first contribution in #2112
- @Liamso made their first contribution in #2166
Full Changelog :
v1.34.0...v1.36.1 - A host bound live is trusted at once. In v1.36.0, adding a credential binding for a new host to a running machine (
-
🔗 Locklin on science Europe ain’t gonna make it rss
Living in the EU is wonderful. The food, the architecture, the scenery, the low levels of criminality, even the people are all a cut above anything in the homeland of the decaying empire. In almost every way the quality of life is better, and it costs less too. Even the physical condition of the people […]
-
🔗 HexRaysSA/plugin-repository commits sync repo: +1 plugin, +1 release rss
sync repo: +1 plugin, +1 release ## New plugins - [ida-ttd](https://github.com/hullabrian/ida-ttd) (1.0.0) -
🔗 Anton Zhiyanov Probabilistic data structures in Go, part 2 rss
Probabilistic data structures give you approximate answers to questions about the data they handle. Does the set contain a certain item? How many unique items are in the collection? What is the 99th percentile in a stream of numbers? How similar are two sets? Unlike deterministic structures, the answers might not be exact, but in return, you can save a lot of memory.
Previously, we reviewed the following data structures: Bloom filter (for checking if an item is in a set), Count-min sketch (for counting items), HyperLogLog (for counting unique items), T-digest (for finding quantiles), and Top-k (for finding the most frequent items).
In this post, we'll talk about other probabilistic structures and compare them to the ones we've already covered. We'll look at how they work and what kinds of guarantees they provide.
All examples use unsure — a package that implements these structures in Go.
Binary fuse filter • UltraLogLog • Log-linear histogram • MinHash
Binary fuse filter A binary fuse filter is a set that trades certainty for space, like a Bloom filter1. It can tell you that an item is definitely not in the set, or that it probably is (which might be a false positive). The filter doesn't store the items, so it's much more compact than a regular set. Unlike a Bloom filter, a binary fuse filter is static: you build it once from all the items, and you can't add more later. In exchange, it uses less memory than a Bloom filter with the same false positive rate. For example, a fuse filter for 1,000,000 items with a 0.39% false positive rate takes 1.13 MB (9 bits per item), while a Bloom filter takes 1.51 MB (12 bits per item). This makes binary fuse filters a good fit for data that is written once and read many times, like the key set of an immutable file in a database (to skip files that don't have the key), or a list of known bad items, such as leaked passwords or malicious URLs. items := [][]byte{[]byte("alice"), []byte("bob")} // An 8-bit filter: 0.39% false positive rate. filter := fuse.New, len(items)) filter.Contains([]byte("alice")) // true filter.Contains([]byte("carol")) // false (or, rarely, true) The fingerprint type (T in New[T]) determines the false positive rate and the memory use: Type | False positive rate | Bits per item ---|---|--- uint8 | 0.39% | 9 uint16 | 0.0015% | 18 uint32 | 2.3e-10 | 36 The constructor takes an iterator of items to add to the filter and the expected number of items (0 if unknown). The number is only used to preallocate memory, so a good estimate makes the build faster. You can check if an item is in the filter, but you cannot add or delete an item, count the number of items, or iterate over them. How it works
The filter2 is an array of b -bit fingerprints (for example, b = 8 for
uint8). Each item is hashed to a 64-bit value h , which gives the item's fingerprint f (b bits computed from h) and three positions in the array (cells). The array is filled so that for every item, the XOR of its cells equals f.┌──────┐ ┌──► f (b bits) item ──►│ hash │──► h ─────────┤ └──────┘ └──► i0, i1, i2 i0 i1 i2 ┌───┬───┬──▼──┬───┬───┬──▼──┬───┬──▼──┬───┐ │ │ │ F0 │ │ │ F1 │ │ F2 │ │ F0 ^ F1 ^ F2 == f └───┴───┴─────┴───┴───┴─────┴───┴─────┴───┘To check an item, you compute h, look up its three cells, and compare their XOR with f. For an item in the set, they always match. For any other item, the XOR is a random b-bit value, which matches f with probability 2^-b.
Each check reads three cells, so for large filters it's three cache misses, against one for a blocked Bloom filter. However, since the reads are independent, the CPU can do them concurrently, so the checks are about as fast as with a Bloom filter.
The filter uses the local wyhash3 implementation for hashing. It performs roughly the same as xxh34 but has a much simpler implementation, without SIMD or assembly.
Benchmarks
Here's an excerpt from the full benchmarks5, comparing unsure to xorfilter6 (binary fuse by the authors of the paper) and bloom (unsure 's own Bloom filter) with 8-bit fingerprints (ns/op, lower is better):
Operation | Items | unsure | xorfilter | bloom
---|---|---|---|---
Build (per item) | 10K | 23 | 25 | 13
| 1M | 30 | 31 | 12
Contains | 10K | 6.2 | 8.0 | 9.3
| 1M | 7.0 | 9.3 | 10.2
| 50M | 39 | 42 | 40Memory, bits per item (lower is better):
Items | Fingerprint | unsure | xorfilter | bloom
---|---|---|---|---
100K | 8-bit | 9.50 | 9.50 | 12.45
10M | 8-bit | 9.02 | 9.02 | 12.10
10M | 16-bit | 18.04 | 18.04 | 27.99Unsure is the same size as xorfilter (same layout) with up to 25% faster checks. Compared to the Bloom filter, it uses up to 36% less memory, with checks as fast or faster, but up to 2.5× slower builds.
-
Bloom filter overview and how it works. ↩︎
-
Binary Fuse Filters paper by Thomas Mueller Graf and Daniel Lemire, 2022. ↩︎
-
Reference wyhash implementation by Wang Yi. ↩︎
-
Reference xxHash implementation by Yann Collet. ↩︎
-
FastFilter/xorfilter by Daniel Lemire. ↩︎
UltraLogLog
UltraLogLog is a unique items counter that trades accuracy for space, like HyperLogLog7. It tells you approximately how many distinct items it has seen, no matter how many times each one appeared. UltraLogLog doesn't store the items, so it's much more compact than a regular set.
UltraLogLog is a newer design (Otmar Ertl, 2024) that uses the space more efficiently: for the same error, it needs about 43% less memory than HyperLogLog. For example, a HyperLogLog sketch with 0.81% standard error takes 16 KB, while an UltraLogLog sketch with 0.86% error takes 8 KB. However, adding, counting, and merging are slower than with HyperLogLog.
UltraLogLog is useful in the same places as HyperLogLog: counting unique visitors, unique search queries, or distinct values in a database column, possibly across many machines or segments.
// Standard error about 0.9% of the true count. sketch := ull.New() sketch.Add([]byte("alice")) sketch.Add([]byte("bob")) sketch.Add([]byte("alice")) sketch.Add([]byte("carol")) sketch.Count() // 3 (approximately)You can merge sketches to get the total number of unique items from all of them, without counting shared items twice.
home := ull.New() // visitors to the home page docs := ull.New() // visitors to the docs // ... home.Merge(docs) home.Count() // visitors to either pageThe sketch has one setting: the precision p , which gives a relative standard error of 0.782/√(2^p). The default is p=13 with 0.86% error in 8 KB, close to the common HyperLogLog default (0.81% in 16 KB).
You can add items to a sketch, get the estimated count, and merge sketches. You cannot check if a specific item was added, remove items, or list them.
How it works
HyperLogLog hashes each item and uses the first p bits of the hash to pick one of m = 2^p registers. It calculates the rank (the number of leading zeros in the rest of the hash, plus one) and keeps the highest rank it has seen in the register. Seeing a rank of k suggests there were about 2^k items in the register. The count is estimated from all the registers together.
p bits ┌──────┐ ┌──────────┬────────────────────────┐ item ──►│ hash │──►│ 01101001 │ 0001101... │ └──────┘ └────┬─────┴───────────┬────────────┘ │ register i └ rank = 3 zeros + 1 = 4 ┌───┬───┬───┬─▼─┬───┬───┬───┬───┬───┬───┐ registers │ 3 │ 0 │ 5 │ 2 │ 1 │ 0 │ 4 │ 2 │ 0 │ 1 │ 2 → 4 └───┴───┴───┴───┴───┴───┴───┴───┴───┴───┘A HyperLogLog register loses some information: it only keeps track of the highest value, not whether any slightly lower values were seen. These lower values show up at least as often as the highest one, so they can tell a lot about the count.
UltraLogLog8 uses the registers more efficiently. Each register is still one byte, but it stores the highest rank k in the upper 6 bits, and whether k−1 and k−2 were seen in the lower 2 bits:
k = 5 k-1 k-2 ┌───────────────┬───┬───┐ register │ 0 0 0 1 0 1 │ 1 │ 0 │ saw 5 and 4, but not 3 └───────────────┴───┴───┘ ┌───────────────┬───┬───┐ add k=6: │ 0 0 0 1 1 0 │ 1 │ 1 │ saw 6, 5, 4 └───────────────┴───┴───┘The count estimate uses the FGRA estimator from the UltraLogLog paper. Each register adds a weight based on its value, and the count is calculated as a power of the sum of the weights. Nearly empty and nearly full sketches get special handling, so the estimate stays accurate from zero to billions of items, without bias tables or a separate formula for small counts.
Unsure keeps a histogram of register values (256 four-byte counters, 1 KB) updated as the registers change. This way,
Countreads the histogram instead of scanning all the registers.Mergechecks 8 registers at a time using a few bitwise operations to find which ones the other sketch would change, and only updates those.The item is hashed once with wyhash , and the 64-bit hash is split into the register index and the rank.
Benchmarks
Here's an excerpt from the full benchmarks9, comparing UltraLogLog to unsure 's own HyperLogLog and axiom10 (HyperLogLog with LogLog-Beta estimator and sparse mode) (ns/op, lower is better):
Operation | p | Size | ull | hll | axiom
---|---|---|---|---|---
Add | 10 | 1 KB | 8.1 | 5.5 | 7.6
| 14 | 16 KB | 8.0 | 5.7 | 7.7
| 18 | 256 KB | 9.4 | 8.3 | 8.0
Count | 10 | 1 KB | 165 | 68 | 17,700
| 14 | 16 KB | 161 | 63 | 348,000
| 18 | 256 KB | 173 | 57 | 4,650,000
Merge | 10 | 1 KB | 2,900 | 720 | 1,740
| 14 | 16 KB | 51,200 | 20,200 | 58,500
| 18 | 256 KB | 818,000 | 341,000 | 955,000Accuracy and memory, relative RMSE over 1,000 sketches (lower is better):
Distinct items | ull p=13 | hll p=14 | axiom p=14
---|---|---|---
1,000 | 0.66% | 0.54% | 0.01%
40,000 | 0.73% | 0.68% | 0.69%
1,000,000 | 0.86% | 0.79% | 0.82%
Memory | 9.1 KB | 16.3 KB | 16.1 KBUltraLogLog provides the same accuracy as HyperLogLog with almost half the memory. However, adding, counting, and merging are noticeably slower.
-
HyperLogLog overview and how it works. ↩︎
-
UltraLogLog paper by Otmar Ertl, 2024. ↩︎
-
axiomhq/hyperloglog by Axiom. ↩︎
Log-linear histogram
A log-linear histogram is a summary of a stream of numbers that trades accuracy for space. It can give you an approximate median, 99th percentile, or any other quantile of the data. It can also estimate what fraction of the numbers are below a certain value (the CDF). The histogram doesn't store the numbers, so it's much more compact than a sorted list.
For example, to find the exact 99th percentile of 1,000,000 response times, you'd have to keep all of them. With 64-bit floats, that takes 8 MB. A log- linear histogram estimates the same percentile within 0.39% of its true value using about 14 KB — almost 600 times less.
The error is relative to the value: if the true 99th percentile is 200 ms, the histogram returns a value between 199.2 and 200.8 ms. This guarantee applies to every quantile, from the median to the most extreme outliers. The size of the histogram doesn't depend on the number of values, only on the accuracy you choose and on how wide the range of the values is.
A log-linear histogram is useful when you need percentiles for positive values that cover a wide range, like latencies, file sizes, or prices.
// Response times in milliseconds. hist := loghist.New() hist.Add(12.5) hist.Add(8.1) hist.Add(130.0) // ... hist.Quantile(0.5) // median hist.Quantile(0.99) // 99th percentile hist.CDF(100) // fraction of responses faster than 100 msYou can merge histograms to gather data from multiple machines or segments (like by hour, endpoint, or region). Merging is exact: a merged histogram is the same as if it had received all the values directly.
east := loghist.New() // latencies on one server west := loghist.New() // latencies on another // ... east.Merge(west) east.Quantile(0.99) // 99th percentile across both serversThe histogram has two settings: relative error and value range. By default, the error is 0.0039 (0.39%) and the range is from 1e-9 to 1e18. Lowering the error or increasing the range uses more memory.
You can add numbers to a histogram, estimate quantiles and the CDF, and merge histograms. You cannot remove numbers or list them.
How it works
A histogram splits the range of values into buckets and counts how many values are in each one. To estimate a quantile, it adds up the counts starting from the lowest bucket until it reaches the requested rank, then returns a value from that bucket. The accuracy of the estimate depends on how wide the bucket is.
With buckets that have equal widths, like 0–10, 10–20, and so on, every estimate has the same absolute error of ±5 around the bucket's midpoint. So the relative error is very large for small values and unnecessarily small for large values:
0 10 20 30 970 980 990 1000 ├───────┼───────┼───────┼─ ··· ─┼───────┼───────┼───────┤ └ 5 ± 5: ±100% 995 ± 5: ±0.5% ┘A logarithmic histogram solves this by making each bucket's width proportional to its value. For example, if the bucket boundaries are powers of 1.02 (1, 1.02, 1.0404, ...), the end of each bucket is 2% larger than its start, so any value in the bucket is within about 1% of the bucket's midpoint. DDSketch11 uses this method. The downside is that finding the right bucket for a value means you have to calculate a logarithm, which is relatively slow.
A log-linear histogram gets almost the same result with cheaper math. First, it splits the values into ranges between powers of two: 1–2, 2–4, 4–8, and so on (these are called octaves). Then it splits every octave into the same number of equal-width buckets. For example, here are three octaves with 4 buckets each:
1 2 4 8 ├─┬─┬─┬─┼───┬───┬───┬───┼───────┬───────┬───────┬───────┤ 4 buckets 4 buckets 4 bucketsEach octave is twice as long as the previous one, so its buckets are twice as wide, and the bucket width grows with the values, as in a logarithmic histogram. Finding the right bucket only takes a few bit operations instead of calculating a logarithm.
HdrHistogram12 is the best-known log- linear histogram. It records integers: the position of the highest 1 bit of a number determines its octave, and the next few bits determine the bucket within the octave.
Unsure works with float64 numbers and finds the bucket in a similar way to HdrHistogram.
IEEE 754 double-precision format
A float64 in Go (and most other languages) is made up of three parts:
- a sign bit,
- an 11-bit exponent e (stored as 1023 + e to avoid negative values),
- and a 52-bit mantissa f.
The number's value is 1.f × 2^e, where 1.f is a binary fraction between 1 and 2.
The exponent determines the octave, from 2^e to 2^(e+1). The top m bits of the mantissa determine one of the 2^m equal buckets within the octave.
For example, here's the number 5.25 with m=3 (8 buckets per octave). In binary, 5.25 = 1.0101₂ × 2², so the exponent is 2 (stored as 1025), and the mantissa starts with 0101:
5.25 = 1.0101₂ × 2² sign exponent top m rest of the mantissa ┌───┬─────────────┬─────┬─────────────────────────┐ │ 0 │ 10000000001 │ 010 │ 1000000000 ... 00000000 │ └───┴──────┬──────┴──┬──┴──┬──────────────────────┘ │ │ └── ignored │ └── bucket 2 of 8 └── 1025 = 2 + 1023: octave [4, 8) 4 8 ├───┬───┬───┬───┬───┬───┬───┬───┤ 0 1 2 3 4 5 6 7 └ 5.25 lands in bucket 2: [5, 5.5)Addfinds the bucket for the given number and increases the count.Mergeadds the counts bucket by bucket.Quantileadds up the counts from the closer end (the leftmost bucket for q ≤ 0.5, the rightmost bucket otherwise) until it reaches the rank.The number of mantissa bits m comes from the requested error: the constructor picks the smallest m for which the maximum error doesn't exceed the requested one. The default is m=7: 128 buckets per octave and an error of 0.39%.
Log-linear histogram vs. t-digest
A t-digest13 also estimates quantiles, but it limits the error in ranks :
Quantile(0.99)returns a value whose rank is close to 99%. A log-linear histogram limits the error in values :Quantile(0.99)returns a value close to the true 99th percentile.In the middle of the data, the two are pretty similar. But in a long tail, values at nearby ranks can be very different, so even a small error in rank can lead to a big difference in value. Here is the mean relative error of an 8.5 KB t-digest (δ=100) on 1M values from three distributions: lognormal (as in the benchmarks), Pareto with α=1.5 (a longer tail), and uniform between 1,000,000 and 2,000,000 (no tail):
Quantile | Lognormal | Pareto | Uniform
---|---|---|---
0.5 | 0.12% | 0.09% | 0.009%
0.99 | 1.7% | 5.6% | 0.015%
0.999 | 8.7% | 67% | 0.009%
0.9999 | 83% | 868% | 0.004%A log-linear histogram of about the same size (1% error, 8 KB) has an error below 0.78% for all these cases.
So a log-linear histogram is better for latencies, sizes, and other positive measurements with long tails. A t-digest is better when you need a fixed size no matter what the values are, or when the values can be arbitrarily close to zero.
Benchmarks
Here's an excerpt from the full benchmarks14, comparing unsure to hdr15 (log-linear, integers only, fixed range) and dd16 (DDSketch, logarithmic buckets) with a lognormal distribution (ns/op, lower is better):
Operation | Error | unsure | hdr | dd
---|---|---|---|---
Add | 1% | 4 | 4 | 19
| 0.4% | 4 | 4 | 19
| 0.1% | 4 | 4 | 19
Quantile | 1% | 48 | 283 | 1,750
| 0.4% | 90 | 1,708 | 3,100
| 0.1% | 337 | 1,712 | 11,967
Merge | 1% | 334 | 16,369 | 302
| 0.4% | 657 | 115,052 | 808
| 0.1% | 3,249 | 115,018 | 2,862Mean relative error at the requested 0.1%, over 1M values (lower is better):
Quantile | unsure | hdr | dd
---|---|---|---
0.5 | 0.033% | 0.033% | 0.050%
0.99 | 0.038% | 0.037% | 0.048%
0.999 | 0.027% | 0.019% | 0.039%
0.9999 | 0.016% | 0.002% | 0.025%Memory after adding 1M values (lower is better):
Error | unsure | hdr | dd
---|---|---|---
1% | 8 KB | 40 KB | 6 KB
0.4% | 14 KB | 264 KB | 13 KB
0.1% | 56 KB | 264 KB | 40 KBUnsure adds values as fast as hdr and 5× faster than dd , queries 5–19× faster than hdr and about 35× faster than dd , and merges about as fast as dd and 35–175× faster than hdr. It's slightly less accurate than hdr (using 5× less memory), and more accurate than dd (using 1.4× more memory).
-
DDSketch paper by Charles Masson et al., 2019. ↩︎
-
HdrHistogram by Gil Tene. ↩︎
-
T-digest overview and how it works. ↩︎
-
HdrHistogram/hdrhistogram-go by Coda Hale. ↩︎
-
DataDog/sketches-go by Datadog. ↩︎
MinHash
MinHash estimates how similar two sets are. It summarizes each set in a short fixed-size signature (for example, 256 numbers). Comparing two signatures gives the approximate Jaccard similarity of the sets: |A∩B| / |A∪B|, the proportion of unique items that both sets share.
The size of a signature doesn't depend on the size of the set, so you can compare two sets of a million items each just by comparing 256 pairs of numbers instead of checking every item. Plus, each set's signature is only calculated once, so comparing lots of sets to each other is relatively cheap.
MinHash is useful for finding near-duplicate documents, like web pages or essays (represented as sets of words or 3-word phrases). It's also useful for finding similar user profiles (as sets of liked items) or overlapping datasets (as sets of keys).
// Two documents as sets of words. strA := "the quick brown fox jumps over the lazy dog" docA := minhash.New(256) for w := range strings.FieldsSeq(strA) { docA.Add([]byte(w)) } strB := "the quick brown cat jumps over the lazy dog" docB := minhash.New(256) for w := range strings.FieldsSeq(strB) { docB.Add([]byte(w)) } sigA, sigB := docA.Signature(), docB.Signature() sigA.Similarity(sigB) // 0.75 (true value 7/9 = 0.78)The MinHash sketch has one setting: the signature size k , which gives a standard error of √(J(1−J)/k) for true similarity J. For example, with k=256 and J=0.5:
- 68% of estimates are within ±3.1 pp of J (0.47–0.53),
- 95% within ±6.2 pp (2·stdErr),
- 99.7% within ±9.4 pp (3·stdErr).
You can add items to a sketch, merge sketches, and get and compare signatures. You cannot check if a specific item was added, count the items, remove them, or list them.
How it works
Classic MinHash17 hashes every item with k different hash functions. Here are two sets, A = {fox, cat, dog, owl} and B = {fox, dog, emu}, and their item hashes for k=4:
item h1 h2 h3 h4 in A in B fox 0.07 0.52 0.66 0.38 ✓ ✓ cat 0.21 0.15 0.80 0.91 ✓ dog 0.48 0.33 0.09 0.74 ✓ ✓ emu 0.63 0.27 0.44 0.12 ✓ owl 0.90 0.71 0.58 0.29 ✓For each hash function, the set keeps only the smallest hash value among its items. These k minimums are the set's signature. To estimate the similarity of two sets, compare their signatures position by position, count the number of equal values, and divide by k:
h1 h2 h3 h4 A signature 0.07 0.15 0.09 0.29 B signature 0.07 0.27 0.09 0.12 equal ✓ ✓ → 2 of 4 = 0.5The estimated similarity (0.5) is different from the actual value (2 shared items / 5 distinct items = 0.4). To get a more accurate estimate, k is usually much larger than in this example.
One permutation hashing18 hashes every item once, with a single hash function, and splits the range of hash values into k equal buckets. Each bucket keeps the smallest hash value among its items. Here are the same sets with k=4, using h1 from above:
bucket 0 1 2 3 range 0.00–0.25 0.25–0.50 0.50–0.75 0.75–1.00 A items fox 0.07 dog 0.48 owl 0.90 cat 0.21 B items fox 0.07 dog 0.48 emu 0.63 A minimums 0.07 0.48 · 0.90 B minimums 0.07 0.48 0.63 ·Each bucket works like a separate MinHash over the items in its range. So the bucket minimums form a signature, and comparing two signatures works the same way. But there is a catch: when a set isn't much larger than k, some buckets end up empty (shown as · above), so there's nothing to compare in them.
Optimal densification19 solves this by filling each empty bucket with the value from another bucket in the same set. Each empty bucket tries other buckets in a pseudo-random order and copies the value of the first non-empty one:
bucket 0 1 2 3 A minimums 0.07 0.48 · 0.90 B minimums 0.07 0.48 0.63 · A signature 0.07 0.48 0.90 (3) 0.90 B signature 0.07 0.48 0.63 │ 0.07 (0) equal ✓ ✓ │ │ → 2 of 4 = 0.5 │ │ │ │ which bucket the value was copied fromThis order depends only on the empty bucket's position, so two similar sets tend to fill empty spots with the same values. This makes the estimate work for sets of any size, with about the same error as classic MinHash.
Unsure keeps the k bucket minimums in the sketch.
AddandMergeuse the original buckets. Densification only happens inSignature, and it makes a copy of the buckets without modifying the sketch.Each item is hashed once with 64-bit wyhash. Multiplying the hash by k once gives both the bucket and the value to store:
┌─────────────────┬─────────────────┬─────────────────┐ │ high 64 bits: │ next 32 bits: │ rest: │ │ bucket in [0,k) │ value │ unused │ └─────────────────┴─────────────────┴─────────────────┘ 127 64 32 0Densification fills empty buckets in a coordinated way, spreading the copies evenly across the non-empty buckets. This keeps the error close to classic MinHash, and makes densification fast even for small sets.
Benchmarks
Here's an excerpt from the full benchmarks20, comparing unsure to dgryski21 (classic MinHash) (ns/op, lower is better):
Operation | k | unsure | dgryski
---|---|---|---
Add | 64 | 5 | 30
| 256 | 5 | 115
| 1024 | 5 | 358
Similarity | 64 | 25 | 24
| 256 | 104 | 103
| 1024 | 378 | 376RMSE of the similarity estimate at k=256 and J=0.5 (lower is better):
Distinct items | unsure | dgryski
---|---|---
256 | 2.89% | 3.07%
1,024 | 2.84% | 3.12%
4,096 | 2.99% | 3.09%
16,384 | 3.11% | 3.07%
Memory | 1.0 KB | 2.0 KBUnsure adds items 6–70× faster than dgryski , compares signatures at the same speed, has roughly the same accuracy, and uses half the memory.
-
Classic MinHash paper by Andrei Broder, 1997. ↩︎
-
One permutation hashing by Ping Li et al., 2012. ↩︎
-
Optimal densification paper by Anshumali Shrivastava, 2017. ↩︎
-
dgryski/go-minhash by Damian Gryski. ↩︎
Wrapping up
Bloom filter and HyperLogLog are everyone's favorites, but they're not the only useful probabilistic data structures out there. In some situations, you might find these helpful:
- Binary fuse filter is a more compact alternative to a Bloom filter when you know all the items in advance.
- UltraLogLog is a more compact (but slower) alternative to HyperLogLog.
- Log-linear histogram is a much more accurate alternative to t-digest (with a variable size).
- MinHash compares large sets for similarity using a tiny fixed-size signature.
To use them in Go, try the __nalgeon/unsure package:
go get github.com/nalgeon/unsure -
-
🔗 HexRaysSA/plugin-repository commits Update known-repositories.txt rss
Update known-repositories.txt -
🔗 smol-machines/smolvm smolvm v1.36.0 release
Behavior changes
These now refuse things earlier versions accepted. Each one closes a way for a guest, a pack or a checkpoint to reach the host.
- A restored checkpoint's host mounts attach only where you name them with
-v(#2301). A checkpoint no longer chooses which host directories its guest gets. - A restored checkpoint's own egress entries cannot re-open host loopback or cloud metadata (#2300). Restore with an egress policy of your own if you need one.
- Branch and fork requests over the HTTP API cannot name host env vars or files as secrets (#2311).
- An artifact-chosen image pulls without this host's saved registry logins (#2303). Pass credentials explicitly for a private image a pack or checkpoint names.
- Disk headers are checked: a packed run's disks attach as raw (#2293), a
--diskqcow2 that names another file is refused (#2296), and a checkpoint disk listed as raw that is really qcow2 is refused (#2299). - Packs and checkpoints cannot carry links among their own files (#2313, #2297), and an artifact cannot name a host directory as its image (#2302).
- Egress: a gateway flow is held to the machine's full policy (#2295),
--block-privateand the strict floor also cover multicast and reserved ranges (#2304), allowed addresses are learned only from successful plain DNS answers (#2306), and IPv4-mapped IPv6 destinations match the watchlist (#2305). - Host loopback on your own computer works as before: a machine reaches the services you run on your Mac or Linux box (
127.0.0.1, via its gateway orhost.docker.internal), as under Docker.--deny-cidr 127.0.0.0/8or--block-privatecloses it. A machine with an allow-list reaches loopback only through a CIDR it names, and cloud workers never allow it (#2352). machine update --no-netalso clears block-private, the guest subnet, a named network and credential bindings (#2307).
New
- Add and remove credential bindings on a running machine (
smolvm machine credentials add|remove,PUT /api/v1/machines/{id}/credential-bindings). A binding for a new host gets its own name-constrained CA, trusted by the guest at once (#2265).
Fixes
- Branches no longer pay twice for their base's untouched memory (libkrun #272, #2317). A branch touching memory its base never used was charged for a shared page and a private copy, and grew the base. That pushed CI runners and branch sources past their memory limits.
- Sparse disk copies and APFS archive holes are preserved; container cleanup recovers across a cancelled workload transfer; a Windows interactive session shows output without waiting for a keypress (#2246).
What's Changed
- docs: say that virtiofs DAX is off on arm64 hosts and SMOLVM_MOUNT_DAX does nothing there by @BinSquare in #2087
- Add smolvm docker: one command starts a Docker engine in a managed machine and points docker at it by @BinSquare in #2089
- Share the home directory with the smolvm docker machine at the same path by @BinSquare in #2090
- Resolve host.docker.internal to the host from smolvm docker containers by @BinSquare in #2091
- Fix a port race in the leader-exit test by @BinSquare in #2096
- Remove smolvm docker by @BinSquare in #2095
- Hand supplied credential values to a running embedded machine at once by @BinSquare in #2097
- Pin libkrunfw with UDP kept inside a TSI guest, and test it by @BinSquare in #2099
- Publish ports below 1024 on macOS, add IPv6 loopback to live-forwarded ports, and lift the 64-mapping cap by @BinSquare in #2092
- Return idle guest memory to the host within two minutes and cap new machines at half the host's RAM by @BinSquare in #2094
- Install a root-owned agent-rootfs when root runs install.sh by @rdslw in #2082
- Announce a changed file to the guest once per change by @BinSquare in #2102
- Answer guest DNS from a host cache that coalesces bursts and resends lost queries by @BinSquare in #2098
- Keep every disk chain under the branch depth limit: fold restored checkpoint layers and frozen-source chains by @BinSquare in #2103
- Exec sessions: commands the node owns, resumable after a dropped connection by @BinSquare in #2101
- Let a guest hold tens of thousands of connections on virtio-net and free their host sockets promptly by @BinSquare in #2104
- Scope the usage journal to the test's own thread by @BinSquare in #2106
- Pin libkrun 526be460 and libkrunfw f290c62b, rebuilt for every platform by @BinSquare in #2109
- Build the agent rootfs as non-root on hosts with user namespaces again by @BinSquare in #2107
- Answer a start missing the mediated interceptor with 400, not 500 by @BinSquare in #2108
- Run tests that need a released file lock free at once in their own process by @BinSquare in #2110
- Pin libkrun 9df62257 and libkrunfw 7f4d4950, rebuilt for every platform by @BinSquare in #2113
- Stop resetting virtio-net connections a server closes first by @BinSquare in #2118
- Upgrade rusqlite to 0.41 for the patched bundled SQLite (RUSTSEC-2026-0459) by @BinSquare in #2128
- Keep a host memory reserve VMs cannot take and charge branch children for growth by @BinSquare in #2127
- Ask before stopping a machine on delete, so a refused or declined delete leaves it running by @connorburgess in #2131
- Prepare SmolVM v1.34.1 for release by @BinSquare in #2135
- Bring a soft open-file limit above kern.maxfilesperproc down to the cap on macOS, so the limit raise_nofile_limit reports is the one in force by @connorburgess in #2132
- Leave no data directory behind when exec, status or stop name a machine that does not exist by @connorburgess in #2129
- Warn when --block-private keeps a named host unreachable by @BinSquare in #2146
- Register Rosetta itself as the x86_64 interpreter when the host answers its start-up ioctl by @BinSquare in #2148
- Make a mounted host directory belong to the workload user so a non-root workload can write to it by @BinSquare in #2149
- Record the image platform on the machine so a Rosetta machine can be created from an amd64 image by @BinSquare in #2147
- Bump libkrun so a Rosetta machine runs amd64 programs directly and a macOS machine stops promptly by @BinSquare in #2150
- Keep a cache disk's chain on its shared base when compaction shortens it by @BinSquare in #2145
- Satisfy Rust 1.100's needless_bool lint in connect_in_progress on Windows by @BinSquare in #2154
- Bound branch admission and reported capacity by the VM slice's memory limit, not just host free memory by @BinSquare in #2152
- Stop throttling the VM slice and reclaim it from the pressure guard instead by @BinSquare in #2153
- Release a paused branch child's VM lock so the memory pressure guard can resume it by @BinSquare in #2157
- Keep a restored machine's local image on its storage disk instead of mounting the capturing host's archive by @BinSquare in #2163
- Update quinn-udp to 0.5.16 for RUSTSEC-2026-0538 by @BinSquare in #2165
- Count every symlink with one mode in the agent rootfs digest so a Mac checkpoint restores on Linux by @BinSquare in #2162
- Carry guest traffic in 64 KB frames over the gateway link so downloads use a quarter of the CPU by @BinSquare in #2168
- Pin libkrun 518949b4 and libkrunfw 0fae3853, rebuilt for every platform by @BinSquare in #2169
- Reserve tmpfs for concurrent RAM captures and sweep abandoned checkpoint scratch at serve start by @BinSquare in #2173
- Let a packed image's branch take the deferred checkpoint save and say when the VM died mid-save by @BinSquare in #2174
- Integrate and validate Docker Engine, automatic ports, and nested Rosetta support by @BinSquare in #2172
- Run x86_64 images in containers Docker starts inside a Rosetta machine, keeping their PID by @BinSquare in #2093
- Serve the Docker Engine API from smolvm, every container a machine by @BinSquare in #2114
- Publish the ports a machine starts listening on, with --auto-ports by @BinSquare in #2136
- Give engine containers user-defined networks, so Docker Compose stacks run by @BinSquare in #2115
- Let engine containers reach the Docker socket, so Testcontainers and Dev Containers work by @BinSquare in #2116
- Branch engine containers from a warm base when many of one image run by @BinSquare in #2117
- Publish engine container ports on the address each one names by @BinSquare in #2119
- Give engine containers a volume for each VOLUME their image declares by @BinSquare in #2120
- Move images in and out of the engine: save, load, push, commit, import, export by @BinSquare in #2121
- Run --network container: containers in that container's machine by @BinSquare in #2122
- Give engine networks IPv6 by @BinSquare in #2123
- Run the Docker API on demand with independent workload supervisors by @BinSquare in #2175
- Fix Buildx volume permissions and macOS restart stalls by @BinSquare in #2178
- Improve default macOS shared-volume write performance by @BinSquare in #2179
- engine: speed up macOS Buildx with automatic overlayfs snapshots by @BinSquare in #2181
- Run the guest keep-alive init as root while workloads and execs keep the image user and its supplementary groups. by @BinSquare in #2004
- engine: fix multi-stage Buildx builds containing deleted files by @BinSquare in #2183
- Scrub injected credential values from what a credential host sends back by @BinSquare in #2180
- Re-authorize a restored checkpoint's credential bindings from the CLI, and refuse a start that could not inject them by @BinSquare in #2182
- Sweep a deleted machine's pause-operation lock along with its fork-operation lock by @connorburgess in #2184
- Let machine update set and remove labels, in any machine state by @josmo in #2143
- Leave the Docker Engine API opt-in so installing or upgrading smolvm never switches the user's Docker context by @BinSquare in #2186
- Bump every workspace crate and the nix flake to 1.35.0 by @BinSquare in #2185
- fix(network): retain OS-allocated local TCP listeners by @kumanday in #2112
- Retry a checkpoint part the object store refuses with a transient error by @BinSquare in #2191
- fix(shim): preserve foreground helper exit statuses by @hfiguera in #2190
- Delete the image seed builder when a CLI start is interrupted, and reap builders whose owner exited (#2083) by @rdslw in #2188
- Honor SMOLVM_DATA_DIR and --state-dir on macOS by @BinSquare in #2193
- Map a mounted host directory to the workload user again, not the keep-alive init's root, so a non-root workload can write to it by @josmo in #2189
- Open the Nix flake bump from main and run its required attribution check, so the bump PR can merge by @BinSquare in #2194
- Bind the port forward tests' ports before using them, instead of picking a free port and binding it again later by @BinSquare in #2195
- engine: use an on-demand native Buildx builder by @BinSquare in #2196
- perf(engine): reduce container lifecycle overhead by @BinSquare in #2198
- perf(engine): improve streaming output throughput by @BinSquare in #2200
- perf(engine): bound log tail reads and stream binary payloads by @BinSquare in #2201
- Compile the auto ports test's port helper only on Unix, where its one caller runs by @BinSquare in #2199
- Keep an image's files under /run when a container starts by @BinSquare in #2203
- Leave the Docker context alone when an engine with its own state directory is set up, and remove its registration by name by @BinSquare in #2202
- Stop a workload supervisor on SIGTERM and when its engine state is deleted, whoever holds the warm base lock by @BinSquare in #2204
- Start a display without a host GPU, check the host GPU before a --gpu start, and finish stop and delete around a process the kernel will not let exit by @BinSquare in #2210
- Allow ARM cloud checkpoints to return to macOS by @BinSquare in #2216
- Refuse a staged sync entry whose parent leads outside the mount through a symlink, so a guest cannot delete host files by @BinSquare in #2242
- Serve at most eight workload log connections, closing the oldest, so a guest cannot exhaust host threads by @BinSquare in #2243
- Bump libkrun so a resumed macOS machine releases the memory its guest frees and keeps it out of checkpoints by @BinSquare in #2244
- Trim the guest's disks before a capture, so deleted files leave the checkpoint and the host disk by @BinSquare in #2245
- Forget a host's learned addresses when a running machine's allow list is left with no hosts by @josmo in #2142
- Point exec and cp on a paused machine at resume, not at a start that refuses it by @connorburgess in #2167
- Bump libkrun so restored macOS machines keep later writes in checkpoints and qcow2 discards free host disk space by @BinSquare in #2248
- Preserve local-image machines across export and restore by @Vishv07 in #1980
- Preserve packed network restrictions and apply overrides atomically by @Vishv07 in #2006
- Clone the case-sensitive layers image instead of formatting a new one by @BABTUNA in #1713
- Preserve staged files when an interactive output pipe closes by @connorburgess in #2164
- Diagnose unsupported macOS virtualization without masking other failures by @Bnjoroge1 in #1323
- Allow disk growth before first boot by @BinSquare in #2211
- Expose machine files and harden engine storage workflows by @BinSquare in #2206
- Close failed port-forward tunnels and reap reply readers by @BinSquare in #2214
- Fix Docker container name filtering by @BinSquare in #2225
- Speed up and isolate first-use disk template expansion by @BinSquare in #2229
- Fix Docker networking and persistent VM lifecycle by @BinSquare in #2234
- Serialize overlay remounts so concurrent prepares don't race by @Liamso in #2166
- Fix interactive stream stalls and idle wakeups by @BinSquare in #2250
- Report Docker container resources from guest kernel accounting by @BinSquare in #2228
- Preserve image index digests for Docker image lookup by @BinSquare in #2224
- Hold back the growth already promised to running branch children when admitting a branch by @BinSquare in #2205
- Share local images with managed Kubernetes and recover filesystem notifications by @BinSquare in #2219
- fix(engine): stop polling idle Docker event streams by @BinSquare in #2251
- fix(checkpoint): retain booted rootfs after app updates by @BinSquare in #2253
- Preserve container sessions and discover local apps by @BinSquare in #2254
- Build a restored checkpoint over the most similar tree the node has, not only a recorded ancestor by @BinSquare in #2255
- Clean up disconnected sessions when guest input is blocked by @BinSquare in #2256
- chore(nix): bump flake to 1.35.3 by @github-actions[bot] in #2249
- Add machine credentials refresh, which hands a running machine new credential values from this shell without a restart by @BinSquare in #2257
- Approve the Nix flake bump PR's held checks, so a release's bump can merge by @BinSquare in #2258
- Let the Nix package keep the guest rootfs's links, and build the flake in CI by @BinSquare in #2261
- Bump libkrun so a Windows guest rewrite keeps a file's owner and a share can serve a default owner by @BinSquare in #2262
- Let a host mount name the guest owner of its files (-v HOST:GUEST:uid=N[,gid=N]) by @BinSquare in #2260
- Keep pack and OCI layer extraction from touching anything outside the layer by @BinSquare in #2264
- Reuse a pack's extraction only for the artifact it came from, and key bundled libraries by SHA-256 by @BinSquare in #2266
- Load a pack's own libraries only when they came from the executable running by @BinSquare in #2267
- Serve only the host on the guest agent's vsock listeners by @BinSquare in #2268
- Keep host loopback closed to gateway flows under --block-private by @BinSquare in #2269
- Pin libkrun at the share-confinement fixes by @BinSquare in #2271
- Add on-demand SSH and SFTP for seamless environment access by @BinSquare in #2272
- Preserve image-backed containers across VM pause and resume by @BinSquare in #2274
- Expose checkpoint reader requirements before local offload by @BinSquare in #2277
- Keep pod volume copies private to the VMM and honor read-only volume mounts by @BinSquare in #2270
- Support POSIX ACLs on a machine's ext4 disks by @BinSquare in #2276
- Keep guest root ownership consistent across hosts by @BinSquare in #2279
- Preserve guest permissions when installing the runtime by @BinSquare in #2281
- Preserve PAX filenames and links containing newlines by @BinSquare in #2283
- Relocate checkpoint mounts without losing ownership by @BinSquare in #2284
- chore(nix): bump flake to 1.35.4 by @github-actions[bot] in #2263
- Preserve machine ownership across lifecycle and transfer operations by @BinSquare in #2289
- Preserve workload dependencies during transfers by @BinSquare in #2290
- Unpack image layers whose entries use absolute paths by @BinSquare in #2291
- Keep the vendored tar crate's lockfile out of git by @BinSquare in #2292
- Clear every networking request when machine update turns the network off by @BinSquare in #2307
- Keep artifacts from naming a host directory as their image by @BinSquare in #2302
- Match an IPv4-mapped IPv6 destination against the watchlist as its IPv4 form by @BinSquare in #2305
- Learn allowed addresses only from a successful answer to a plain DNS query by @BinSquare in #2306
- Floor multicast and reserved addresses under the private and strict egress floors by @BinSquare in #2304
- Hold a gateway flow to the full egress policy on the loopback address it reaches by @BinSquare in #2295
- Attach a restored checkpoint's host mounts only where the user names them by @BinSquare in #2301
- Give a pack entry its mode and owner where it landed, never through a link by @BinSquare in #2297
- Refuse a checkpoint disk listed as raw that is a qcow2 image by @BinSquare in #2299
- Attach a packed run's disks as raw instead of trusting their header by @BinSquare in #2293
- Refuse to attach a disk whose qcow2 header names another file by @BinSquare in #2296
- Attach the pod share to the sandbox VM read-only by @BinSquare in #2294
- Refuse a restored checkpoint's egress policy when its own entries reach the host by @BinSquare in #2300
- Preserve sparse disk copies and APFS archive holes by @BinSquare in #2310
- Bind workload previews to image and machine identities by @BinSquare in #2309
- Keep this host's registry logins out of pulls for an artifact-chosen image by @BinSquare in #2303
- Treat a branch or fork request's secret refs as untrusted, like every HTTP request by @BinSquare in #2311
- Refuse symlinks among a pack's or checkpoint's own files, and non-file objects on export by @BinSquare in #2313
- Recover container cleanup across workload transfer cancellation by @BinSquare in #2312
- Check that the bundled guest kernels are built with gcc by @josmo in #2308
- Bring the installer header, default memory text and docs/llms.txt up to date by @NickyHeC in #2273
- Fix the Windows native test build by @BinSquare in #2318
- Pin libkrun so branches are not charged twice for their base's untouched memory by @BinSquare in #2317
- Show a Windows interactive session's output without waiting for a keypress by @BinSquare in #2246
- Allow checkpoint restores to override egress policy by @NickyHeC in #2280
- Refuse API requests that web pages send from origins that are not allowed by @BinSquare in #2319
- Serve a packed machine's published ports without turning on egress by @BinSquare in #2320
- Present the restore's registry token only to registries the server is configured for by @BinSquare in #2321
- Check checkpoint lineage ids and tie restored trees to the checkpoint they came from by @BinSquare in #2322
- Fetch a run's image on the host instead of opening its registry to the workload by @BinSquare in #2323
- Run an init bake under the run's private-range floor and deny rules by @BinSquare in #2324
- Keep a machine's egress interceptor requirement across a checkpoint restore by @BinSquare in #2325
- Share a staged mount's host directory with the guest read-only by @BinSquare in #2326
- Mount a pod share nodev,nosuid so copied device nodes stay inert on the host by @BinSquare in #2331
- Have the boot helper refuse a boot config the launcher did not write by @BinSquare in #2330
- Rotate machine logs without following a link the machine directory's owner planted by @BinSquare in #2332
- Stage each agent rootfs install in a tree of its own by @BinSquare in #2328
- Read a fork disk chain's layer formats from what the host declared by @BinSquare in #2327
- Keep an in-guest pull's registry login in memory, never on the storage disk by @BinSquare in #2329
- Hold a reference's tag and registry host to the characters a registry URL allows by @BinSquare in #2333
- Serve a cached pack only to a caller the registry authorizes for that repository by @BinSquare in #2334
- Give API commands the secrets the machine's record grants, not a stale entry's by @BinSquare in #2335
- Floor the clouds' IPv6 metadata endpoints in every egress mode by @BinSquare in #2336
- Keep a registry's token realm and redirects off the host's own and private addresses by @BinSquare in #2337
- Contain Docker and OCI image archive references by @BinSquare in #2212
- Refuse a tenant image on a private registry, as a tenant registryRef already is by @BinSquare in #2338
- Accept a display WebSocket only from the display's own page by @BinSquare in #2340
- Refuse credential hosts a URL parser reads as an IPv4 address by @BinSquare in #2339
- Run image init without reading the host keyboard by @BinSquare in #2192
- Resume a paused machine on the same host without decoding its artifact by @BinSquare in #2085
- Let a machine whose guest cannot confirm shutdown still be deleted by @BinSquare in #2151
- Restore read-only checkpoint files from cloned cache entries by @BinSquare in #2217
- Name the OS error when a checkpoint or layer entry fails to unpack by @BinSquare in #2068
- Preserve Docker container filesystem lifetime by @BinSquare in #2213
- Follow a machine's shared pack pointer only to a shared extraction by @BinSquare in #2341
- Check a carried agent rootfs's digest before it reaches the store by @BinSquare in #2342
- Adopt only indexed checkpoint objects that hash to their names by @BinSquare in #2344
- Publish a pause's kept-resume record whole, so a resume never reads it half-written by @BinSquare in #2345
- Refuse a launch whose mount source now resolves to a protected path by @BinSquare in #2346
- Hand out a per-VM uid only once no process still runs as it by @BinSquare in #2347
- Keep per-machine ready markers out of the rootfs every guest shares by @BinSquare in #2350
- Revoke the share the host attached for a detached path, not the one the guest names by @BinSquare in #2343
- Walk a machine directory by descriptor when handing it to the VM's uid by @BinSquare in #2348
- Record the disk backings root attaches and report chains that name any other by @BinSquare in #2351
- Add and remove credential bindings on a running machine, with a name-constrained CA of its own for each new host by @BinSquare in #2265
- Reach the host's local services by default on your own computer by @BinSquare in #2352
New Contributors
- @rdslw made their first contribution in #2082
- @connorburgess made their first contribution in #2131
- @josmo made their first contribution in #2143
- @kumanday made their first contribution in #2112
- @Liamso made their first contribution in #2166
Full Changelog :
v1.34.0...v1.36.0 - A restored checkpoint's host mounts attach only where you name them with
-
🔗 HexRaysSA/plugin-repository commits sync repo: +5 releases, -2 releases rss
sync repo: +5 releases, -2 releases ## New releases - [btf2ida](https://github.com/nightshift-labs-ai/btf2ida): 0.1.25 - [cfiscope](https://github.com/nightshift-labs-ai/cfiscope): 0.1.24 - [llm-explainer](https://github.com/pgarba/ida-llm-explainer): 1.16.0, 1.15.0 - [memlens](https://github.com/nightshift-labs-ai/memlens): 0.3.32 ## Changes - [btf2ida](https://github.com/nightshift-labs-ai/btf2ida): - removed version(s): 0.1.1 - [memlens](https://github.com/nightshift-labs-ai/memlens): - removed version(s): 0.3.7 -
🔗 Ampcode News Puck in the Car rss
You can now talk to Puck in your car, so you can work more safely while driving without looking at a screen. In the rare case that you do need to look at something, it's displayed very big so a quick glance is enough.
The Amp apps for iPhone and Android will automatically enter car mode if you use them there.
If you have a Tesla or any other device that can browse the web in your car, open ampcode.com/car.
(If you have kids in the car, they might enjoy throwing Puck in the air. Puck likes this.)
See more in the Puck in the Car docs.
-
- November 20, 2026
-
🔗 IDA Plugin Updates IDA Plugin Updates on 2026-11-20 rss
IDA Plugin Updates on 2026-11-20
New Releases:
- ida-llm-explainer v1.15.0 — agent server: IDA 9.4/9.5 fixes + type-work tools
- ida-llm-explainer v1.16.0 — task agent: autonomous goal-driven reverse engineering
Activity:
- augur
- haruspex
- plugin-ida
- 79c01c22: fix: clean up Docker test stacks and volumes (#44)
- rhabdomancer
-
🔗 MetaBrainz State of MetaBrainz 2026 rss
I joined MetaBrainz as Executive Director in August this year, 7 months after we lost Rob. This is the written summary of the talk I gave at our October summit in Barcelona: where we stand, what worries me, and what I plan to do in 2027.
A year of loss, and what held
Losing Rob this year touches everything in this report. What I want to recognize is how people responded:
- The team kept the lights on and the engines running.
- The community kept editing, even through the outages.
- The board focused on funding so we could keep going.
I wasn't here yet for most of that, so the credit belongs to all of you.
Who I am
I started in August, and I've spent the months since learning how everything works. My first focus is infrastructure and the funding it requires. My second is raising money more broadly.
I've worked in open data, open standards and open source since 2004, mostly in open government. I care a great deal about privacy: I served on the board of EFF-Austin for 12 years and was a legislative liaison for the ACLU on technical issues. I also have a background in AI, which I know is a sore subject here but this means I can help. I have always fought for artists and creators, and I think you'll find we're in sync on the realities we face.
The money
At the time of the summit, income for 2026 stood at 300K, which put us 55K behind for this time of year. We normally bring in about 400K a year, and Nicolás (reosarevok) and I think we can still get there by year-end. But because of increased infrastructure costs we still have a shortfall for this year.
What has been done:
- The board has spent the year renewing supporter contracts.
- We are creating new kinds of contracts, because ListenBrainz is used very differently from MusicBrainz and our existing tiers don't fit.
- I've been researching what comparable data sells for. The finding: our top tier is the industry standard price. Every tier below it is priced well under that, on purpose, to support small businesses and independent creators.
What is pushing costs up:
- Infrastructure. AI agent traffic means we need more capacity, and AI demand has raised hardware and networking prices.
- The summit. Flights cost about three times what they did, especially from the United States.
We are also building a CRM using Twenty, which is open source and self-hosted. It brings together what lives on our website and in our accounting, helps us track privacy requests, and lets us send fewer routine emails and more useful ones, such as yearly tax letters to donors.
The CRM matters for a reason specific to US nonprofits: we have to show the IRS that our support comes from a broad public, and individual donations count toward that. It is also what lets us write to our users to ask for support, which we are planning on doing for the first time soon.
The team
This is my view as the new person, not a measurement.
What I see is an extraordinarily dedicated group. It's why I took this job: I wanted to work with data nerds. The volunteer engagement is remarkable, from the userscripts and apps people have built to the number of edits made through thick and thin. The team is self-motivated and self-organizing. Everyone wants to carry Rob's legacy forward, and I am in awe of that.
I also see that people are tired, and I'm worried about burnout.
- Too many roles are unfilled. Teams of one or two people are not enough.
- Coordination could be better, which is why we worked on leads and roles at the summit.
- Our infrastructure needs serious attention. With it in better shape, we'd be more comfortable opening up to outside contributions.
Fixing this takes money, which is why so much of this post is about funding.
2027
I'm preparing two budgets for the board.
The conservative budget covers:
- Following up with supporters and past donors through the CRM.
- Two summits: one in person, and a Virtual Summit in spring with rooms and topics the whole community can join.
The aspirational budget adds:
- Edit-a-thons, code-a-thons and voting-a-thons attached to existing events, starting with an edit-a-thon in the fall. Picture a session the day before a metal festival or a classical music festival, where our editors go and find their people. Sponsorship for events comes out of companies' marketing budgets, which are far larger than their donation budgets.
- A UX summit to review our interfaces together.
- Grants. I've found more than 30 to apply for, ranging from 250,000 to 5 million. Many EU heritage preservation grants fit us, because archiving is what we do. AI companies also fund nonprofits affected by AI traffic, and I intend to ask.
Two more things are on my list:
- Getting our name out to the right people. When I took this role, I kept hearing "Oh, that's still around?" from people who used to edit. I don't want mass publicity. I want to reach the people who are passionate about music and data.
- The website. It needs to explain who the team is, what a nonprofit open data project means, why human-verified data matters and why our editors are the reason it's good. We also need better onboarding: tutorials, videos and a sandbox.
Thank you
Rob and I are very different people, though I think we shared the same fundamental views. One difference is that I do the money thing. Another is that I will resist getting involved in the code and we manage differently, which means we'll need some new ways of communicating.
Thank you for everything, and for your patience while I fill some brightly colored shoes.
Silona Bonewald
Executive Director, MetaBrainz Foundation
-
🔗 anthropics/claude-code v2.1.330 release
What's changed
- Added sign-in to organizations managed in Anthropic's Enterprise Admin Console: after
claude auth login, Claude Code applies the organization's settings and uses its cloud provider or gateway - Added easel, a built-in mod that draws charts when asked and under MCP metrics results, on Pro, Max and, where available, Team and Enterprise on macOS and Linux; turn automatic charts off in
/config - Added
CLAUDE_CODE_FULL_SIGN_IN_LINK=1to print the full sign-in link, if the short one shows an error or a script reads values from it - Self-hosted runner: Added
--start-dir/SELF_HOSTED_RUNNER_START_DIRto have Claude start its work in a folder of a repository, while settings and hooks load as without it - Added a notice in cloud and self-hosted runner sessions when a plugin marketplace can't be fetched because its repository isn't one of the session's
- Self-hosted runner: Added a notice when Anthropic-managed git refuses a plugin's own repository, naming the plugin and what to do
- Added
commandPrintedtoclaude plugin install --jsonresults, true when the plugin's install command wrote to stderr, andcommandFailedwhen it exited with an error, was killed or timed out - Added
claude_code_self_hosted_runner_order_to_registered_secondsto the self-hosted runner's/metrics: seconds from work order issued to registration accepted, on orchestrator-spawned runners - Added
claude_code_self_hosted_runner_order_to_first_session_secondsto the self-hosted runner's/metrics: seconds from work order to first session handed over, on runners started for a session - Fixed Claude Code freezing for up to several minutes right after compacting a very long conversation
- Fixed WebFetch freezing the session for minutes on some pages, and returning an empty result for some others
- Fixed
ExitWorktreeand the worktree exit dialog deleting a worktree that another running Claude Code session was working in - Fixed changes to user settings being lost when several Claude Code processes saved them at the same time
- Fixed
--continueand--resumeopening an empty session or failing when the last saved message had a missing or invalid timestamp - Fixed the first prompt after a sleep of two minutes or more waiting three minutes on a connection that had died, on Linux and WSL
- Fixed turns failing with "JSON schema is invalid", and session files growing by many megabytes, when many MCP tools have an input schema that the API refuses
- Linux: Fixed Bash commands waiting seconds and showing no file diff for the rest of a session in slow repositories with large ignored folders such as
node_modules - Windows: Fixed Bash commands running slower for the rest of a session after Git Bash took 10 to 60 seconds to start, on machines with no custom start-up files
- Fixed
/rewindsometimes restoring an older version of a file when two queued prompts, or stacked skills, ran together right after a turn that changed it - Fixed text and images added when approving a permission prompt being dropped when the approved command or tool then failed
- Fixed MCP resources from claude.ai connectors and plugin servers not being attached when @-mentioned in the terminal's prompt box
- Fixed an MCP server that subagents declare being shut down when one of them finished, while other subagents or the session were still using it
- Fixed Claude in Chrome staying "not connected" after a brief connection problem, even though Chrome was open and signed in
- Fixed terminal sessions on Amazon Bedrock (Mantle) started with no model selected ignoring a pinned Opus model, and still calling an unavailable default model after announcing a fallback
- Fixed the rest of what you were typing being lost when a plan arrived in fullscreen mode
- Fixed claude.ai connectors with different names being dropped when they share a server URL (#101856)
- Fixed plugins going missing from the installed list when several
claude plugincommands ran at the same time - Fixed task dependencies and metadata being lost when several task updates ran at the same time
- Fixed incomplete backups of
~/.claude.jsonbeing kept, and displacing good ones, when the disk was full - Fixed a long pause in Code Mode after code that read hundreds of files in projects with path-scoped rules or Read deny rules
- Fixed the built-in chart tool failing when Claude called it in Code Mode
- Fixed Code Mode ignoring an MCP tool's request to end the turn from a script in auto and bypass permissions modes
- Fixed Code Mode in auto mode dropping earlier thinking and rewriting the prompt cache when a mod added a note after a script loaded a skill
- Fixed Code Mode not restoring a file that a script had read after Esc and
/compact - Fixed
/contextundercounting system tools in Code Mode before Claude's first reply - Fixed a stopped background subagent sometimes not staying stopped
- Fixed Claude still waiting for a background agent that was stopped just as it finished, in sessions run by an app or the SDK
- Fixed background sessions sometimes waking in their previous permission mode after approving a plan
- Remote Control: Fixed the note about background agents ended by a Stop from a phone or the web showing in the terminal as if you had typed it
- Remote Control: Fixed the mobile apps hiding the Diff and pull request buttons, or showing a stopped session as working, after turning it on mid-conversation
- Fixed environment variables written by a SessionStart hook being lost with
claude -p --continue - Fixed
claude -pexiting 0 with no message when its output went to a file on a full disk: it now prints an error and exits 1, though a full NFS export may go unnoticed - Fixed the system prompt keeping the earlier model's instructions when the model was changed after
/contextbut before the first message - Fixed Claude sometimes replying to its commit attribution reminder and ending the turn early after the model changed mid-turn; it can still happen where managed settings set the PR attribution line
- Fixed Esc not ending an LSP tool call that was waiting for a slow or stuck language server
- Fixed LSP tool calls and diagnostics failing when several calls or edits arrived while a language server was still starting
- Fixed
/mcplisting plugin servers as built-in: they now stand under "Plugin MCPs",--mcp-configand built-in servers under "Other MCPs", and a server's page names its plugin - Fixed an "MCP server blocked by enterprise policy: easel" warning showing at every start when an MCP allowlist or denylist excludes the built-in chart tool, which stays blocked
- Fixed
/statscounting new activity in UTC days instead of your local time zone - Fixed
/ultrareviewfailing or reviewing the wrong code after the shell moved into another repository: it now stops and names both folders - Fixed Grep reporting no matches when the pattern held a line break without multiline mode; it now reports the rejected pattern
- Fixed Jupyter notebooks saved with a byte order mark being reported as invalid JSON by the Read and NotebookEdit tools
- Fixed link reference definitions being dropped from CLAUDE.md and memory files that contain an HTML comment
- Fixed running Monitors keeping the earlier conversation in memory until they end
- Fixed some Claude Desktop sessions on third-party providers, other than scheduled tasks, ending a turn with "Prompt is too long" when a PDF larger than the context window followed a long conversation
- Fixed the choice between two user or project agent files declaring the same name depending on the order the file search listed them
- Fixed
claude daemon logsnever exiting inside a git repository when there is no log file - Fixed markdown hiding a character or two after bold or italic text when a backslash came before an emoji later in the paragraph
- Fixed Edit refusing some valid hook commands in Claude settings files
- Fixed
Readwith a page range showing both halves of a scanned two-page spread on each of its pages - Fixed line breaks and class stereotypes missing from Mermaid diagrams in HTML artifacts
- Fixed the Project instructions picker in
/configshowing only one of its four choices in a 24-row fullscreen window - Fixed a subagent's own subagents and forks running on the plan-mode model in plan mode under
opusplanorhaiku - Fixed WebFetch page summaries ignoring the
/effortlevel when a gateway refuses the small fast model - Fixed
claude -pon Google Cloud's Agent Platform ignoring--settings '{"fastMode":true}'when the model comes fromANTHROPIC_MODELor a settings file; such runs now bill at the fast mode price - Fixed startup under
forceLoginOrgUUIDbeing refused after one temporary server error or dropped connection - Fixed
claude mcp removegiving no way forward for a claude.ai connector: it now says to turn it off in /mcp or remove it on claude.ai - Fixed the /mcp "Connect on claude.ai" check saying "not connected" when claude.ai has a connector at the server's URL without its query
- Fixed
/install-github-appand/design-loginshowing a generic failure for an account on hold instead of the on-hold notice and appeal link - Fixed a running MCP task being reported as stopped when you move a session to the background; the background session can now follow the task, but not if its server uses stdio or sets headers
- Fixed self-hosted runners ignoring a session until they exited, after its failure report was lost or the session was given back to the same runner
- Fixed self-hosted sessions losing the prompt cache and earlier thinking when the list of repositories a restart couldn't prepare changed
- Self-hosted runner: Fixed tool calls behind a permission prompt vanishing with no result when a new runner took over the prompt, in sessions with telemetry off
- Fixed resumed self-hosted runner sessions starting without their pushed work in large repositories when
--push-outcome-on-releaseis set - Fixed self-hosted runner sessions being shown as working when Claude Code hangs at every start and
--startup-timeout-minis from 2 to about 6 - Fixed
pkill -fin self-hosted runner sessions on Linux ending its own shell with exit code 144, or the runner (needs apkillwith--ignore-ancestors) - Fixed scheduled tasks on self-hosted runners having no tool to notify their owner when telemetry is off or a third-party provider is used
- Self-hosted runner: Fixed one slow
spawn-runnerhook keeping the orchestrator from claiming sessions for its free slots; it now polls every 4 to 6 seconds while a slot is free - Self-hosted runner: Fixed a 403, such as an IP allowlist's, logged as a bad secret or token: most such lines now lead with the server's reason, so update log alerts that match the old words
- Fixed self-hosted runners' warn mode for repository settings stopping at the first finding of most kinds: it now goes on, up to 50 for a session, and says if it stops early
- Self-hosted runner: Fixed runners that start on a full disk taking sessions and failing them; they now wait for room and exit 1 after a minute with no session, unless started from a work order
- Self-hosted runner: Fixed a failed start suggesting a retry when the runner's machine had no git credentials; the error now says whom to ask and what to do if the repository is wrong
- Fixed the self-hosted runner's
last_poll_age_secondsreading 0 while the runner had never polled successfully - Fixed the notice about a skipped scheduled task that names no organization: it now says to start Claude Code with
--resume, because/resumeinside a running session doesn't run the task - Fixed
claude plugin validatewrongly warning that a mod'sAbovePromptorAbovePromptListhook never runs in VS Code - Fixed
/design-syncdeleting a file it had just uploaded when Claude Design stored that file under a changed name - Reverted 2.1.329's removal of the automatic retry when
max_tokensexceeds a model's or gateway's limit - Improved the claude.ai sign-in link shown by /login,
claude auth loginandclaude setup-token: it is now much shorter - Windows: Improved Grep and Glob speed by no longer starting a console host for each built-in ripgrep search on a local path
- Improved the speed of file diffs
- Improved
/configsearch: most settings whose name starts with what you type come first, "effort" finds Model, and "dark" or "light" finds Theme - Improved
/resume: sessions where you only opened a screen such as/modeland left are no longer listed - Improved Reconnect in
/mcpand/plugin: a server's page now stays open, with the cause in view, when the server still fails or needs sign-in - Improved the error on macOS when sandbox deny lists are too long: it now names the long lists and how to shorten them
- Improved
/pluginin fullscreen mode: the page of a plugin with errors now starts with those errors - Improved
/ultrareview's cost confirmation on Team and Enterprise plans: it now says how much of your monthly spend limit is left when that is less than a review usually costs - Improved self-hosted runner sessions on Amazon Bedrock or Google Cloud's Agent Platform to say so when they start on another default model because your account refused the first
- Windows: Improved the error when a session's folder is on a drive Claude Code can't verify: it says why, and whether retrying can help
- Improved Code Mode: Claude is now told how to look at images and PDFs
- Improved Code Mode: after Esc, "Interrupted" now shows under the stopped command in place of a red error
- Improved Code Mode: the terminal freezes for far less time after a subagent's script makes thousands of tool calls
- Changed recurring scheduled tasks and
/loopto run up to 30 days instead of 7 while their session keeps running, and say when they end; tasks made before this release still end at 7 days - Changed more
rmcommands aimed at the root, home, a top-level folder or the working folder to ask for approval; where nobody can answer, they're refused - Changed
deniedMcpServersname entries to hide only the named claude.ai connector, not others at its URL; to block them all, deny its exact URL - Changed
claude --teleportin some setups to print the git commands for switching branch instead of running them; with-pit exits 1 until you switch - Changed unrecognized model names containing "sonnet" or "haiku" to use the shorter system prompt, like other unrecognized names;
CLAUDE_CODE_SIMPLE_SYSTEM_PROMPT=0gives every model the full one - Changed skills that Claude runs with a
modelsetting, other thancontext: forkskills, to leave subagents, forks, compaction and/recapon the session's model - Changed a subagent's model fallback to carry over: agents with no model and forks it then starts run on the fallback, and the agents they start use its Bedrock region
- Self-hosted runner: Changed
spawn-runnerhooks to start while earlier ones still run, up to--hook-concurrencyper orchestrator (4 by default); set it to 1 if yours can't run beside another - Self-hosted runner: Changed Bash commands to skip the file diff when nothing needs it, so transcripts can lack it; set
bashEditDiffEnabledto true in managed settings to get every diff - Changed self-hosted runners to stop a session's start at once, without trying other runners, when a checkout hook exits with status 108
- Changed prompt hooks to accept model aliases such as
haikuorsonnetin theirmodelfield - Changed
/design-sync's fallback build of the reference Storybook to use only a Storybook installed in the project - Changed subagent progress summaries in terminal sessions signed in to a Claude apps gateway to be written from short notes instead of the whole conversation, using far fewer tokens
- [VSCode] Added
/forkto fork a conversation after its last reply (#69272) - [VSCode] Added
/workflows, which opens the agent map with running workflows - [VSCode] Added the
claudeCode.escapeStopsClaudesetting; turn it off so Escape does not stop Claude (#91536) - [VSCode] Added the
claudeCode.pinPromptsetting to let your message scroll away instead of staying pinned - [VSCode] Added the
claudeCode.contextUsageThresholdsetting for when the context indicator shows (#93036) - [VSCode] Added a
promptargument to the "Open in Side Bar" command for keybindings and extensions - [VSCode] Added Move up and Move down to a session group's menu (#98654)
- [VSCode] Fixed VS Code opening and focusing its terminal on every prompt of a connected terminal session
- [VSCode] Fixed copying a code block adding a trailing newline that ran the command on paste (#96976)
- [VSCode] Fixed holding Enter on
/rewindrestoring files, and a double click on Remove or Delete removing a memory, MCP server or plugin marketplace, without confirmation - [VSCode] Fixed Enter on a question card sending your earlier answer instead of picking the focused one, and arrow keys not working after an "Other" answer; answered questions reopen on your pick
- [VSCode] Fixed a held-down Enter key sending a half-written message or running a typed slash command
- [VSCode] Fixed Cmd+A, C, V, X and Z not working in the rename box and dialogs on macOS
- [VSCode] Fixed Ctrl+F and Ctrl+P not moving the caret in the message box on macOS
- [VSCode] Fixed the Accept and Reject buttons doing nothing on a proposed diff moved to a new window
- [VSCode] Fixed Accept and Reject Proposed Changes showing over the chat, the terminal tab and other files; they now show only on the proposed diff
- [VSCode] Fixed a slow-starting Claude tab taking the keyboard away from the file you had gone on typing in
- [VSCode] Fixed unsaved changes and new problems being missed on macOS and Linux for files whose path contains
#,?or%20, such as aC#folder - [VSCode] Fixed whole-line selections counting one line too many in the selection chip, in @-mentions and in what Claude is told, and file links leaving out the last line of a range
- [VSCode] Fixed a conversation forked in the panel re-running an old, unanswered prompt by itself after a window reload
- [VSCode] Fixed a forked conversation running the original conversation's
/loopschedules a second time - [VSCode] Fixed /clear giving no sign that the session still runs without a newly trusted folder's CLAUDE.md and settings
- [VSCode] Fixed dialogs closing, and losing typed text, when a text selection was dragged past their edge
- [VSCode] Fixed advisor calls showing as "Unsupported content type" (#73499, #64158, #90471, #73637)
- [VSCode] Fixed the session list showing no status for the sidebar chat's session (#93898)
- [VSCode] Fixed the plan preview's Add Comment button vanishing after a fast double click on a word
- [VSCode] Fixed long lines cut off in the Edit Notebook Cell row, permission rules squeezed in a narrow panel, hard-to-see question card marks, and menus moving the chat after a declined trust prompt
- [VSCode] Fixed signing in to an account on hold showing a generic failure instead of the on-hold notice and appeal link
- Added sign-in to organizations managed in Anthropic's Enterprise Admin Console: after
-
🔗 Hex-Rays Blog Recovering from Indirect Branch Obfuscation with Hex-Rays Microcode rss
This article uses samples obfuscated with the Hikari- LLVM19 framework to present a recovery method for AArch64 indirect branch obfuscation. The method is not intended to handle all indirect branches. Different obfuscators may compute target addresses in entirely different ways, so the target resolver still needs to match the specific obfuscation semantics. However, once one or two successors can be reliably identified, the subsequent CFG completion, function range expansion, and microcode rewriting steps can be reused directly.

-
🔗 New Music Releases Rammstein - Live in Mexico City rss
Rammstein - a new release is available:
- 2026-11-20: Live in Mexico City (Live)
Amazon: Canada | Deutschland | France | United Kingdom | United States
Visit muspy for more information.
-
🔗 New Music Releases Trivium - Crown in the Grave rss
Trivium - a new release is available:
- 2026-11-20: Crown in the Grave (Album)
Amazon: Canada | Deutschland | France | United Kingdom | United States
Visit muspy for more information.
-
🔗 New Music Releases Thy Catafalque - XIII: Sárga erdo rss
Thy Catafalque - a new release is available:
- 2026-11-20: XIII: Sárga erdo (Album)
Amazon: Canada | Deutschland | France | United Kingdom | United States
Visit muspy for more information.
-
- November 19, 2026
-
🔗 IDA Plugin Updates IDA Plugin Updates on 2026-11-19 rss
IDA Plugin Updates on 2026-11-19
New Releases:
Activity:
- apiscout
- abc5c49c: Merge pull request #64 from r0ny123/fix/mfc-def-names
- ffxiv_bossmod
- 02a16b44: Merge pull request #819 from Kagekazu/rotations
- 21723545: oi bruv
- 517d1e06: Merge pull request #817 from Nonunon/shinryu
- 821ede07: Merge pull request #818 from Kagekazu/modules
- 681c010d: comment out
- e2e0f233: remove dead code
- a9337f40: more ff16
- 73068b18: collab fixes
- edf40394: m12n and event
- a1160de6: Merge branch 'awgil:master' into rotations
- 7a73783f: Merge branch 'awgil:master' into modules
- e0614c6c: Merge remote-tracking branch 'origin/rotations' into rotations
- f49fb988: RPR updates
- rhabdomancer
- apiscout
-
🔗 anthropics/claude-code v2.1.329 release
What's changed
- Added a trust dialog warning that says where a folder's hooks are declared
- Added a warning in the conversation, in Claude Desktop and other non-interactive hosts, when hooks in managed settings fail to load
- Added this session's scheduled tasks,
/loopwakeups, the goal and this conversation's forks to/tasks; x stops one after asking - Added a "Server message" row to a server's page in
/mcpthat shows the JSON-RPC error message of a remote HTTP MCP server that refuses the connection - Added a "Marketplace auto-update" row to
/statusthat names managed marketplaces that get no automatic updates, and why - Added support for turning on Code Mode while OpenTelemetry events and metrics are enabled; each tool call the code makes sends its events; tracing still keeps it off
- Fixed
~/.claude.jsonsometimes being reset to defaults when a network stall or file lock made it unreadable and cleared during a save - Fixed repeated sign-outs on macOS when Claude Code could read the Keychain but not save to it. That session now stops at expiry and says why, and other sessions stay signed in
- Fixed
/terminal-setupcorrupting VS Code settings or keybindings files around block comments, and reporting success while losing the Shift+Enter binding where keybindings.json has an unclosed string - Fixed files accepted through the IDE diff being saved without their last newline, and losing their byte order mark (BOM) when an edit was accepted by saving the diff in VS Code
- Fixed picking a cloud session in
/teleportreplacing your open conversation: the pick now starts a new session, as/cleardoes, and/resumebrings the old one back - Fixed
/usage-creditsasking Pro and Max users to log in again after opening the browser, and the link disappearing after 8 seconds if the browser doesn't open and a task stops for usage credits - Fixed
/usagesaying usage credits are off when they had run out or reached the monthly limit, and/modelnot telling Pro and Max users when that limit blocks a model that runs on usage credits - Fixed the spend limit menu showing your spend as your monthly limit and wrapping its rows under the pointer in narrow windows
- Fixed a status line script that prints without end freezing the prompt and using gigabytes of memory
- Fixed an empty, frozen screen after approving managed settings while the --resume picker, the trust dialog or another set-up screen was waiting
- Fixed choosing Default in
/modelreplacing your saved model with your organization's default when the Default row already showed your saved model - Fixed an MCP server being signed in again after you cleared its authentication while a token refresh was running
- Fixed background MCP tasks that stalled after a slow reconnect: Claude Code now reconnects most HTTP MCP servers by itself when one is left on an older protocol version
- Fixed PDFs, images and
.docx,.xlsxor.pptxfiles that MCP servers or websites send asapplication/octet-streambeing saved as .bin, which kept Claude from reading the PDFs and images - Fixed
/code-review <pr number>sometimes reviewing the checked-out branch instead of the pull request without saying so: it now reads the pull request withgh pr diff, or says when it can't - Fixed
/code-reviewstopping at a permission prompt, on most models, to look for a~/.claude/CLAUDE.mdthat doesn't exist - Self-hosted runner: Fixed
--push-outcome-on-releasesometimes deleting a session's branch on the git host - Fixed Code Mode hiding a script's finished edits and the stopped command after Esc, and losing them on exit
- Fixed a runaway loop in Code Mode filling the machine's memory; it is now stopped at a limit
- Fixed a background agent running on when it was stopped while it was being resumed
- Fixed background shell commands using memory for the earlier conversation until they exit
- Fixed Remote Control using memory for the earlier conversation after a compaction or
/clearin sessions run by Claude Desktop, IDEs or the SDK - Fixed Stop not ending a request in Claude Desktop sessions on Bedrock while it waits on a hung AWS credential_process or sign-in call
- Fixed Claude sometimes failing to send you a file on its first try on Opus 4.8 and Opus 5
- Fixed Claude not being told that a connected MCP server's tools could not be loaded, and taking it for a server with no tools, in sessions with tool search
- Fixed
claude mcp loginand/mcpsaying a service doesn't accept sign-ins from Claude Code when the service's client registration had been retired (HTTP 410 Gone) - Fixed another case of claude.ai-synced plugin hooks failing with "Plugin directory does not exist" while a session was still running on macOS
- Fixed auto mode asking for manual approval to
rma symlink that points outside the working directory or at itself - Fixed
/sandboxon Linux listingallowUnixSocketsentries as allowed: they don't open those sockets there, and/sandboxnow says so - Fixed pressing Esc twice to clear a mistyped code ending the sign-in in
/install-github-app - Remote Control: Fixed sessions going back to their first effort level after a restart while the app still showed the level you picked (not yet for sessions that start in Ultracode)
- Fixed a removed plugin's MCP server staying connected in headless sessions after
reload_pluginsor when the account's plugin list drops it - Fixed the Claude Docs connector's tools going missing when a plugin or MCP server at the same address failed to connect, and its error wrongly suggesting
/login - Fixed a new skills, commands or agents folder being missed when
--add-dirnames the working directory or Claude Code starts in the home folder - Fixed sessions started from a pre-warmed process ignoring the
autoCompactWindowsetting in the project's.claude/settings.json - Fixed
CLAUDE_AUTOCOMPACT_PCT_OVERRIDEstaying in effect in a running session after it is removed from settings.json - Fixed the Agent tool's
effortparameter being ignored for named teammates in agent teams - Fixed
/auto-mode-setupignoring recent auto mode denials when it scans a project for rules to suggest; it may now offer allow rules from them, and you review each before it's saved - Fixed a false "Couldn't save this change" warning after adding a permission rule or directory in a subfolder or worktree whose own
.claude/settings.local.jsonis unreadable or malformed - Fixed cloud sessions telling Claude to run a network proxy check after a failed request, which auto mode then blocked
- Fixed headless rewind and fork going ahead while a message sent right after a model change still waited on it
- Fixed Claude not being told when a background task was stopped while a cloud session was restarting
- Fixed
/team-onboardingreporting a guide as shared on Team and Enterprise plans when the server refused the upload - Fixed panels and questions being cut off at the prompt in fullscreen,
/help, history search and the background tasks list losing rows or titles in short windows, and tables wrapping in dialogs - Fixed resumed sessions showing "Rejected" or "Declined" for edits, questions and plans that were cut off when the session ended
- Fixed
/passesshowing the wrong number of passes after a server error, and offering usage credits for sharing when no guest passes are left - Fixed
claude --helpoutput being cut short when piped to another program - Fixed
/terminal-setupturning on "Use Option as Meta key" in Terminal.app on macOS 27, and tips there suggesting Option+Enter instead of Shift+Enter - Self-hosted runner: Fixed setup failing on Git LFS repositories cloned through Anthropic-managed git; sessions now start on pointer files, and
git lfs pullfetches the content - Fixed sessions on self-hosted environments not starting from a git remote with an SSH host alias, GitHub SSH certificates or a GHE.com SSH user; an unresolved alias's error gives two git commands
- Fixed remote MCP servers in self-hosted runner sessions staying without tools, or (over https) disconnected, after a timeout or network error
- Fixed self-hosted runner sessions being shown as having stopped responding while Claude Code was still starting
- Fixed Code Mode keeping in memory every large text file that code read, and memory growing each time a background subagent was woken
- Fixed Code Mode stopping a script at its ten-minute limit while an MCP form, an MCP link prompt or a prompt that always asks was waiting for an answer
- Fixed Code Mode scripts receiving a "moved to the background" message as data from most MCP calls over two minutes: the script now waits up to ten minutes, then gets an error
- Fixed mods that list only some tools silently turning Code Mode off; such a mod no longer keeps it off, so use managed settings for that
- Fixed Code Mode ignoring an MCP tool's request to end the turn when the tool was called from a script that Claude waits for
- Fixed a Code Mode script's
let x;keeping the value that an earlier script gavex - Fixed a Code Mode script's call with no argument failing with a missing-parameter error on tools that need none
- Fixed Code Mode scripts losing access to tools through
toolsin sessions with more than 4,096 tools - Fixed the
/code-reviewfindings card often showing "high" for a review that ran at medium, on most models - Fixed key hints in permission prompts, questions,
/modeland/rewindignoringkeybindings.json - Fixed auto-scroll, the PR status badge, the auto-compact warning and the ultracode tag not following the
/configswitches that control them in a running session - Fixed a custom cancel key not working in
/add-dir,/tuifeedback and the save-workflow form - Fixed arrow keys in the save-workflow form moving the selection in the workflow view behind it
- Fixed
/configsaying nothing, or "dismissed", after changing many settings - Fixed Read and @-mentions showing one line too many for files that end in a newline
- Fixed
/statusnot naming the model that opusplan and haiku use in plan mode - Fixed
claude doctoradvising a Keychain unlock inside a macOS sandbox, where unlocking can't help - Fixed the "Jump to bottom" pill staying hidden after copying text and scrolling away, the row under it going blank when its label changed, and quick PageUp presses scrolling too far in fullscreen
- Fixed a screen update sometimes being skipped when memory is low
- Fixed long code blocks losing a blank line and repeating another in scrollback
- Fixed prompt suggestions sometimes showing placeholder text such as
_(no suggestion)_ - Fixed the line about earlier messages on resume blaming a damaged file when the file was intact
- Fixed characters disappearing from the prompt when its text held a color code that sets several styles and a keyword or command was highlighted
- Fixed
/renameandUserPromptSubmithook titles inclaude remote-controlsessions not showing on claude.ai and mobile - Fixed the Remote Control diff listing a file twice when the branch renamed it and it was then edited
- Improved the automatic clean-up of old sessions on computers with managed settings
- Improved
/tuiand other in-place restarts to wait briefly for a login refresh, so they are less likely to sign you out - Improved memory use in long sessions that edit many files, and in long Claude Desktop sessions on macOS and Linux with many large MCP tool results
- Windows: Improved start-up and the first search on PCs where Claude Code's search program starts slowly
- Improved auto mode's handling of a short reply such as "yes" to Claude's question when telemetry is off, behind a gateway to the Anthropic API, or on Microsoft Foundry
- Improved memory use of idle Claude Desktop and SDK sessions after a long turn, and after
--resumeor--continueof a session that holds screenshots or large tool results - Improved how fast a Claude Desktop Code session with Remote Control on is ready for the next message after an answer
- Improved cloud sessions to retry plugins that failed to download at startup
- Improved Code Mode: the terminal freezes for far less time after a script makes thousands of tool calls
- Improved Code Mode: after starting a subagent, Claude now gets the same guidance on waiting as outside Code Mode
- Updated computer use on macOS to newer safety rules, so some actions are refused and some apps have less access
- Changed saved scheduled tasks: in new signed-in sessions, most saved by earlier versions need scheduling again, though
--resumeof their own session still runs them - Changed
/code-reviewwith no target on most models to review the whole branch against the default branch, and fixed it losing the diff on multi-commit branches - Changed auto mode to run
git statusless often so most requests wait less in large repositories; a git command that discards changes may be blocked until the working tree is checked - Changed
/code-review <pr number> --fix, and/code-reviewgiven a pull request URL, to stop without reviewing whengh pr diffis refused or fails - Changed 'Exit and stop tasks' to end this session's scheduled tasks so they don't run again on resume, unless you exit while Claude is responding
- Changed some teammate panes to start through /bin/sh, so they may not read shell start-up files
- Changed computer use on macOS to give up on an app launch that has not finished after 30 seconds
- Gateway: Changed the start-up warning shown while
access_control.allow_cidrsis empty to a notice at every start, boxed in text logs: never expose the gateway to the public internet - Self-hosted runner: Changed a second host name's clone of the same owner/name to go under
_repos/clones/<host>/in the base folder; no clone moves - Self-hosted runner: Changed repositories with unusual characters in their address path to clone anew in a new folder; rules and volumes naming the old one stop applying, and the old clone stays put
- Self-hosted runner: Changed
--repository-folderto take most folders in the base folder at--capacity 1(above 1, one there stops start-up); another repository's session overlapping one is refused - Changed Code Mode so a PreToolUse hook that errors no longer refuses a script's tool call, as outside Code Mode; set
"onFailure": "block"on a command, HTTP or MCP tool hook that must refuse - Changed Code Mode to refuse a script's read of a line range over 256 MiB, which could use gigabytes of memory, and fixed reads of very long lines timing out
- Changed Code Mode to also start when telemetry, nonessential traffic or feature flags are turned off; an administrator can keep it off in managed settings
- Changed Code Mode to run a script that declares its own
log,previeworsleep, which it used to refuse - Changed macOS login renewal to test the Keychain with a
Claude Code-write-checkitem - Changed the
/tasksheader and the footer's background count to one number covering shells, monitors, MCP calls, agents, workflows and scheduled tasks - Changed Stop and SubagentStop hooks to list a Monitor's script as
monitor, notshell, inbackground_tasks - Removed 2.1.326's automatic retry at the limit named in a
max_tokenserror; behind a gateway whose model takes fewer output tokens, setCLAUDE_CODE_MAX_OUTPUT_TOKENSto that limit - [VSCode] Added a line above the message box after you decline the trust prompt, with Review trust to bring the prompt back without reloading the window
- [VSCode] Fixed being signed out of Claude Code in every window and terminal when the sign-in server took 10 to 30 seconds to answer the extension's token refresh
- [VSCode] Fixed keys pressed while an input method (IME) is composing moving focus on or declining a permission prompt, running menu rows and closing dialogs (#106358)
- [VSCode] Fixed the permission prompt for Bash, Edit, Write and other built-in tools not showing why a safety check asks
- [VSCode] Fixed a half-written plan comment being lost or moved to another passage, and an input method's Enter sending the comment, ending a session rename or picking an @-mentioned file
- [VSCode] Fixed the limit banner not saying when usage credits are in use, and the session survey covering that banner and the usage credits card
- [VSCode] Fixed screen readers not announcing a permission request that arrived while the Account & Usage dialog was open until that dialog was closed
- [VSCode] Fixed a proposed-edit diff tab staying open, with an Accept button that did nothing, after its terminal Claude Code session disconnected
- [VSCode] Fixed short tool inputs and outputs cut off at the panel's edge with no way to read the rest (they now open in an editor tab), and dragging to select text also opening one
- [VSCode] Fixed the Up key putting an earlier message over text that an input method (IME) is composing in the message box (#101294)
- [VSCode] Fixed dropping an Explorer folder onto the chat inserting nothing on VS Code 1.103 to 1.139 or in a floating chat window, and the drop highlight vanishing with a false "Hold Shift" hint
- [VSCode] Fixed a permission prompt moving keyboard focus away from the details you were scrolling as its buttons switched on
- [VSCode] Fixed file links in a Claude tab opening in another editor group when
claudeCode.lockEditorGroupsis off (#108884) - [VSCode] Fixed ranges written with a single tilde (
3~5 … 7~10) losing their tildes and showing struck-through text between them; only~~text~~is struck through now - [VSCode] Fixed dictation errors wrapping into a narrow column, the spinner turning while a question card waits, and a NUL symbol after each letter in the output of a failed UTF-16 command
- [VSCode] Changed Down to stop at the last item of a permission prompt instead of wrapping to Yes
- [VSCode] Changed command output to show hidden characters and control sequences other than plain colors as symbols, so Persian, Khmer, Lao, Sinhala and Malayalam text can look broken or out of order
-
🔗 HexRaysSA/plugin-repository commits sync repo: +3 releases, -1 release rss
sync repo: +3 releases, -1 release ## New releases - [cfiscope](https://github.com/nightshift-labs-ai/cfiscope): 0.1.23 - [kflow](https://github.com/nightshift-labs-ai/kflow): 0.0.8 - [memlens](https://github.com/nightshift-labs-ai/memlens): 0.3.31 ## Changes - [memlens](https://github.com/nightshift-labs-ai/memlens): - removed version(s): 0.3.6 -
🔗 backnotprop/plannotator v0.29.1 release
Follow @plannotator on X for updates
Missed recent releases? Release | Highlights
---|---
v0.29.0 | A redesigned code review window with two panes, a file tree, image diffs and a minimap, semantic diffs for moved and renamed code, talk through a review comment with your agent, Code review in the Inbox is a switch in Settings, hide a pull request or a repository, playback speed for videos,plannotator routinecommands and a/create-routineskill
v0.28.67 | Drag threads to Priority, Archive or Quiet, or onto another thread to combine them, mention another thread in your reply, Linear hover cards, pick any tag colour, a linked computer's pictures and files open here, pull request cards say why they could not load
v0.28.66 | Pick several threads and archive or snooze them at once, combine picked threads into one; Tidy follows your own words, rows take their tag's colour; filter and search by tag, files an agent's message names open beside the thread, swipe rows on phone or iPad; list can show archived threads, Antigravity and Orca use the Inbox; T3 Codex threads get replies, Open in lists JetBrains IDEs, Routines: run a saved prompt on a schedule
v0.28.65 | Take back a reply your agent has not received yet, over Tailscale, Plannotator opens only for your own account, tag a linked machine's threads; one tag across machines, T3 Code threads get the Inbox with no setup, long threads open on slow connections
v0.28.64 | Installs and updates download a smaller, compressed copy, a Videos filter on the Artifacts page, GitLab comments on a whole file get their own thread, pull request pictures and videos show in the Inbox
v0.28.63 | Pair Grok Bot and other cloud agents from Settings, Hermes Agent, OpenClaw and Muse Code can use the Inbox, add a thread to Priority to keep it on top, tag threads, and find each tag in the sidebar, Pull requests board as a table, with bulk Merge
v0.28.62 | Agents started from the Inbox now work on Windows, pick a model and effort when you start an agent, rules for your agents, written in your own words, post a thread's decisions on its pull request, the Inbox loads faster on a slow connection
v0.28.61 | Updates now update the Claude Code plugin too, an agent's chosen face shows on every icon of it, filter the Inbox list by pull request state, Modern dark shows section bands and the Reply button, one conversation no longer shows as two agents
v0.28.60 | Click a word to highlight it, a one-time Themes dialog, Settings → Rows rebuilt, tell your agent how you want your rows, starred threads as pills above the list, a pill for new messages out of view, a half-circle face picker with ten Glass colours, a new phone sidebar and reply box
v0.28.59 | A quieter Agents section in the sidebar, machine names only when agents run on more than one machine, agent icons that are always gently alive and lean toward your pointer
v0.28.58 | Start Codex from New message, an Agents section in the sidebar, start an agent in a folder on any drive, play audio attachments and comment at a moment, Claude Code's Plannotator tools work on Windows
v0.28.57 | Pin artifacts, and see every artifact on one page, filter the list by project, date or agent, a thread shows its pull requests and their state, choose what the sidebar shows, and in what order, Ask AI starts from Side in the selection barWhat's New in v0.29.1
TL;DR
- New: Start the Inbox's agents in Rex, each in its own tab, on a Mac or on a Linux or FreeBSD server
- New: Search inside the list's Filter menu when a section is long
- New: Start a thread from a pull request's page in Reviews
- New:
/picture-it, a built-in skill that asks an agent for one page of pictures explaining a change - New: Questions that propose a change show it as Now and After
- New: Threads side by side, a switch in Settings (off by default)
- New: Status marks for every agent in the sidebar, a switch in Settings (off by default)
- New: Tag a project, and filter the list and the Board by that tag
- Changed: Play a sound now rings for every agent message by default; "when an agent asks you" keeps the old behaviour
- Changed: The "N new" bar stays at the top of the list and says what came
- Changed: On a computer where the Inbox has never run, nothing starts it until you run
plannotator inbox, and Claude Code gets no Inbox tool until then - Fixed: In code review, the symbol hover card closed while the pointer was in it
- Fixed: Your Inbox rules and reminder never reached sessions that connect over MCP
- Fixed: Invisible or faint text in several built-in themes
v0.29.1 is mostly an Inbox release, with a round of fixes to the code review window that v0.29.0 introduced. Agents the Inbox starts can now run as tabs in Rex, the list's filter gets a search field, and a pull request's page can start a thread. On a computer where the Inbox has never run, it now stays off until you run it. The release has 56 PRs. Fifteen come from outside contributors: fourteen fixes from @rudycelekli, merged together in #3658, and one from @sx4im.
The Inbox turns on only when you run it
On a computer where the Inbox has never run, nothing starts it on its own any more. Claude Code gets no
plannotator_inboxtool and no Inbox reminder, and a background start by a plugin or an agent's Inbox call answers with one line instead:The Plannotator Inbox is off on this computer.
plannotator inbox --openturns it on. If you are an agent, ask the person in the chat instead, and turn it on only if they ask you to.The Inbox turns on when you run
plannotator inboxyourself (bare,--no- openor--open;/plannotator-inboxruns--open), or when your agent runsplannotator inbox --openfrom the Inbox setup prompt. That first--openalso connects the agents it finds, within half a minute.If you have already run the Inbox on this computer, nothing changes: the first time Plannotator checks after the update, it sees that the Inbox ran here and records that once. One edge: a Claude Code session that already had the plugin loaded before you first turned the Inbox on needs one restart to get the tool, because a session decides at its start whether it has it.
Start agents in Rex
Rex is a terminal server with sessions, tabs and panes. The Inbox can now start its agents there instead of in the background.
Settings → Agents → Start new agents in has two choices: In the background (the default) and Rex. The row shows while Rex is running on this computer, or while Rex is already the choice. With Rex picked, a New message, or a reply that starts a session, opens a new tab named for the agent, in a Rex session the Inbox keeps for that project. The agent runs its ordinary interactive command there and keeps running after the Inbox closes. Rex's app is not brought to the front when a tab opens. Your message never goes on a command line; the agent receives it as its first turn through its own Inbox connection.
- Claude Code, Pi and OpenCode can start in Rex. Codex always starts in the background, and so does every routine run, so a routine does not open a tab per run.
- Where it lives. An agent in a Rex pane shows "Rex · session / tab" on its hover card, in the To picker and in its spoken name. This includes agents you started in Rex yourself, while Rex is the setting.
- Show in Rex on the agent's menu moves Rex's app to that agent's tab. It needs Remote Control turned on in Rex's settings; if it is off, the Inbox says so.
- Status marks. An agent in Rex gets a mark on its icon when its pane reports that it is working, waiting on you, done or failed.
- Stop closes that agent's own tab in Rex and nothing else. Open in Terminal is not offered for an agent in Rex, because it would start a second process on the same session.
- When Rex is not there, or does not open a tab, the agent starts in the background and the run line says why. A reply to an agent that stopped starts it again in a new tab, as the same session.
Rex also runs as a server on Linux and FreeBSD, with no app on that machine and apps attaching from other computers. The Inbox finds such a server in the places Rex's manual gives, and starts agents there without an app. Show in Rex then asks the Rex apps attached to that server. For an agent on a linked machine, Show in Rex goes through the machine link to the Inbox beside that Rex. A click made on another computer never moves a Mac's own Rex app.
The Inbox only talks to Rex through its existing socket, owned by your user. It never starts a Rex server, never types into a pane and never reads what a pane shows.
#3606, #3693, for #3303 from @tommyent
Search the list's filter
When a section of the list's Filter menu has more than eight rows, a Search filters field sits at the top of the menu. Typing narrows every section at once (Agent, Project, Tag, Pull request, Routine and the rest), bolds the matching part of each row and ignores case and accents. A section with no match goes away, and a row you already ticked stays so you can untick it.
The arrow keys move through the rows while the field keeps focus, Enter ticks a row and leaves the menu open, and Escape clears the field before it closes the menu. On a phone the field sits under the sheet's title, and opening the menu with a tap does not raise the keyboard. With short lists the menu is the same as before.
Start a thread from a pull request
On a pull request's page in Reviews, when no thread is about that pull request yet, the Review thread section offers Start a thread. The page turns into an empty thread for the pull request in place: its header line with title, branch, changes and checks, one line ("Ask anything about this pull request. Your first message starts the thread."), and the reply box. The reply box's To control lists this computer's live agents in the pull request's project, then a new session of each agent.
Nothing is made until you press Send. Your words come first in the message, and the pull request's details follow under a fold, "Sent with: this PR's details", which shows exactly what the agent received. From then on the pull request's row in Reviews and its page open that thread. Closed and merged pull requests, stacks of several pull requests, and pull requests outside a project do not get the button.
Picture it
/picture-itis a new built-in skill, first among the built-ins in the reply box's/list. It asks the agent for one self-contained HTML page that explains what you are discussing, mostly drawings with short labels: for a code change, what changed and why. The skill tells the agent to take file names, lines and numbers from the code or the thread, to make the page read at phone width and take your Inbox theme, and not to change code while it makes the page. The agent sends the page back in the same thread as an attachment.The Inbox also recognises a page made this way from a mark in its head, and records which attachment it is. Nothing in the window uses that yet.
Before and after on a question card
A question that proposes a change, to words, a screen, code or a setting, can now show it. The agent writes
Where:,Before:andAfter:lines, and the Inbox draws them as a quiet Now and After pair: removed words struck through on a red tint, added words on a green tint. A line that changes almost entirely is shown whole instead of marked word by word. A value can be a picture, and two pictures sit side by side on a wide card. Each choice can carry its ownAfter:, so a question about three wordings shows three versions.The agent tool's instructions,
plannotator inbox --help before-afterand the plannotator skill teach agents the format. Plan review, annotate and older Inboxes show these lines as plain text, and a question without them looks exactly as before.Threads side by side
Settings → General → Appearance → Threads side by side is a new switch, off by default. Turned on, a thread's right-click menu offers Open to the side , and you can drag a thread next to the open one. The change applies at once in every open Inbox window, with no reload. Turned off, the Inbox works exactly as it does today. A phone always shows one thread, so the row is not shown there. If you had turned on the hidden preview in
config.json(inboxSplitView), the switch is already on.The panes themselves were also improved: Escape closes only the pane you are in, closing a pane by keyboard moves focus to the pane that is left, a column holds at most two panes, and the panes you are not in have a stronger grey header. When the window narrows and a pane steps aside, a toast says so, and the pane comes back when the window widens.
Agent status marks
Show agent status (Settings → General → Appearance, under Sidebar, and in the list's ⋮ menu) puts a status mark on every agent in the sidebar's Agents list, not only on agents in Rex. It is off by default. A mark shows when an agent is working, when it waits on a prompt where it runs ("Waiting for your permission in the agent" or "Waiting for your answer in the agent"), and when a thread waits on you. An agent at rest draws nothing. Marks show only in the Agents list, never on thread rows or the Board. A mark that could stay on "Waiting for your permission in the agent" when a prompt was answered within a second was fixed before release.
Permission and question prompts are reported by Claude Code (questions, and permission prompts for Bash on Claude Code 2.1.326 and later), OpenCode 2, Pi and Oh My Pi.
One part of this applies with the setting off: an agent that does not report when it is working (Codex, T3 Code, Antigravity and cloud agents, for example) is no longer called "Idle". Its hover card says "Doesn't say when it's working".
Tag a project
A project's ⋯ menu has Add tag , with the same tag list as a thread's menu. Picking a tag in the list's Filter then keeps threads that have the tag and threads in a project that has it, and the Board's tag filter does the same. This lets you see, say, every Work project together. Nothing looks different until you tag a project. Tags on a linked machine's project are kept on that machine.
Play a sound: for every agent message
Play a sound (Settings → General, under "When an agent sends you something") now has a choice: when an agent asks you (the behaviour until now) and for every agent message , which is the new default. With the default, a plain reply, a new thread or a question from an agent rings the bell. Either way it rings only while no Inbox tab is in front, once for a burst of messages within 30 seconds, and never for your own messages or for snoozed threads. If you had turned the sound off, it stays off.
The new-messages bar
The "N new · Show" bar above the list now stays at the top while you scroll, and says what came on one line, for example
Claude Code replied in “Checkout redesign” · Showor2 replies from Claude Code and Codex · Show. In a project or filter view, news from elsewhere gets a second line with Show all. The bar arriving no longer moves the rows you are reading. The floating New pill now shows only after you press Show, for rows that landed out of view.Code review: the symbol hover card
Moving the pointer from a symbol into its hover card ("8 references") often closed the card a moment later, with the pointer still in it. It now stays open until the pointer leaves the card. The hover underline and hand cursor now show only on names that can open a card, so comments, keywords and
;no longer look clickable. The card's footer is one line: "Click to jump · ⌘ click for all references" (Ctrl+click on other systems).Code review fixes
- Lines no longer move under you when semantic notes arrive. Once you start reading (scroll, click, type or jump to a file), a file's moved and renamed notes that arrive later are offered in its header ("1 moved", one click shows them) instead of redrawing the file at a new height. Files below the view still get their notes as they arrive. #3674
- Semantic diffs on a slow connection. The first download of the engine and of each language could hit the three-second limit and fail the file. A language's first answer now gets 30 seconds. Lines you open stay where they are, and with the semantic switch off no file header shows a semantic note. A comment on any old-side line inside a folded "Moved N lines" block now opens the block. #3662
- Expand arrows. A mouse click on an expand arrow or on the "N unmodified lines" label sometimes did nothing, mostly in Safari, because the row was redrawn during the press. The click now always opens the lines. #3666
- Two Git settings no longer change what a review reads. With
diff.relative=true, a review started in a subdirectory showed only that subdirectory, and expanding, staging and unstaging broke. Withlog.showSignature=true, a signed commit's short SHA and subject were read wrong. Every review Git command now turns both off. #3664 - File tree. Escape in an empty search box moves focus to the tree's current row instead of the page. A renamed file's tooltip reads
old → new. On the Inbox PR page, switching between Changes and All files keeps focus on the switch. #3663 - A review job that ends at once no longer shows Running forever. If a Guided Review or agent review finished (or failed) before the window had read the answer to its own start request, that late answer set it back to Running until a reload. A finished job now stays finished, and one that fails at once shows Failed. #3747
- Review agent instructions say in plain words that missing tests are a finding only when a change adds non-trivial logic with no test coverage at all. #3703
Your Inbox rules reach MCP sessions
Sessions that connect to the Inbox over MCP, such as every session T3 Code starts, only ever saw the built-in server instructions. The rules and reminder under Prompts → Inbox reached sessions started from a terminal but not these. The MCP server now adds your rules for all agents, then your reminder, after its built-in lines, and follows the same reminder switch. How much room they get depends on the client: Claude Code 2.1.296 and later keeps more than older Claude Code and other Claude apps, and other clients get the terminal path's limit. Rules and reminder are each sent whole or left out whole, never cut. Settings → Prompts shows the count against Claude Code's room and a "Not sent to …" note when your text is too long for some agents. A change applies to the next session, with no restart.
By @sx4im in #3567, closing #3555 from @stjepanvrbic
Fixes from
Fourteen fixes from @rudycelekli, merged together in #3658 with each pull request's commits and authorship kept:
- Paired cloud agents saw
computer_asleepwhile the computer was awake. The Inbox now pings its relay connection and replaces one that stopped answering. A follow-up keeps the connection through a slow, large upload, such as a video sent to a phone. #3636, closing #3577 from @kyletruong - Oh My Pi:
/new, resume and fork move the Inbox connection to the new session, so replies reach it (#3644, closing #3564 from @omederos), and a session switch resets plan mode and closes the open plan review (#3650). - Less repeated work on list and status reads. Each session's restart check is worked out once per response. #3637, part of #3623 from @Arobotmaster
- Pull request stacks rank the forge's default branch as trunk ahead of an older branch named
main(#3639), and an open pull request stays in its stack through five merged layers (#3641). - Bulk actions: a failed later batch of a bulk hide or show no longer undoes the batches that went through (#3640), and a bulk merge confirmation resets when a picked pull request's head, base or machine changes (#3649).
- Linked machines: a linked machine's Board is read again after its first read fails (#3646), and a Reviews read in flight is dropped when that machine is unlinked (#3647).
- Review diffs: removed lines such as
----or--- xcount in a file's +/−, the same in the file tree, the file header and stack cards (#3642); paths with leading or trailing spaces are kept (#3643); and blank context lines read correctly whatever yourdiff.suppressBlankEmptysetting (#3651). - Comment boxes stay open when Escape only closes an input method's candidate list. #3648
Theme contrast
Some text in the built-in themes was hard or impossible to read.
- Invisible text in Simple and Neutral. Text on red buttons, such as the Inbox's confirm button, the "This review was replaced" banner and the remove × on attachments, was the same red as the button, or nearly. It is now near-white.
- Pale accent text in Simple, Neutral and Quantum Rose light now reads at 4.5:1.
- Faint grey text in light themes. Muted text in light themes such as Min, Material, Solarized, Tokyo Night, One Light, Rosé Pine, Vitesse and the Everforest themes is darker, to at least 4.5:1. In six of them the body text is darkened too, so it still reads stronger than the grey. Dark modes are unchanged.
Which version of an attachment you are viewing
When an attachment opened beside a thread has changed since it was sent, the line above it now says which version is on screen, for example "Viewing the current file (edited 5:51 PM). Claude Code sent an earlier version at 3:41 PM." with View sent version , or "Viewing the version Claude Code sent at 3:41 PM." with View current file. Full screen's chip uses the same sentence and link.
Additional Changes
- Internal work with nothing new to see in this release: #3677, #3678, #3679, #3680, #3681, #3684, #3685, #3694, #3699, #3701, #3708, #3713
- Code moved into shared packages, no change in behaviour: #3682, #3686, #3688
- Test upkeep: #3722
Known issues
- Rex on Linux and FreeBSD has been tested against a stand-in for Rex's server, not a real one.
- Threads side by side: narrowing the window does not fold the docked sidebar, so fewer panes fit than could, and Tab moves through panes in the order they were opened, not the order they sit on screen.
- Code review: clicking the header of a file with opened lines still folds them back.
Install / Update
macOS / Linux:
curl -fsSL https://plannotator.ai/install.sh | bashWindows:
irm https://plannotator.ai/install.ps1 | iexClaude Code Plugin: The install script above also updates the plugin when
claudeis on your PATH. Otherwise, in a terminal:claude plugin marketplace update plannotator claude plugin update plannotator@plannotator --scope userThen restart Claude Code. Inside Claude Code, run
/plugin marketplace update plannotator, then open/plugin→ Installed → plannotator → Update now.Pi:
pi update npm:@plannotator/pi-extensionOpenCode: Re-run the install script above. It also clears the OpenCode 2 plugin cache.
What's Changed
- File tree: Escape focus, rename tooltip, focus after switching lists in #3663
- Reconnect the Inbox when a relay socket stops answering by @rudycelekli in #3636
- Reuse restart judgments in Inbox thread and status responses by @rudycelekli in #3637
- Prefer the forge's default branch when grouping PR stacks by @rudycelekli in #3639
- Keep successful entries when a later bulk hide or show fails by @rudycelekli in #3640
- Keep an open PR attached through five merged stack layers by @rudycelekli in #3641
- Count patch-marker-like lines in review hunks by @rudycelekli in #3642
- Preserve whitespace in Git review paths by @rudycelekli in #3643
- Move the Inbox wake when Oh My Pi switches sessions by @rudycelekli in #3644
- Retry a linked Board after its first read fails by @rudycelekli in #3646
- Discard linked Reviews reads when their machine is unlinked by @rudycelekli in #3647
- Keep comment composers open on an IME Escape by @rudycelekli in #3648
- Refresh bulk merge confirmation when its target changes by @rudycelekli in #3649
- Restore plan mode when Oh My Pi changes sessions by @rudycelekli in #3650
- Read Git hunks that omit blank context prefixes by @rudycelekli in #3651
- Fourteen fixes from @rudycelekli, merged together in #3658
- Review: pin
diff.relativeandlog.showSignatureoff in review Git commands in #3664 - Review: a click on an expand arrow always opens the lines in #3666
- Inbox: Start a thread from a PR's page, an empty thread in place in #3629
- Semantic diffs: opened lines stay put, switch off and on, slow links in #3662
- Inbox: where an agent lives in Rex, Open in Rex, Show in Rex in #3606
- Internal: move shared Inbox types in #3682
- CI: internal change in #3677
- Semantic diffs: notes that land after you started reading are offered, not swapped in in #3674
- Internal: move question answer code in #3686
- Internal: name a list row rule in #3688
- Inbox server: internal change in #3678
- Mobile: internal work in #3679
- Mobile: internal work in #3681
- Inbox: search the list filter when a section is long in #3620
- Relay: internal change in #3680
- Inbox: send your Inbox rules and reminder to MCP sessions by @sx4im in #3567
- Mobile: internal work in #3684
- Mobile: internal work in #3685
- Mobile: internal work in #3699
- Mobile: internal work in #3701
- Review instructions: say plainly when missing tests are a finding in #3703
- Inbox: the version line says which version you are viewing in #3704
- Mobile: internal work in #3694
- Inbox list: the N new bar sticks; the New pill shows only after Show in #3616
- Fix blank text and faint light muted text in the built-in themes in #3706
- Mobile: internal work in #3708
- Inbox: tag a project, and let the filter pick the tag in the list and on the Board in #3697
- Inbox: status marks for every agent, behind a setting in #3710
- Show a proposed change on a question card: Where, Now and After in #3714
- Fix a flaky test: a grammar download that never ends in #3722
- Inbox sound: ring for every agent message, or only when an agent asks in #3695
- Mobile: internal work in #3713
- Inbox: a Settings switch for thread panes (off by default) in #3719
- Review: keep the symbol hover card open while the pointer is in it in #3728
- Rex on any server: Linux and FreeBSD servers, starts with no app, Show in Rex from other computers in #3693
- Review: a one-line footer on the symbol hover card in #3732
- Picture it: the
/picture-itskill and the page mark in #3723 - Agent status: a prompt set and cleared between two looks reaches the window in #3735
- The Inbox turns on only when you run it in #3729
- Review: a finished job stays finished when its launch answer arrives late in #3747
Contributors
@rudycelekli sent fourteen fixes this time, across the relay connection, Oh My Pi, pull request stacks, bulk actions, linked machines, review diffs and comment boxes (#3636 to #3651). They landed together in #3658 with each commit and its authorship kept. Two of them close reported issues: the dead relay socket and Oh My Pi's
/new.@sx4im made the MCP server carry your Inbox rules and reminder, sized to what each client keeps of its instructions, with a count and notes in Settings → Prompts (#3567).
Thanks also to the people whose reports shaped this release:
- @stjepanvrbic reported that Inbox rules and the reminder never reached sessions connecting over MCP (#3555)
- @kyletruong measured an idle Inbox losing its relay connection after about an hour and never reconnecting, leaving paired cloud agents with
computer_asleep(#3577) - @omederos found that a session started with
/newin Oh My Pi did not get Inbox replies, and traced it to the session switch event (#3564) - @Arobotmaster reported thread-list latency that depended on the session (#3623)
- @tommyent asked for the Inbox to say where each agent runs (#3303), which the Rex work answers for agents in Rex
Full Changelog :
v0.29.0...v0.29.1 -
🔗 smol-machines/smolvm smolvm v1.35.5 release
What's Changed
- docs: say that virtiofs DAX is off on arm64 hosts and SMOLVM_MOUNT_DAX does nothing there by @BinSquare in #2087
- Add smolvm docker: one command starts a Docker engine in a managed machine and points docker at it by @BinSquare in #2089
- Share the home directory with the smolvm docker machine at the same path by @BinSquare in #2090
- Resolve host.docker.internal to the host from smolvm docker containers by @BinSquare in #2091
- Fix a port race in the leader-exit test by @BinSquare in #2096
- Remove smolvm docker by @BinSquare in #2095
- Hand supplied credential values to a running embedded machine at once by @BinSquare in #2097
- Pin libkrunfw with UDP kept inside a TSI guest, and test it by @BinSquare in #2099
- Publish ports below 1024 on macOS, add IPv6 loopback to live-forwarded ports, and lift the 64-mapping cap by @BinSquare in #2092
- Return idle guest memory to the host within two minutes and cap new machines at half the host's RAM by @BinSquare in #2094
- Install a root-owned agent-rootfs when root runs install.sh by @rdslw in #2082
- Announce a changed file to the guest once per change by @BinSquare in #2102
- Answer guest DNS from a host cache that coalesces bursts and resends lost queries by @BinSquare in #2098
- Keep every disk chain under the branch depth limit: fold restored checkpoint layers and frozen-source chains by @BinSquare in #2103
- Exec sessions: commands the node owns, resumable after a dropped connection by @BinSquare in #2101
- Let a guest hold tens of thousands of connections on virtio-net and free their host sockets promptly by @BinSquare in #2104
- Scope the usage journal to the test's own thread by @BinSquare in #2106
- Pin libkrun 526be460 and libkrunfw f290c62b, rebuilt for every platform by @BinSquare in #2109
- Build the agent rootfs as non-root on hosts with user namespaces again by @BinSquare in #2107
- Answer a start missing the mediated interceptor with 400, not 500 by @BinSquare in #2108
- Run tests that need a released file lock free at once in their own process by @BinSquare in #2110
- Pin libkrun 9df62257 and libkrunfw 7f4d4950, rebuilt for every platform by @BinSquare in #2113
- Stop resetting virtio-net connections a server closes first by @BinSquare in #2118
- Upgrade rusqlite to 0.41 for the patched bundled SQLite (RUSTSEC-2026-0459) by @BinSquare in #2128
- Keep a host memory reserve VMs cannot take and charge branch children for growth by @BinSquare in #2127
- Ask before stopping a machine on delete, so a refused or declined delete leaves it running by @connorburgess in #2131
- Prepare SmolVM v1.34.1 for release by @BinSquare in #2135
- Bring a soft open-file limit above kern.maxfilesperproc down to the cap on macOS, so the limit raise_nofile_limit reports is the one in force by @connorburgess in #2132
- Leave no data directory behind when exec, status or stop name a machine that does not exist by @connorburgess in #2129
- Warn when --block-private keeps a named host unreachable by @BinSquare in #2146
- Register Rosetta itself as the x86_64 interpreter when the host answers its start-up ioctl by @BinSquare in #2148
- Make a mounted host directory belong to the workload user so a non-root workload can write to it by @BinSquare in #2149
- Record the image platform on the machine so a Rosetta machine can be created from an amd64 image by @BinSquare in #2147
- Bump libkrun so a Rosetta machine runs amd64 programs directly and a macOS machine stops promptly by @BinSquare in #2150
- Keep a cache disk's chain on its shared base when compaction shortens it by @BinSquare in #2145
- Satisfy Rust 1.100's needless_bool lint in connect_in_progress on Windows by @BinSquare in #2154
- Bound branch admission and reported capacity by the VM slice's memory limit, not just host free memory by @BinSquare in #2152
- Stop throttling the VM slice and reclaim it from the pressure guard instead by @BinSquare in #2153
- Release a paused branch child's VM lock so the memory pressure guard can resume it by @BinSquare in #2157
- Keep a restored machine's local image on its storage disk instead of mounting the capturing host's archive by @BinSquare in #2163
- Update quinn-udp to 0.5.16 for RUSTSEC-2026-0538 by @BinSquare in #2165
- Count every symlink with one mode in the agent rootfs digest so a Mac checkpoint restores on Linux by @BinSquare in #2162
- Carry guest traffic in 64 KB frames over the gateway link so downloads use a quarter of the CPU by @BinSquare in #2168
- Pin libkrun 518949b4 and libkrunfw 0fae3853, rebuilt for every platform by @BinSquare in #2169
- Reserve tmpfs for concurrent RAM captures and sweep abandoned checkpoint scratch at serve start by @BinSquare in #2173
- Let a packed image's branch take the deferred checkpoint save and say when the VM died mid-save by @BinSquare in #2174
- Integrate and validate Docker Engine, automatic ports, and nested Rosetta support by @BinSquare in #2172
- Run x86_64 images in containers Docker starts inside a Rosetta machine, keeping their PID by @BinSquare in #2093
- Serve the Docker Engine API from smolvm, every container a machine by @BinSquare in #2114
- Publish the ports a machine starts listening on, with --auto-ports by @BinSquare in #2136
- Give engine containers user-defined networks, so Docker Compose stacks run by @BinSquare in #2115
- Let engine containers reach the Docker socket, so Testcontainers and Dev Containers work by @BinSquare in #2116
- Branch engine containers from a warm base when many of one image run by @BinSquare in #2117
- Publish engine container ports on the address each one names by @BinSquare in #2119
- Give engine containers a volume for each VOLUME their image declares by @BinSquare in #2120
- Move images in and out of the engine: save, load, push, commit, import, export by @BinSquare in #2121
- Run --network container: containers in that container's machine by @BinSquare in #2122
- Give engine networks IPv6 by @BinSquare in #2123
- Run the Docker API on demand with independent workload supervisors by @BinSquare in #2175
- Fix Buildx volume permissions and macOS restart stalls by @BinSquare in #2178
- Improve default macOS shared-volume write performance by @BinSquare in #2179
- engine: speed up macOS Buildx with automatic overlayfs snapshots by @BinSquare in #2181
- Run the guest keep-alive init as root while workloads and execs keep the image user and its supplementary groups. by @BinSquare in #2004
- engine: fix multi-stage Buildx builds containing deleted files by @BinSquare in #2183
- Scrub injected credential values from what a credential host sends back by @BinSquare in #2180
- Re-authorize a restored checkpoint's credential bindings from the CLI, and refuse a start that could not inject them by @BinSquare in #2182
- Sweep a deleted machine's pause-operation lock along with its fork-operation lock by @connorburgess in #2184
- Let machine update set and remove labels, in any machine state by @josmo in #2143
- Leave the Docker Engine API opt-in so installing or upgrading smolvm never switches the user's Docker context by @BinSquare in #2186
- Bump every workspace crate and the nix flake to 1.35.0 by @BinSquare in #2185
- fix(network): retain OS-allocated local TCP listeners by @kumanday in #2112
- Retry a checkpoint part the object store refuses with a transient error by @BinSquare in #2191
- fix(shim): preserve foreground helper exit statuses by @hfiguera in #2190
- Delete the image seed builder when a CLI start is interrupted, and reap builders whose owner exited (#2083) by @rdslw in #2188
- Honor SMOLVM_DATA_DIR and --state-dir on macOS by @BinSquare in #2193
- Map a mounted host directory to the workload user again, not the keep-alive init's root, so a non-root workload can write to it by @josmo in #2189
- Open the Nix flake bump from main and run its required attribution check, so the bump PR can merge by @BinSquare in #2194
- Bind the port forward tests' ports before using them, instead of picking a free port and binding it again later by @BinSquare in #2195
- engine: use an on-demand native Buildx builder by @BinSquare in #2196
- perf(engine): reduce container lifecycle overhead by @BinSquare in #2198
- perf(engine): improve streaming output throughput by @BinSquare in #2200
- perf(engine): bound log tail reads and stream binary payloads by @BinSquare in #2201
- Compile the auto ports test's port helper only on Unix, where its one caller runs by @BinSquare in #2199
- Keep an image's files under /run when a container starts by @BinSquare in #2203
- Leave the Docker context alone when an engine with its own state directory is set up, and remove its registration by name by @BinSquare in #2202
- Stop a workload supervisor on SIGTERM and when its engine state is deleted, whoever holds the warm base lock by @BinSquare in #2204
- Start a display without a host GPU, check the host GPU before a --gpu start, and finish stop and delete around a process the kernel will not let exit by @BinSquare in #2210
- Allow ARM cloud checkpoints to return to macOS by @BinSquare in #2216
- Refuse a staged sync entry whose parent leads outside the mount through a symlink, so a guest cannot delete host files by @BinSquare in #2242
- Serve at most eight workload log connections, closing the oldest, so a guest cannot exhaust host threads by @BinSquare in #2243
- Bump libkrun so a resumed macOS machine releases the memory its guest frees and keeps it out of checkpoints by @BinSquare in #2244
- Trim the guest's disks before a capture, so deleted files leave the checkpoint and the host disk by @BinSquare in #2245
- Forget a host's learned addresses when a running machine's allow list is left with no hosts by @josmo in #2142
- Point exec and cp on a paused machine at resume, not at a start that refuses it by @connorburgess in #2167
- Bump libkrun so restored macOS machines keep later writes in checkpoints and qcow2 discards free host disk space by @BinSquare in #2248
- Preserve local-image machines across export and restore by @Vishv07 in #1980
- Preserve packed network restrictions and apply overrides atomically by @Vishv07 in #2006
- Clone the case-sensitive layers image instead of formatting a new one by @BABTUNA in #1713
- Preserve staged files when an interactive output pipe closes by @connorburgess in #2164
- Diagnose unsupported macOS virtualization without masking other failures by @Bnjoroge1 in #1323
- Allow disk growth before first boot by @BinSquare in #2211
- Expose machine files and harden engine storage workflows by @BinSquare in #2206
- Close failed port-forward tunnels and reap reply readers by @BinSquare in #2214
- Fix Docker container name filtering by @BinSquare in #2225
- Speed up and isolate first-use disk template expansion by @BinSquare in #2229
- Fix Docker networking and persistent VM lifecycle by @BinSquare in #2234
- Serialize overlay remounts so concurrent prepares don't race by @Liamso in #2166
- Fix interactive stream stalls and idle wakeups by @BinSquare in #2250
- Report Docker container resources from guest kernel accounting by @BinSquare in #2228
- Preserve image index digests for Docker image lookup by @BinSquare in #2224
- Hold back the growth already promised to running branch children when admitting a branch by @BinSquare in #2205
- Share local images with managed Kubernetes and recover filesystem notifications by @BinSquare in #2219
- fix(engine): stop polling idle Docker event streams by @BinSquare in #2251
- fix(checkpoint): retain booted rootfs after app updates by @BinSquare in #2253
- Preserve container sessions and discover local apps by @BinSquare in #2254
- Build a restored checkpoint over the most similar tree the node has, not only a recorded ancestor by @BinSquare in #2255
- Clean up disconnected sessions when guest input is blocked by @BinSquare in #2256
- chore(nix): bump flake to 1.35.3 by @github-actions[bot] in #2249
- Add machine credentials refresh, which hands a running machine new credential values from this shell without a restart by @BinSquare in #2257
- Approve the Nix flake bump PR's held checks, so a release's bump can merge by @BinSquare in #2258
- Let the Nix package keep the guest rootfs's links, and build the flake in CI by @BinSquare in #2261
- Bump libkrun so a Windows guest rewrite keeps a file's owner and a share can serve a default owner by @BinSquare in #2262
- Let a host mount name the guest owner of its files (-v HOST:GUEST:uid=N[,gid=N]) by @BinSquare in #2260
- Keep pack and OCI layer extraction from touching anything outside the layer by @BinSquare in #2264
- Reuse a pack's extraction only for the artifact it came from, and key bundled libraries by SHA-256 by @BinSquare in #2266
- Load a pack's own libraries only when they came from the executable running by @BinSquare in #2267
- Serve only the host on the guest agent's vsock listeners by @BinSquare in #2268
- Keep host loopback closed to gateway flows under --block-private by @BinSquare in #2269
- Pin libkrun at the share-confinement fixes by @BinSquare in #2271
- Add on-demand SSH and SFTP for seamless environment access by @BinSquare in #2272
- Preserve image-backed containers across VM pause and resume by @BinSquare in #2274
- Expose checkpoint reader requirements before local offload by @BinSquare in #2277
- Keep pod volume copies private to the VMM and honor read-only volume mounts by @BinSquare in #2270
- Support POSIX ACLs on a machine's ext4 disks by @BinSquare in #2276
- Keep guest root ownership consistent across hosts by @BinSquare in #2279
- Preserve guest permissions when installing the runtime by @BinSquare in #2281
- Preserve PAX filenames and links containing newlines by @BinSquare in #2283
- Relocate checkpoint mounts without losing ownership by @BinSquare in #2284
- chore(nix): bump flake to 1.35.4 by @github-actions[bot] in #2263
- Preserve machine ownership across lifecycle and transfer operations by @BinSquare in #2289
- Preserve workload dependencies during transfers by @BinSquare in #2290
- Unpack image layers whose entries use absolute paths by @BinSquare in #2291
New Contributors
- @rdslw made their first contribution in #2082
- @connorburgess made their first contribution in #2131
- @josmo made their first contribution in #2143
- @kumanday made their first contribution in #2112
- @Liamso made their first contribution in #2166
Full Changelog :
v1.34.0...v1.35.5 -
🔗 exe.dev Rex-on-exe rss
Using Rex to Access exe
If you’re one of the “lucky few” who’s running Rex as their daily shell, adding exe.dev hosts to Rex is easy. Create a new vm with
ssh exe.dev new, and then, from inside a Rex terminal, run:rex server install ssh://<your-vm-name>.exe.xyzThis installs the Rex server on your exe VM. After that, you can connect using the
ssh://URLs, and you’re all set.With that out of the way, it's kind of fun to look under the hood to see how it all works.
What's All the Fuss About?
In an agentic world, what's old is new again, and many of us are doing work on remote machines rather than our laptops. Some of the reasons for this are:
- VMs isolate agents
- VMs facilitate parallelism
- We can do "dev-is-prod" in VMs by developing and deploying on the same machine
Working on remote machines kinda stinks, without rich affordances. If you SSH to a remote machine and you close your laptop, your session will drop, taking all of its state with it. This is not a new problem. Tailscale abstracts away the network so that your session doesn't drop.
moshintroduces a terminal synchronization protocol and is resilient to drops. Eternal Terminal is similar to Mosh.tmuxandscreenvirtualize your sessions, so you can reconnect to them.zmx,tmate,dtach,atch,abudco,reptyr... so many options in this space. Perhaps the most common approach is tmux , but it comes with one major downside: you have to use tmux, and now things as simple as splitting your terminal into two panes becomeCtrl-B ", and who's got time for all that?Rex splits up the problems nicely. The Rex server runs on the remote machine, and manages multiple sessions (which in their terminology contain windows, which contain blocks, which are terminals). The Rex server listens locally on a Unix socket. The protocol is HTTP. If the server is killed, all its sessions go with it. That's not supposed to happen very often. This Unix socket is forwarded over SSH to your Mac, where the client app runs. The client app displays whatever sessions are available. The state lives on the Rex server on the remote machine, so when you create a split from the command line on your Linux machine, it is reflected in the client app.
If you (or your agent) want to do some advanced trickery, Rex ships with an
llms.txtwhich you can pull out with something likecurl -s --unix-socket /run/user/$(id -u)/rex/server.sock http://rex/llms.txt. It explains the protocols at quite some length and enables giving your session to an agent.Session Persistence, Terminals, Apples, and Oranges
There are several interwoven concerns at play when doing session persistence. Different tools solve different subsets of the problems. The table below highlights which tools solve which bits of the problem. I'm delighted that Rex is trying to solve many of the problems in one tool, rather than forcing me to cobble together solutions from multiple. Here at exe, we've felt many of the same problems and it's no surprise that
exe- scrolland our Mac, iOS, and web apps share similar underpinnings (e.g.,ghosttyfor terminal emulation and a unix socket on the server).I want to highlight "good for agents" in the table below: When the pi coding agent came on the scene, I realized that tmux wasn't just a terminal multiplexer. It was a CLI (
tmux capture-pane,tmux send-keys) to let an agent manipulate a terminal session.As you look through the table, note how much SSH is doing. I think there's a lot of space for more approaches to auth and connectivity; SSH is showing its age. I'm particularly excited about systems like
tailcatandirohand web-based solutions. There are enough dimensions here that you can combine tools to get great experiences, but not all bundling combinations have been tried yet.| Plain SSH| SSH over Tailscale| Mosh| tmux| dtach| Terminal apps| Rex| exe- scroll| exe.dev apps
---|---|---|---|---|---|---|---|---|---
Auth| SSH| Tailscale identity| SSH| Unix socket| Unix socket| n/a| Unix socket via SSH or Tailscale| Unix socket| HTTP cookies or SSH
Transport| TCP| WireGuard (UDP)| TCP to initiate, then UDP| Unix socket| Unix socket| Local pty| SSH or Tailscale| Unix socket| HTTPS or SSH
Process model| 1/connection| 1/connection| 1/session| 1 process, N terminals| 1/session| 1 app process, N terminals| 1/machine, N terminals| 1/terminal| exe-scroll
Switching networks| No| Yes| Yes| Partly1| Partly1| n/a| Yes| Yes| Yes
Multiple clients to same terminal| No| No| No| Yes| Yes| n/a| Yes| Yes| Yes
Outlives the connection| No| Yes| Yes2| Yes| Yes| n/a| Yes| Yes| Yes
Scrollback after reconnect| No| No| No| Yes| No| n/a| Yes| Yes| Yes
Splits| n/a| n/a| n/a| Yes| n/a| Yes| Yes| n/a| n/a
Native affordances| Yes| Yes| Partly3| No| n/a| Yes| Yes| n/a4| Yes
Good for agents| Partly5| Partly5| No| Yes6| No| No| Yes| Yes| Yes
Scriptable| Partly7| Partly7| No| Yes| No| n/a| Yes| Yes| Not sure
Speculative local echo| No| No| Yes| No| No| n/a| No| No| No
Viewing remote port| Yes| Yes| No| n/a| n/a| n/a| Yes| n/a| Yes- Reattach
- Same client only
- No scrollback
- Via the apps
- One-off commands
send-keysandcapture-pane- Commands only
One Last Thing
Vincent was kind enough to record a demo; check it out!
-
🔗 The Pragmatic Engineer The Pulse: What can we learn from the Railway hack? rss
Hi, this is Gergely with a bonus, free issue of the Pragmatic Engineer Newsletter. In every issue, I cover Big Tech and startups through the lens of senior engineers and engineering leaders. Today, we cover one out of four topics from last week 's issue of The Pulse . Full subscribers received the article below 7 days ago. If you 've been forwarded this email, you can subscribe here .
Over the past two weeks I've talked with several CTOs and founders at infra companies, and in those circles, it's an open secret that companies are being targeted by what looks like Chinese attackers, using abliterated AI models (those with no safeguards). These attackers seem to only want AI model keys; most likely to sell at discounted rates. "Popping" an infra company and accessing thousands of AI keys can be profitable, so it's economical to spend heavily on offensive abliterated models.
Cloud provider Railway was one of the several infra providers that was hacked two weeks ago, with customer secrets leaked. The company has released a very detailed postmortem, which is the most in-depth description of how such an attack happens and how fast attackers adapt.
At a high level, this is what happened:
- Phase #1: Several unsuccessful exploit attempts. On 18 Oct, the attacker created dummy Railway accounts and tried unsuccessfully to get into the company's systems. The attacks are blocked, but the attacker did not give up.
- Phase #2: Get Railway 's monorepo code (5 steps in 11 hours). The steps:
- Attacker finds a vulnerability so they can read files on Railway's build system
- -> steals build credentials
- -> tries the credentials on several internal systems
- -> accesses a Temporal cluster that stores build histories
- -> finds Railway's monorepo as a build history and downloads it
- Phase #3: Gain SSH access to Railway 's cloud environment (4 steps in 10 hours):
- Scans the downloaded code; tries using old endpoints
- -> Gets a short-lived cloud credential by exploiting a misconfigured OpenID Connect binding in the deploy pipeline
- -> Uses the short-lived credential to pull a long-lived cloud credential
- -> Finds an SSH key with the long-lived cloud credential
- Phase #4: Get access to customers ' AI provider keys (3 steps in 3 hours):
- With cloud access, they query the production database and access encrypted environment variables. The attacker filters for AI provider keys
- -> Figures out that there's a key management service that can decrypt the keys, which the attacker has access to with their access to the cloud environment
- -> Calls the key management service to decrypt customer secrets (AI provider keys)
Let's visualize how the attack unfolded:
Visualizing
the attack on RailwayI talked with Railway founder and CEO Jake Cooper, who said the attack was especially frustrating because at one point, they were only minutes behind the attacker: it was down to 1-8 minutes that the attack could unfold in the way it did because Railway's team was alerted to their build system's credentials being probed on internal systems eight minutes after the attacker started in phase #2. Railway revoked credentials the attacker used to download the monorepo just one minute after the attacker used them:
Frustrating:
in phase #2, Railway's team got close to stopping the attackWhat makes attacks by abliterated AI models different
Railway's summary is the first in-depth account of how an attack from an offensive AI model plays out, and there are several noteworthy details:
From the attacker's side:
- Stolen code can be exploited within hours by an AI model. If a human got access to Railway's monorepo, it would have likely taken days or weeks for them to figure out the weaknesses to launch further attacks at. But with AI models, all this is sped up: six hours after downloading the code, the attacker figured out a plan to get access to the AI provider keys, and knew where to look from then on.
- Abliterated AI models are like bloodhounds: relentless in chasing their goal. The offensive AI model just kept going and going, trying to get access to ever more systems with the sole goal of accessing AI provider keys. It's hard to imagine such durability by a human in keeping going through hoop after hoop to finally get access to AI keys!
- Attackers never give up, not even after all doors and windows are sealed shut. Railway evicted the attacker and revoked all the paths they used to get in. But the attacker returned and probed for new weaknesses the same night!
From the defender's point of view:
- Storing hashes of customer secrets is a very smart approach. As soon as Railway discovered the breach, they sent over the hashes of AI provider keys to all AI providers, so those providers could cancel them to avoid the attacker draining customer accounts. Hashing allowed Railway to send the keys without knowing them, and for providers to revoke them immediately.
- Defenders are handicapped by models ' capabilities. Attackers have access to abliterated AI models, while the models Railway has for defense - from the likes of OpenAI and Anthropic - refuse to engage in cybersecurity activity, including defensive work. Railway had no access to Project Glasswing during the incident, which would have allowed removal of some restrictions. As of today, Railway does have access, but many infra companies don't have that privilege.
- Railway decided to move to a new build system, instead of patching the existing one. Once Railway realized that its build infra was how the attacker gained entry, they shut down all builds. This was a problem for customers, given they needed to re-deploy builds with rotated keys! Railway decided to move every customer to an unreleased build system, and not attempt to patch the existing one. Fortunately for Railway, they had the new build system nearly ready to go!
During such an attack, the vendor often has to very quickly choose between "bad" and "worse" decisions. Railway faced a couple of these:
- To simply notify customers that their API keys were leaked, or immediately notify vendors like Anthropic and OpenAI, sending over API key hashes? Railway did the latter at the risk of upsetting some customers, and even causing unaffected customers' services to stop working until they created and set up a new API key. The trade-off was that this limited overall financial damage.
- Should Railway have allowed builds to happen after revoking the attacker's build system credentials? Allowing customers to do builds would have meant less service disruption, but the attacker could have returned via a slightly different path and stolen the rotated keys. Railway decided to bite the bullet by halting builds and rebuilding its build system in a matter of hours.
Lessons from this incident
I'm impressed by how much Railway has reflected on the structural problems that made it easier for the attacker to succeed, and how the company fixed them:
- Builds should not run on shared machines. The whole attack started with the attacker being able to attack the build's isolation boundary (the sandbox on the VM), and getting access to the build machine's environment. Since that build machine ran several customers' builds, it had credentials that were valuable to the attacker. Railway has now rebuilt its build stack so that each build gets its own throwaway virtual machine - which is a much stronger boundary than a sandbox on a VM.
- Add fine-grained access control for all internal secrets. Assume that an attacker will appear within your trust boundary and try to use secrets to get access to internal services. After the attack, Railway rebuilt its CI system to separate out sensitive components, with fine-grained access control. Getting access to important and sensitive credentials now requires 2FA, and even biometrics.
- Assume that attackers have full access to your source code. The attacker was able to come up with a better plan of attack only after getting access to Railway's source code. Securing all of your source code is very hard - and might not even be possible in the context of social engineering attacks via an employee. So, design security as if attackers already have full source code access.
- Decommission old, unused systems. The attacker probed credentials on Railway's old systems, and although they didn't get far, they could have found more weaknesses. Following this attack, Railway has shut down old, unused systems.
- Increase logging and alerting. Even if you do all of the above, an attacker could get access to your systems in unexpected or novel ways. As and when this happens, ensure that you will be alerted for unusual usage patterns, like some services being accessed with invalid or old credentials, unusual internal network activity, etc.
- It 's essential to respond to suspicious activity within minutes, not hours or days later. Attackers with AI are much faster at hopping between systems than we've been used to seeing. Defenders have the advantage that they can spot unusual patterns; after all, an attacker is fumbling around inside an unfamiliar system. But you need to act fast to evict an attacker inside your system!
**Seeking to gain from competitors ' problems: what goes around, comes
around**
There's an unwritten rule among software vendors that you don't turn competitors' outages into a sales pitch to try and poach their customers for yourself.
But Northflank evidently didn't get this memo. On the day of Railway's outage, the market rival published a blog post titled "How to migrate off Railway." The article started by linking to Railway's security incident disclosure, and explained how to safely migrate to Northflank. In the article, Northflank also boasted about its security capabilities:
"Security controls also include BYOC, workload isolation, network security, and envelope encryption, helping teams manage infrastructure access and reduce exposure."
The article reads like a naked attempt to grab customers from Northflank's rival, stating: "Railway got hacked, come on over to Northflank, which is a platform that cares about security."
Any engineering teams that decided to take the offer ended up getting hacked not once, but twice. Nine days after Railway's hack, Northflank got hacked in a near-identical way. From Northflank's incident summary:
"The first known decryption of [customer AI] secrets occurred between 02:39 UTC and 03:08 UTC on 30 October. Northflank received its first security platform alert at 11:43 UTC, and our engineers responded within minutes. The exploit was patched within 60 minutes of notification, and customers were notified within two hours.
Some customers have reported unauthorised use of AI secrets. Please rotate all secrets now, both integration secrets and project secrets, even if you haven't seen suspicious activity. We recommend starting with AI provider keys, cloud provider credentials, payment provider keys, private keys, and database and other service credentials.
We also recommend reviewing your provider logs for unusual activity. If you have seen unexpected AI usage or spend, contact your AI providers directly, such as OpenAI and Anthropic."
So, Northflank took nine hours to detect that customer secrets had been stolen, 11 hours to notify customers, and - unlike Railway - they did not proactively notify AI providers to revoke the keys. Objectively, this is a worse response than Railway's, yet it was Northflank that tried to capitalize on the security outage.
In this particular context, companies would do better to help other players in the market, rather than dunk on their competitors, and indeed, Railway's CEO texted Northflank to offer support and information about their attack. At first glance, this might appear a bit counter-intuitive to help rivals, but Jake Cooper realized what Northflank's leadership seems to have missed: that it's bad for all infra providers if many of them get hacked because customers will stop trusting all infra providers! It's in the interest of providers to collaborate on this matter and harden their own security. Once they do so, then companies win the market based on features, pricing, and innovation.
Plus, it's just a very short-sighted way of doing business to try to capitalize on novel security incidents, especially as Northflank seems to have been worse at dealing with the breach than the competitor they went after!
I have no affiliation with Railway or Northflank and struggle to see why Northflank did not remove the article about Railway's security incident article. One guess would be that it's a sign the business isn't exactly thriving, and that they're ready to try anything to keep things afloat.
Read the full issue of The Pulse this is from, or check out this week 's The Pulse. This week's issue covers:
- Anthropic: the largest-ever IPO. The leading AI frontier lab raised $107B with its IPO, and around 600 early employees could see gains of $100M or more. It's absolutely incredible for a startup that is only five-and-a-half years old.
- Is Amazon 's writing culture collapsing because of AI? A former Amazon software engineer sees signs that written artifacts - the 'six-pager' documents the company uses to promote good decision making - are increasingly AI-generated and AI-read, and warns it's not a positive development.
- Meta struggles to understand devs & reverses Conductor shutdown. Meta shuttered the AI coding harness Conductor after acquiring it, but is now reversing its decision - possibly after learning that a rival harness, T3 Code, is getting four times the usage of the latest Gemini model. Oops!
- Is AI making us pay off decades of tech debt? The industry is currently on a speedrun of vulnerabilities being uncovered and patched or exploited. One way of looking at it could be that we're on a speedrun to pay off decades of tech debt.
-
🔗 Works in Progress The trouble with serendipity rss
Saloni Dattani explores accidental discoveries in history, and comes away learning that scientists ' lives were messier than she expected.
This is a column: a lighter piece from the Works in Progress extended universe, designed to be enjoyed inprint. If you'd like to opt out of columns, or any other section, you can do so here.
People love accidental discoveries. Penicillin's discovery by Alexander Fleming is a classic example. Fungal spores wafted in through an open window, fell onto a plate of bacterial colonies, and dissolved them. Another is Louis Pasteur's discovery of a chicken cholera vaccine, the second vaccine ever developed. After Pasteur left a broth overexposed to oxygen, it went stale. But he ran out of fresh broth, so used it anyway to study the effects of an infection, and found, surprisingly, that it protected the chickens. Or how about the discovery of X-rays? Wilhelm Rontgen was working with a cathode ray tube in a dark room when he suddenly noticed a screen glowing nearby, even though he'd wrapped the tube in cardboard.
Though they're great stories, I've come to believe none of them happened that way. Rontgen had his notes burned after his death, and the story is just a hypothesis. Pasteur was extremely secretive as well, and forbade his family from making his notes and letters public after his death. His grandson, however, did, and after poring over their contents, historians have found that the key experiments were done deliberately by Pasteur's then-assistant Émile Roux while Pasteur was away for his daughter's wedding.
And what about Fleming? His first paper describing penicillin in 1929 never says where the spores came from. Of course, it's hard to see how he could have known, given they would have been microscopic. But Fleming first told the window story in an interview in 1945, sixteen years after his first report, and his colleagues testified the window was 'seldom if ever opened'. They weren't able to replicate the discovery as he described, either: penicillin would have needed to be present on the plate before the bacteria grew, because it blocks bacteria from building their cell walls, rather than killing them once they've grown.
Several people have tried to work out what really happened. Fleming's would-be biographer Ronald Hare made dozens of attempts and found just one reliable way to reproduce the discovery that fit the facts. The spores, he argues, were an unusually productive strain; came from the lab of a fungal researcher on the floor below, rather than the window; settled on the plate roughly when Fleming seeded it with bacteria; Fleming forgot to incubate it; and all this happened during a cold spell in the summer that let the mold grow before the bacteria. Hare noted how much more serendipitous this sequence of events was: 'the odds against the occurrence of the phenomenon become almost astronomical', though he ultimately believed it. While writing this column, I read through many of his notes and letters archived at the Wellcome Library and have come to agree with his view: Hare was exceedingly careful in corroborating the events from multiple people and sources from the time.
Part of the reason I find the popular stories fascinating is because it's jarring to realize how little they're based on. I do expect some stories of accidental discovery will survive the test of time. In medicine, for example, it's fairly common to test a drug for one disease and find, unexpectedly, that it works for another: colchicine was used for centuries to treat gout before it was found effective against cardiovascular disease, and sildenafil (Viagra) was being tested for angina when its more famous effect was noticed. Side effects are difficult to predict.
But I wonder why the popular versions have survived so long. Maybe they're more enjoyable? They're certainly easier to recount than the other explanations, which are convoluted. A fungal spore floating through an open window to reveal a world-changing antibiotic is a far better dinner party story than a meandering one involving several more coincidences you've probably already forgotten. Or the stories make scientists feel just like us: anyone can stumble upon a discovery, and then the challenge is merely to... spend years turning it into something useful?
'Chance favors only the prepared mind', as Pasteur put it. I think there's something to it: the brilliance of these scientists isn't necessarily in their initial discoveries, but in seeing their potential and doing something with them. Edward Jenner, for example, wasn't the first to notice that cowpox infections protected against smallpox, but he documented it thoroughly and popularized the method, spreading smallpox vaccination worldwide.
But what bothers me is that calling these discoveries accidents is sometimes the opposite of reality. Pasteur and Roux, for example, carried out hundreds of experiments to find reliable methods to create new vaccines - the popular framing is actively misleading and diminishes their work.
My friend Niko McCarty recently dug into other famously serendipitous discoveries in biology, such as those of green fluorescent protein and nanopore sequencing, and explained they came from systematic trial and error. He also describes the idea of 'engineered serendipity': in optogenetics, for example, 'the key breakthrough came about because the inventors wrote down the exact requirements they were looking for [...] and then enumerated , or wrote down, all the ways they could possibly imagine to make this happen'. It makes me wonder if learning how they really happened could help understand how to make more discoveries systematically.
Yet I'm still left with questions. Why credit chance events instead of hard work? Why hide or burn your notebooks?
Messiness, mistakes, and privacy come to mind. But here's another theory: competition and rivalry. Gerald Geison, a historian of Pasteur, suggests the method he ultimately used to develop chicken cholera vaccines was 'remarkably simple' and could be applied to other diseases too: 'had he revealed immediately the method of attenuation through exposure to ordinary air, Pasteur might have faced a host of competitors in the search for other vaccines'. Pasteur was probably the best-paid scientist in France at the time, and sold his inventions commercially. His secrecy might have been rational: patents weren't allowed on medicines in France then, so keeping the method secret would have helped him maintain his monopoly on producing them. Pasteur was so cagey that he didn't allow his collaborators to take notes, took his notebooks with him when he traveled, and published his methods (without much detail) only months after announcing his discoveries.
Meanwhile, Wilhelm Rontgen, who discovered X-rays and had his notes burned after his death, had been in a long dispute with another scientist, Philipp Lenard. Lenard had spent years researching cathode rays before him, and shared his methods and discharge tube with Rontgen. Once Rontgen became famous, Lenard accused him of having robbed him of the discovery. That dispute, historians suggest, could have motivated the note- burning, but it's hard to know without being able to read them. (Incidentally, Émile Roux, too, had his notes burned periodically, and it's only because Pasteur's were released that we know what happened at all.)
Science seems like it should be above the messiness. It's an institution we've built to guard against our biases. But it's also just people - who forget, hide their notebooks from their colleagues, burn their papers, and spend years fighting over who deserves credit. It's shaped by rivalries, incentives, obsessions, and years of unglamorous work, most of which is forgotten. That, to me, makes it far more interesting than a story about an open window.
Saloni Dattani is an editor at Works in Progress.
-
🔗 Console.dev newsletter Sponsor: WarpBuild rss
WarpBuild - Braintrust, Raycast and Jane Street run CI on WarpBuild. Get started with $50 in free credits.
-
🔗 Console.dev newsletter Kiri rss
Docker Desktop alternative.
What we like: Single, Docker-compatible daemon (CLI, Compose, buildx). Performance optimized with a small memory footprint. Includes networks, volumes, k8s. Dev tools like auto-HTTPs endpoints with publicly sharable URLs. Supports macOS, Windows, Linux.
What we dislike: Non-native UI, unlike something like Orbstack (which is macOS only). “Machines” are containers with filesystem access, not true VMs.
-
🔗 Console.dev newsletter Jiff rss
Datetime library for Rust.
What we like: Understands timezones natively and handles daylight sayings. Built-in handling of common date operations like durations, differences, calculations, geo regions. Uses Rust-native formatting and display options, including friendly formats.
What we dislike: Shows you how complex dates and times actually are, but that probably means fewer bugs!
-
🔗 Console.dev newsletter Sponsor: Coresignal rss
Agentic B2B search for builders
-
🔗 @binaryninja@infosec.exchange Binary Ninja is in Japan! We're attending TenguCon and CODE BLUE this week. If mastodon
Binary Ninja is in Japan! We're attending TenguCon and CODE BLUE this week. If you're around, make sure to come say hi to the team!
-
🔗 anthropics/claude-code v2.1.328 release
What's changed
- Added auto mode for Claude Opus 4.6 and Sonnet 4.6 on Amazon Bedrock, Google Cloud's Agent Platform, Microsoft Foundry and Claude apps gateway; interactive sessions with no permission mode start in it
- Added
"onFailure": "block"formcp_toolhooks, as for command and HTTP hooks: a hook whose call fails blocks the action - Added a warning when a message from a session that skips permission prompts may be held and dropped by a cloud session
- Added a notice in
/statusandclaude doctorwhen an OpenTelemetry exporter has no endpoint and its data would likely be lost - Added
CLAUDE_CODE_DISABLE_DEFERRED_TOOL_RESUME, which lets a host stopclaude -p --resumeand--continuefrom running a tool call that a hook deferred - Added support for apps that embed Claude Code to switch on the policy plugin's
allowManagedModsOnlyoption; an admin's managed settings still win - Added a startup warning to the Claude apps gateway when a policy's
maxEffortLevelis not a valid effort level - Self-hosted runner: Added
--repository-folderto name the folder that sessions use for a repository at--capacity 1, in place of its path under the base folder, which can't be a symbolic link - Self-hosted runner: Added a start-up warning when the host's settings.json sets a default permission mode that sessions ignore
- Self-hosted runner: Added
--hook-labeltoclaude self-hosted-runner orchestrator, to hand chosen session labels to thespawn-runnerhook - Self-hosted runner: Added
--metadata key=valuetoclaude --environment, to label a session for thespawn-runnerhook - Self-hosted runner: Added
claude_code_self_hosted_orchestrator_session_queue_wait_by_reason_secondsto the orchestrator's/metrics, so a re-opened session's wait can be told from a new one's - Self-hosted runner: Added an orchestrator metric,
claude_code_self_hosted_orchestrator_sessions_given_up_total, that counts by cause how often Anthropic gave up starting a runner for a session - Fixed Bash commands in zsh stopping with a "not found" error at a word that starts with
=, such asecho ====or[ a == b ];=cmdno longer expands to a command's path - Fixed automatic compaction reusing the session's earlier system prompt instead of rebuilding it the way
/compactdoes - Fixed markdown rendering freezing on some very long or malformed input
- Fixed rare screen freezes
- Fixed Esc often being lost at a permission prompt or question when you typed straight after it; in terminals that send Alt as Esc and a key, an unused Alt or Option key now declines there
- Fixed a paste or a terminal's reply being typed into the prompt when a slow connection cut it in two
- Fixed saving a scheduled task erasing the project's other saved tasks when the scheduled tasks file can't be read, on third-party providers or with telemetry or feature flags turned off
- Fixed a scheduled task with a typo in the project's scheduled tasks file being deleted the next time that file was saved
- Fixed a case where a resumed cloud session could lose its compaction summary or recent messages when a message was saved late
- Fixed the token counts on the spinner and for subagents counting a retried reply twice, missing replies that were not streamed, and standing still while Claude thinks
- Fixed the error shown when usage credits run out mid-response, which named a rate limit
- Fixed auto mode failing every turn outside Claude Desktop with
CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETASset behind a gateway rejecting betas, on Bedrock, Agent Platform, Foundry or Claude apps gateway - Fixed
CLAUDE_STREAM_IDLE_TIMEOUT_MSnot lengthening the 5-minute connection limit on gateways, custom base URLs and cloud providers - Fixed some Claude Desktop sessions on third-party providers, other than scheduled tasks, ending for good with "Prompt is too long" after large tool results; the largest are now left out
- Fixed MCP tools whose input schema starts with
anyOf,oneOforallOfgoing missing on third-party providers or with telemetry or feature flags turned off - Fixed an MCP tool with an invalid input schema failing requests on third-party providers or with telemetry or feature flags turned off; the tool is now left out and Claude is told why
- Fixed effort being turned off for a subagent's model for the session if Bedrock, Google Cloud's Agent Platform or Foundry refused its progress summary's effort setting (regression in 2.1.327)
- Fixed Code Mode stopping a script when a permission prompt outside auto or bypass mode, a plan approval or a question stayed open for ten minutes
- Fixed Code Mode scripts in auto and bypass-permissions modes failing to call an MCP server that had connected while the previous script was running
- Fixed Code Mode scripts not running in the background in auto or bypass permissions mode in a session chosen in the
claude --resumepicker - Fixed Code Mode losing a loaded skill, hook context or a note typed with a permission approval when resuming a session in which one reply ran several scripts
- Fixed Claude not being told that a Code Mode script was cut off when the session was resumed from the picker or in a mode that asks for permission
- Fixed Code Mode silently using
undefinedfor top-level variables that an earlier failed script never set - Fixed Code Mode scripts not being told when a failing command's long output was cut
- Fixed Code Mode refusing valid scripts that start with a
{block - Fixed Code Mode refusing scripts that use both a top-level
awaitand a top-levelreturn - Fixed an @-mentioned small file not being attached in Code Mode after a script had read or written it
- Fixed Code Mode offering
write()andedit()to read-only subagents that can't call them - Fixed Claude starting a turn by itself in Code Mode when Esc was followed by a command such as
/model - Fixed Claude in Code Mode not being told to run workflows only when you ask, or the workflow size you set in
/config - Fixed Remote Control repeating the same disconnect message, and telling you to retry a session that can't reconnect
- Fixed a waiting permission prompt being lost, and its answer ignored, when a remote session restarted while the service was slow
- Fixed cloud sessions resuming a cleared conversation after a rewind followed by
/clear - Fixed a remote session losing a turn's tool calls and results when its runner or worker was lost after a dropped model stream had been retried
- Fixed cloud and Remote Control sessions that just started, or have an @ in their title, being unreachable in cross-session messaging from a session with Remote Control on
- Fixed Claude being told that cloud sessions can never reply; it now learns when a reply can come and how else to get the result
- Fixed
/diff, the Changes pane of Remote Control sessions and the diff beside an edit leaving out committed work after a command moved into another repository - Fixed Remote Control not showing a running workflow's agents when a session run by an IDE extension or other SDK app is opened over an hour after the workflow last made progress
- Remote Control: Fixed an idle Desktop or VS Code session showing as running after Remote Control is turned on
- Fixed the model saying background agents were still running after an SDK interrupt had stopped them
- Fixed Send now in the desktop app and SDK hosts telling Claude that a stopped web search found no results
- Fixed Cmd+letter being typed into the prompt in terminals that report Cmd
- Fixed Ctrl+click opening a link twice in GNOME Terminal, side mouse buttons acting as clicks, and the first wheel notch in the other direction being ignored after a pause, in fullscreen mode
- Fixed Shift+Enter in Konsole outside tmux and ssh, and Alt shortcuts on non-Latin keyboard layouts in terminals that speak the kitty keyboard protocol
- Linux: Fixed pasting in other apps freezing while Claude Code is suspended with Ctrl+Z, when
xcliporwl-copyis installed - Linux: Fixed Ctrl+V missing the clipboard image, pasting an old one or hanging
- Fixed text copied in fullscreen mode including the quote bar, losing spaces at line wraps when a drag scrolled upward, or missing words under the "Jump to bottom" pill
- Fixed an image path pasted into a
!command becoming an attachment - Fixed Ctrl+C showing no exit warning while the
?shortcuts list is open - Fixed Ctrl+R search in fullscreen mode and the
/themecolor editor picking the wrong row when keys arrive together, and keys being dropped there and in the search of/configand/plugin - Fixed wrong or missing colors inside GNU screen
- Fixed many background notifications cutting into the top border of open dialogs in fullscreen mode
- Fixed a message to a background agent showing a long file path in place of a pasted image
- Fixed
/goalremoving a skill's Stop hook, or ending early on another hook's result, when both had the same wording - Fixed
/bugsaying cancelled after the report was sent - Fixed Esc not dismissing the transcript share question for Pro and Max users
- Fixed
/hookslosing your place when going back - Fixed
/exportwriting a file named.txtwhen the name was left empty - Fixed
/terminal-setupin Zed replacing a symlinkedkeymap.jsonwith a plain file - Fixed
/install-github-appadding a code review workflow when asked to update the existing workflow file - Fixed
/pluginreopening a skill, or closing the open page, when a slow save or removal finished after you went back - Fixed
/pluginasking to uninstall the wrong plugin, or ignoring Esc, after leaving a plugin while a change was still running - Fixed typing and arrow keys not working on the
/pluginInstalled tab after a search with no results or a click on the tab row - Fixed holding Enter in
/pluginturning off several installed plugins - Fixed the
/usageplugin total stopping at 2,000 tokens on 1M context models, and low token estimates in/usageand/pluginwhen no model is picked - Fixed Esc on the Bedrock access keys step closing
/logininstead of going back - Fixed
/exitand Ctrl+D describing running work differently, and/exitwarning about a workflow that had stopped - Fixed Claude calling an artifact private after reading one in a shared folder or publishing to another organization's, and saying only named people can open one when its folder's people can too
- Fixed a plugin's toast sometimes showing another plugin's text
- Fixed a mod saved just after a turn began sometimes reloading mid-turn instead of at the turn's end
- Fixed one malformed
OTEL_RESOURCE_ATTRIBUTESentry dropping the variable's other labels from metric points, events, and spans. Now only that entry is left off - Fixed agent hooks running past their timeout while compacting after a request was refused as too large
- Fixed a crash at startup when
FORCE_COLORis set to a negative number - Fixed a crash in secret masking when the machine is almost out of memory
- Fixed the Bash sandbox on Linux renaming
.git/HEADafter each command when the branch name is not valid UTF-8 - Self-hosted runner: Fixed all running sessions being stopped when a proxy or web filter answered a poll with HTTP 200 and a body such as
{}; the runner now retries such a poll - Self-hosted runner: Fixed deletion of a kept clone's objects or refs, and of commits that existed only there, after a temporary disk error; that start now fails instead
- Fixed self-hosted runners stopping when their token ran out on a host whose clock is slow or was set back
- Self-hosted runner: Fixed sessions with Anthropic-managed git losing git access to GitHub after a script or hook in the session ran
claudeagain - Fixed self-hosted runners with Anthropic-managed git being unable to fetch or push where the machine's git config sets
http.proactiveAuth - Self-hosted runner: Fixed a runner that exited without telling the server when setup failed after it had registered; it now deregisters with a reason, and an on-demand runner reports the failed start
- Self-hosted runner: Fixed archiving or requeueing a session not taking effect while it waited for another session to prepare the same repository (
--capacityabove 1) - Self-hosted runner: Fixed a session with a damaged
.claude.jsonfailing every later start under--trust-workspace false; it now starts on defaults, with MCP servers turned off there on again - Self-hosted runner: Fixed a failed start's message losing the words that say what failed when a checkout hook or git printed a lot
- Fixed the self-hosted runner skipping its post-session hook when a disk stalled for a few seconds; on a dead disk a session's end can take 25 seconds longer by default
- Fixed self-hosted runners: a session that resumes in a new Claude config directory no longer loses its task list
- Fixed Claude not being told when a self-hosted session starts without one of its repositories, and why
- Self-hosted runner: Fixed
--correlation-idofclaude --environmentnot reaching thespawn-runnerhook - Fixed the self-hosted runner setup wizard's key rotation advice, which now warns that revoking a key stops the sessions running under it
- Improved
claude -pand SDK sessions to fetch managed-settings plugins that have their own git repository, in the background, for a later session - Improved how soon managed-settings plugins from a git marketplace load on a fresh machine in
claude -p, SDK and Claude Desktop sessions; a short run may exit up to 30 seconds later - Improved the time to resume large sessions
- Improved memory use when resuming a session with many images
- Improved memory use and response time in long SDK and desktop sessions that run slow commands or tools
- Improved Code Mode's speed in auto and bypass-permissions modes by removing a 0.75 second pause after most scripts
- Improved prompt caching for new Code Mode sessions that have MCP servers, and Claude is now told when a server is still connecting and when the list of servers changes
- Improved Code Mode's token use with shorter tool descriptions
- Improved Code Mode to show the command a script is running, and its output, while it runs
- Improved Code Mode edits: an edit that changes nothing no longer stops a script, and Claude is told where a failed edit matches or comes closest
- Improved Code Mode: Claude is now told which tool calls were still running when a script failed
- Improved how Claude starts dev servers in Code Mode's auto and bypass modes: Claude is told to run them as background tasks that show in
/tasks - Windows: Improved Code Mode by telling Claude that scripts' shell commands run in Git Bash and that PowerShell aliases run instead of functions with the same name
- Improved starting several in-process teammates at once: far fewer now fail with "Lock file is already being held"
- Improved the computer use approval dialog: it now shows each app's level of access and plainer warnings
- Improved cross-session messaging: Claude now explains that Remote Control is off when a cloud session or another computer is not listed
- Improved
claude -ptext output to say on stderr when a message from another session is held or dropped, and how to allow it - Improved Claude's answers on who can open an artifact it published: Claude is now told to check the artifact again instead of repeating the last publish's answer
- Improved resumed self-hosted runner sessions: Claude now checks whether its earlier work is still there, and says what is missing
- Changed plan mode and Bash prompts for Opus 4.6 and Sonnet 4.6 on third-party providers to use and offer auto mode, as on newer models;
disableAutoModeturns both off - Changed Code Mode to no longer run UserPromptSubmit hooks, managed ones included, on scripts' output; to redact that output, use a PostToolUse hook with
updatedToolOutput - Changed
/code-reviewon most models to report only bugs and CLAUDE.md violations; run/simplifyfor reuse, simplification and efficiency cleanups - Changed
/code-reviewto mark each finding Important, Pre-existing or Nit on most models, and to end each summary with a suggested fix; a clean review's list now reads "Code review found no issues." - Changed
deniedMcpServersentries of the formclaude.ai <name>to apply to that connector in cloud and self-hosted runner sessions too - Changed managed
PostToolUsehooks to no longer fire for calls refused before they ran: no log entry, rewrite, block or stop there;PostToolBatchgets most, not marked as refused - Changed
/bugto ask Yes or No before sending, so repeated Enters no longer send a report or open GitHub - Changed subagents in
claude -p, the Agent SDK, desktop and VS Code to wait for their own subagents by default whenCLAUDE_CODE_FORK_SUBAGENT=0is set - Changed
claude -pwithCLAUDE_CODE_FORK_SUBAGENT=0to count a background subagent and those it waits for against one 10-minute wait; raiseCLAUDE_CODE_PRINT_BG_WAIT_CEILING_MSfor longer chains - Changed a shell command rewritten by a PermissionRequest hook to a sandbox-excluded command to run outside the sandbox
- Changed the Claude in Chrome welcome screen and
/chrometo say that Claude Code asks before Claude acts on a site, unless your permission mode or a rule in/permissionsanswers - Changed Claude Desktop and Agent SDK sessions on third-party providers or with telemetry or feature flags off to end the turn when closed with a question open, instead of continuing without an answer
- Changed pasted text to be marked for Claude as pasted, on third-party providers or with telemetry or feature flags turned off
- Changed subagent progress summaries in terminal sessions on the Anthropic API to be written by the default small fast model from short notes, also with telemetry off, using far fewer tokens
- Changed how a sandbox that can't start is reported, unless
sandbox.failIfUnavailableis set: the next sandboxed Bash command is refused and says that the sandbox is off for the session - Changed
/list-agentsto show its list to you alone; Claude lists sessions itself when needed - Self-hosted runner: Changed the built-in
gh apito be off by default where settings guard Claude's GitHub tools by name;--use-anthropic-gh trueturns it on - Self-hosted runner: Changed a
claudethat a wrapper script runs before the session's ownclaudeis up, or after it has ended, to have no Anthropic-managed git - Self-hosted runner: Changed
CLAUDE_RUNNER_SESSION_UUIDandCLAUDE_CODE_REMOTE_SESSION_UUIDto both be set for the session and itscheckout,post-sessionandspawn-runnerhooks - Changed self-hosted runners at
--capacity 1to refuse a session earlier when the path of a repository it pushes to is a symbolic link - [VSCode] Added a notice when a message from another session is held, with a link to the settings file that can allow it
- [VSCode] Fixed the permission prompt cutting off its No button, reply field or title when the panel is low or a command, URL or description is long
- [VSCode] Fixed failed or blocked tool calls showing no reason or a reason cut short, and Glob and Grep counting an error as results
-
- November 18, 2026
-
🔗 IDA Plugin Updates IDA Plugin Updates on 2026-11-18 rss
IDA Plugin Updates on 2026-11-18
New Releases:
Activity:
- apiscout
- eb2e94ea: DB builder: refuse DEF files of the other bitness, parser follow-ups
- 42efe485: DB builder: check DEF files against named exports, review follow-ups
- 616d09ef: DB builder: name exports by ordinal only from DEF files (#7)
- eb8de9b0: Merge pull request #63 from danielplohmann/fix/ida-view-not-opened
- 66c698aa: IDA plugin: open the results view from a timer
- 8ac70a58: Merge pull request #61 from danielplohmann/ci/release-process
- 0519a86c: ci: adopt the shared release process for v3.0.0
- 2fb89f70: Merge pull request #60 from r0ny123/refactor/repo-layout
- 070f283e: Merge pull request #59 from r0ny123/feat/min-confidence-default
- df558b4d: Move the Binary Ninja plugin folder to plugins/binja_scout
- 74577494: Move the IDA and Ghidra plugins to plugins/
- 309e43ce: Run the DB builder as a module, vendored pefile in _vendor
- 3846483c: scan: drop hits with a confidence below 20 by default
- 20487906: Merge pull request #58 from r0ny123/feat/plugin-load-addresses
- 1783ca87: Merge pull request #57 from r0ny123/fix/review-followups
- 1f57e269: Merge pull request #56 from r0ny123/feat/symbols-keyed-speed
- 4ad4e54e: Merge pull request #54 from r0ny123/feat/api-hashes
- 9d507ad1: Merge pull request #53 from r0ny123/feat/explain-match
- 9086bf2b: Merge pull request #52 from r0ny123/feat/hit-confidence
- augur
- haruspex
- oh-my-pi
- rhabdomancer
- apiscout
-
🔗 exe.dev Hey Shelley, Fix My Monitor rss
Earlier this year, I was on the hunt for a new monitor. My old one was a 27” 4K (Dell U2720Q). I wanted something slightly bigger and ideally 5-6K. After doing a bit of research, I realized that my options were fairly limited. The Apple Pro Display XDR was pretty but 4x my budget. The Apple Studio Display was 5K and 27”, so it didn’t fit the bigger screen requirement. The Dell U3224KB was 2.5x my budget.
But then I lucked out and found a brand new Dell U3224KB for ~$1,100 on Facebook Marketplace. I was so excited when I plugged it in, but then I realized it had a manufacturing issue where these lights would just continuously cycle on and off. I think the intent was for them to turn on when my hand was near them, but they’d turn off for a few seconds and then turn right back on. It was almost like a perpetual notification coming in and distracting me from my work. I stopped using the monitor for a few months.

Any reasonable person would have tried to contact Dell support and have them fix the issue. But the thought of going through their website and figuring out how to chat with them and not having the original receipt just didn’t feel like a good use of time. So I just continued using my laptop and feeling sad about my purchase.
A few weeks ago, I saw that people were using agents to reverse-engineer and remove cruft from their smart TVs. That gave me the idea of asking Shelley to fix my monitor. After giving it access, I spun up a conversation with 6.1 Sol and gave it a video of the symptoms and asked it to figure out how to stop the lights from cycling without disabling the buttons.
Sol was able to read the firmware from the monitor, disassemble it and propose a few fixes. Over the course of two days (mostly because I kept getting distracted with life and work), it attempted to flash a few fixes that didn’t take. Then Astra stepped in and tried a few as well until ultimately it did a bad firmware flash and the audio controller just stopped working entirely. Astra and Opus tried to fix the issue to no avail: the audio controller had entered DFU mode and would not accept updates. Every attempt put it in an error state. We even booted up a Windows VM to see if we could get the original firmware updater to fix the thing. That failed too. After a few attempts, I gave up.
When I asked the agent, “What do I do now?” I got this response:
I’m sorry, Maisem. You wanted an annoying light fixed, and my mistake left you with a broken audio controller. That’s on me.
On the bright side, the lights completely went away. I was actually happier in this state. I didn’t particularly like the audio quality from the monitor anyway, and the lights were so distracting that the tradeoff was worth it.
Then Fable 5.2 launched and I decided to see if it could recover the audio controller.
Four minutes later, I got this:
Got it back. The monitor's audio/button controller is running again as the normal Dell device (not recovery mode). I loaded the original Dell firmware into its memory over USB.
But how?!
Turns out two things had to be true: the chip had to be freshly powered on, and the firmware had to be sent starting partway into Dell's file (offset 0x3000, the part the chip actually runs) instead of from the start. Apparently Astra had been trying to flash it incorrectly.
So I told Fable to fix the lights. It correctly flashed the same firmware that Astra had built. The lights all went off, and the audio still worked. But now the buttons didn’t work correctly.
So Fable restored the stock firmware, then followed it with a 2-byte change (as opposed to Astra’s 8-byte change) and that fixed the buttons not working. But now the lights remained on. This was arguably a great place to stop.
But I did not do that. In fact, I thought, why not push the model further? I asked Fable to have the lights come on when I touch the panel and then fade out after 10 seconds. It had me press the buttons so that it could watch the events, and about 18 minutes later, it had added a new routine to the firmware which would reset a timer after every press and then fade out the lights. It worked beautifully.
All this is to say that the AI models have gotten remarkably good and they can now do things that only a handful of people could do before. I could not have ever imagined doing something like this, but now it just took a few prompts. The possibilities are seemingly endless.
PS: My wife and friends tell me that I could have used black tape to cover the blinking lights. But where’s the fun in that?
-
🔗 smol-machines/smolvm smolvm v1.35.4 release
What's Changed
- docs: say that virtiofs DAX is off on arm64 hosts and SMOLVM_MOUNT_DAX does nothing there by @BinSquare in #2087
- Add smolvm docker: one command starts a Docker engine in a managed machine and points docker at it by @BinSquare in #2089
- Share the home directory with the smolvm docker machine at the same path by @BinSquare in #2090
- Resolve host.docker.internal to the host from smolvm docker containers by @BinSquare in #2091
- Fix a port race in the leader-exit test by @BinSquare in #2096
- Remove smolvm docker by @BinSquare in #2095
- Hand supplied credential values to a running embedded machine at once by @BinSquare in #2097
- Pin libkrunfw with UDP kept inside a TSI guest, and test it by @BinSquare in #2099
- Publish ports below 1024 on macOS, add IPv6 loopback to live-forwarded ports, and lift the 64-mapping cap by @BinSquare in #2092
- Return idle guest memory to the host within two minutes and cap new machines at half the host's RAM by @BinSquare in #2094
- Install a root-owned agent-rootfs when root runs install.sh by @rdslw in #2082
- Announce a changed file to the guest once per change by @BinSquare in #2102
- Answer guest DNS from a host cache that coalesces bursts and resends lost queries by @BinSquare in #2098
- Keep every disk chain under the branch depth limit: fold restored checkpoint layers and frozen-source chains by @BinSquare in #2103
- Exec sessions: commands the node owns, resumable after a dropped connection by @BinSquare in #2101
- Let a guest hold tens of thousands of connections on virtio-net and free their host sockets promptly by @BinSquare in #2104
- Scope the usage journal to the test's own thread by @BinSquare in #2106
- Pin libkrun 526be460 and libkrunfw f290c62b, rebuilt for every platform by @BinSquare in #2109
- Build the agent rootfs as non-root on hosts with user namespaces again by @BinSquare in #2107
- Answer a start missing the mediated interceptor with 400, not 500 by @BinSquare in #2108
- Run tests that need a released file lock free at once in their own process by @BinSquare in #2110
- Pin libkrun 9df62257 and libkrunfw 7f4d4950, rebuilt for every platform by @BinSquare in #2113
- Stop resetting virtio-net connections a server closes first by @BinSquare in #2118
- Upgrade rusqlite to 0.41 for the patched bundled SQLite (RUSTSEC-2026-0459) by @BinSquare in #2128
- Keep a host memory reserve VMs cannot take and charge branch children for growth by @BinSquare in #2127
- Ask before stopping a machine on delete, so a refused or declined delete leaves it running by @connorburgess in #2131
- Prepare SmolVM v1.34.1 for release by @BinSquare in #2135
- Bring a soft open-file limit above kern.maxfilesperproc down to the cap on macOS, so the limit raise_nofile_limit reports is the one in force by @connorburgess in #2132
- Leave no data directory behind when exec, status or stop name a machine that does not exist by @connorburgess in #2129
- Warn when --block-private keeps a named host unreachable by @BinSquare in #2146
- Register Rosetta itself as the x86_64 interpreter when the host answers its start-up ioctl by @BinSquare in #2148
- Make a mounted host directory belong to the workload user so a non-root workload can write to it by @BinSquare in #2149
- Record the image platform on the machine so a Rosetta machine can be created from an amd64 image by @BinSquare in #2147
- Bump libkrun so a Rosetta machine runs amd64 programs directly and a macOS machine stops promptly by @BinSquare in #2150
- Keep a cache disk's chain on its shared base when compaction shortens it by @BinSquare in #2145
- Satisfy Rust 1.100's needless_bool lint in connect_in_progress on Windows by @BinSquare in #2154
- Bound branch admission and reported capacity by the VM slice's memory limit, not just host free memory by @BinSquare in #2152
- Stop throttling the VM slice and reclaim it from the pressure guard instead by @BinSquare in #2153
- Release a paused branch child's VM lock so the memory pressure guard can resume it by @BinSquare in #2157
- Keep a restored machine's local image on its storage disk instead of mounting the capturing host's archive by @BinSquare in #2163
- Update quinn-udp to 0.5.16 for RUSTSEC-2026-0538 by @BinSquare in #2165
- Count every symlink with one mode in the agent rootfs digest so a Mac checkpoint restores on Linux by @BinSquare in #2162
- Carry guest traffic in 64 KB frames over the gateway link so downloads use a quarter of the CPU by @BinSquare in #2168
- Pin libkrun 518949b4 and libkrunfw 0fae3853, rebuilt for every platform by @BinSquare in #2169
- Reserve tmpfs for concurrent RAM captures and sweep abandoned checkpoint scratch at serve start by @BinSquare in #2173
- Let a packed image's branch take the deferred checkpoint save and say when the VM died mid-save by @BinSquare in #2174
- Integrate and validate Docker Engine, automatic ports, and nested Rosetta support by @BinSquare in #2172
- Run x86_64 images in containers Docker starts inside a Rosetta machine, keeping their PID by @BinSquare in #2093
- Serve the Docker Engine API from smolvm, every container a machine by @BinSquare in #2114
- Publish the ports a machine starts listening on, with --auto-ports by @BinSquare in #2136
- Give engine containers user-defined networks, so Docker Compose stacks run by @BinSquare in #2115
- Let engine containers reach the Docker socket, so Testcontainers and Dev Containers work by @BinSquare in #2116
- Branch engine containers from a warm base when many of one image run by @BinSquare in #2117
- Publish engine container ports on the address each one names by @BinSquare in #2119
- Give engine containers a volume for each VOLUME their image declares by @BinSquare in #2120
- Move images in and out of the engine: save, load, push, commit, import, export by @BinSquare in #2121
- Run --network container: containers in that container's machine by @BinSquare in #2122
- Give engine networks IPv6 by @BinSquare in #2123
- Run the Docker API on demand with independent workload supervisors by @BinSquare in #2175
- Fix Buildx volume permissions and macOS restart stalls by @BinSquare in #2178
- Improve default macOS shared-volume write performance by @BinSquare in #2179
- engine: speed up macOS Buildx with automatic overlayfs snapshots by @BinSquare in #2181
- Run the guest keep-alive init as root while workloads and execs keep the image user and its supplementary groups. by @BinSquare in #2004
- engine: fix multi-stage Buildx builds containing deleted files by @BinSquare in #2183
- Scrub injected credential values from what a credential host sends back by @BinSquare in #2180
- Re-authorize a restored checkpoint's credential bindings from the CLI, and refuse a start that could not inject them by @BinSquare in #2182
- Sweep a deleted machine's pause-operation lock along with its fork-operation lock by @connorburgess in #2184
- Let machine update set and remove labels, in any machine state by @josmo in #2143
- Leave the Docker Engine API opt-in so installing or upgrading smolvm never switches the user's Docker context by @BinSquare in #2186
- Bump every workspace crate and the nix flake to 1.35.0 by @BinSquare in #2185
- fix(network): retain OS-allocated local TCP listeners by @kumanday in #2112
- Retry a checkpoint part the object store refuses with a transient error by @BinSquare in #2191
- fix(shim): preserve foreground helper exit statuses by @hfiguera in #2190
- Delete the image seed builder when a CLI start is interrupted, and reap builders whose owner exited (#2083) by @rdslw in #2188
- Honor SMOLVM_DATA_DIR and --state-dir on macOS by @BinSquare in #2193
- Map a mounted host directory to the workload user again, not the keep-alive init's root, so a non-root workload can write to it by @josmo in #2189
- Open the Nix flake bump from main and run its required attribution check, so the bump PR can merge by @BinSquare in #2194
- Bind the port forward tests' ports before using them, instead of picking a free port and binding it again later by @BinSquare in #2195
- engine: use an on-demand native Buildx builder by @BinSquare in #2196
- perf(engine): reduce container lifecycle overhead by @BinSquare in #2198
- perf(engine): improve streaming output throughput by @BinSquare in #2200
- perf(engine): bound log tail reads and stream binary payloads by @BinSquare in #2201
- Compile the auto ports test's port helper only on Unix, where its one caller runs by @BinSquare in #2199
- Keep an image's files under /run when a container starts by @BinSquare in #2203
- Leave the Docker context alone when an engine with its own state directory is set up, and remove its registration by name by @BinSquare in #2202
- Stop a workload supervisor on SIGTERM and when its engine state is deleted, whoever holds the warm base lock by @BinSquare in #2204
- Start a display without a host GPU, check the host GPU before a --gpu start, and finish stop and delete around a process the kernel will not let exit by @BinSquare in #2210
- Allow ARM cloud checkpoints to return to macOS by @BinSquare in #2216
- Refuse a staged sync entry whose parent leads outside the mount through a symlink, so a guest cannot delete host files by @BinSquare in #2242
- Serve at most eight workload log connections, closing the oldest, so a guest cannot exhaust host threads by @BinSquare in #2243
- Bump libkrun so a resumed macOS machine releases the memory its guest frees and keeps it out of checkpoints by @BinSquare in #2244
- Trim the guest's disks before a capture, so deleted files leave the checkpoint and the host disk by @BinSquare in #2245
- Forget a host's learned addresses when a running machine's allow list is left with no hosts by @josmo in #2142
- Point exec and cp on a paused machine at resume, not at a start that refuses it by @connorburgess in #2167
- Bump libkrun so restored macOS machines keep later writes in checkpoints and qcow2 discards free host disk space by @BinSquare in #2248
- Preserve local-image machines across export and restore by @Vishv07 in #1980
- Preserve packed network restrictions and apply overrides atomically by @Vishv07 in #2006
- Clone the case-sensitive layers image instead of formatting a new one by @BABTUNA in #1713
- Preserve staged files when an interactive output pipe closes by @connorburgess in #2164
- Diagnose unsupported macOS virtualization without masking other failures by @Bnjoroge1 in #1323
- Allow disk growth before first boot by @BinSquare in #2211
- Expose machine files and harden engine storage workflows by @BinSquare in #2206
- Close failed port-forward tunnels and reap reply readers by @BinSquare in #2214
- Fix Docker container name filtering by @BinSquare in #2225
- Speed up and isolate first-use disk template expansion by @BinSquare in #2229
- Fix Docker networking and persistent VM lifecycle by @BinSquare in #2234
- Serialize overlay remounts so concurrent prepares don't race by @Liamso in #2166
- Fix interactive stream stalls and idle wakeups by @BinSquare in #2250
- Report Docker container resources from guest kernel accounting by @BinSquare in #2228
- Preserve image index digests for Docker image lookup by @BinSquare in #2224
- Hold back the growth already promised to running branch children when admitting a branch by @BinSquare in #2205
- Share local images with managed Kubernetes and recover filesystem notifications by @BinSquare in #2219
- fix(engine): stop polling idle Docker event streams by @BinSquare in #2251
- fix(checkpoint): retain booted rootfs after app updates by @BinSquare in #2253
- Preserve container sessions and discover local apps by @BinSquare in #2254
- Build a restored checkpoint over the most similar tree the node has, not only a recorded ancestor by @BinSquare in #2255
- Clean up disconnected sessions when guest input is blocked by @BinSquare in #2256
- chore(nix): bump flake to 1.35.3 by @github-actions[bot] in #2249
- Add machine credentials refresh, which hands a running machine new credential values from this shell without a restart by @BinSquare in #2257
- Approve the Nix flake bump PR's held checks, so a release's bump can merge by @BinSquare in #2258
New Contributors
- @rdslw made their first contribution in #2082
- @connorburgess made their first contribution in #2131
- @josmo made their first contribution in #2143
- @kumanday made their first contribution in #2112
- @Liamso made their first contribution in #2166
Full Changelog :
v1.34.0...v1.35.4 -
🔗 @HexRaysSA@infosec.exchange 🔧 IDA 9.5 brings native UEFI firmware support mastodon
🔧 IDA 9.5 brings native UEFI firmware support
Load a full SPI flash dump into one database. IDA maps the modules, names the globals, identifies known GUIDs and links protocol calls to their implementations across modules.
👉🏽 https://hex-rays.com/blog/introducing-native-uefi-firmware-support-in- ida-9.5
-
🔗 HexRaysSA/plugin-repository commits sync repo: +1 plugin, +4 releases, -1 release rss
sync repo: +1 plugin, +4 releases, -1 release ## New plugins - [apiscout](https://github.com/danielplohmann/apiscout) (3.0.0) ## New releases - [cfiscope](https://github.com/nightshift-labs-ai/cfiscope): 0.1.22 - [kflow](https://github.com/nightshift-labs-ai/kflow): 0.0.7 - [memlens](https://github.com/nightshift-labs-ai/memlens): 0.3.30 ## Changes - [memlens](https://github.com/nightshift-labs-ai/memlens): - removed version(s): 0.3.5 -
🔗 backnotprop/plannotator v0.29.0 release
Follow @plannotator on X for updates
Missed recent releases? Release | Highlights
---|---
v0.28.67 | Drag threads to Priority, Archive or Quiet, or onto another thread to combine them, mention another thread in your reply, Linear hover cards, pick any tag colour, a linked computer's pictures and files open here, pull request cards say why they could not load
v0.28.66 | Pick several threads and archive or snooze them at once, combine picked threads into one; Tidy follows your own words, rows take their tag's colour; filter and search by tag, files an agent's message names open beside the thread, swipe rows on phone or iPad; list can show archived threads, Antigravity and Orca use the Inbox; T3 Codex threads get replies, Open in lists JetBrains IDEs, Routines: run a saved prompt on a schedule
v0.28.65 | Take back a reply your agent has not received yet, over Tailscale, Plannotator opens only for your own account, tag a linked machine's threads; one tag across machines, T3 Code threads get the Inbox with no setup, long threads open on slow connections
v0.28.64 | Installs and updates download a smaller, compressed copy, a Videos filter on the Artifacts page, GitLab comments on a whole file get their own thread, pull request pictures and videos show in the Inbox
v0.28.63 | Pair Grok Bot and other cloud agents from Settings, Hermes Agent, OpenClaw and Muse Code can use the Inbox, add a thread to Priority to keep it on top, tag threads, and find each tag in the sidebar, Pull requests board as a table, with bulk Merge
v0.28.62 | Agents started from the Inbox now work on Windows, pick a model and effort when you start an agent, rules for your agents, written in your own words, post a thread's decisions on its pull request, the Inbox loads faster on a slow connection
v0.28.61 | Updates now update the Claude Code plugin too, an agent's chosen face shows on every icon of it, filter the Inbox list by pull request state, Modern dark shows section bands and the Reply button, one conversation no longer shows as two agents
v0.28.60 | Click a word to highlight it, a one-time Themes dialog, Settings → Rows rebuilt, tell your agent how you want your rows, starred threads as pills above the list, a pill for new messages out of view, a half-circle face picker with ten Glass colours, a new phone sidebar and reply box
v0.28.59 | A quieter Agents section in the sidebar, machine names only when agents run on more than one machine, agent icons that are always gently alive and lean toward your pointer
v0.28.58 | Start Codex from New message, an Agents section in the sidebar, start an agent in a folder on any drive, play audio attachments and comment at a moment, Claude Code's Plannotator tools work on Windows
v0.28.57 | Pin artifacts, and see every artifact on one page, filter the list by project, date or agent, a thread shows its pull requests and their state, choose what the sidebar shows, and in what order, Ask AI starts from Side in the selection bar
v0.28.56 | Questions can show trade-offs and a prototype to try, a thread with many big pictures no longer crashes the tab, Escape closes New message and keeps your draft, read threads stop being bold and keep their place, agent messages that name no thread start a new oneWhat's New in v0.29.0
TL;DR
- New: A redesigned code review window: two panes, a faster file tree, image diffs and a minimap
- New: Semantic diffs: moved, renamed and reformatted code drawn as what it is, in eleven languages
- New: Comment in a code review and talk it through with your agent, through the Inbox
- New: Code review in the Inbox is now a switch in Settings → Capabilities (off until you turn it on)
- New: Hide a pull request or a whole repository from Reviews and the PR board
- New: Playback speed for videos and recordings in the Inbox
- New: Routines:
plannotator routinecommands, a/create-routineskill, Edit and Runs tabs, a list filter - Fixed: On Claude Code 2.1.326 with a Team or Enterprise account, the agent could not open Plannotator
- Fixed: A linked machine whose Inbox started before Tailscale stayed "asleep"
- Fixed: Typing in the reply box on very long threads lagged, and undo took back one letter at a time
- Removed: Code Tour
v0.29.0 is the code review release. The review window that
plannotator reviewand/plannotator-reviewopen has been rebuilt: a new file tree, two panes with tabs, semantic diffs, image diffs, a minimap, one launch pad for guided reviews and review agents, and review comments that become conversations with your agent. In the Inbox, the Code review switch is now in Settings for everyone. The release also fixes two problems that stopped things working: Plannotator could not open from the agent on Claude Code 2.1.326 for Team and Enterprise accounts, and a linked machine could stay unreachable after Tailscale came back. The release has 48 PRs. Thirteen come from outside contributors: twelve fixes from @rudycelekli and a playback speed menu from @MaxKless, their first contribution.Fixed: Plannotator would not open from the agent on Claude Code 2.1.326
(Team and Enterprise)
Claude Code 2.1.326 added an "early run" rule to its built-in
cc-plugin-sec- defaultguard, which is on for Team and Enterprise accounts and on machines with managed settings. The rule refuses a plugin that starts a program repeating a tool call the model just made. Plannotator's Claude Code plugin starts the review window at exactly that moment, so on these accounts an agent'splannotatorcall (annotate, review, last) failed with:Plannotator could not start: plannotator: $.process.run: this repeats a Bash call that is not allowed; serve an allowed call at tool.runA
Bash(plannotator:*)allow rule did not help. Slash commands you typed yourself, such as/plannotator-review, still worked, and so did the Inbox.The plugin now waits for the tool's run step, where the guard allows it, and opens the window there. On a guarded machine the call first goes through your session's own permission check (your rules, mode or a prompt), as the guard requires. On older Claude Code versions nothing changes. One cost remains on guarded machines whose organization has its own tools, such as managed MCP servers or organization plugins: Claude Code may print one "plannotator: its hook was skipped" line per session. It is harmless, and it does not stop Plannotator from opening.
This was tested on Claude Code 2.1.287, 2.1.325 and 2.1.327 against a stand-in that follows the guard's rule, not on a guarded account itself. If Plannotator still does not open for you on a Team or Enterprise account after updating, please open an issue with the message you see.
A new code review window
The review window has been rebuilt from the file tree out. Everything it did before still works, with these changes:
- A new file tree. Changes and All files are one fast tree, built on Pierre's tree library. Group files by kind (Code, Docs, Tests, Generated) or by Git status (Committed, Staged, Unstaged, Untracked) from the tree's menu. Git status is no longer a separate tab: pick that grouping and it opens the same way. Git add and unstage sit on each row, long names shorten in the middle and keep their extension, and the arrow keys move through files and open each one.
- Two panes and tabs. "Open to the side" puts a second file beside the first, with a divider you can drag. Tabs sit in the header row, so opening a file never pushes the code down. Each tab can show the Diff, the Current file or the Original. A review you open again comes back with the same panes, tabs and divider.
- Image diffs. A changed image shows side by side, as a swipe with a divider you drag, or as an onion skin with an opacity slider. Highlight differences tints the pixels that changed, and an SVG can show as an image or as source.
- A minimap at the right edge of long diffs shows where the changes and comments are. Click it to jump there.
- One launch pad in the Agents tab: Guided Review and Review agent, each with a Start button that uses your saved picks. Your saved guides for this repository are listed under This diff, This PR and Earlier, with how much you have read, and can be renamed, downloaded, shared or deleted. Past runs list their findings by rank, and a click goes to the most serious one.
- Collapse all files sits in the top bar. On a commit-by-commit review, Expand all now stays on as you step from commit to commit.
- Cmd/Ctrl-click on a name now jumps straight to its definition when there is exactly one. Otherwise it opens References, as before.
- Large diffs open and scroll faster , and a tap right after a scroll is no longer lost.
Removed: Code Tour, with its dialog, settings and Mod+Shift+T shortcut. A review saved in tour mode opens as a normal code review. The nine first-run announcements in the review window are gone too.
Semantic diffs: moved and renamed code, drawn as such
A plain diff shows moved code as a deletion in one place and an addition in another. With semantic diffs, the review window draws it as what it is:
- Moved code folds into one "Moved N lines" row in its old place, with a band to where it went. Code that moved and also changed stays open, in purple.
- A rename highlights only the name that changed.
- Code that was only reformatted is drawn quiet and grey, so a real edit next to it stands out.
- Each block is labelled moved, moved & edited, renamed, reformatted, extracted or inlined. Each file header has a sem N menu listing that file's changes, and the Semantic diff tab lists every change in the review by name, for example
rate -> taxRate. A row in either one jumps to the change.
It reads TypeScript and TSX, JavaScript, Python, Go, Rust, Java, C#, PHP, Ruby, Kotlin and Swift. The work happens in your browser, and no code leaves your computer for it. Other files, and anything that takes longer than about three seconds, keep the normal diff. Turn it off with Show moved & renamed code in the diff display options, or turn off the whole feature with Settings → Analysis → Semantic changes.
Power Up (Settings → Semantic diffs) is an optional second look by a model, for changes the engine could not label on its own, such as code extracted into a new function. It is off until you add a key for one of its two models. When it is on, the code in question goes to the model you chose. You can turn down a link it draws.
The Inbox PR page now draws semantic diffs too, with the same switch in its diff options.
Talk through a review comment with your agent
When the Inbox is running, a comment in the review window can go straight to your agent as a conversation. Type
@in the comment box to pick a connected agent and send it now, or leave comments as before and use Send or Send all in the new Threads tab. Send all goes to the agent as one review, with each comment as its own thread.Replies show under the lines they are about, with Queued, Delivered and Read, a reply box, and Resolve. If the code changes under a thread, the thread stays on the lines that took its place and shows the old code. If the code moved, the thread follows it. Each conversation is an ordinary Inbox thread, and Open the review of … in that thread's header opens the review again with its threads in place.
The first comment goes to the agent that opened the review (Claude Code, Pi and OpenCode). Without a running Inbox, the comment box works as it did.
Code review in the Inbox, now in Settings
Settings → Capabilities → Code review is now shown to everyone. It is off until you turn it on, and the Inbox does not offer it in a pop-up. If you already had it on, it stays on. Turning it on gives you:
- Reviews in the sidebar: your agents' reviews and your open GitHub and GitLab pull requests in one list, with a project filter. Type
/in a reply to ask an agent for a review, then approve it, send feedback to the agent, or post it on the pull request. - The Pull requests board , as a grid or a table, Open or Merged, with bulk actions. It now follows the project chosen in Reviews, and its running checks mark turns while checks run.
- PR pages with the same file tree as the review window and semantic diffs. Your unsent comments and Viewed ticks stay until a new commit lands, even when someone adds a label or a comment. When you send feedback on a pull request you opened yourself, the agent makes the change and pushes it to the branch. On a teammate's pull request it still changes nothing unless you ask.
- Hide for a pull request (row menu in Reviews, the PR page bar, the board's tile and select mode) and for a whole repository (its header on the board). Hidden pull requests leave Reviews, the board and every count, and nothing is done on GitHub or GitLab. Each Hide has Undo, and a Hidden fold at the end of Reviews lists them with Show again. A hidden pull request stays hidden through new commits and comments until you show it again.
- Set risk rules : describe in your own words what makes a pull request risky, and an agent ranks each open pull request High, Medium or Low against them, with one sentence why. It runs only once you have written rules.
Code review in the Inbox is separate from
plannotator review, which works the same with the switch on or off.#3626, #3610, #3613, #3609, #3627, #3612, #3628, #3653, #3622, with earlier work in #2640 and #2694
Fixed: a linked machine stayed "asleep" after Tailscale came back
Two faults on the far machine kept a linked machine unreachable:
- An Inbox that started while Tailscale was not running never published its link for other machines, and never tried again. It now checks for Tailscale after 30 seconds, then less and less often, up to every five minutes, and publishes the link as soon as Tailscale runs. While the link is up, it checks every ten minutes that Tailscale still points at it.
- After an Inbox crashed or stopped while Tailscale was off, the mapping it left behind pointed at a port where nothing listened. The next Inbox refused it as someone else's mapping. The Inbox now remembers the mappings it made and points its own dead ones at the new run. A mapping it did not make, or one in use, is never touched.
Typing on long threads
On a heavy page, such as a list of about 550 threads or a thread of about 600 messages, every key in the reply box did work that grew with the page, so holding Backspace could fall seconds behind. Each key now does a fixed, small amount of work. Chrome's undo also takes back a whole run of typing again instead of one letter at a time, and a pick from the
/,$or@list is its own undo step. That last part is for Chrome and other Chromium browsers; Safari is listed under Known issues. A/,$or@list now opens only when you type, not when you delete back into a trigger.Routines
For people who use Routines:
- Agents can make routines.
plannotator routine create|list|get|update|on|off|run|deletecovers every field of the editor. The Inbox has a built-in/create-routineskill that teaches an agent how. A routine an agent makes arrives off, and only you turn it on the first time. When you ask for it yourself with/create-routine, that request counts as your approval, and the routine is made on. - Edit and Runs tabs on each routine. Runs lists the newest 20 runs, each one a link to that point in the thread. The Edit tab shows how the last run went, in red when it did not start or did not finish.
- Filter the list by routine. The list's Filter has a Routine group: "Routine threads" and "Other threads".
- A one-time intro to Routines, with No thanks and Turn on , shown once to people who have sent messages in the Inbox on three different days.
- Two fixes from @rudycelekli: rescheduling a one-time routine while its run was getting ready no longer runs the old time and marks the new one Done (#3545), and two windows editing the same routine no longer undo each other's changes or bring back a deleted routine (#3552).
Playback speed for videos and recordings
Videos and recordings in the Inbox have a speed menu: 1x, 1.2x, 1.5x, 1.7x and 2x. The speed you pick applies to every video and recording you open in that tab until you close it. On a video, the "1x" chip sits in the line under the film, so it never covers the browser's own controls. On a phone, the menu opens as a sheet.
By @MaxKless in #3534, their first contribution, finished in #3582 with their commits kept
Fixes from
@rudycelekli sent twelve fixes, each with a test that failed before it:
- Last commit on a branch with one commit now shows that commit. Before, it showed nothing on a clean checkout, or your uncommitted edits. #3547
- Before the first commit , Uncommitted changes and Since base now include files you have staged with
git add. #3551 - Staging
row[1].txtfrom the review tree no longer also stagesrow1.txt. Stage and unstage now take the file name literally. #3544 - A submodule change shows as its normal one-line pointer change whatever your
diff.submodulesetting is. #3542, related to #3533 from @luwanglin - OpenCode Ask AI reports a prompt that OpenCode rejects, such as an unknown model, instead of waiting for a reply that never comes (#3548), and no longer starts a second
opencode servewhen it is stopped during startup (#3543). - Linked documents in plan review and annotate open in the order you clicked them, and a note you add while the next file loads is kept. #3550
- Restoring an annotate draft no longer drops an older note when a new one arrives from the same source. #3546
- An MP4 you upload to the Inbox keeps its length and size, and an audio-only MP4 shows as a recording, as it does when an agent attaches it. #3549
- The two routine fixes listed under Routines (#3545, #3552), and a fix to how CI picks the browser tests for a change when a path has unusual characters (#3541).
Ten of them landed together in #3624, with each commit and its authorship kept.
Additional Changes
- Your Inbox rules reach Claude Code sessions the Inbox starts. The rules under Prompts → Inbox ("Rules for your agents") reached sessions you started in a terminal, but a session started from the Inbox only got them after a compaction. They now come with its first wake. #3594
- Pick an OpenCode agent at launch. With OpenCode picked in To, the model menu has an Agent column: Default, build, plan and any primary agents you made. The thread's start line names it, and a reply that starts OpenCode again keeps it. #3621
- Contents for short documents. A Markdown document opened in the Inbox shows its Contents rail from two headings, not four. #3621
- Remove a link from a Board card. Each link in an opened card has a quiet ×. The card's history says what was removed. #3621
- Groundwork with no visible change: card parts for host apps in
@plannotator/ui, and Inbox work that stays off. #3572, #3579, #3581, #3586, #3587, #3569, #3570, #3584 - Test upkeep: #3608
Known issues
- Python docstrings. A change inside a docstring can be labelled "reformatted" in a semantic diff, so it is drawn quiet and grey although the words changed.
- Semantic diffs on a phone. The moved and renamed bands show without their labels, and the switch to turn them off is not offered there.
- Comments in a folded moved block. Commenting on lines inside a folded "Moved N lines" block opens the fold only when the comment sits on the old side's hidden lines. A comment that starts inside the block and ends outside it leaves the block folded.
- The file tree's search box shows what you type in lower case. The search itself is not affected.
- Undo after a pick in Safari. In the reply box, one undo right after picking from the
/,$or@list empties the box. Redo brings it back. Chrome is not affected. - Opened lines can move on a pull request page. If you open hidden lines in a file during the first few seconds, before the moved and renamed notes have arrived for the files above it, those lines shift by a few rows when the notes arrive. Nothing is lost; scroll back to them. Opening lines after the notes have drawn is not affected.
- An expand arrow may need a second click while a file's header still says "reading…". This is most common in Safari, and also happens in Chrome on the first click after a pull request opens.
Install / Update
macOS / Linux:
curl -fsSL https://plannotator.ai/install.sh | bashWindows:
irm https://plannotator.ai/install.ps1 | iexClaude Code Plugin: The install script above also updates the plugin when
claudeis on your PATH. Otherwise, in a terminal:claude plugin marketplace update plannotator claude plugin update plannotator@plannotator --scope userThen restart Claude Code. Inside Claude Code, run
/plugin marketplace update plannotator, then open/plugin→ Installed → plannotator → Update now.Pi:
pi update npm:@plannotator/pi-extensionOpenCode: Re-run the install script above. It also clears the OpenCode 2 plugin cache.
What's Changed
- Inbox: internal groundwork, off in #3569
- UI frame: card parts for host apps in #3572
- Inbox: internal groundwork, off in #3570
- UI frame: card grid gap by size; the focus ring's colour in the docs in #3579
- UI frame: card rows and a visible row focus in #3581
- Inbox: playback speed menu for videos and recordings (1x to 2x) by @MaxKless in #3534
- Inbox: playback speed menu under the film, a sheet on a phone (finishes #3534 by @MaxKless, with their commits) in #3582
- Inbox: internal groundwork, off in #3584
- UI frame: card rows keep their title in narrow lists in #3586
- UI frame: plain names in the card example in #3587
- Claude Code: a session the Inbox starts gets your Inbox rules on its first wake in #3594
- Routines: Edit and Runs tabs on a routine in #3596
- Code review redesign: file tree, two panes, semantic diffs, image diffs, minimap, launch pad, live review threads; Code Tour removed (carries #3324, #3331, #3332, #3337, #3338, #3340, #3342, #3347, #3349, #3353, #3357, #3360, #3361, #3389, #3391, #3394, #3408, #3413, #3417, #3428) in #3383
- Inbox:
plannotator routinecommands and the/create-routinebuilt-in skill in #3601 - Fix a flaky selection bar browser test in #3608
- Inbox: a one-time Routines intro after three days of use in #3604
- Code review: fixes from the 0.29.0 hands-on QA in #3605
- Inbox typing on long threads: no per-key page-wide work; Chrome undo per typing run again in #3603
- Reviews: the risk dialog is titled Set risk rules in #3612
- Report rejected OpenCode Ask AI prompts instead of waiting for a reply by @rudycelekli in #3548
- Keep OpenCode Ask AI startup from spawning a duplicate server after disposal by @rudycelekli in #3543
- Review: Expand all stays on from commit to commit; Cmd/Ctrl-click jumps to one clear definition in #3618
- Board: show the selected segment in dark theme in #3622
- Claude Code: open behind the guard's early-run rule at the tool's run step in #3619
- Filter routines in the Inbox list in #3615
- Inbox: publish the link for other machines once Tailscale runs; re-point a dead mapping the Inbox made in #3614
- Fix browser slice selection for Git-quoted paths by @rudycelekli in #3541
- Preserve submodule pointer hunks in Git reviews by @rudycelekli in #3542
- Stage and unstage review filenames literally by @rudycelekli in #3544
- Keep a rescheduled Inbox routine from being marked done by its old run by @rudycelekli in #3545
- Keep distinct external comments when restoring annotate drafts by @rudycelekli in #3546
- Preserve audio and video metadata when people upload to the Inbox by @rudycelekli in #3549
- Keep linked document navigation ordered and preserve pending edits by @rudycelekli in #3550
- Include staged files in working-tree reviews before the first commit by @rudycelekli in #3551
- Preserve concurrent changes when editing Inbox routines by @rudycelekli in #3552
- Ten fixes from @rudycelekli, merged together in #3624
- Inbox: hide a pull request from Reviews and the PR board in #3610
- Show the first commit in Last commit reviews by @rudycelekli in #3547
- Show the Code review switch in Settings to everyone; never show its offer in #3626
- Board: same surface as the list beside it; running checks turn in #3628
- Inbox: Contents for short documents, remove a card link, OpenCode's agent at launch in #3621
- A pick from the skill or @ list is its own undo step in #3632
- Release batch: Code review switch, board surface, Inbox small fixes, undo after a pick in #3634
- PR board: follow Reviews' project filter; Hide repository in #3613
- Inbox: the PR page's file list is the code review tree in #3609
- Inbox window: draw diffs with the vendored diff library fork in #3625
- File tree: arrow keys work after a search; 44 px All files rows on a phone in #3627
- Inbox PR page: semantic diffs (moved and renamed code) in #3630
- Reviews: name the filtered project when everything in it is hidden; leave select mode after a bulk hide in #3653
- Inbox PR page: an expand arrow used before a file's moved and renamed note arrives no longer leaves its header on "reading…" in #3656
New Contributors
Contributors
@rudycelekli sent twelve fixes across code review, annotate, OpenCode Ask AI, Inbox uploads and Routines (#3541 to #3552). Each one came with a test that failed before the fix, most of them against a real Git repository: the first commit in Last commit reviews, staged files before the first commit, file names with brackets, submodule pointers, rejected OpenCode prompts, a duplicate OpenCode server, linked document order, annotate drafts, uploaded video details, and two races in Routines.
@MaxKless built the playback speed menu for Inbox videos and recordings (#3534), with keyboard and screen reader support and tests, and recorded it in Chrome, Safari and on a phone. It ships in #3582 with their commits kept. First contribution.
Thanks also to @luwanglin, who asked for code review to cover submodules in #3533. #3542 makes the submodule pointer show the same way under every Git setting; reviewing inside a submodule is still open there.
The new review tree and diffs are built on Pierre's
@pierre/treesand@pierre/diffslibraries.Full Changelog :
v0.28.67...v0.29.0 -
🔗 HexRaysSA/plugin-repository commits sync repo: +5 releases, -2 releases rss
sync repo: +5 releases, -2 releases ## New releases - [btf2ida](https://github.com/nightshift-labs-ai/btf2ida): 0.1.24 - [cfiscope](https://github.com/nightshift-labs-ai/cfiscope): 0.1.21 - [ida-bochs-binaries](https://github.com/hexrayssa/ida-bochs-binaries): 2.0.2, 1.0.7 - [memlens](https://github.com/nightshift-labs-ai/memlens): 0.3.29 ## Changes - [btf2ida](https://github.com/nightshift-labs-ai/btf2ida): - removed version(s): 0.1.0 - [memlens](https://github.com/nightshift-labs-ai/memlens): - removed version(s): 0.3.4
-
