- ↔
- →
- November 16, 2026
-
🔗 backnotprop/plannotator v0.28.66 release
Follow @plannotator on X for updates
Missed recent releases? Release | Highlights
---|---
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 one
v0.28.55 | Floating reply drafts, now a setting under Experimental, open questions sit next to Reply again, a comment box that keeps unsent comments as Drafts, choose how your list looks: Minimal, Balanced or Detailed, update an older linked machine from this Inbox
v0.28.53 | Start an agent in a new folder, or from a git URL, "+" on each project row starts a session there, a reaction tray, a thread's Links, Settings → Activity, New message offers the open thread's files, Bro mode: agents write to you in plain wordsWhat's New in v0.28.66
TL;DR
- New: Pick several threads and archive or snooze them at once
- New: Combine picked threads into one; Tidy follows your own words
- New: Rows take their tag's colour; filter and search by tag
- New: Files an agent's message names open beside the thread
- New: Swipe rows on phone or iPad; list can show archived threads
- New: Antigravity and Orca use the Inbox; T3 Codex threads get replies
- New: Open in lists JetBrains IDEs
- Off by default: Routines: run a saved prompt on a schedule
v0.28.66 is mostly an Inbox release. You can pick several threads and act on them at once, ask one agent to combine them into a new thread, or have Tidy follow your own instructions. You can also swipe a row on a phone or iPad. Tags show on rows, under a thread's subject, in Filter and in Search. A file that an agent's message names opens beside the thread, and Google Antigravity joins the agents that can use the Inbox. Plan review and annotate get optional source line numbers and coloured text, and the Open in menu lists JetBrains IDEs. The release has 100 PRs. 15 of them are from 8 outside contributors, and 5 of those people made their first contribution.
Pick several threads and act on them at once
You can now pick thread rows and act on all of them together. ⌘-click (Ctrl- click on Windows and Linux) adds or removes a row, and Shift-click picks a range. You can also choose Select in a row's right-click menu or a phone's long-press sheet, or Select threads in the list's ⋮ menu. While rows are picked, a bar takes the place of the list header. It shows how many are picked, with Archive, Snooze, Tidy…, Combine… and Done. On a phone the actions are a sheet at the bottom of the screen. A right-click on a picked row acts on every pick. Each action gives one toast with one Undo. A thread that lives on a linked machine goes to that machine; if the machine is asleep, the change waits for it.
Tidy now takes your own words. Its popover has "Add instructions (optional)" and remembers the instructions you used recently. Tidy on picked threads asks each thread's own agent about those threads only.
Combine asks one agent to write a new thread from the picked ones. You choose the agent and can say what the new thread is about. The picked threads are archived only once the new thread arrives. If the agent ends or stops first, nothing is archived and the window says so. While it waits, the rows read "Combining…", with "Stop combining" in their menu. Undo brings the threads back.
On a phone, every bottom sheet now fits the screen and scrolls inside, so the first items of a long menu are always in reach.
Swipe a row, and show archived threads in the list
On a phone or an iPad, swipe a thread row as in Mail. Swipe right to mark it read (on a read row, the right side offers Mark unread). Swipe left to archive it. A long swipe or a flick runs the action when you lift your finger. A short swipe leaves the row open on its button, so you can tap it. Toasts, Undo and the "Set aside N open questions?" warning work as they do from the row menu.
Archived threads can now show at the bottom of the list. Turn on Show archived in the list's ⋮ menu (it is off until you pick it). An Archived section then sits under Snoozed, closed until you open it. It shows the newest archived threads first, 20 at a time, up to 100, and then points you to Search. Each row says when it was archived. Unarchive is in the row's hover action, its menu, and a left swipe on a phone. The choice is the same on every linked machine and every open window.
Tags on rows, in the thread header, in Filter and in Search
Rows take their tag's colour. Each tag now has a colour. A new tag gets one at once from a calm set (green, amber, the accent colour and grey), and tags you already have get one on the first load. A tagged row is tinted across its width and shows the tag's name. If you already use tags, your rows are coloured after you update. To change a tag's colour, right-click the tag in the sidebar and pick Highlight rows : five presets, your own recent colours, a hue strip, a hex field, or None. To turn every tint off, untick Show tag colors in the list's ⋮ menu. Colours and the switch are the same on every linked machine.
A thread's tags show under its subject , each opening its tag's list, with a
+to add one. A thread with no tags looks as before.Filter and Search. The list's Filter has a Tag section that shows how many threads each tag leaves, and you can tick several. Search has a Tag chip after "From anyone". With the Board off, resting on a
#Tagin a message shows a preview of the tag's latest threads.Add tag no longer loses what you type when the menu moves under a still mouse.
Every file an agent's message names opens beside the thread
In an agent's message, a link to a file, a code span that is a path (
src/a.ts:42,README.md) and a bare path in the text now open that file beside the thread.:42,:6-13and#L6-L13jump to and mark the lines. Opening the file attaches nothing. Your first comment on it (a text selection, a code line, a point on a picture, a moment in a video) makes it an attachment of that message, and from then on it is counted and sent like any attachment. A relative path starts in the thread's folder. Secrets never open: dotenv files, SSH keys and credential stores are refused. Your own messages keep their links as they are.Prototypes you can click through, and prototypes on the web
An agent's prototype page now behaves in the Inbox as it does in a browser tab. A link to the same page with a query (
?variant=2) loads that variant in place, GET forms and#links work, and the "Try prototypes" window follows links to another option's page or to a web page (in a new tab). Each option can open the same attached file with its own query, so stepping between options switches the variant.An agent can also point an option at a public
https://page. "Try prototypes" opens it straight from the web, with Comment for a whole-page comment and a button to open it in a new tab. Plainhttp://on another host is still refused.Reply to a new session when the one that asked has ended
When the session that asked you has ended, the "who gets this reply" list now ends with a row such as "New Claude Code session in ledger". Pick it and your reply starts a new session of the same agent, in the same folder, on the same machine, and that session then owns the thread. The ended session stays the default, so nothing starts unless you pick the row. If the start fails, your reply is kept and the thread offers Try again.
On a computer, that list now shows each session's title, with the agent and folder under it, as the phone already did. Two sessions with the same title get the agent's name added. In the sidebar, the Agents list keeps a fixed order (newest first seen at the top), so rows no longer jump when a turn starts or ends. An agent's name follows one rule on every device: the name you gave, then the name set in the agent, then its title.
#3442, #3447 finishing #3343 by @sx4im, #3454, #3448
Antigravity can use the Inbox
Google Antigravity (the app, the IDE and the
agycommand) can now write to your Inbox, and your reply starts a turn in the conversation that asked. When Antigravity is on the computer,plannotator inboxadds the Inbox to its MCP config. The app and the IDE need nothing else. Anagyconversation is told to runplannotator inbox antigravityonce per launch when the Inbox cannot reach it yet. Each reply goes in once. The wake was tested withagyon macOS. The IDE, Windows and Linux are not tested yet.T3 Code: replies reach Codex threads too
A Codex thread running inside T3 Code could write to the Inbox, but your replies never showed up in T3. Now a reply to any T3 thread, Claude or Codex, goes in through T3's own
t3 thread sendon this computer, with no setup. When T3 is closed, the reply says "Waiting for T3 Code" at once, and the list row says the same as the thread. A T3 started from a Claude Code terminal, or one of T3's own short runs, no longer takes a reply meant for the thread.Settings → Agents has a T3 Code entry when T3 is on this computer. It says whether your replies arrive as a new turn, and when they cannot, it shows the sign-in command with Copy.
Orca gets the Inbox and the plannotator tool
Claude Code chats in Orca now get what the VS Code panel gets: the
plannotator_inboxtool with the reply wake, and theplannotatortool. This changes plan review in Orca: Orca shows its own "Review proposed plan" card, so Plannotator's plan review no longer opens there.#3460 closing #3325 reported by @ninjz, with the Orca work from #3400 by @rudycelekli
Cloud agents use the whole Inbox
A paired cloud agent can now do what a local agent's Inbox tool does. It can list, read and search every thread in every project, reply in any thread, start threads in any project (named by project name), resolve and snooze threads, change a thread's pull requests, and send guided reviews. It can use cards and steps while those are on. It still cannot name a path on your computer. It can also attach files up to 100 MB, videos included, by sending them in pieces.
Plan review and annotate: source line numbers, coloured text, and Open in
JetBrains
Source line numbers. Settings → Display has a Source line numbers switch, off by default. Turn it on and each block in plan review and annotate shows its source lines in a quiet gutter:
42for one line,42–45for a span. The numbers stay out of copied text and out of an annotation's quote, and they are hidden on phones and in print.Coloured text. An author can now colour a few words with
<span style="color: …">or<font color="…">. The colour shows in plan review, annotate, Inbox messages and Markdown attachments, including table cells. Colours that are almost see-through are refused.Open in JetBrains IDEs. The Open in menu now lists IntelliJ IDEA, WebStorm, PyCharm, GoLand, Rider, PhpStorm, RubyMine, CLion and RustRover when they are installed. The file opens at the line.
Annotate's default view. A new config.json key,
annotateView("wide","focus"or"edit"), sets the view an annotate session opens in.A table indented under a list item no longer draws its header one column to the right.
#3373 by @mvanhorn closing #1650 requested by @de-tre, #3378 closing #3345 requested by @zane668, #3372 by @mvanhorn (related to #3368 by @JasonLandbridge), #3463, #3314 by @BenNewman100
A quicker Inbox window
The Inbox window now keeps the open thread in one cache and applies live changes to it in place, instead of reading the thread again. When you press Send, your words show in the thread at once with "Sending…". If the send fails, they come back into the reply box with the reason. In a long thread, one new message now redraws only itself (before, a 266-message thread redrew 291 parts). Each agent message across four windows takes half the requests it did. On an iPad, the first load no longer stalls before the first tap works.
Phones and iPads
- The comment card stays above the keyboard. On an iPhone or iPad, the comment box ended up under the keyboard and the screen jumped on every key. It now sits above the keyboard. #3380
- Step through a thread's files on an iPad with large previous and next buttons under the open file, or a sideways swipe. A swipe that starts at the screen's edge stays Safari's Back or Forward. #3425
- The tag (@) and recipient pickers are no longer cut off by the reply box. #3440 by @sx4im closing #3427 reported by @llwt
- Leaving a picture's full view no longer redraws every tile button in the thread under your finger. #3371
config.json can live in your dotfiles
The Inbox used to write its own records into
config.json: when each one-time dialog was due or shown, the tour, and similar bookkeeping. These differ on every machine and change by themselves, soconfig.jsoncould not be kept in a dotfiles repo. They now go tostate.jsonnext to it. Your settings stay inconfig.json. Old copies inconfig.jsonare read and never removed, so an older version or another machine sharing the file keeps working.plannotator uninstall --purgeremovesstate.jsontoo.#3458 closing #2852 reported by @robsonpeixoto
Updates, installs and proxies
- Updates run at low priority. A background update (Update now, or auto-update) now runs at low CPU and disk priority, so the Inbox stays quick while it downloads.
plannotator updatein a terminal keeps normal priority. This applies from the update after this one. #3466, for #2788 reported by @zane668 - A download mirror for the binary.
install.shnow downloads the binary itself fromPLANNOTATOR_RELEASE_DOWNLOAD_URLwhen it is set, not only the checksum. The checksum check still applies. #3310 by @rudycelekli closing #3298 reported by @navin-moorthy - A proxy no longer breaks the Inbox. With
http_proxy(orHTTP_PROXY,ALL_PROXY) set, Plannotator sent its requests to 127.0.0.1 through the proxy.plannotator inbox statusthen said "not running", and an agent's send could start a second Inbox and stop yours. Local requests now skip the proxy. #3461, found while working on #3350 reported by @zane668 - A plan review whose parent is gone exits. When the program that started a classic plan review is killed, the review's server now exits after about 10 seconds instead of running on with nobody to read its decision. #3461
Routines: off by default
A routine is a saved prompt with a name, a schedule and a folder. When it is due, the Inbox on this computer starts a fresh agent session in that folder, and every run lands in one thread. Turn Routines on in Settings → Capabilities (config
inboxScheduledThreads). It is not offered on Windows, and it needs "Start agents from New message" on. While it is off, nothing runs and nothing is written.- Schedules: hourly, daily, weekdays, weekly, once, a custom cron, or none (run by hand). Runs are at least 15 minutes apart.
- Missed runs: "Run once when I'm back" (the default) or "Skip it". A catch-up is one run, never a burst.
- Runs use Claude Code, Codex, OpenCode or Pi, with your own permission mode. Your reply goes to the newest run's session.
- Agents can create routines, but one an agent creates arrives off, and only you can turn it on the first time. Each change an agent makes posts a line in the routine's thread, with the old and new values.
- Start at login: while Routines is on, the Inbox adds a login item (launchd on macOS, a systemd user unit on Linux) so it starts quietly and routines can run. Turning Routines off or
plannotator uninstallremoves it.
A routine is managed on the computer that made it. Its thread works from a linked machine like any thread.
Reach the Inbox through your own Cloudflare: off until you set it up
For people who do not use Tailscale, the Inbox and your review, annotate and last sessions can now be reached through your own Cloudflare Tunnel and Cloudflare Access. As over Tailscale, one owner gets in and nobody else does: only the e-mail you type at setup can sign in. Settings → Remote devices has a Cloudflare card with Set up. You can also run
plannotator inbox cloudflare-access setup --email <you>. Setup needs a Cloudflare account with a domain, an API token (never saved) andcloudflared. It creates the tunnel, the sign-in gate and two addresses, checks from outside that a request without your sign-in is refused, and only then turns it on and shows the address with a QR code.teardownremoves everything it made. Sessions take--cloudflare- access.Additional Changes
- Last 3 days in the list's Updated filter: today and the two days before, moving with the clock. #3401 by @rudycelekli closing #3301 requested by @zane668
- Let a trusted local app show the Inbox in a frame. A new config.json key,
inboxFrameAncestors, lists the apps on this computer that may embed the Inbox window. Unset, nothing changes. #3376 closing #3299 requested by @jroquejr plannotator review<word>with no such folder now stops with a clear error, instead of reviewing the folder the terminal is in. #3387plannotator review<folder>reviews that folder even when the shell exportedGIT_DIR. #3377- Mod+Shift+Enter in code review opens "Send with a note…" instead of posting the review with no note. #3210 by @rudycelekli, #3403
- DeepSeek Harness keeps the backslashes in a typed Windows path, so
/plannotator-review C:\dev\featureopens that folder. #3214 by @rudycelekli - A link whose URL has parentheses (such as a Wikipedia link) now works in guided reviews and PR descriptions. #3213 by @rudycelekli
- OpenCode's annotate-last opens on the reply to your own prompt, not to a message a plugin added. #3358 by @xunguangzlj-cloud closing #3312 reported by @marwashan
- Pi inside an Electron app gets a TLS warning that tells you to update the host app, with its Electron and Node versions. #3351 by @jiangjiang248 closing #3346 reported by @xueccci
- After
/bgon a busy Claude Code session, the Inbox tool stays connected. #3370 by @uvw closing #3369, which he also reported - A malformed address answers 400 in the Shapes routes, the review servers and the Inbox. In Pi it could stop the extension's host. #3414 by @sx4im closing #3411 reported by @brunnojob, #3456
- Your words are kept. Take back is no longer offered on a reply that carried answers (the server refused it). A dialog no longer closes when a text selection ends on its backdrop. Closing the reply box while it says Transcribing keeps the take, and a file opened over the box while recording closes the mic and posts nothing. #3426, #3445
- Questions. A question repeated in an attached file is asked once, not twice. Choices that differ only in case or a mark ("Yes" and "Yes!") are kept apart. #3422
- Reply files keep the order you picked them in , on the phone and from another window. #3441
- Pin / Unpin in an attachment's menu , after Download. The dialog for updating a linked machine now reads "Update {name} yourself". #3424
- A sleeping machine's projects stay in New message's folder menu , after a reload or in a new tab. #3468
- Short GitLab merge request references go to the project's own server. A short reference such as
group/project!45now goes to the project's own GitLab server, including self-hosted names likegitlab-master.example.com. Before, it could point at gitlab.com. If a short reference still goes to the wrong place, for example when your GitLab is reached on a port or the project's remote uses an SSH alias, name the server ingitlabHostsin config.json. A reference saved before this fix keeps its old address until you remove it and add it again. From a user report. #3525 - The thread header shows its PR button when an agent links PRs while the thread is open. #3451
- A thread opened from a link stays in its place in the list instead of dropping into Quiet. #3407
- Sidebar: the Tags and Agents header buttons show when you hover the header, like its arrow. #3395
- Linked machine updates: Try Again no longer shows "The update didn't install" while the update is working. On touch, a quick second tap on the face picker no longer picks a face by mistake. #3446
- Guided reviews: End and Home no longer load files halfway down, and Collapse all works after switching views. #3366, #3467
- Agent text. A session started from the Inbox is told on its first turn that you read the Inbox. Agents get eleven short lessons from the owner (for example: open a prototype and click through it before sending it). When an agent names a PR that is on no thread, the send's result suggests attaching it. #2999, #3436, #3435
- The Board across linked machines. With the Board turned on, it shows the cards of every linked machine in the same lanes, and each action on a card goes to the machine that holds it. #3341
- For people who already turned on code review in the Inbox: the Pull requests board spans linked machines, picked PRs can start review threads, the stack page can open a range of layers as one diff and marks what changed since you looked, the next review round asks only for what changed, and a review note no longer widens a wrapped diff on a phone. #3392, #3396, #3398, #3432, #3431, #3170 by @robfeldmann
- Site and docs: plannotator.ai/llms.txt is now a short index that leads with the Inbox, the Inbox install prompt gives each agent its own steps, OpenClaw installs from npm (
openclaw plugins install npm:@plannotator/openclaw),plannotator inbox --helphas two lines corrected, the README has a new Inbox picture and a shorter top, and the end of the Inbox page now offers the install prompt first. #3379, #3382, #3374, #3384, #3465, #3474, #3479, #3478 - Groundwork with no visible change: the thread pane as a self-contained part #3450, #3464
- Test and CI upkeep: #3457, #3215 by @rudycelekli, #3399, #3211, #3459, #3421, #3420, #3419, #3439, #3406, #3481
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
- fix(review): a named directory is reviewed even when the shell exported GIT_DIR in #3377
- OpenClaw: install from npm (site and plugin README) in #3374
- llms.txt: route agents, Inbox first in #3379
- Markdown: keep an author's text colour in #3378
- Phone and iPad: the comment card stays above the keyboard in #3380
- Inbox: leaving a phone's full view no longer swaps the thread's tile buttons in #3371
- Guided review: End and Home stop mounting files halfway when the scroll stalls or the observer lags in #3366
- Inbox: let a trusted local app frame the window (inboxFrameAncestors) in #3376
- Inbox frontend foundation, step 1: one cache for the open thread in #3103
- Inbox window: data layer step 2 (half the requests, Send shows at once, list in the cache) in #3115
- Inbox window: an arriving message draws its own body only; first break-up of App.tsx and Thread.tsx in #3123
- Inbox window: check the held copy against a fresh read (random sequences, and after every browser spec) in #3211
- Inbox prompt: each agent's own steps, and a Supported agents link in #3382
- inbox --help: two lines brought up to date in #3384
- Inbox Board: one Board across linked machines in #3341
- review: a sole folder name that is not there stops with a clear error in #3387
- Inbox: one PR board across linked machines in #3392
- fix(review): Mod+Shift+Enter opens the note composer, it no longer posts by @rudycelekli in #3210
- Claude Code mod: a turn that starts before session.start finishes keeps the Inbox link by @uvw in #3370
- Inbox tags: Add tag's field keeps focus while typing; same-millisecond tags keep their order in #3393
- Fix table header shifted one column right when the table is indented under a list item by @BenNewman100 in #3314
- Inbox: settings known before the first row on load; equal settings redraw nothing in #3386
- Cloud agents use the whole Inbox, like a local agent in #3306
- Tests: the snooze tests restore the time zone they started in in #3406
- fix(pi): point Electron TLS warnings to the host app by @jiangjiang248 in #3351
- Inbox sidebar: Tags and Agents header buttons show with the chevron in #3395
- ci: run the Claude Code mod's engine-harness tests in #3399
- Inbox: a thread opened from a link is looked at after the first list read lands in #3407
- Cloud agents send files up to 100 MB in pieces in #3318
- fix(review): a remounted decision control does not reopen the note composer in #3403
- Inbox: a question's prototype can be a public https page in #3319
- Inbox: tell a launched session where the person reads, on its first turn in #2999
- Prefer human-prompt replies in OpenCode annotate-last by @xunguangzlj-cloud in #3358
- Inbox: colour rows by tag, with a Show tag colors switch in #3402
- Claude Code mod: a T3 thread is the process with T3's t3-code tools in #3381
- Inbox: wake T3 threads (Claude and Codex) through t3 thread send in #3375
- Inbox: every file a message names opens in the viewer, attached when commented on in #2875
- Inbox: archived threads as a group in the thread list in #3404
- Inbox T3: the waiting line shows at once, and the row says what the thread says in #3412
- Inbox: pick threads and act on them at once, Tidy with your words, Combine in #3405
- Inbox: a new Combine/Tidy key after a refusal; cap tag colour times at now in #3418
- Inbox Archived: fix the two-machine test's same-millisecond tie (main's unit-2) in #3419
- Inbox T3 test: hold the wake's send in flight while the mod polls in #3420
- Inbox: swipe a thread row to mark it read or archive it in #3135
- Give the thread-state model test a budget it fits in in #3421
- Inbox: Pin in an attachment's menu; "Update {name} yourself" in #3424
- Inbox: step a thread's files on an iPad with a bar and a swipe in #3425
- Inbox: stop losing the person's words (Take back, dialog backdrop, dictation) in #3426
- Inbox: every phone bottom sheet fits the screen (the thread's ⋮ too) in #3433
- Inbox and sessions through your own Cloudflare Tunnel and Access (opt-in) in #3388
- Inbox: ask a repeated file question once; refuse choices that read the same in #3422
- Inbox: the next review round asks only for what changed in #3431
- Inbox tags step 2: header tag line, Tag filter, tags in Search, Board-off preview in #3397
- Inbox agent text: the owner's lessons for agents in #3436
- Ended-reply test: let the disposed wake's last poll land before the clock moves in #3439
- Inbox: name unattached PRs (bare #N too) in send_message's result in #3435
- Inbox stack page: Layers i–j as one diff, and changed since you looked in #3432
- Routines: run a saved prompt on a schedule, on this computer in #3409
- Inbox: a T3 Code group in Settings → Agents in #3438
- Inbox: let people click and navigate inside an agent's prototype page in #3162
- Inbox PR board across machines: say what the window check stops, pin the gh routes, test merge in #3396
- Inbox: reply files keep the order the person picked them in in #3441
- Inbox: Antigravity, with a wake in #3390
- Inbox PR board: Start review thread for picked PRs in #3398
- Antigravity page: say the IDE is untested in #3444
- Inbox: a cover while recording posts nothing again in #3445
- fix(dsh): a typed Windows path reaches the review whole by @rudycelekli in #3214
- Inbox reply picker: show each session's title on a computer (finishes #3343 by @sx4im, with their commits) in #3447
- Guide viewer: a link's URL keeps its own closing paren by @rudycelekli in #3213
- Inbox: thread header shows its PR button when the read after a change fails in #3451
- Inbox: reply to a brand-new session when the one that asked has ended in #3442
- fix(inbox): a closed note or a folded thread no longer widens a wrapped diff past a phone by @robfeldmann in #3170
- Fix nine flaky tests, the machine update's false "didn't install" and the face picker's early tap in #3446
- Inbox: Agents list keeps a fixed order, marks who waits on you, names by one ladder in #3448
- fix(shape): return 400 for malformed percent-encoded shape paths by @sx4im in #3414
- Inbox: the reply picker names an unnamed session by its agent, not its first thread in #3454
- Add a rolling three-day Inbox update filter by @rudycelekli in #3401
- Inbox: the thread pane as a self-contained slot, keyed by pane (no visible change) in #3450
- ci: three path gates skipped PRs that break the job they gate by @rudycelekli in #3215
- Malformed path escapes answer 400 in the review servers and the Inbox in #3456
- Fix forward: option card on a phone and the row badge hover (main red) in #3459
- README: a new Inbox picture (desktop and phone) in #3465
- Open in: JetBrains IDEs, at the line by @mvanhorn in #3372
- install.sh: download the binary from PLANNOTATOR_RELEASE_DOWNLOAD_URL by @rudycelekli in #3310
- Inbox: tag and recipient pickers escape the reply box scroll region by @sx4im in #3440
- Inbox: each pane opens and reads its own thread in #3464
- Annotate: a config.json key for the default view (Wide, Focus or Edit) in #3463
- Plan and annotate: optional source line numbers beside each block by @mvanhorn in #3373
- CI: run an affected slice of browser specs on each PR (#3455) in #3457
- Updates run at low priority, so the Inbox stays quick while one downloads in #3466
- Keep machine state out of config.json (#2852) in #3458
- Guide viewer: Collapse all works after switching views in #3467
- Loopback requests ignore a proxy; a classic plan review exits when its parent is gone in #3461
- Claude Code mod: Orca chat gets the tools and the wake; no Plannotator plan review in Orca (#3325; includes #3400 by @rudycelekli) in #3460
- Inbox: keep a sleeping machine's projects in New message in #3468
- README: Inbox section moves up; Annotate HTML below Herdr Annotate in #3474
- Inbox page: the ending offers the install prompt first in #3479
- Open in test: the macOS expectation for a JetBrains app at a line in #3481
- README: shorter top, AI built in below Commands, one short Sharing section in #3478
- fix(inbox): a short group/project!45 lands on the project's own GitLab, never gitlab.com in #3525
New Contributors
- @rudycelekli made their first contribution in #3210
- @robfeldmann made their first contribution in #3170
- @xunguangzlj-cloud made their first contribution in #3358
- @jiangjiang248 made their first contribution in #3351
- @sx4im made their first contribution in #3343, merged through #3447
Contributors
@rudycelekli sent the most work from outside the project in this release, in his first contributions. He made Mod+Shift+Enter open the note composer in code review instead of posting (#3210), kept typed Windows paths whole on DeepSeek Harness (#3214), fixed links with parentheses in the guide viewer (#3213), added the Last 3 days filter (#3401), made
install.shdownload the binary from a mirror (#3310), and fixed three CI path gates that let breaking changes skip the job meant to catch them (#3215). His Orca work (#3400) ships inside #3460.@mvanhorn added source line numbers to plan review and annotate (#3373) and JetBrains IDEs to the Open in menu (#3372).
@sx4im made his first contribution: session titles in the reply picker (#3343, finished in #3447 with his commits kept). He also fixed the tag and recipient pickers that the reply box cut off (#3440) and malformed addresses in the Shapes routes (#3414).
@robfeldmann found and fixed a wrapped diff that jumped while he reviewed on his phone (#3170), with recordings from a real iPhone. First contribution.
@xunguangzlj-cloud made OpenCode's annotate-last open on the reply to your own prompt (#3358). First contribution.
@jiangjiang248 made Pi's TLS warning point to the host app when Pi runs inside Electron (#3351). First contribution.
@BenNewman100 fixed the header of a table indented under a list item (#3314).
@uvw reported and fixed the Inbox tool going "not connected" after
/bgon a busy Claude Code session (#3369, #3370). His fix also made the Claude Code mod's test harness run on Windows.Community reports and requests that shaped this release:
- @zane668 asked for Last 3 days (#3301) and coloured text in Markdown (#3345), reported the Inbox slowing down while an update downloads (#2788), and kept digging into leftover Inbox processes (#3350), which turned up the proxy and plan review fixes
- @robsonpeixoto asked for a
config.jsonthat works in dotfiles (#2852) - @de-tre asked for source line numbers (#1650)
- @ninjz asked for the Inbox tools in Orca (#3325)
- @jroquejr asked to embed the Inbox in a trusted app (#3299)
- @navin-moorthy reported that
install.shignored the download mirror for the binary (#3298) - @llwt reported the cut-off pickers in the reply box (#3427)
- @brunnojob reported malformed addresses crashing the Shapes routes (#3411)
- @marwashan reported annotate-last opening on replies to plugin messages (#3312)
- @xueccci reported the TLS advice Electron users could not act on (#3346)
- @JasonLandbridge asked for more editors in Open in (#3368); the JetBrains IDEs are a first step
Full Changelog :
v0.28.65...v0.28.66 -
🔗 HexRaysSA/plugin-repository commits sync repo: +2 plugins, -1 plugin, +8 releases, -2 releases rss
sync repo: +2 plugins, -1 plugin, +8 releases, -2 releases ## New plugins - [IDAAutoTheme](https://github.com/baiguqing/idaproautotheme) (1.0.1) - [ida-discord-rpc](https://github.com/reversedcodes/ida-rpc) (1.3.0, 1.1.0) ## New releases - [SigMaker](https://github.com/mahmoudimus/ida-sigmaker): 1.17.0 - [btf2ida](https://github.com/nightshift-labs-ai/btf2ida): 0.1.23 - [cfiscope](https://github.com/nightshift-labs-ai/cfiscope): 0.1.20 - [ida-mcp-bridge](https://github.com/eitapreulajhol/ida_mcp): 0.4.1 - [memlens](https://github.com/nightshift-labs-ai/memlens): 0.3.28 ## Changes - [memlens](https://github.com/nightshift-labs-ai/memlens): - removed version(s): 0.3.3 ## Removed plugins - IDA-Discord-RPC -
🔗 Andrew Healey's Blog Introducing the World's Strongest Sokoban Solver rss
Using agents to do state-of-the-art solver research.
-
- November 15, 2026
-
🔗 @HexRaysSA@infosec.exchange See the 🆕 IDA Malware Analysis add-on live! mastodon
See the 🆕 IDA Malware Analysis add-on live!
Join us for a walkthrough of the new add-on for IDA Pro.You’ll see how it:
→ recognizes packed samples on load and offers to unpack them
→ lets you step through code safely with full-system Windows emulation, no VM needed
→ shows sandbox events, like API calls, right in the disassembly and pseudocodeDemos, use cases, then Q&A. Pick the session that fits your time zone:
📅 Europe: Fri 27 Nov, 15:00 CET
📅 US: Fri 4 Dec, 11:00 ET / 08:00 PTCan’t make it live? Register anyway and we’ll send you the recording.
👉 Save your spot: https://share- eu1.hsforms.com/2KjZMQF5hT3-IU12OLkNb7w2dgu4h
-
🔗 HexRaysSA/plugin-repository commits sync repo: +1 release rss
sync repo: +1 release ## New releases - [kflow](https://github.com/nightshift-labs-ai/kflow): 0.0.4 -
🔗 Register Spill Joy & Curiosity #106 rss
In the Company of the Future episode of Raising An Agent, Quinn and I talked about what a typical week at Amp looks like:
-
I send out a message to the team on Sunday or early Monday morning. Not always, but when I think it's needed or when I'm in the mood to write. There's no strict formula, but these messages are often about what Quinn and I think are the most important things we should be thinking about.
-
On Monday morning we then have our team meeting. That's the only scheduled meeting we have.
-
In that meeting we talk about what's important, then we have silent writing time in which everyone writes down what they plan to ship this week. Then we go through that list.
-
Then we all work on what we talked about and constantly talk to each other in Amp or on Slack.
Justin Jackson decided to implement this at Transistor: message with important things, then meeting on Monday. And he seemed very happy about the outcomes!
So I thought I'd share a little bit about that Monday meeting (since it's coming up tomorrow and already on my mind) because in the podcast we didn't get into the details of it. But, disclaimer: it's a very simple meeting, it's not perfect, it's slightly different each week (intentionally so!), and if you've ever been a part of one you might smile at the idea that there's anything really worth talking about.
Here's the top of the Monday meeting Google Doc right now:
It's important that everyone on the call has that document open and is fully focused on it. No other windows, not prompting the agent on the side. People should pay attention, listen to what others are saying, and build up peripheral vision of the whole team. It's the only meeting in the week, it's an hour. Everyone should be able to focus.
(Also: everybody should have their camera on!)
There are four sections to the meeting: Leave , Talk , Shipping , News Posts. And that already makes it sound fancier than it is.
Because what the whole thing boils down to is this: get everybody on the same page as to what's important this week and together figure out how to achieve those goals or solve those problems. The rest is just there to help.
For the first five minutes of the meeting, we shoot the shit and just talk about whatever until everybody's in the call.
Then we talk about Leave : who's out this week, who's out next week, who's maybe out in 3 weeks. My rule of thumb: the longer you're off, the earlier you should tell your team about it. If you're off on Friday, it's fine to share that on Monday. If you're going to be off for two weeks in the jungle somewhere, you should probably share that two, three weeks in advance. Be an adult.
After that, we get to the main thing of the meeting, the Talk section. In the screenshot above, you can see that I've already put three topics in. These are the most important things I think we should talk about tomorrow. Everybody can add their own topics. While talking about things, we might add sub-bullet- points and notes and links and whatnot.
The Talk section takes up 45min or so. I try to be a good timekeeper and watch the clock so we can get to everything that's in the doc. I probably say "any thoughts, questions, concerns, ideas?" ten times in that meeting, before moving on to the next section. I want everybody to participate.
The results of Talk are different each week: sometimes we find new things to do while talking and I might ask "who wants to own this?" Other times we conclude that we just need to keep doing what we've been doing that week. Or we call out 4-5 things that we need to ship ASAP and formulate a plan for that. Or we all think there's a single most important thing that week and we try to figure out how we can all contribute.
It's very loose. Anything goes really. Again, the goal is alignment and everybody being on the same page. The goal isn't to follow The Process. Many roads lead to alignment.
After Talk and towards the end of the meeting, we get to Shipping and News Posts. For that, I set a timer on my phone, for 2-3 minutes, and we all write down in silence what we plan to ship this week. The goal is to be ambitious. Don't write down things you check off a few hours later. We talked about the important things, now the question is: how are you planning to contribute based on that?
(Last year, when new people joined the Amp team, I often said: the first task on the Amp team is to figure out what your first task should be. I know it sounds silly, or rude, or like we're throwing people into the deep end, and maybe we are, but it's an incredible filter. There are tremendously good people who can show up and after 45min of talking go "how about I do …" Everybody on the Amp team is like that.)
When the timer rings, we go through the list top to bottom, and everybody says in 2-3 sentences what their goal for the week is, their focus areas. I might ask follow-up questions or suggest collaboration, or others might ask whether they can help, etc.
While we go through that, we try and make sure to note down any News Posts(see ampcode.com/chronicle) we need to write and ship that week. In other words: what are you planning to publicly release that week and when exactly? It's important to at least get a rough sense of the timeline, so we don't end up with 3 major features being shipped on the same day.
And… that's it. Then everybody goes off and works on their thing.
But that doesn't mean we won't talk to each other again for a week. No, it's the opposite. There will be lots of in-progress work being shared in #wip and others will ask and give feedback. There will be huddles and tagging of each other in Amp. There will be feedback in #orb-good and #orb-bad and plans will get adjusted based on that.
Could the meeting be better? Sure. But I do think we've hit on a sweet spot where we have just enough process for everybody to be aligned but little enough so it's not a pain in the ass and we have freedom to adjust plans often.
-
And they say models can't be creative: "I asked Fable 5.2 to 'go wild' making a game, and all I got was this Pong clone. And then I played it ..."
-
You have more influence over the future than you think: "The future will be fun. It will be exciting. You will soon be able to create any digital artifact imaginable within a couple of minutes. And many physical artifacts too, though that part is a bit more unclear to me."
-
Linus on "keeping the flame": "Counterintuitively, I've come to learn that keeping the flame alive is far more important to the integrity of our creative pursuits than actually producing the work itself. If we put something into the world that disappoints us, that's okay. We can try again tomorrow, and the day after that, and after that, because the flame will still be there. But if we let the flame wither, by letting the firewoods run out or allowing others to blow it out, there is no tomorrow. There is no fight left in us. We have to start all over again, which may take months, or even years. How do we keep the flame alive?"
-
And since we're talking about creativity… In case you've never seen this clip of Paul McCartney composing Get Back I highly recommend you do. It's an impressive clip on its own, but in the context of the whole Get Back documentary it's extraordinary. They sit there in this huge warehouse studio, they're bored, they're waiting a lot, and not much is going on; they're drinking tea and talk; there's a crew standing around looking at them at all times. And then McCartney feels like he has to push things forward and do something and he sits down and George and Ringo are yawning and it's what I imagine to be the least inspiring atmosphere and yet McCartney starts riffing and that song emerges…. It's very easy and comforting to think that creativity is something that happens or doesn't and that you can't do anything about it. And, hey, that's true, the phrase "some things you can't force" isn't just a cliche. But sometimes, man, I think sometimes you just have to put your head down and see if you can't make creativity happen.
-
I'm really not a big space guy (don't know why, honestly; rockets & space are cool but don't excite me that much), but this was one hell of a video: "Mechazilla catches Starship! Congratulations to the entire SpaceX team on this incredible achievement!" The music! Is that Steely Dan? Who puts such chill music on for this moment? And then it cuts out and you go "holy shit" and then the music comes back and you wonder whether you just watched a little recap scene from a movie filmed in 2053.
-
Paul Ford: The Web Is More Than Enough. Hell yes! I love the web. I stored the link to this post in a little web app that I built on my phone. A native app would be nice, but man, the web is so much better. I can run an agent on the box on which the web app is running, I can deploy ten trillion times a day, I can get easy debug logs, … The web is awesome.
-
This is very, very, very, very, very good: Writing as a thinking tool. So many things to quote here -- the part about writing in the age of LLMs, the "Mess up" rule, the thought about externalized thinking -- so go and read it and then write something.
-
Michael Crichton, psychology, and AI. In the last two years, we've all heard many "… but only a human can do this" claims only for them to look silly a couple months later. So now, whenever something just starts to sound like it's a similar claim, my eyebrows go up. But this one is different. At least I think it is? Interesting stuff.
-
New Ways to Read Ebooks. I'm very much not a "I need to own all my ebooks as files on my disk" kinda guy. I love my Kindle and, hey, maybe love is too strong a word, but I like Amazon. But by now it's just frustrating that I can't give my agent access to my Kindle library and help me find quotes and answers. I'd even buy more books just so I can feed them to my agent, not to read them for me, but to help me refind and extract things. That's all I could think about while reading this post. And that I have to get Amp to hack my Xteink X4.
-
CHIMERA. I don't even know what to say here. It has taken over my brain. All day long I think of this voice. Click that link, watch that video. You must. And then watch these: one, two, three, four, five, six, seven, eight, nine, ten, eleven, and mine. After that, your brain has been taken over too. The next step is to then fork CHIMERA and point your agent at it and go crazy. And then lean back and think about what's going on. Think: if I had to make a computer emit sound like a human voice, how would I do it? And after you've thought about that for a while, remember what CHIMERA does: "my vocal synth models the vocal tract as a network of branching acoustic tubes." And then open it up again and think "this is fucking crazy."
-
If you ever feel sad, watch this video. Works every time.
-
What a job! "You don't have to tell me what day it is." There are just very few things better than watching someone be exceptional at what they do.
If you think "meetings? fuck yeah!" then, uhm, I don't know. But I think you should subscribe:
-
-
🔗 smol-machines/smolvm smolvm v1.35.1 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
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
Full Changelog :
v1.34.0...v1.35.1 -
🔗 HexRaysSA/plugin-repository commits sync repo: +1 plugin, +7 releases, -2 releases rss
sync repo: +1 plugin, +7 releases, -2 releases ## New plugins - [BinQL](https://github.com/thalium/binql) (1.0.0) ## New releases - [btf2ida](https://github.com/nightshift-labs-ai/btf2ida): 0.1.22, 0.1.21 - [cfiscope](https://github.com/nightshift-labs-ai/cfiscope): 0.1.19 - [ida-mcp-bridge](https://github.com/eitapreulajhol/ida_mcp): 0.4.0 - [memlens](https://github.com/nightshift-labs-ai/memlens): 0.3.27, 0.3.26 ## Changes - [memlens](https://github.com/nightshift-labs-ai/memlens): - removed version(s): 0.3.2, 0.3.1 -
🔗 backnotprop/plannotator v0.28.65 release
Follow @plannotator on X for updates
Missed recent releases? Release | Highlights
---|---
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 one
v0.28.55 | Floating reply drafts, now a setting under Experimental, open questions sit next to Reply again, a comment box that keeps unsent comments as Drafts, choose how your list looks: Minimal, Balanced or Detailed, update an older linked machine from this Inbox
v0.28.53 | Start an agent in a new folder, or from a git URL, "+" on each project row starts a session there, a reaction tray, a thread's Links, Settings → Activity, New message offers the open thread's files, Bro mode: agents write to you in plain words
v0.28.52 | Start agents from the Inbox, on by default, a new reply box, Ask AI for everyone, Insights in Settings → Decision data, Plannotator reloads itself after an updateWhat's New in v0.28.65
TL;DR
- New: Take back a reply your agent has not received yet
- Changed: Over Tailscale, Plannotator opens only for your own account
- New: Tag a linked machine's threads; one tag across machines
- Changed: T3 Code threads get the Inbox with no setup
- Fixed: Long threads open on slow connections
0.28.65 lets you take back a reply your agent has not received yet. Over Tailscale, Plannotator now opens only for the account that owns the computer. Tags now work across linked machines, and a T3 Code thread gets the Inbox without any setup. The release has 25 PRs. One is from an outside contributor, @stjepanvrbic, who made a first contribution.
Take back a reply before your agent gets it
Before, once you sent a reply, you could not change it while it waited for the agent. To correct it, you had to send a second message, which could leave two different instructions in the queue. Now a reply that no agent has received yet has a Take back button. It shows beside Send now on the waiting band, on the reply's delivery line, and in the message's ⋯ menu.
Take back saves what you are typing first. Then it puts the reply's words and files back above it in your reply box, with the line "Taken back. Claude Code never got it. Send it again when it's ready." If the reply was the only message in its thread, the thread goes away and New message opens with the same words, files and recipient. When you send again, it goes as a new message.
The Inbox keeps one rule for every agent: a message either is still yours or has been handed over. Once an agent has the message (it was delivered, an agent read the thread, or it went into Codex's queue or a T3 or cloud send), Take back is no longer offered. If you press it at the wrong moment, a quiet line explains why: "Claude Code already has this message, so it can't be taken back. Reply below to change it." A message that has been handed over now reads "Handed to Codex; it takes this at its next step." instead of offering Send now. A taken-back message is gone from every agent's read, from search, from Activity and from decision exports. There is no keyboard shortcut.
#3290, #3291, #3293, #3294, requested in #3229 by @Arobotmaster
Over Tailscale, only the account that owns this computer
Plannotator has no sign-in and is for one person. Over Tailscale, the Inbox now opens only for the Tailscale account that owns the computer. That account gets the full Inbox from any of its devices. Any other Tailscale account is refused. A browser gets a short page that says "This Inbox belongs to this computer's owner" and names the account that tried. An API call, the event stream and
/mcpget a 403 withtailnet_identity_refused.This is a behavior change. Before, the Inbox let in any other login listed in config.json
inboxTailscaleAllowas a guest with a smaller Inbox. Sessions started withplannotator review --tailscaleorplannotator annotate --tailscaleopened for anyone on the tailnet. Both now refuse every account except the owner's. On a machine where Tailscale names an owner,inboxTailscaleAllowis ignored, and startup prints one line that says so. The key still names the owner on a tagged machine, which Tailscale gives no owner. A--tailscalesession on a tagged machine with noinboxTailscaleAllowcannot tell who the owner is, so it does not start, and it says why.Phones and linked Macs are unchanged, because they connect through their own doors. If you shared an Inbox or a
--tailscalereview with another Tailscale account, that account can no longer open it.Tags across linked machines
With two linked Inboxes, such as a MacBook and a Mac mini, you can now tag a thread that lives on the other machine. Add tag is in the row's right-click menu, the phone's long-press sheet and the thread's ⋯ menu, when the other machine runs this version. Tags with the same name are one tag. Spaces at the ends and letter case are ignored, so "Release" and "release" match. When you open a tag in the sidebar, it lists the threads from both machines together, and its counts include them.
Rename, Delete tag and the delete's Undo now change the tag on every linked machine that holds it, from the sidebar and from the Board's Tags dialog. If a machine is asleep, the change waits and applies when the machine is back. An older machine keeps its own tags, and nothing is sent to it. The Board's tag filter and Tags dialog also list tags that only the other machine holds.
T3 Code threads get the Inbox with no setup
Before, a Claude thread in T3 Code needed three steps to use the Inbox:
plannotator t3 login, aclaude mcp addentry and a restart. Now the Claude Code plugin runs in a T3 thread's Claude by itself. The model gets theplannotator_inboxtool. Its messages are filed as that T3 thread, and your reply goes in as a new turn of the running session. T3 keeps its own Plan mode. The T3 sign-in stays useful as a fallback: T3 stops an idle Claude after 30 minutes, and after that the T3 wake sends what still waits.The plugin now also runs in
claude -p, in other Agent SDK apps and in Claude Desktop. There the model getsplannotator_inboxand can write to your Inbox. Nothing wakes those sessions, so the send tells the agent to read the thread later. Plan review and reviews in those sessions work as before.When a reply to a T3 thread cannot go in, the Inbox now says why under the reply: no T3 sign-in, a sign-in that ran out, a sign-in that cannot send into that thread, or T3 not answering. Where signing in fixes it, the line shows the sign-in command with Copy. The line goes away once the reply is delivered.
T3 threads also get two fixes. The Inbox now wakes every kind of T3 thread, not only threads made in the app. That includes threads made over T3's MCP, launched by an agent, scheduled, delegated or provider threads. A reply to a T3 thread also stays owed to that thread when another agent reads the Inbox thread first.
#3362, #3365, #3261 by @stjepanvrbic closing #3311 reported by @agents-nils, #3348 closing #3339 reported by @stjepanvrbic
Long threads open on slow connections
On a slow link, a long thread could fail to open at all. The thread read had an 8-second limit for the whole answer. A 450-message thread is about 450 KB, so at 50 KB/s it could never finish, and the Inbox retried forever. Now the limit counts from the last bytes received, so a slow answer that keeps arriving is read in full. In a test at 50 KB/s, that thread opened in 8.8 s. A read whose bytes stop still fails, and a read cut off partway now shows as a failure instead of an empty answer.
An attached HTML page is now sent compressed both ways, which cuts the bytes for each open from about 617 KB to 175 KB. The Inbox also sends less on its first load: Tater mode's pictures left the Inbox's script, which went from 2,510 KB to 1,991 KB. Switching threads, opening Settings, opening search and picking a file in code review redraw much less. The PR's measurements show these steps 10 to 25% faster.
The Inbox's SQLite store is removed
0.28.63 added an Inbox store in SQLite, off by default. It is now removed, and the Inbox keeps its records in its files only. If you never turned it on, nothing changes. If your Inbox was on SQLite, it moves back to its files at the next start, with every message, and prints one line in the terminal or
inbox.log. The database is kept as a read-only backup in a datedbackup-…-sqlitefolder inside the Inbox's data folder. If the database cannot be read, the Inbox does not start and does not change anything. It says where the messages are and how much disk to free. TheinboxSqlitesetting,PLANNOTATOR_INBOX_SQLITE, Settings → Storage's Backup group andplannotator inbox exportare gone.Code review in the Inbox: off by default
These show only with Code review turned on in Settings → Capabilities.
- Close pull requests from the board. Select mode on the Pull requests board has a Close N action. It closes the picked PRs one at a time through your own
ghorglab. A toast says "Closed N" with Undo, and Undo reopens exactly those PRs. If a PR cannot be closed, the reason shows under the bar in the forge's words. Only the window can close a PR. No agent tool or command can. #3287 - Post a GitLab review after new commits. Posting a review on a GitLab merge request that got new commits after you read it used to be refused. It now posts at the commit you read, as GitHub already did, with line comments placed on that version of the merge request. #3244
Additional Changes
- A self-managed GitLab at any address. A merge request, issue or work item link on a company's own GitLab, such as
git.acme.com, is now recognized by its path, gets the GitLab mark, and attaches to a thread. Withglabsigned in to that host, it also shows live state. The Inbox learns such hosts from glab's own config file (host names only). Post decisions now runs only against github.com, gitlab.com or a host yourghorglabis signed in to. #3305 - One Claude Code session is one participant. A Claude Code session that wrote through a hand-added
plannotator inbox mcpentry could show up as "An agent" and "An agent 2" beside "Claude Code" in a thread's reply picker. It now shows as one participant, and a reply wakes it. #3336, reported in #3309 by @Arobotmaster - A sandboxed agent no longer replaces your Inbox. An agent whose shell cannot reach the Inbox's local address could start a second Inbox and stop yours, so the window had to ask for notifications again. Such a start now refuses with "Could not reach the running Inbox: …" and leaves yours running. #3354
- Start lines in the debug log. With the Inbox's debug log on, each process that starts or waits for an Inbox writes what it waits for to
inbox.log. This helps track down leftover Inbox processes. #3352, for #3350 reported by @zane668 - Sidebar header buttons line up. In the sidebar, Agents' buttons now read Add machine, then Add agent, so Add agent sits under Tags' "+". While a section is closed, its buttons show when you hover or focus its header. #3328
- A killed start no longer blocks the next one. A start that was killed while it took the start lock could make every start in the next 30 seconds fail with "try again". #3300
- The agent face moves to the shared UI , so other parts of Plannotator can show the same animated agent face. The Inbox is unchanged. #3344
- Test and guidance upkeep: #3307, #3327
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: post a GitLab review after new commits, at the commit read by @backnotprop in #3244
- Inbox PR review tests: load the TypeScript grammar before the first test by @backnotprop in #3307
- Inbox: a start killed while taking the start lock no longer blocks the next start by @backnotprop in #3300
- Inbox: remove the SQLite backend; an Inbox on it returns to its files by @backnotprop in #3320
- Inbox: take back an undelivered message (server) by @backnotprop in #3290
- Inbox: taken-back messages leave lists and counts; a handed item says so by @backnotprop in #3291
- Inbox window: Take back an undelivered message by @backnotprop in #3293
- Inbox take back: docs, and the relay, launch and old-plugin proofs by @backnotprop in #3294
- Inbox way back: a starter no longer gives up as the Inbox finishes starting; the test holds on a file by @backnotprop in #3326
- Agent guidance: one experience across a person's linked machines by @backnotprop in #3327
- Inbox: recognise a self-managed GitLab at any address by @backnotprop in #3305
- Frontend performance, batch 1: no bytes or redraws nobody asked for by @backnotprop in #3317
- Inbox: one Claude Code session is one participant in a thread by @backnotprop in #3336
- Inbox: tag a thread from any linked machine; one tag across machines by @backnotprop in #3330
- fix(inbox): wake T3 Code threads whatever id T3 gives them by @stjepanvrbic in #3261
- Inbox sidebar: Tags and Agents headers place and show their add buttons the same way by @backnotprop in #3328
- Inbox: Close picked pull requests from the board, with Undo by @backnotprop in #3287
- T3: a reply stays owed to its thread when another agent reads first by @backnotprop in #3348
- Inbox: with the debug log on, each start says what it waits for (diagnostic for #3350) by @backnotprop in #3352
- Inbox: a starter that cannot reach a running Inbox does not start a second one by @backnotprop in #3354
- Share the Inbox's living agent face with the rest of the UI by @backnotprop in #3344
- Over Tailscale, only the account that owns this computer by @backnotprop in #3141
- Frontend performance, batch 2: slow links (long threads open; HTML pages sent compressed) by @backnotprop in #3356
- Claude Code mod: active in every session, interactive or not by @backnotprop in #3362
- Inbox: a reply waiting on T3 says why and what to do by @backnotprop in #3365
New Contributors
- @stjepanvrbic made their first contribution in #3261
Contributors
@stjepanvrbic wrote the fix that lets the Inbox wake T3 Code threads whatever id T3 gives them (#3261). The fix covers MCP, launched, scheduled, delegated and provider threads. He tested it against a real T3 Code and ran the full CI on his fork. He then reported the case it left open (#3339): another agent's read could take a reply meant for a T3 thread. He also warned that holding such a reply for good would strand a dead thread's reply. That warning shaped the fix in #3348.
Community reports and requests that shaped this release:
- @agents-nils reported that T3 threads made over MCP were never woken (#3311)
- @sx4im opened a fix for the same
mcp:case (#3313), closed in favor of the broader #3261 - @Arobotmaster asked for a way to change a message before the agent gets it (#3229), which became Take back, and reported one Claude Code session showing as several anonymous agents (#3309)
- @zane668 reported leftover background Inbox processes and found a reproduction (#3350), which led to the debug start lines and the sandbox fix
Full Changelog :
v0.28.64...v0.28.65
-
- November 14, 2026
-
🔗 HexRaysSA/plugin-repository commits sync repo: +1 release rss
sync repo: +1 release ## New releases - [kflow](https://github.com/nightshift-labs-ai/kflow): 0.0.3 -
🔗 smol-machines/smolvm smolvm v1.35.0 release
Highlights
- Docker Engine API. smolvm serves the Docker Engine API, with every container running as its own machine. It supports Compose networks, Testcontainers and Dev Containers, image save/load/push/commit, IPv6 networks, and Buildx, which is faster on macOS. (#2172, #2178, #2179, #2181, #2183)
--auto-portspublishes the ports a machine starts listening on. (#2172)- Mac → cloud restore fixed. A checkpoint captured on macOS now restores on Linux hosts, including the agent rootfs digest, packed images and the virtio-fs file state. (#2162, #2163, libkrun #238, #239)
- Branch checkpoints no longer fill the source's RAM. (#2174, libkrun #241)
- Concurrent RAM captures reserve tmpfs, and serve cleans up abandoned checkpoint scratch when it starts. (#2173)
- Supplementary groups are kept on execs into branched and restored machines. (#2004, fixes #2075)
- Credential hosts: injected values are scrubbed from responses. (#2180)
machine updatecan set and remove labels in any machine state. (#2143)
Behavior changes
- In image machines, PID 1 (smolvm's keep-alive init) now runs as root. The workload, every exec, shells and upload ownership still use the image's
USERand its/etc/groupgroups. (#2004) - A CLI start or branch of a machine with supplied-only credentials and no external interceptor now errors. Before, it intercepted silently with no value. A CLI restore with a matching
--credentialre-authorizes the checkpoint's bindings. The embedded and serve paths are unchanged. (#2182) - The Docker Engine API is opt-in. Installing or upgrading never runs
smolvm engine; run it yourself to point docker at smolvm (it selects thesmolDocker context). (#2186) - Credential-host requests are sent with
Accept-Encoding: identityand withoutRange. A response in an encoding other than gzip or deflate is answered with a 502. (#2180)
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
New Contributors
- @rdslw made their first contribution in #2082
- @connorburgess made their first contribution in #2131
- @josmo made their first contribution in #2143
Full Changelog :
v1.34.0...v1.35.0 -
🔗 Luke Muehlhauser Composing classical music with AI agents rss
For 20 years I've wanted to compose contemporary classical music, but I never had the skill or time to do so. Thanks to AI, now I can!
Some of my favorites pieces I've composed with AI so far are:
- hey claude write me a symphony thx (written entirely from only that phrase): a Romantic minimalist symphony inspired by Philip Glass and John Adams
- hey claude write me an oboe concerto thx (same): a Romantic oboe concerto with beautiful melodies
- "Duck-Rabbit": a never-changing Banjo riff sounds different every few measures due to auditory illusions created by the orchestra playing around it
- "De Natura": a dark, driving orchestral piece inspired by prog-rock band Magma
- "Pen Pals to Lovers": an American banjo and Japanese koto send each other "letters," gradually learn the other's language, trade ideas more quickly in person, then fall in love and play together
- "Castells": a musical representation of building a Catalonian "castell" — a tower made of people standing atop one another
- Floating Dreams: a pastoral slow-building orchestral piece inspired by a track by Pat Metheny & Lyle Mays
- Homage to The Necks: an homage to five long minimalist grooves by the jazz trio The Necks
- "Opus 2": a meditative James Syler theme transformed into an epic mini-symphony for large orchestra and choir
- "Squall": inspired by Godspeed You! Black Emperor's "Storm," but with an orchestra, and the end is a cello concerto
My process is simple: I describe the piece I want to the AI (e.g. Claude or ChatGPT), it writes the first draft composition in a notation format called MusicXML, I open that in MuseScore Studio (free) to see the sheet music and play it back with virtual instruments, and then I either ask AI to make adjustments and then import & listen again, or I export the piece to MP3 and ask AI to make a "scrolling score" video I can upload to YouTube. Every piece above was composed with 10 or fewer prompts.
Claude (the AI) is so good at composing that, by the measure of "how many hours of music by this artist do I strongly enjoy listening to?", Claude is already my 32nd favorite musical artist across all genres, from just one month of output alone
(In my experience, Claude Opus 5.5 and Fable 5.2 are better composers than GPT-6.1 Sol.)
The pieces would sound even better if I spent more time "producing" the music in a digital audio workstation (DAW) like Reaper (which AI can also do for you), and if I paid for higher-quality virtual instruments (e.g. Vienna Performer).2
In addition to bringing your own compositional ideas to life, AI can also give new life to works that would otherwise remain unheard. For example, AI can:
- write a speculative completion of a famous unfinished symphony, based on the composer's sketchbooks
- give a Brahms/Dvorak-style orchestral treatment to obscure folk dances catalogued by ethnomusicologists
- create semi-realistic "performances" of classical works that have been published but never recorded3
You'll often get pretty fun (and sometimes good) results just by trying things like "please write me a 4-movement symphony in MusicXML; my favorite composers are [A, B, and C]." But if you want to invest more time for better results, here are some tips from my experience so far:
- If the AI's first attempt at your compositional idea isn't very close to something you want, it's typically better to try again with an updated prompt in a new session, rather than trying to massage the bad first draft closer to what you want.
- In a text file in your working folder, give AI context on your classical music preferences. List favorite composers, point to Spotify playlists, etc. The more detail you've got on specific compositions you've liked vs. disliked, or specific styles you like vs. don't, the better it'll do at composing music you like. (But in some cases you may want the AI to ignore your preferences file, if you're composing for other purposes.)
- To stimulate or amplify your creativity, ask AI for composition ideas meeting certain criteria, or ask it for potential improvements to your own ideas, before you have it write the piece. Items 3, 5, and 6 above are all based off ideas AI came up with.
- Have AI "sketch" ideas for you to give feedback on before it writes an entire piece or movement, especially a large complicated piece with many parts. For example, you might say "Write me a MusicXML file with 20 different melodies with [some properties] played on piano solo, then I'll tell you what my favorites are, and you can use those as the main themes of the piece." Or "Write me a MusicXML file with 20 different kinds of polymeter played on congas and drumset, and I'll tell you which grooves I like best."
- Build and maintain composition-related skill files. (A skill file is just a text file with instructions on how the AI should do a particular thing.) For example, I maintain skill files on (a) how to write MusicXML files that will play correctly in MuseScore, and (b) how to achieve various orchestration effects/sounds.
- You don't need to write these yourself; you can just say "Please write a skill file on how to write MusicXML files that will be 'performed' well when imported into MuseScore" or "Please read as much as you can find online about skillful orchestration and how to achieve different kinds of orchestral effects and sound profiles, and write your findings to a skill file." And then after each composition session, say "Please update the MusicXML skill and the orchestration skill based on what you learned during this composing session."
- E.g. AI added things like this to my MusicXML skill file: "Generate with a script, never hand-typed XML" and "MusicXML can't set MS4's beam groups. MS4 4.7.5 beams 7/8 as 3+2+2." (I don't even know what beam groups are.)
- Consider asking AI to do extensive research before you compose a piece. E.g. for Far-Flung Work Songs, I asked AI to gather as many fully-transcribed "work songs" from folk music traditions around the world as it could find, and keep them in a unified catalogue. It kept a log of sources it couldn't automatically acquire, some of which I could download en masse via a script it wrote, others of which I could choose to acquire manually for it. After the AI had assembled many thousands of work songs from dozens of folk traditions around the world, I asked it to create a simple MIDI file (from the ethnomusicologist's transcription) for each of 50 of the songs from the catalogue that it thought I would find the "most catchy." I then listened to the basic melodies and rhythms of those 50, picked my seven favorites, and asked AI to write orchestrations of them.
-
In general, if you're stuck wondering "Can the AI do X?" or "What questions am I not thinking to ask?" or "Where are skill files stored?" or "How can I make this process simpler for me?" or whatever… Just ask the AI!
-
My favorites are listed here. Of course, Claude has the advantage of composing based on my own desires, and of being able to write music vastly faster than any human can.
- I have purchased the MuseSounds Pro package already, which gets you lots of instruments for a low price.
- I haven't done this myself yet, but for an already-existing score, an AI can be used to (a) transfer a written score into a notation format like MusicXML, and (b) improve the details of that MusicXML file for ideal performance by a program like MuseScore.
-
- November 13, 2026
-
🔗 IDA Plugin Updates IDA Plugin Updates on 2026-11-13 rss
IDA Plugin Updates on 2026-11-13
New Releases:
Activity:
- augur
- haruspex
- IDAPluginList
- cc429fe6: chore: Auto update IDA plugins (Updated: 19, Cloned: 0, Failed: 0)
- plugin-ida
- 7611e42e: fix: declare idaVersions as a range so IDA 9.5 resolves (#39)
- rhabdomancer
-
🔗 HexRaysSA/plugin-repository commits sync repo: +1 plugin, +5 releases, -1 release rss
sync repo: +1 plugin, +5 releases, -1 release ## New plugins - [ida-mcp-bridge](https://github.com/eitapreulajhol/ida_mcp) (0.3.0) ## New releases - [btf2ida](https://github.com/nightshift-labs-ai/btf2ida): 0.1.20 - [cfiscope](https://github.com/nightshift-labs-ai/cfiscope): 0.1.18 - [memlens](https://github.com/nightshift-labs-ai/memlens): 0.3.25 - [threatray](https://github.com/threatray/plugin-ida): 3.0.5 ## Changes - [memlens](https://github.com/nightshift-labs-ai/memlens): - removed version(s): 0.3.0 -
🔗 backnotprop/plannotator v0.28.64 release
Follow @plannotator on X for updates
Missed recent releases? Release | Highlights
---|---
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 one
v0.28.55 | Floating reply drafts, now a setting under Experimental, open questions sit next to Reply again, a comment box that keeps unsent comments as Drafts, choose how your list looks: Minimal, Balanced or Detailed, update an older linked machine from this Inbox
v0.28.53 | Start an agent in a new folder, or from a git URL, "+" on each project row starts a session there, a reaction tray, a thread's Links, Settings → Activity, New message offers the open thread's files, Bro mode: agents write to you in plain words
v0.28.52 | Start agents from the Inbox, on by default, a new reply box, Ask AI for everyone, Insights in Settings → Decision data, Plannotator reloads itself after an update
v0.28.51 | Starred threads, a note when an agent's session has ended, "Back from snooze", Ask about a past decision, expand arrows in guided reviewsWhat's New in v0.28.64
TL;DR
- Changed: Installs and updates download a smaller, compressed copy
- New: A Videos filter on the Artifacts page
- Changed: GitLab comments on a whole file get their own thread
- Off by default: Pull request pictures and videos show in the Inbox
0.28.64 is a small release. Installs and updates now download a compressed copy of Plannotator, the Artifacts page can show only videos, and a GitLab comment on a whole file posts as its own thread. It has 5 PRs, all from the maintainer.
Smaller downloads for installs and updates
Each release now carries compressed copies of the Plannotator binary next to the plain one: a
.tar.xzfor macOS and Linux, and a.gzfor every platform. On macOS (Apple silicon) the download goes from 195.6 MB to 44.9 MB as.tar.xz, or 73.9 MB as.gz.The installers try them in order. On macOS, the install script takes the
.tar.xz, then the.gz, then the plain file. On Linux it takes the.tar.xzonly whenxzis installed, and otherwise starts with the.gz. On Windows, bothinstall.ps1andinstall.cmdtake the.gz, then the plain file. Each copy is unpacked and checked against the same SHA-256 as the plain binary before anything is replaced. If a copy is missing, fails to download or unpack, or does not match, the installer quietly moves on to the next one. Only the plain file can fail the install, with the same messages as before. The installer prints one new line that names the file it used, such asDownloaded plannotator-darwin-arm64.tar.xz.In a test on a Mac, with the download limited to 2 MB/s, an update took about 24 s with the
.tar.xz, 36 s with the.gzand 94 s with the plain file. Updates from inside Plannotator run the same install script, so they get the smaller download too. Older releases have no compressed copies, so installing one of them downloads the plain file as before. To force the plain download, setPLANNOTATOR_SKIP_COMPRESSED_DOWNLOAD=1.A Videos filter on the Artifacts page
The Artifacts page (the Artifacts row in the sidebar) listed videos, but its filters were Images, Pages, Documents and Other files, and every video counted as an image. There was no way to see only the clips. The page now has a Videos filter after Images, and an mp4 or webm sits there instead of under Images. Audio stays under Other files. A thread's own Artifacts grid is unchanged.
GitLab: a comment on a whole file gets its own thread
On a GitLab merge request, a comment on a whole file used to be folded into the review's main note as
**path:** text. It now posts as its own thread on that file, as it already did on GitHub. This works fromplannotator reviewand from the Inbox's Post to GitLab, and was checked on gitlab.com, where each one shows as "started a thread on a file".If GitLab refuses a file thread, as an older self-hosted GitLab may, that comment goes into the main note as before, so nothing is lost. If the file threads go and the note then fails, a retry sends only what is left, so no file thread is posted twice.
Code review in the Inbox: off by default
This shows only with Code review turned on in Settings → Capabilities.
- A pull request's own pictures and videos. On a PR from github.com, the pictures in its description, comments and line threads now show in place, on the PR page and in a thread's full review. Before, each one was a chip saying it opens on the forge. Screenshots written as
<img>tags, such as before and after pairs in a table, show as pictures too. A click, or Enter or Space, opens a picture full screen in the attachment viewer, and a video GitHub saved as a link plays there on a plain click. The Inbox fetches each file through your ownghsign-in, only from GitHub's attachment hosts and only when the PR's text names it. A picture that fails to load stays a chip. GitLab merge requests keep their chips for now. #3165
Additional Changes
- Setup pages for each agent. The site has a new page at plannotator.ai/inbox/agents that lists the agents that work with the Inbox and what each one supports, with a setup page per agent: steps to copy, how to check it works, and fixes for common problems. #3183
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
- Marketing: pages for each agent and what works with the Inbox by @backnotprop in #3183
- Inbox: a PR's own pictures show in its text and open in the viewer by @backnotprop in #3165
- Inbox Artifacts page: a Videos filter by @backnotprop in #3304
- GitLab: a comment on a whole file becomes its own file thread by @backnotprop in #3245
- Installers download a compressed copy of the binary when the release has one by @backnotprop in #3302
Full Changelog :
v0.28.63...v0.28.64 -
🔗 HexRaysSA/plugin-repository commits sync repo: +1 release rss
sync repo: +1 release ## New releases - [kflow](https://github.com/nightshift-labs-ai/kflow): 0.0.2 -
🔗 Anton Zhiyanov Probabilistic data structures in Go 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? Which items appear most often? Unlike deterministic structures like sets and frequency tables, the answers might not be exact, but in return, you can drastically reduce memory usage.
In this post, we'll talk about what probabilistic structures are, how they work, and what kinds of guarantees they provide. I'll also introduce unsure — a package that implements these structures in Go. It's simple (the core logic for each data structure is 100–300 LOC), fast (usually several times faster than other implementations), and has no dependencies except for the standard library.
Bloom filter • Count-min sketch • HyperLogLog • T-digest • Top-k
Bloom filter
A Bloom filter is a set that trades certainty for space. 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 actually store the items, so it's much more compact than a regular set.
For example, a regular set with 1,000,000 distinct 8-byte strings takes about 64 MB. A Bloom filter for the same strings, with a 1% false positive rate, uses only 1.24 MB (about 10 bits per item) — that's 50 times smaller. The size of the filter doesn't depend on the item size, so the difference gets even bigger with longer strings.
A Bloom filter often resides in memory and helps minimize expensive I/O operations such as disk reads or network calls. You check if an item is in the filter, and if the answer is "no", you skip the costly lookup. If the answer is "yes", you still have to perform the lookup because it might be a false positive.
// A filter for 1000 items with a 1% false positive rate. filter := bloom.New(1000, 0.01) filter.Add([]byte("alice")) filter.Add([]byte("bob")) filter.Contains([]byte("alice")) // true filter.Contains([]byte("carol")) // false (or, rarely, true)The filter is sized for the given number of items with a given false positive rate. You can add more, but the false positive rate will go up.
You can add an item to a Bloom filter and check if an item is in the filter, but you cannot delete an item, count the number of items, or iterate over them.
How it works
Bloom filter1 is a large array of m bits, all set to zero at first. To add an item, you compute k hash values for it and set the k bits at those positions:
┌──────┐ ┌───────┐ item ──►│ hash │──► h1, h2, ..., hk ──►│ mod m │──► i1, i2, ..., ik └──────┘ └───────┘ i1 i2 ik ┌───┬───┬─▼─┬───┬───┬─▼─┬───┬───┬───┬───┬─▼─┬───┐ │ 0 │ 0 │ 1 │ 0 │ 0 │ 1 │ 0 │ 0 │ 0 │ 0 │ 1 │ 0 │ └───┴───┴───┴───┴───┴───┴───┴───┴───┴───┴───┴───┘ 0 1 2 m-1To check if an item is in the filter, you compute the same k hashes and check if all k bits are set:
- If any of the bits is not set, the item definitely was never added.
-
If all the bits are set, the item was probably added, but it's not guaranteed (the bits could have been set by other items).
i1 i2 ik┌───┬───┬─▼─┬───┬───┬─▼─┬───┬───┬───┬───┬─▼─┬───┐ │ 1 │ 0 │ 1 │ 0 │ 0 │ 1 │ 1 │ 0 │ 1 │ 0 │ 1 │ 0 │ all 1 → probably in the set └───┴───┴───┴───┴───┴───┴───┴───┴───┴───┴───┴───┘
┌───┬───┬───┬───┬───┬───┬───┬───┬───┬───┬───┬───┐ │ 1 │ 0 │ 1 │ 0 │ 0 │ 0 │ 1 │ 0 │ 1 │ 0 │ 1 │ 0 │ any 0 → definitely not └───┴───┴───┴───┴───┴─▲─┴───┴───┴───┴───┴───┴───┘ in the set (!)
The k bits are randomly distributed throughout the entire array. When the filter is larger than the CPU cache, each bit access could result in a cache miss, so a lookup may wait on memory k times.
Unsure uses a blocked Bloom filter2. The bit array is divided into 512-bit blocks, each matching the size of a CPU cache line. When you add or check an item, it is hashed once: part of the hash selects a block, and the rest selects k bits within that block. Each add or check only accesses one cache line, so the filter stays fast even when it's very large.
┌──────┐ ┌──► high 32 bits ──► block item ──►│ hash │──► h ───┤ ┌─────────┐ └──────┘ └──► low 32 bits ──►│ × salts │──► i1, i2, ..., ik └─────────┘ block ┌───────┬───▼───┬───────┬───────┬───────┬───────┐ │ 0 │ 1 │ 2 │ 3 │ ... │ n-1 │ └───────┴───────┴───────┴───────┴───────┴───────┘ │ │ ┌───────┘ └───────────────────────────────┐ │ i1 i2 ik │ ├───┬───┬─▼─┬───┬───┬─▼─┬───┬───┬───┬───┬─▼─┬───┤ │ 0 │ 0 │ 1 │ 0 │ 0 │ 1 │ 0 │ 0 │ 0 │ 0 │ 1 │ 0 │ └───┴───┴───┴───┴───┴───┴───┴───┴───┴───┴───┴───┘ 0 1 2 511In a blocked Bloom filter, some blocks end up with more items than others, which increases the false positive rate. To make up for this, the filter needs to be a bit larger. Compared to a standard Bloom filter, it uses about 3% more memory at a 1% false positive rate, 8% more at 0.1%, and 15% more at 0.01%.
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 bits- and-blooms6 (a classic Bloom filter) and gloom7 (a blocked one) (ns/op, lower is better):
Operation | Items | unsure | bits-and-blooms | gloom
---|---|---|---|---
Add | 10K | 9 | 37 | 17
| 1M | 10 | 36 | 19
| 50M | 38 | 170 | 63
Contains, hit | 10K | 8 | 32 | 16
| 1M | 9 | 32 | 18
| 50M | 34 | 129 | 60
Contains, miss | 10K | 8 | 41 | 27
| 1M | 9 | 48 | 33
| 50M | 34 | 113 | 60Memory, bits per item at 10M items (lower is better):
False positive rate | unsure | bits-and-blooms | gloom
---|---|---|---
10% | 4.84 | 4.80 | 5.39
1% | 9.90 | 9.59 | 10.79
0.1% | 15.49 | 14.38 | 16.18Unsure is about 4× faster than bits-and-blooms and 2× faster than gloom , using 1–8% more memory than bits-and-blooms and 4–10% less than gloom.
-
Space/time trade-offs in hash coding with allowable errors by Burton H. Bloom, 1970. ↩︎
-
Cache-, hash-, and space-efficient Bloom filters by Felix Putze et al., 2009. ↩︎
-
Reference wyhash implementation by Wang Yi. ↩︎
-
Reference xxHash implementation by Yann Collet. ↩︎
-
bits-and-blooms/bloom by Daniel Lemire. ↩︎
-
jcalabro/gloom by Jim Calabro. ↩︎
Count-min sketch
A count-min sketch is a frequency table that trades accuracy for space. It tells you approximately how many times each item has appeared. The estimate is never less than the actual count, but it can be higher. The sketch doesn't actually store the items, so it's much more compact than a regular map of per- item counts.
For example, a regular map counting 1,000,000 distinct 8-byte strings takes about 64 MB. A count-min sketch for the same strings, with estimates within 0.01% of the total count (with 99% probability), uses only 0.55 MB — that's 116 times smaller. The size of the sketch doesn't depend on the number of distinct items or their size, only on the accuracy you choose. So the difference gets even bigger with more or longer strings.
A count-min sketch is useful when you want to track how many times an item shows up in a large stream of events. It's often used to check if something has happened a certain number of times, like rate-limiting an IP after X requests or sending an alert after an error happens Y times. A sketch can also help decide if a key is worth keeping in the cache given how often it was requested.
// Estimates within 0.1% of the total count, with 99% probability. sketch := countmin.New(0.001, 0.01) sketch.Add([]byte("alice")) sketch.Add([]byte("bob")) sketch.AddN([]byte("alice"), 2) sketch.Count([]byte("alice")) // 3 (or, rarely, more) sketch.Count([]byte("bob")) // 1 (or, rarely, more) sketch.Count([]byte("carol")) // 0 (or, rarely, more) sketch.Total() // 4The sketch uses two settings: epsilon ε and delta δ. If the actual count for any given item is X and the total of all counts is N, then the estimated count for this item will usually be between X and X+ε·N. However, rarely (with a probability of δ) the estimate could be even higher.
For example, if ε is 0.001, δ is 0.01, and N is 1 million, then the estimate could be off by up to 1,000 (ε·N) with at least 99% probability (1−δ), and by more than 1,000 with at most 1% probability (δ).
The counting error in a sketch depends on the total of all counts, not on each individual item. Therefore, frequent items are estimated more or less accurately relative to their count, but rare items are not — the absolute error is too high for them.
You can increase the per-item counter in a sketch and get the estimated count for an item, but you cannot decrease a counter or iterate over the items.
How it works
Count-min sketch8 is a table of counters with d rows and w columns, all starting at zero. Each row uses its own hash function that maps an item to one of the w counters. To add an item, you increment its counter in each row:
┌──────┐ ┌───────┐ item ──►│ hash │──► h1, h2, ..., hd ──►│ mod w │──► i1, i2, ..., id └──────┘ └───────┘ ┌───┬───┬─▼─┬───┬───┬───┬───┬───┬───┬───┐ row 1 │ 0 │ 2 │ 4 │ 0 │ 1 │ 0 │ 0 │ 3 │ 0 │ 1 │ 4 → 5 ├───┼───┼───┼───┼───┼───┼─▼─┼───┼───┼───┤ row 2 │ 1 │ 0 │ 0 │ 0 │ 2 │ 0 │ 3 │ 0 │ 1 │ 0 │ 3 → 4 ├───┼───┼───┼───┼───┼───┼───┼───┼─▼─┼───┤ row d │ 0 │ 1 │ 0 │ 2 │ 0 │ 0 │ 1 │ 0 │ 5 │ 0 │ 5 → 6 └───┴───┴───┴───┴───┴───┴───┴───┴───┴───┘ i1 i2 idTo estimate an item's count, you take the smallest value from its d counters:
- Other items might hash to the same counter, so each counter value is ≥ true count.
- The smallest counter is the one with the fewest collisions, so it's the best estimate.
┌───┬───┬─▼─┬───┬───┬───┬───┬───┬───┬───┐row 1 │ 0 │ 2 │ 4 │ 0 │ 1 │ 0 │ 0 │ 3 │ 0 │ 1 │ 4 ├───┼───┼───┼───┼───┼───┼─▼─┼───┼───┼───┤ row 2 │ 1 │ 0 │ 0 │ 0 │ 2 │ 0 │ 3 │ 0 │ 1 │ 0 │ 3 ├───┼───┼───┼───┼───┼───┼───┼───┼─▼─┼───┤ row d │ 0 │ 1 │ 0 │ 2 │ 0 │ 0 │ 1 │ 0 │ 5 │ 0 │ 5 min = 3 └───┴───┴───┴───┴───┴───┴───┴───┴───┴───┘
With w = e/ε columns, each counter's error is at most ε·N, with probability at least 1 − 1/e. If you use d = ln(1/δ) rows, the chance that all d of the item's counters exceed its true count by more than ε·N is ≤ δ.
Unsure uses a conservative update. When you add n to an item, it first finds the current estimate E (the smallest counter), then increases only the counters that are below E+n, leaving the larger ones unchanged. This keeps the same accuracy guarantee, but the actual error is about 2× lower. The tradeoff is that counts can't be decreased.
┌───┬───┬─▼─┬───┬───┬───┬───┬───┬───┬───┐ row 1 │ 0 │ 2 │ 4 │ 0 │ 1 │ 0 │ 0 │ 3 │ 0 │ 1 │ 4 → 4 ├───┼───┼───┼───┼───┼───┼─▼─┼───┼───┼───┤ row 2 │ 1 │ 0 │ 0 │ 0 │ 2 │ 0 │ 3 │ 0 │ 1 │ 0 │ 3 → 4 ├───┼───┼───┼───┼───┼───┼───┼───┼─▼─┼───┤ row d │ 0 │ 1 │ 0 │ 2 │ 0 │ 0 │ 1 │ 0 │ 5 │ 0 │ 5 → 5 └───┴───┴───┴───┴───┴───┴───┴───┴───┴───┘Counters are 32-bit instead of the usual 64-bit, so the sketch uses 2× less memory. The item is hashed once, and each row gets its own position from that hash by salting it (multiplying by a random per-row constant).
┌──────┐ ┌─────────┐ item ──►│ hash │──► h ──►│ × salts │──► i1, i2, ..., id └──────┘ └─────────┘The sketch uses wyhash for hashing.
Benchmarks
Here's an excerpt from the full benchmarks9, comparing unsure to BoomFilters10 (a classic count-min sketch with 64-bit counters) (ns/op, lower is better):
Operation | ε | Size (unsure) | unsure | BoomFilters
---|---|---|---|---
Add | 0.001 | 55 KB | 13 | 19
| 0.00001 | 5.4 MB | 17 | 32
| 0.000001 | 54 MB | 81 | 98
Count | 0.001 | 55 KB | 9 | 51
| 0.00001 | 5.4 MB | 14 | 64
| 0.000001 | 54 MB | 52 | 139Accuracy at ε=0.0001, N=10M additions over 1M distinct items, mean overestimate (lower is better):
Distribution | unsure | BoomFilters
---|---|---
Uniform | 139 | 302
Zipf, s = 1.1 | 23 | 44
Zipf, s = 1.5 | 0.3 | 0.8
Size | 536 KB | 1080 KBUnsure is about 1.5× faster for Add and 4× faster for Count, using 2× less memory with 2–2.7× lower error.
-
An improved data stream summary: the count-min sketch and its applications by Graham Cormode and S. Muthukrishnan, 2005. ↩︎
-
tylertreat/BoomFilters by Tyler Treat. ↩︎
HyperLogLog
HyperLogLog is a unique items counter that trades accuracy for space. It tells you approximately how many distinct items it has seen, no matter how many times each one appeared. HyperLogLog (also called a sketch from here on) doesn't actually store the items, so it's much more compact than a regular set.
For example, a regular set of 1,000,000 distinct 8-byte strings takes about 64 MB. A HyperLogLog sketch counting the same strings with about 0.8% error uses only 16 KB — that's almost 4,000 times smaller. The size of the sketch doesn't depend on the number of items or their size, only on the accuracy you choose. A 16 KB sketch counts a billion items as accurately as a thousand.
HyperLogLog is useful when you need to count unique things in a large stream: unique visitors to a website, unique search queries per day, or distinct values in a database column.
// Standard error about 0.8% of the true count. sketch := hll.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 gather data from multiple machines or segments (like by hour, page, or region). When you merge two sketches, you get the total number of unique items from both, without counting shared items twice.
home := hll.New() // visitors to the home page docs := hll.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 (stdErr) of 1.04/√(2^p). A common default is p=14, which gives 0.81% error.
With p=14 and 1 million distinct items:
- 68% of the time the estimate is within 0.81% (8,100) of the true count,
- 95% within 1.6% (2·stdErr),
- 99.7% within 2.4% (3·stdErr).
The error is relative to the count, so the standard error is the same 0.81% for a thousand items or a billion.
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
HyperLogLog11 is based on a simple observation. If you hash items to random bit strings, about half of them start with 1, a quarter with 01, an eighth with 001, and so on. Seeing a hash with k leading zeros suggests there were about 2^(k+1) distinct items. Duplicates hash to the same value, so they don't affect the result.
A single observation is unreliable, so the sketch divides the items into m = 2^p groups, where p is the selected precision. The first p bits of the hash pick a group (a register), and the register keeps the highest rank (leading zeros plus one) it has seen in the rest of the hash:
┌──────┐ ┌──────────┬────────────────────────┐ item ──►│ hash │──►│ 01101001 │ 0001101... │ └──────┘ └────┬─────┴───────────┬────────────┘ │ register i └ rank = 3 zeros + 1 = 4 ┌───┬───┬───┬─▼─┬───┬───┬───┬───┬───┬───┐ registers │ 3 │ 0 │ 5 │ 2 │ 1 │ 0 │ 4 │ 2 │ 0 │ 1 │ 2 → 4 └───┴───┴───┴───┴───┴───┴───┴───┴───┴───┘The count is estimated from all the registers together, using a harmonic mean of 2^register. The standard error is about 1.04/√m. Merging two sketches is just taking the maximum value from each pair of registers.
The original estimator is biased when dealing with small counts (up to a few times m), so in these cases it uses a different formula called linear counting. This switch creates a sudden change in error, and some implementations (like HyperLogLog++12) address it by using large tables of bias corrections based on real data.
Unsure uses the improved estimator by Otmar Ertl13. Instead of a harmonic mean of the registers, it works from a histogram : how many registers have value 0, value 1, and so on. A formula applied to the histogram gives an accurate estimate for any number of items, from zero to billions, so there's no need for a separate formula for small counts or for correction tables.
The sketch updates the histogram whenever registers change. Most adds don't change any registers, so this is almost free. Counting always takes the same amount of time, no matter how big the sketch is. Other implementations scan all the registers on every count, which takes from microseconds to milliseconds.
Registers are one byte each, and the histogram has 64 four-byte counters (256 bytes). 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 benchmarks14, comparing unsure to axiom15 (HyperLogLog with LogLog-Beta estimator and sparse mode) (ns/op, lower is better):
Operation | p | Size | unsure | axiom
---|---|---|---|---
Add | 10 | 1 KB | 5.5 | 7.6
| 14 | 16 KB | 5.6 | 7.6
| 18 | 256 KB | 8.1 | 7.9
Count | 10 | 1 KB | 68 | 18,300
| 14 | 16 KB | 62 | 350,000
| 18 | 256 KB | 57 | 4,710,000
Merge | 10 | 1 KB | 730 | 1,710
| 14 | 16 KB | 20,100 | 58,600
| 18 | 256 KB | 341,000 | 951,000Accuracy at p=14 (0.81% standard error), relative RMSE over 100 sketches (lower is better):
Distinct items | unsure | axiom
---|---|---
1,000 | 0.63% | 0.02%
40,000 | 0.64% | 0.71%
1,000,000 | 0.79% | 0.89%Memory at p=14 after adding the given number of distinct items (lower is better):
Distinct items | unsure | axiom
---|---|---
100 | 16 KB | 1.2 KB
1,000 | 16 KB | 4.2 KB
10,000 | 16 KB | 16 KB
1,000,000 | 16 KB | 16 KBUnsure adds about as fast as axiom , counts 270–83,000× faster, and merges 2.3–2.9× faster, with the same accuracy and memory for counts above the number of registers. When there are fewer items than registers, axiom 's sparse mode makes it more accurate and compact.
-
HyperLogLog: the analysis of a near-optimal cardinality estimation algorithm by Philippe Flajolet et al., 2007. ↩︎
-
HyperLogLog in practice by Stefan Heuleet et al., 2013. ↩︎
-
New cardinality estimation algorithms for HyperLogLog sketches by Otmar Ertl, 2017. ↩︎
-
axiomhq/hyperloglog by Axiom. ↩︎
T-digest
A t-digest 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 digest doesn't actually 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 numbers, you'd have to keep all of them. With 64-bit floats, that takes 8 MB. A t-digest estimates the same percentile within about 0.03% of the rank (between the 98.97th and the 99.03rd percentile) using only 8 KB — 1,000 times smaller. The size of the digest doesn't depend on the number of values, only on the accuracy you choose. An 8 KB digest summarizes a billion values as well as a million.
A t-digest is useful when you need quantiles over a large stream: latency percentiles for a service, the distribution of request sizes or prices, or the outlier thresholds in sensor data.
// Response times in milliseconds. digest := tdigest.New() digest.Add(12.5) digest.Add(8.1) digest.Add(130.0) // ... digest.Quantile(0.5) // median digest.Quantile(0.99) // 99th percentile digest.CDF(100) // fraction of responses faster than 100 msYou can merge digests to gather data from multiple machines or segments (like by hour, endpoint, or region). A merged digest estimates the percentiles of all values, but with less accuracy than individual digests do.
east := tdigest.New() // latencies on one server west := tdigest.New() // latencies on another // ... east.Merge(west) east.Quantile(0.99) // 99th percentile across both serversThe digest has one setting: the compression δ , which limits the number of centroids (see How it works below) to δ+2. A common default is δ=100, which takes 8 KB. Increasing δ uses more memory but reduces estimation error.
The error is measured in ranks: a rank error of 0.03% at quantile q=0.99 means the value returned by
Quantile(0.99)is somewhere between the 98.97th and the 99.03rd percentile of the actual values. Tail estimates, such as q=0.99 or q=0.999, are more accurate than the median (q=0.5).You can add numbers to a digest, estimate quantiles and the CDF, and merge digests. You cannot remove numbers or list them.
How it works
T-digest16 summarizes the numbers as a sorted list of centroids. Each centroid has a mean and a weight — the number of values it represents. To estimate a quantile, the digest finds the centroids around the requested rank and interpolates between their means.
The trick is in how big the centroids are allowed to grow. A scale function k(q) maps a quantile q to a number from -δ/4 to δ/4, and each centroid may only span 1 unit of k: if a centroid covers the quantiles from q₁ to q₂, then k(q₂) − k(q₁) ≤ 1.
The arcsine scale function, k(q) = δ/(2π)·asin(2q-1), is steep near q=0 and q=1 and flat near the median. This means the centroids it produces are larger in the center and smaller at the ends:
weight │ ┌──┐ │ ┌──┤ ├──┐ │ ┌──┤ │ │ ├──┐ │ ┌──┤ │ │ │ │ ├──┐ │ ┌─┬──┤ │ │ │ │ │ │ ├──┬─┐ └──┴─┴──┴──┴──┴──┴──┴──┴──┴──┴──┴─┴──► value min q=0.25 median q=0.75 maxWith 1M values and δ=100, the centroids around the median hold about 27,000 values each, those around the 99th percentile about 5,000, and the outermost ones about 500. This keeps the error near the tails small.
Unsure is the merging t-digest from the Dunning and Ertl paper. New values go to a buffer of 5·δ numbers. When the buffer is full, the digest sorts it and merges it with the centroids (already sorted) in a single pass, building new centroids from left to right as long as each one fits within its span of k. Every other pass goes right to left, so that neither tail ends up with fuller centroids.
Quantile,CDFandMergeflush the buffer first.The centroids are kept in two fixed arrays of δ+2 entries (the current list and the next one being built), along with the cumulative weights for a binary search in
QuantileandCDF. With δ=100, that's 16·102·2 + 8·103 bytes for the centroids, and 8·500 bytes for the buffer, about 8 KB in total.Centroids with weight 1 are treated as exact values rather than spread around their mean, and the exact minimum and maximum are used at the ends. So digests with few values give exact results, and
Quantile(0)andQuantile(1)are always exact.Benchmarks
Here's an excerpt from the full benchmarks17, comparing unsure to influxdata18 (merging t-digest with the same scale function) (ns/op, lower is better):
Operation | δ | unsure | influx
---|---|---|---
Add | 50 | 44 | 78
| 100 | 49 | 86
| 500 | 59 | 105
Quantile | 50 | 11 | 13
| 100 | 13 | 13
| 500 | 15 | 16
Merge | 50 | 296 | 2,060
| 100 | 630 | 4,330
| 500 | 2,720 | 23,950Accuracy at δ=100, mean rank error over 1M normal values (lower is better):
Digest | Quantile | unsure | influx
---|---|---|---
Single | 0.5 | 0.007% | 0.015%
| 0.99 | 0.018% | 0.016%
| 0.999 | 0.011% | 0.009%
Merged | 0.5 | 0.055% | 0.037%
| 0.99 | 0.023% | 0.021%
| 0.999 | 0.006% | 0.016%Memory at δ=100 (lower is better): unsure 8.5 KB, influxdata 14.4 KB.
Unsure adds values about 1.8× faster than influxdata , queries at the same speed, merges 7–9× faster, and uses 40% less memory at about the same accuracy.
-
Computing extremely accurate quantiles using t-digests by Ted Dunning and Otmar Ertl, 2019. ↩︎
-
influxdata/tdigest by InfluxData. ↩︎
Top-k sketch
A Top-k sketch finds the k most frequent items in a stream (the "heavy hitters"), along with their approximate counts. It uses a fixed amount of memory based only on k, no matter how many different items are in the stream.
To find the exact top items, you'd have to count every unique item, for example with a map of per-item counts. With millions of distinct items, that takes tens or hundreds of megabytes. A Top-k sketch for the top 1000 items takes about 360 KB, and it usually finds all of them.
A Top-k sketch is useful when you want to identify the "hottest" data: the most requested URLs, the most active users, or the most common search queries. Unlike a count-min sketch, it keeps the actual items, so it can list them.
// Track the 2 most frequent items. sketch := topk.New(2) sketch.Add([]byte("alice")) sketch.Add([]byte("bob")) sketch.Add([]byte("carol")) sketch.AddN([]byte("alice"), 4) sketch.AddN([]byte("carol"), 2) sketch.Top() // [{alice 5} {carol 3}] sketch.Count([]byte("alice")) // 5 sketch.Count([]byte("bob")) // 0 (not in the top 2) sketch.Total() // 9Topreturns up to k items, from the most frequent to the least frequent. Counts are estimates: they're usually exact for the most frequent items, but may be slightly lower than the actual count for less common items.The sketch works best when the stream is skewed, meaning a few items appear much more often than the others. This is common in real situations. If all items are about equally frequent, there is no clear top k, and the results become less accurate.
You can add items to the sketch and get the top items with their counts, but you can't decrease counts or check items that aren't in the top k.
How it works
HeavyKeeper19 is a table of buckets that estimates item counts. It has d rows and w columns, and each item maps to one bucket in each row. Each bucket holds a fingerprint of the item and a count. To add an item, you update its bucket in each row:
- If the bucket is empty or owned by the item, increase its count.
- If the bucket is owned by another item, decay it: decrease its count by 1 with probability b^count (b < 1). When the count reaches 0, the new item takes over the bucket with a count of 1.
┌──────┐add x ──► │ hash │──► h ──► high 32 bits ──► fingerprint = 7 └──────┘ │ │ map to buckets ┌──┴────────────┐ ┌───────┬───▼───┬───────┬───│───┬───────┐ row 1 │ │ fp=7 │ fp=3 │ │ │ fp=5 │ column 2 is owned by x: │ │ 41 │ 2 │ │ │ 980 │ 41 → 42 ├───────┼───────┼───────┼───▼───┼───────┤ row 2 │ fp=9 │ │ │ fp=2 │ fp=4 │ column 4 is owned by another: │ 17 │ │ │ 3 │ 1 │ 3 → 2 with probability b^3 └───────┴───────┴───────┴───────┴───────┘ col 1 col 2 col 3 col 4 col 5
The item's estimated count is the largest count among its buckets. Frequent items quickly reach counts that make decay very unlikely, so they keep their buckets. Rare items keep replacing each other without affecting the frequent ones. An item that becomes frequent later in the stream can still outnumber a less frequent owner and take over its bucket.
Next to the table, the sketch keeps a min-heap with the k items that have the largest estimates so far. After an item's buckets are updated, if its estimate is larger than the smallest count in the heap, the item is added to the heap, and the smallest item is removed. If the item is already in the heap, its count is increased.
┌───────────┐ add x (15) ───────►│ bob 12 │ the root has the smallest count └─────┬─────┘ ┌──────────┴────────┐ ┌─────┴─────┐ ┌─────┴─────┐ │ alice 30 │ │ dave 14 │ 15 > 12: x replaces bob at the root └─────┬─────┘ └───────────┘ 15 > 14: x moves down, dave moves up ┌───────┴──────┐ ┌─────┴─────┐ ┌─────┴─────┐ │ eve 980 │ │ fay 41 │ └───────────┘ └───────────┘Unsure uses d = 2 rows of max(16k, 256) buckets, and a decay base of b = 0.8. The probabilities b^count are precomputed as 64-bit thresholds, so decay is cheap: the count c decreases if a random number is below the c-th threshold.
The original HeavyKeeper uses b = 1.08⁻¹ ≈ 0.93, and more rows. A smaller b lets frequent items lock their buckets faster, which makes the sketch more precise on flat streams. However, if b is too small (like 0.5), the first items to claim buckets keep them permanently, so items that become frequent later are never counted, even if they end up being the most frequent. Using b = 0.8 keeps most of the precision and still catches most late-arriving frequent items. As for the rows, two are enough to protect frequent items from collisions in a single row, and adding more rows only makes the sketch slower.
The item is hashed once. The hash is mapped to a position in each row by salting it (multiplying by a random per-row constant). The fingerprint is the top 32 bits of the hash. The heap uses the 64-bit hash to identify items, so it doesn't compare the actual item bytes.
Each bucket is 8 bytes (a 32-bit fingerprint and a 32-bit count), so the table takes 256·k bytes. The heap takes about 100 bytes per item plus the item itself.
The sketch uses wyhash for hashing and wyrand for random numbers.
Benchmarks
Here's an excerpt from the full benchmarks20, comparing unsure to keiler21 (HeavyKeeper with b = 0.9 and d = ln k) and dgryski22 (Filtered Space-Saving23) on the Zipf s=0.8 stream (time/op, lower is better):
Operation | k | unsure | keiler | dgryski
---|---|---|---|---
Add | 10 | 24 ns | 64 ns | 59 ns
| 100 | 25 ns | 84 ns | 70 ns
| 1000 | 33 ns | 130 ns | 73 ns
Top | 10 | 0.34 µs | 0.64 µs | 0.77 µs
| 100 | 3.7 µs | 13 µs | 14 µs
| 1000 | 75 µs | 270 µs | 292 µsPrecision is the fraction of the reported top k that is in the true top k (higher is better):
k | Zipf s | unsure | keiler | dgryski
---|---|---|---|---
100 | 0.6 | 0.90 | 0.38 | 0.19
| 0.8 | 1.00 | 0.78 | 0.85
| 1.0 | 0.99 | 1.00 | 1.00
| Size | 39 KB | 27 KB | 39 KB
1000 | 0.6 | 0.97 | 0.70 | 0.52
| 0.8 | 1.00 | 0.98 | 1.00
| 1.0 | 1.00 | 1.00 | 1.00
| Size | 364 KB | 414 KB | 453 KBCount error is the mean of |estimate − true| / true over the reported items (lower is better):
k | Zipf s | unsure | keiler | dgryski
---|---|---|---|---
100 | 0.6 | 14% | 94% | 428×
| 0.8 | 0.10% | 46% | 230%
| 1.0 | 0.01% | 0.12% | 0.0%
1000 | 0.6 | 2.4% | 62% | 18×
| 0.8 | 0.23% | 1.9% | 0.31%
| 1.0 | 0.05% | 0.24% | 0.02%Unsure is 2–4× faster than the others for Add and 1.8–4× faster for Top. On flat streams (s=0.6), it finds the true top k with 90–97% precision, while keiler drops to 38–70% precision with a count error of 62–94%, and dgryski to 19–52% with counts 18× or more too high. On skewed streams (s=1.0), all three are about equally accurate.
-
HeavyKeeper: An Accurate Algorithm for Finding Top-k Elephant Flows by Junzhi Gong et al., 2018. ↩︎
-
keilerkonzept/topk by KEILERKONZEPT. ↩︎
-
dgryski/go-topk by Damian Gryski. ↩︎
-
Efficient Computation of Frequent and Top-k Elements in Data Streams by Ahmed Metwally et al., 2005. ↩︎
Wrapping up
As engineers, we usually want exact answers from our data. But sometimes, allowing a bit of uncertainty can cut memory usage by tens, hundreds, or even thousands of times. That's where probabilistic data structures come in:
- Bloom filter checks if an item might be in a set.
- Count-min sketch estimates how many times each item has occurred.
- HyperLogLog estimates the number of distinct items.
- T-digest estimates quantiles of a stream of numbers.
- Top-k sketch identifies the most frequent items in a stream.
To use them in Go, try the __nalgeon/unsure package:
go get github.com/nalgeon/unsure -
🔗 smol-machines/smolvm smolvm v1.34.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
New Contributors
- @rdslw made their first contribution in #2082
- @connorburgess made their first contribution in #2131
Full Changelog :
v1.34.0...v1.34.4 -
🔗 backnotprop/plannotator v0.28.63 release
Follow @plannotator on X for updates
Missed recent releases? Release | Highlights
---|---
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 one
v0.28.55 | Floating reply drafts, now a setting under Experimental, open questions sit next to Reply again, a comment box that keeps unsent comments as Drafts, choose how your list looks: Minimal, Balanced or Detailed, update an older linked machine from this Inbox
v0.28.53 | Start an agent in a new folder, or from a git URL, "+" on each project row starts a session there, a reaction tray, a thread's Links, Settings → Activity, New message offers the open thread's files, Bro mode: agents write to you in plain words
v0.28.52 | Start agents from the Inbox, on by default, a new reply box, Ask AI for everyone, Insights in Settings → Decision data, Plannotator reloads itself after an update
v0.28.51 | Starred threads, a note when an agent's session has ended, "Back from snooze", Ask about a past decision, expand arrows in guided reviews
v0.28.50 | A faster, lighter Inbox, session names across the Inbox, initiatives on the Board, earlier comments on a file, global comments on Guided ReviewsWhat's New in v0.28.63
TL;DR
- New: Pair Grok Bot and other cloud agents from Settings
- New: Hermes Agent, OpenClaw and Muse Code can use the Inbox
- New: Add a thread to Priority to keep it on top
- New: Tag threads, and find each tag in the sidebar
- Off by default: Pull requests board as a table, with bulk Merge
0.28.63 brings personal and cloud agents into the Inbox. You can pair an agent that runs somewhere else, such as Grok Bot or Muse by Meta, and Hermes Agent, OpenClaw and Muse Code can now message you from the same computer. The Inbox also gets Priority, tags, replies that quote what they answer, and OpenCode in New message. It has 81 PRs. Three come from external contributors, and one of those is a first contribution: welcome @mauricedesaxe.
Personal and cloud agents
Pair a cloud agent from Settings
A cloud agent is an agent that runs somewhere other than your computer: a Claude Code routine, Grok Bot, Muse by Meta, a Hermes Agent or OpenClaw server, or any other agent you can send a message to. Settings → Cloud agents pairs one. Pick its kind, give it a name, and copy the one message Plannotator shows you. The message is shown only once. Send it to the agent and it sets itself up from a public page on plannotator.ai. A Claude Code routine gets three short pieces for its settings instead. The card then says "Waiting for to connect…" until the agent's first call, and "Connected" after that.
Once paired, the agent shows in New message's To list and in the sidebar's Agents. It can start threads, read the threads it started, was sent or was tagged in, and answer in them. It cannot answer your questions, approve anything, run anything on your computer, open your files, or read any other thread. Its messages pass through Plannotator's relay sealed end to end, so the relay cannot read them. If your computer is asleep, a read says so and a send waits at the relay until the computer is back.
To have the agent start when you write to it, add its wake address and key, then press Send a test. The thread then shows a line such as "Woke Nightly fixer · run started". Without a wake address the agent checks for new messages by itself, and your reply reads "Saved for …" and then "Delivered", like a reply to Muse Code or Cursor. Muse by Meta has no wake address, so it always checks by itself. New pairing stops the old pairing at once, and Remove cuts the agent off. A How does this work? button beside the section's title opens a five-step walk-through in pictures.
The section appears once the Inbox has reached the relay. #3138, #3178, #3187, #3197, #3212, #3223, #3254, #3270
Hermes Agent, OpenClaw and Muse Code on your computer
Three more agents can use the Inbox from the same computer.
- Hermes Agent (Nous Research) gets the
plannotator_inboxtool through a new plugin, and your reply comes back into the Hermes session that asked, as a new turn. Only your own sessions get it: the terminal, the TUI, the Desktop app and your own direct messages. Install it withhermes plugins install backnotprop/plannotator/apps/hermes-plugin --enable, then runplannotator inboxonce to turn the tool on. That line installs the plugin from this repository's main branch; the plugin's README explains the reply switchplannotator inboxturns on, and how to turn it off. #3217, #3238, #3249 - OpenClaw gets the tool in your own chats only: OpenClaw on this computer and your own direct messages, never a shared chat or a channel. Your reply arrives in the same chat as a new message, once. It needs OpenClaw 2026.11.5-beta.1 or newer. The
@plannotator/openclawpackage is not on npm yet; the plugin's README shows how to install it from a checkout of this repository today. #3216, #3251, #3263 - Muse Code (Meta's coding agent in the terminal) is connected when you run
plannotator inbox. Its messages show as Muse Code, with Muse's own mark. Replies don't start a Muse turn, so Muse reads your answer on its next turn, as Gemini CLI and Cursor do. #3209, #3262
Each has a row in Settings → Agents and a mark of its own in the sidebar, the list and the To list. The Inbox tool for Hermes Agent and OpenClaw starts off until
plannotator inboxor Settings → Agents turns it on.After two days of use, a one-time dialog says that your personal agents are welcome in the Inbox, with Connect one , which opens Settings → Cloud agents. It shows only while none is connected. #3280
Starting and managing agents
- Start OpenCode from New message. To offers "OpenCode · New session" next to Claude Code, Codex and Pi, with a model and a variant (OpenCode's word for effort). Replies, Stop, the run line and Open in Terminal work as they do for Pi and Codex. It needs OpenCode 2 and the Plannotator OpenCode plugin from this release. #3186
- Pick Codex's model and effort. The "Default model" button now works for Codex too, and Effort shows only the levels the picked model takes. #3177
- Find a model in a long list. When the Model column lists more than 8 models, it starts with a "Find a model" field that narrows the list as you type, the way Pi's own model selector matches. #3200
- A machine switch in To. With a linked machine, the top of New message's To list has one button per machine, with how many agents run there. Pick one to see what runs there and what you can start; an asleep machine says since when. #3257
- Stop and Delete from the sidebar. An agent the Inbox started now has "Stop" and "Delete … session…" in its sidebar menu. Delete asks in a dialog, and its "Also archive its N threads" box is off by default. #3241
- Rename an agent. Right-click an agent in the sidebar, or use its ⋯, and choose Rename…. The name shows everywhere the Inbox names that agent. Agents still see their own labels. #3180
- Linked machines keep their own marks. An agent's icon and name, and a star on a thread, now live on the machine the agent or thread belongs to, so every linked window shows the same one. Starring another machine's thread used to fail with "No thread". #3234, #3246
- Starting agents on a linked machine. Four fixes: the "+" tip no longer names the machine twice, "+" no longer opens an empty To for an asleep machine this page never read, picking an agent kind only another machine has now starts it there, and the Board's New card lists only this Inbox's projects. #3233
- A Claude Code turn that ends in an error says so. When a session the Inbox started hits a credit, sign-in or rate-limit error, the thread gets one note with Claude Code's own words and a Try again button. A notification follows for Claude Code, Codex and Pi, under the same rules as a question's notification. #3184, #3195
- Claude Code in VS Code's chat panel. Sessions in the Claude Code extension's panel now get the Inbox tool and are woken by your replies, as in the terminal. This has not yet been tried in a real VS Code panel. #3151, toward #3111 by @Qwenjin
Plannotator Inbox
Priority
The row menu, the phone's long-press sheet and a thread's ⋯ menu have Add to Priority. The thread moves to a Priority section at the top of the list, shown only when it holds a thread, and stays there until you remove it or archive it. Its row keeps all its marks. A toast offers Undo.
An agent can also mark a thread with send_message's new
priority: true, or take the mark out withpriority: false. Its instructions say to follow you: use it when you said something matters most to you, and take it out when that is over. An agent's mark is the same as yours, and you can remove it at any time. Agents never see which threads are in Priority. #3232, #3277A one-time dialog, "Put a thread first in your list", shows how to add a thread to Priority. It comes the day after an update at the earliest, and only if you have never used Priority. #3286
Tags
A thread can now have tags. Add tag is in a row's menu and a thread's ⋯ menu: find a tag, tick it, or type a new name. Tags get their own section in the sidebar, under Starred, with each tag's waiting count; a click lists that tag's threads. Right-click a tag to rename or delete it, with Undo. Typing
#Namein your own reply tags the thread too.On the Board, "Initiative" is now "Tag", and a Board card's tag is the same tag a thread has. Existing initiatives show up as tags, with nothing to move. Agents never see a thread's tags. #3228, #3272
Reply with a quote
Press ↩ on an older message, and the reply box gets one quiet line with that message's author, time and first words. Select words in a message first, and the line quotes those words instead. Your own messages get ↩ too. The sent reply shows the same line, which takes you back to the original. The agent reads which message, or which words, you answered. A plain Reply is unchanged. #3160, closing #3109 by @Arobotmaster
See which session wrote what
A thread that several agent sessions wrote in used to show only a people icon and a count. The header now shows the sessions' marks and "N sessions"; hover, tap or focus it to see each session's name and state ("waiting on you", "working", "idle", "ended"), and click a name to filter the list to it. Each message in such a thread leads with its session's name. #3163, closing #3108 by @zane668
Comments
- On your own messages and on questions. Select words in your own earlier message, or in any part of a question card (the prompt, the context, a choice), to comment on them. A comment never answers or settles a question, and a click on a choice still picks it. #3176
- Files, voice and a kept draft. The comment card now takes any file, not only pictures, and has the reply box's microphone. A global comment's words and files are kept while you write, so a reload or another window opens the card with them. #2862 by @iurysza
- Send waits for comments still saving. On a slow connection, a Send pressed while a comment was still saving went out without it, and the comment stayed behind as a draft. Send now waits, so one reply carries every comment. A review's verdict waits the same way. #3240
Bitbucket pull requests on threads
An agent can now attach a Bitbucket Cloud pull request to its thread by its URL. The row and the header show its state, checks and review, a Bitbucket PR link in a message gets a hover card, and a Board card moves to Done once its PR is merged. Bitbucket has no CLI, so the new config key
bitbucketTokenCommandcan read the token from a command, such as one that reads your Keychain, instead of from an environment variable or a plain-text file. The token stays in memory and never reaches the agents the Inbox starts. #3076 by @uvw, closing #3075 by @uvwMore in the Inbox
- Filter to Not seen. The list's Filter menu has a new first row, Not seen , that shows only the bold threads. #3226
- Accept recommended steps aside while you type. On a phone it sat just above the keyboard's Done, and one stray tap replaced your answer. It now hides while you type in a question's fields, keeps your Other… words, and adds Undo to the card's status line. #3268
- Your reply box is yours. A draft that arrives late, or from another device, no longer drops into a reply box you already opened. It waits beside the box as Restore draft. #3250
- HTML files open in Interact. An HTML file beside a thread now opens with the pen off, so a click does what the page says. Turn Annotate on and it stays on as you move through the thread's files.
]and[step between files from inside a page too. #3235 - Arrow keys between attachments. With focus on one of a message's file tiles, the arrow keys move between that message's tiles. The O keycap now shows only when no file is open. #3237
- The agent icon picker. A click on an agent's icon now opens the picker instead of stepping through faces. A picked set icon or picture gets its own page with Use this icon , so nothing changes until you press it, and the dialog stays centred. #3227
- Hide Starred and Projects. Customize sidebar, and the sidebar's right-click menu, can now hide the Starred and Projects sections. #3252
- Highlighting by touch. On an iPad, a selection made with a finger turned into a highlight mid-drag and lost iOS's handles. It now waits until the finger lifts, and the selection stays. #3142
- Picture choices open on their set. A waiting question's picture opened from a file tile or the Artifacts view now opens on the question's set, at its choice, as the zoom button does. #3255
- Pictures inside the choices. Agents are now told to put each option's picture inside its choice, so you can pick by picture, and the hint to resend a question as picture choices fires only when the pictures really are the options. #3179, #3167
- Two choices that start the same. Two choices with the same words before the dash were read as one answer, and the agent heard the first one whichever you tapped. Each now keeps its whole text. #3260
- Back on a phone moves an answered thread out of "Waiting on you", and an opened earlier reply now says "Delivered to ". #3258
- Self-managed GitLab. A merge request attached by its short form (
team/project!45) now opens on the project's own GitLab host instead of gitlab.com. #3225 - A thread's stacked PRs show one under the other in the desktop PR card, instead of squeezed side by side. #3283
Code review in the Inbox: off by default
These show only with Code review turned on in Settings → Capabilities. Until 0.29 that switch shows only if you turned Code review on before.
- The Pull requests board as a table. A desktop's board bar gets Grid | Table. The table has a row per PR (title, author, state, checks, risk, updated, size) under each repository, with sortable columns that keep a stack together. #3243
- Select and bulk Merge. Select on the board picks PRs, a whole repository at once or a range with shift-click. Merge N merges the picked PRs that can merge now, one at a time, after a second click to confirm; it lists what stays and why, and reports each result. #3247, #3279
- One PR opens its own page. Clicking a single open PR in Reviews, or its tile on the board, opens one page for it: the guided review, the diff, its review thread and Details. #2743
- Open review thread. In a thread's PR list, each open PR has an "Open review thread" line that opens its review thread, or its page in Reviews if it has none yet. #3278
- GitLab's whole-stack view now opens more lines with the expand arrows, and compares a layer from a fork instead of saying it can't. #3242
Code review
- Videos in PR descriptions play. A video attached to a GitHub PR description now plays in the review instead of showing as a link. Videos inside an HTML document or embed can also go full screen. #2952 by @mauricedesaxe, closing #2941 by @mauricedesaxe
- GitLab's MR switcher and stacks.
plannotator review <MR url>showed an empty switcher. It now lists the project's recent merge requests, finds the stack from them, and numbers them!12. #3248 - Code colouring.
.mfiles are coloured as Objective-C and.plas Perl (they were Wolfram and Prolog).justfile,*.gradle,.zshrcand*.svgget colour, as do the fence labelspatch,env,postgresql,mysql,gradleandhpp. A suggestion is coloured like the diff beside it. #3281 - Collapse all files right away. A click on Collapse all files just after opening All changes was dropped while the code view loaded. It now applies once the view shows. #3253
Additional Changes
- Inbox storage on SQLite, still off unless you set it.
inboxSqliteinconfig.jsonnow has a proof on all six release builds, and fixes for moving the files on Windows and for a 30-second wait after a hard kill. Files stay the default for everyone. #3124 - Relay. Mailbox creation has a strict per-address limit (per /64 for IPv6), and the relay refuses plain HTTP itself. The relay is deployed on its own. #3273, #3275
- README and docs. The README describes the Inbox as the review layer for work with many agents and names personal assistants. #3266, #3251
- Site deploy keeps hand-uploaded files under
assets/hosted/. #3276 - CI. The Test jobs can run on self-hosted runners, never for a fork's or a bot's pull request, and TypeScript is pinned at the root. #3259, #3267
- Tests. No test can reach the hosted relay any more, and a guard keeps it so. Several flaky and stale tests are fixed. #3274, #3282, #3284, #3224, #3231, #3269, #3285, #3288
- Release pipeline packs and publishes
@plannotator/openclawlike the Cline plugin. #3289
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
- Run the Claude Code mod in the VS Code extension's chat panel by @backnotprop in #3151
- Show a Claude Code turn that ended in an API error in its thread by @backnotprop in #3184
- Inbox: the folder box's never-start list keeps the folders' order by @backnotprop in #3224
- Inbox: say "choices have no pictures" only when the pictures are the options by @backnotprop in #3167
- Reply with a quote: say which message, or which words, a reply answers by @backnotprop in #3160
- OpenClaw plugin: the Inbox in the owner's own OpenClaw chats, with replies coming back by @backnotprop in #3216
- Inbox: comments on your own messages and on questions by @backnotprop in #3176
- Inbox: tell agents to put each option's picture in its choice by @backnotprop in #3179
- Inbox: wake a paired cloud agent by its webhook (step 1) by @backnotprop in #3138
- Inbox: filter the list to threads you have not seen by @backnotprop in #3226
- Hermes Agent plugin for the Inbox: tool, owner filter and native reply wake by @backnotprop in #3217
- Notify when a launched session's turn ends in an error by @backnotprop in #3195
- Name each session in a thread with several sessions by @backnotprop in #3163
- Rename an agent from its sidebar row by @backnotprop in #3180
- Inbox: a paired cloud agent gets its own agent door (step 2) by @backnotprop in #3178
- Inbox: a paired cloud agent reaches the Inbox through the relay (step 4) by @backnotprop in #3187
- Inbox: pair a cloud agent from Settings with one message to send it (step 5) by @backnotprop in #3197
- Inbox: say when plannotator inbox turns on Hermes's wake switch, and how to undo it by @backnotprop in #3238
- Inbox: Muse by Meta as a cloud agent by @backnotprop in #3212
- Inbox: a star on a linked machine's thread lives on that machine by @backnotprop in #3234
- e2e: the Mark read toast spec taps Undo where the toast rests, after the last Undo has ended by @backnotprop in #3231
- Inbox: short GitLab refs open on the project's own GitLab host by @backnotprop in #3225
- Inbox: fix starting agents on a linked machine (tip, asleep +, agent kind, Board projects) by @backnotprop in #3233
- Inbox: an HTML file opens in Interact, and the pen keeps your choice through the thread by @backnotprop in #3235
- Highlighting by touch waits until the selection is finished, and keeps it by @backnotprop in #3142
- Inbox: tags for threads and Board cards (step 1: sidebar section, Add tag, the Board says Tag) by @backnotprop in #3228
- Inbox: one PR opens its launchpad by @backnotprop in #2743
- Inbox: pick Codex's model and effort when starting it by @backnotprop in #3177
- Inbox: connect Muse Code by @backnotprop in #3209
- Inbox: Bitbucket Cloud pull requests on threads, and a Bitbucket token read from a command by @uvw in #3076
- Inbox: Customize sidebar can hide Starred and Projects by @backnotprop in #3252
- Inbox: hide the O keycap while a file is open; arrow keys between a message's attachments by @backnotprop in #3237
- Inbox storage: SQLite behind a setting; the compiled binary proven on six builds by @backnotprop in #3124
- Fix two flaky tests: an early Collapse all click, and the import crash test by @backnotprop in #3253
- fix(review): play GitHub attachment videos in PR descriptions by @mauricedesaxe in #2952
- Inbox: start OpenCode sessions from New message, with model and variant by @backnotprop in #3186
- OpenClaw and Hermes docs: version floor, why the tool starts off, what was tested by @backnotprop in #3251
- Inbox: Hermes Agent's mark is its own Nous girl by @backnotprop in #3249
- Inbox: Back takes an answered thread out of Waiting on you; an opened reply says Delivered by @backnotprop in #3258
- Inbox: a click opens the agent icon picker, a picked icon gets a page with Use this icon, and the dialog sits centred by @backnotprop in #3227
- Let a repo variable move the Test jobs to self-hosted runners by @backnotprop in #3259
- Inbox Settings: Cloud agents under Agents, six kinds, one calm setup step by @backnotprop in #3223
- Questions: keep two choices with the same words before the dash apart by @backnotprop in #3260
- Give global comments the reply composer by @iurysza in #2862
- Inbox: the Pull requests board as a table by @backnotprop in #3243
- Cloud agents: How does this work? walk-through by @backnotprop in #3254
- Close the gaps the self-hosted Test proof run found by @backnotprop in #3267
- README: describe the Inbox as the review layer and name personal assistants by @backnotprop in #3266
- Fix the browser smoke test: Agents link locator matched two links by @backnotprop in #3269
- Inbox: open a waiting question's picture choice on its set from a tile or the Artifacts view by @backnotprop in #3255
- Thread tag marks read in the same order while open and after a restart (flaky every-read test) by @backnotprop in #3272
- Keep a linked machine's agent's face and name on that machine by @backnotprop in #3246
- Inbox: Select mode on the Pull requests board by @backnotprop in #3247
- Relay: a hard per-IP count on mailbox creation by @backnotprop in #3273
- Site deploy: keep hand-uploaded files under assets/hosted/ by @backnotprop in #3276
- Tests never contact the hosted relay by @backnotprop in #3274
- Accept recommended steps aside while you type, keeps Other words, and can be undone by @backnotprop in #3268
- Inbox: the person's Priority (PR 1 of 2) by @backnotprop in #3232
- Inbox: a reply to a cloud agent with no wake address reads Saved, then Delivered by @backnotprop in #3270
- Inbox: filter long model lists when starting an agent, as Pi's model selector does by @backnotprop in #3200
- Inbox: Muse's mark is Meta's blue Muse squiggle by @backnotprop in #3262
- Settings and OpenClaw README: why OpenClaw and Hermes start off; how to install OpenClaw before it is published by @backnotprop in #3263
- Inbox priority spec: never the hosted relay by @backnotprop in #3284
- relay: IPv6 /64 brake key, https-only Worker, live check (builds on #3273) by @backnotprop in #3275
- Inbox: a Send waits for comments still saving, so one reply carries them all by @backnotprop in #3240
- Tests never contact the hosted relay: unit tests' hand-built child envs by @backnotprop in #3282
- Inbox: a thread's stacked PRs one under the other in the desktop PR card by @backnotprop in #3283
- Colour .m, .pl, more file names and fence labels; colour suggestions like their diff by @backnotprop in #3281
- Inbox: Stop and Delete on a sidebar agent's menu by @backnotprop in #3241
- Inbox: bulk Merge on the Pull requests board by @backnotprop in #3279
- feat(inbox): one-time dialog announcing personal agents by @backnotprop in #3280
- Fix two stale browser tests: comment pictures input, Accept recommended after a note by @backnotprop in #3285
- Inbox: "Open review thread" under each open PR in a thread's PR list by @backnotprop in #3278
- Inbox: an agent can mark a thread Priority (send_message priority: true|false) by @backnotprop in #3277
- Inbox To: a machine switch for linked machines by @backnotprop in #3257
- Pages only spec: expect the window's picture policy as served (one hosted folder) by @backnotprop in #3288
- Inbox: a draft that arrives after the reply box was opened waits behind Restore draft by @backnotprop in #3250
- GitLab: MR switcher list and stack discovery in the review app by @backnotprop in #3248
- Inbox: expand arrows and fork layers in GitLab's whole-stack view by @backnotprop in #3242
- Inbox: a one-time Priority dialog in the line of one-time dialogs by @backnotprop in #3286
- Release: pack and publish @plannotator/openclaw like @plannotator/cline by @backnotprop in #3289
New Contributors
- @mauricedesaxe made their first contribution in #2952
Contributors
@uvw wanted Bitbucket pull requests on Inbox threads without leaving the token in every program's environment, filed it as #3075, and built it in three layers: Bitbucket links read as pull request refs, a token read from a command and held only in memory, and the Inbox's rows, hover cards and Board marks. A clean-room test of the agent text, in the same PR, caught a smaller model storing a Bitbucket PR as a GitHub ref, and the wording was fixed.
@mauricedesaxe reported that a video attached to a PR description showed as a bare link (#2941), then made it play in the review, with a fallback to the link whenever the video can't load.
@iurysza gave global comments pictures, files, voice and a kept draft. That work became the one comment card the Inbox now uses everywhere.
Thanks also to the people whose issues shaped this release:
- @Arobotmaster asked for Reply to show which message, or which words, it answers (#3109)
- @zane668 reported that a thread's header showed only a count of sessions, not their names (#3108)
- @Qwenjin reported that Inbox replies did not wake Claude Code sessions in the VS Code extension (#3111)
Full Changelog :
v0.28.62...v0.28.63 -
🔗 smol-machines/smolvm smolvm v1.34.3 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
New Contributors
- @rdslw made their first contribution in #2082
- @connorburgess made their first contribution in #2131
Full Changelog :
v1.34.0...v1.34.3 -
🔗 Project Zero Policy and Disclosure: 2026 Edition rss
Since 2021, Project Zero has followed a “90 + 30” vulnerability disclosure policy, allowing vendors up to 90 days to remediate a vulnerability plus an extra 30 days “soak time” for patch rollout. Our goal was to encourage faster patching and give vendors time to deliver patches to users. The advent of AI- assisted vulnerability discovery and exploitation has changed the threat landscape such that the vulnerability remediation timeline encouraged by our disclosure policy is clearly insufficient.
LLMs have increased the speed at which attackers can find and exploit vulnerabilities, alongside the risk that multiple parties, including malicious ones, discover the same bug. A vulnerability reported today presents a much higher immediate risk to users than one reported last year. In this new environment, it is crucial that vendors move towards remediating vulnerabilities faster.
LLMs have also decreased the time it takes for attackers to reverse engineer and exploit a vulnerability based on a patch, to the extent that zero patch- to-exploitation time is a reasonable, though imperfect, model of attacker behavior. Patch soak time is no longer meaningful in a world where attackers can almost immediately determine bug details from a patch, and can put users at risk by creating a false sense of secrecy. “Patch gap” is the time between a fix being released for a security vulnerability and the user installing the relevant update. It is equally crucial that vendors reduce patch gap, either by reducing patch rollout time or using other strategies to protect users while remediation is in progress.
LLMs have also increased the volume of vulnerabilities that Project Zero reports. We are finding several vulnerabilities a week in targets where we once found a few vulnerabilities a year. Aspects of our policy that require vendor negotiation or agreement, including determining whether a bug is fixed and whether grace period applies, are quickly becoming unmanageable.
Today, we are announcing a new vulnerability disclosure policy, created with the following goals in mind:
- Encourage faster vulnerability remediation
- Encourage vendors to reduce “patch gap”
- Allow for the policy to be automated by both Project Zero and vendors
Our new policy: “Full X”
Vulnerabilities will be disclosed X days after they are reported to the vendor.
Starting today, our policy is “Full 90”, i.e. vulnerabilities will be disclosed 90 days after they are reported to the vendor.
On February 2, 2027, we will move to a “Full 60” policy where vulnerabilities are disclosed after 60 days.
On January 3, 2028, we will move to a “Full 30” policy where vulnerabilities are disclosed after 30 days.
We are also removing most ‘special cases’ from our disclosure policy, including grace period and variant policy. The only exceptions to our new policy are:
- Vulnerabilities actively exploited in the wild -- ITW vulnerabilities will be handled according to Google’s application security vulnerability disclosure policy
- Public vulnerabilities -- Project Zero may make details of a vulnerability public, at our discretion, if the details have already been made public by others
- Vendor request -- We will make vulnerability details public if the vendor we reported it to requests it
Why reduce remediation time gradually?
Project Zero solicited feedback from the vendors we report the most vulnerabilities to as a part of developing this new policy. An overarching concern was that immediately changing the policy could harm users by making unfixed vulnerabilities available to attackers while vendors are in the process of improving their remediation processes and technology. While the benefits of delaying disclosure are declining due to the increased probability that attackers will discover a vulnerability during the embargo period, we still feel there are benefits in the short term.
In addition, vendors mentioned two more subtle concerns. One was that an overly-aggressive disclosure policy would encourage fixing bugs reported under the new policy with more priority, even if they are less severe than other reported vulnerabilities. The other was that immediately enforcing a policy that some vendors aren’t equipped to meet might lead to a state where vendors accept that they cannot fix bugs within the deadline and don’t attempt to.
We decided on a policy that encourages vendors to improve remediation time on a schedule that is challenging but realistic, with the hope that this will lead to vendors broadly improving their remediation processes and infrastructure in a way that eventually enables them to fix all reported vulnerabilities quickly.
What about severity?
While our analysis isn’t always perfect, Project Zero only reports vulnerabilities with substantial severity and demonstrated security impact in our tracker. That said, we don’t feel severity is an effective metric for making disclosure decisions, especially in the current environment. A vulnerability’s severity does not affect the likelihood that it will be discovered by attackers, only its impact on users.
When vendors determine severity and use it to prioritize bug fixes, they are making decisions about what risks they are willing to expose their users to, and it is reasonable to accept the risk of low-severity bugs, like unexploitable null pointer crashes or minor info leaks in a lot of circumstances. But this doesn’t change the availability of these vulnerabilities to attackers, and we want our policy to reflect this reality.
It’s also important to acknowledge that Project Zero holds itself to high standards with regards to the reproducibility, readability, reachability and reported security impact of the vulnerabilities we report. This policy assumes bugs reports are of this quality, and it is reasonable for vendors to treat low quality-bug reports differently.
What about hardware?
We encourage all vendors to consider how they would respond to imminent disclosure of a serious vulnerability, including non-patch strategies, as there is no guarantee that defenders will be the first to find a bug. That said, Project Zero has occasionally granted exceptions to our policy on rare occasions, including Spectre and Meltdown, and will continue to do so in the future.
Are you really not going to check whether bugs are fixed?
The question of whether a bug is fixed for the purposes of our policy has always been challenging and somewhat unresolved, particularly with regards to code that is not shipped directly to users and not publicly available. It is not unusual for Project Zero to communicate with vendors multiple times for each bug report to come to an agreement on whether a vulnerability is fixed. As more vendors experiment with vulnerability remediation strategies that are not patching like temporarily disabling code paths, we expect this to become even more complex.
We still plan to track whether bugs are fixed and communicate if they are not, however, this will not be a decision point in our policy. This will enable us to share technical details of how users are protected without needing to make a binary judgement with consequences for the vendor.
-
🔗 smol-machines/smolvm smolvm v1.34.2 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
New Contributors
- @rdslw made their first contribution in #2082
- @connorburgess made their first contribution in #2131
Full Changelog :
v1.34.0...v1.34.2 -
🔗 Jeremy Fielding (YouTube) I Built An Automated High Speed Camera Robot rss
This work was supported by the Alfred P. Sloan Foundation, enhancing public understanding of science and technology in the modern era, in partnership with IMI: watch what matters. https://www.theimi.co/ & https://sloan.org/programs/public-understanding
Order custom parts Send Cut Send 👉 http://sendcutsend.com/jeremyfielding
PBC Linear Rail Shown in the video 👉 https://pbclinear.com/blogs/blog/mt-series-belt-driven-linear-actuators-which-one-should-you-choose?utm_source=youtube&utm_medium=video&utm_campaign=jf&utm_term=mtb-actuators
If you want to join my community of makers and Tinkers consider getting a YouTube membership 👉 https://www.youtube.com/@JeremyFieldingSr/join
If you want to chip in a few bucks to support these projects and teaching videos, please visit my Patreon page or Buy Me a Coffee. 👉 https://www.patreon.com/jeremyfieldingsr 👉 https://www.buymeacoffee.com/jeremyfielding
Social media, websites, and other channel
Discord 👉https://discord.gg/F3XuyhNRPc Instagram https://www.instagram.com/jeremy_fielding/?hl=en Twitter 👉https://twitter.com/jeremy_fielding TikTok 👉https://www.tiktok.com/@jeremy_fielding0 LinkedIn 👉https://www.linkedin.com/in/jeremy-fielding-749b55250/ My websites 👉 https://www.jeremyfielding.com 👉https://www.fatherhoodengineered.com My other channel Fatherhood engineered channel 👉 https://www.youtube.com/channel/UC_jX1r7deAcCJ_fTtM9x8ZA
Notes:
Technical corrections
Nothing yet
-
🔗 Filip Filmar TxHDL today: a Rust HDL, its parts, and what runs on it rss
TxHDL is a hardware description language that is a Rust library, and a complete system ready to use. Its standard library holds the parts a system on chip needs: buses, a network on chip, memory, an MMU, Ethernet, video, debug and system control. On top of them run a RISC-V core that boots Linux, a GPU and a FireSim host link. Simulation, formal proof and the official RISC-V tests check all of it. This page describes TxHDL as it stands in November 2026. The earlier posts show it at the stages it passed through.
-
