- ↔
- →
- November 18, 2026
-
🔗 gildas-lormeau/single-file-cli v2.27.3 release
SingleFile CLI 2.27.3
CLI fixes and improvements
- On Windows, the capture works again with a Chromium-based browser launched by the tool. In 2.27.1 and 2.27.2, every capture failed with "No available debugging port", unless
--browser-serverwas used (#212 by @johanjohan). - The browser launch is now tested on Windows before each release.
Co-authored by Claude (Claude Code)
- On Windows, the capture works again with a Chromium-based browser launched by the tool. In 2.27.1 and 2.27.2, every capture failed with "No available debugging port", unless
-
🔗 @HexRaysSA@infosec.exchange 🔧 IDA 9.5 brings native UEFI firmware support mastodon
🔧 IDA 9.5 brings native UEFI firmware support
Load a full SPI flash dump into one database. IDA maps the modules, names the globals, identifies known GUIDs and links protocol calls to their implementations across modules.
👉🏽 https://hex-rays.com/blog/introducing-native-uefi-firmware-support-in- ida-9.5
-
🔗 HexRaysSA/plugin-repository commits sync repo: +1 plugin, +4 releases, -1 release rss
sync repo: +1 plugin, +4 releases, -1 release ## New plugins - [apiscout](https://github.com/danielplohmann/apiscout) (3.0.0) ## New releases - [cfiscope](https://github.com/nightshift-labs-ai/cfiscope): 0.1.22 - [kflow](https://github.com/nightshift-labs-ai/kflow): 0.0.7 - [memlens](https://github.com/nightshift-labs-ai/memlens): 0.3.30 ## Changes - [memlens](https://github.com/nightshift-labs-ai/memlens): - removed version(s): 0.3.5 -
🔗 gildas-lormeau/single-file-cli v2.27.2 release
SingleFile CLI 2.27.2
CLI fixes and improvements
- With Chromium, the screenshot embedded by
--embed-screenshotno longer shows the top of the page again on long pages. The browser does not render more than 16,384 px of height in one capture, so a longer page is now captured in several regions which are joined into one image (#213 by @johanjohan). When--embed-screenshot-optionsis set, the page is still captured in one piece with the options given.
Co-authored by Claude (Claude Code)
- With Chromium, the screenshot embedded by
-
🔗 gildas-lormeau/single-file-cli v2.27.1 release
SingleFile CLI 2.27.1
CLI fixes and improvements
--embed-screenshotand--embed-pdfembed the screenshot and the PDF again. Since 2.18.1, the file was saved without them, and without any warning, unless a settings file definedremoveAlternativeImages(#212 by @johanjohan).--remove-alternative-imagesgiven on the command line is no longer ignored when a settings file defines the same option.- With Chromium,
--browser-widthand--browser-heightnow set the size of the viewport, as they already did with Firefox. They used to set the size of the window, and the browser kept 87 px of its height for itself: a page was laid out in 1280x633 by default, it is now laid out in 1280x720.--browser-device-widthand--browser-device-heightstill take precedence. - When the page crashes in Chromium during the capture (e.g. when it runs out of memory), the error is now "Page crashed" and it is reported at once. It used to be reported as a capture timeout, after the whole delay.
- With Firefox, a page that navigates to another URL from a script before its load event is now captured. The capture failed with a navigation error.
- A capture now checks that the browser it connects to is the one it launched. When several captures were started at the same time with Chromium, two of them could be given the same debugging port, and one of them failed.
- Updated single-file-core to 1.14.3:
- an imported stylesheet that is truncated or leaves a block, a string or a comment open no longer swallows the rules that follow it in the page
- the adopted stylesheets of a shadow root are now saved after its own
<style>elements, which is their place in the cascade
Co-authored by Claude (Claude Code)
-
🔗 backnotprop/plannotator v0.29.0 release
Follow @plannotator on X for updates
Missed recent releases? Release | Highlights
---|---
v0.28.67 | Drag threads to Priority, Archive or Quiet, or onto another thread to combine them, mention another thread in your reply, Linear hover cards, pick any tag colour, a linked computer's pictures and files open here, pull request cards say why they could not load
v0.28.66 | Pick several threads and archive or snooze them at once, combine picked threads into one; Tidy follows your own words, rows take their tag's colour; filter and search by tag, files an agent's message names open beside the thread, swipe rows on phone or iPad; list can show archived threads, Antigravity and Orca use the Inbox; T3 Codex threads get replies, Open in lists JetBrains IDEs, Routines: run a saved prompt on a schedule
v0.28.65 | Take back a reply your agent has not received yet, over Tailscale, Plannotator opens only for your own account, tag a linked machine's threads; one tag across machines, T3 Code threads get the Inbox with no setup, long threads open on slow connections
v0.28.64 | Installs and updates download a smaller, compressed copy, a Videos filter on the Artifacts page, GitLab comments on a whole file get their own thread, pull request pictures and videos show in the Inbox
v0.28.63 | Pair Grok Bot and other cloud agents from Settings, Hermes Agent, OpenClaw and Muse Code can use the Inbox, add a thread to Priority to keep it on top, tag threads, and find each tag in the sidebar, Pull requests board as a table, with bulk Merge
v0.28.62 | Agents started from the Inbox now work on Windows, pick a model and effort when you start an agent, rules for your agents, written in your own words, post a thread's decisions on its pull request, the Inbox loads faster on a slow connection
v0.28.61 | Updates now update the Claude Code plugin too, an agent's chosen face shows on every icon of it, filter the Inbox list by pull request state, Modern dark shows section bands and the Reply button, one conversation no longer shows as two agents
v0.28.60 | Click a word to highlight it, a one-time Themes dialog, Settings → Rows rebuilt, tell your agent how you want your rows, starred threads as pills above the list, a pill for new messages out of view, a half-circle face picker with ten Glass colours, a new phone sidebar and reply box
v0.28.59 | A quieter Agents section in the sidebar, machine names only when agents run on more than one machine, agent icons that are always gently alive and lean toward your pointer
v0.28.58 | Start Codex from New message, an Agents section in the sidebar, start an agent in a folder on any drive, play audio attachments and comment at a moment, Claude Code's Plannotator tools work on Windows
v0.28.57 | Pin artifacts, and see every artifact on one page, filter the list by project, date or agent, a thread shows its pull requests and their state, choose what the sidebar shows, and in what order, Ask AI starts from Side in the selection bar
v0.28.56 | Questions can show trade-offs and a prototype to try, a thread with many big pictures no longer crashes the tab, Escape closes New message and keeps your draft, read threads stop being bold and keep their place, agent messages that name no thread start a new oneWhat's New in v0.29.0
TL;DR
- New: A redesigned code review window: two panes, a faster file tree, image diffs and a minimap
- New: Semantic diffs: moved, renamed and reformatted code drawn as what it is, in eleven languages
- New: Comment in a code review and talk it through with your agent, through the Inbox
- New: Code review in the Inbox is now a switch in Settings → Capabilities (off until you turn it on)
- New: Hide a pull request or a whole repository from Reviews and the PR board
- New: Playback speed for videos and recordings in the Inbox
- New: Routines:
plannotator routinecommands, a/create-routineskill, Edit and Runs tabs, a list filter - Fixed: On Claude Code 2.1.326 with a Team or Enterprise account, the agent could not open Plannotator
- Fixed: A linked machine whose Inbox started before Tailscale stayed "asleep"
- Fixed: Typing in the reply box on very long threads lagged, and undo took back one letter at a time
- Removed: Code Tour
v0.29.0 is the code review release. The review window that
plannotator reviewand/plannotator-reviewopen has been rebuilt: a new file tree, two panes with tabs, semantic diffs, image diffs, a minimap, one launch pad for guided reviews and review agents, and review comments that become conversations with your agent. In the Inbox, the Code review switch is now in Settings for everyone. The release also fixes two problems that stopped things working: Plannotator could not open from the agent on Claude Code 2.1.326 for Team and Enterprise accounts, and a linked machine could stay unreachable after Tailscale came back. The release has 48 PRs. Thirteen come from outside contributors: twelve fixes from @rudycelekli and a playback speed menu from @MaxKless, their first contribution.Fixed: Plannotator would not open from the agent on Claude Code 2.1.326
(Team and Enterprise)
Claude Code 2.1.326 added an "early run" rule to its built-in
cc-plugin-sec- defaultguard, which is on for Team and Enterprise accounts and on machines with managed settings. The rule refuses a plugin that starts a program repeating a tool call the model just made. Plannotator's Claude Code plugin starts the review window at exactly that moment, so on these accounts an agent'splannotatorcall (annotate, review, last) failed with:Plannotator could not start: plannotator: $.process.run: this repeats a Bash call that is not allowed; serve an allowed call at tool.runA
Bash(plannotator:*)allow rule did not help. Slash commands you typed yourself, such as/plannotator-review, still worked, and so did the Inbox.The plugin now waits for the tool's run step, where the guard allows it, and opens the window there. On a guarded machine the call first goes through your session's own permission check (your rules, mode or a prompt), as the guard requires. On older Claude Code versions nothing changes. One cost remains on guarded machines whose organization has its own tools, such as managed MCP servers or organization plugins: Claude Code may print one "plannotator: its hook was skipped" line per session. It is harmless, and it does not stop Plannotator from opening.
This was tested on Claude Code 2.1.287, 2.1.325 and 2.1.327 against a stand-in that follows the guard's rule, not on a guarded account itself. If Plannotator still does not open for you on a Team or Enterprise account after updating, please open an issue with the message you see.
A new code review window
The review window has been rebuilt from the file tree out. Everything it did before still works, with these changes:
- A new file tree. Changes and All files are one fast tree, built on Pierre's tree library. Group files by kind (Code, Docs, Tests, Generated) or by Git status (Committed, Staged, Unstaged, Untracked) from the tree's menu. Git status is no longer a separate tab: pick that grouping and it opens the same way. Git add and unstage sit on each row, long names shorten in the middle and keep their extension, and the arrow keys move through files and open each one.
- Two panes and tabs. "Open to the side" puts a second file beside the first, with a divider you can drag. Tabs sit in the header row, so opening a file never pushes the code down. Each tab can show the Diff, the Current file or the Original. A review you open again comes back with the same panes, tabs and divider.
- Image diffs. A changed image shows side by side, as a swipe with a divider you drag, or as an onion skin with an opacity slider. Highlight differences tints the pixels that changed, and an SVG can show as an image or as source.
- A minimap at the right edge of long diffs shows where the changes and comments are. Click it to jump there.
- One launch pad in the Agents tab: Guided Review and Review agent, each with a Start button that uses your saved picks. Your saved guides for this repository are listed under This diff, This PR and Earlier, with how much you have read, and can be renamed, downloaded, shared or deleted. Past runs list their findings by rank, and a click goes to the most serious one.
- Collapse all files sits in the top bar. On a commit-by-commit review, Expand all now stays on as you step from commit to commit.
- Cmd/Ctrl-click on a name now jumps straight to its definition when there is exactly one. Otherwise it opens References, as before.
- Large diffs open and scroll faster , and a tap right after a scroll is no longer lost.
Removed: Code Tour, with its dialog, settings and Mod+Shift+T shortcut. A review saved in tour mode opens as a normal code review. The nine first-run announcements in the review window are gone too.
Semantic diffs: moved and renamed code, drawn as such
A plain diff shows moved code as a deletion in one place and an addition in another. With semantic diffs, the review window draws it as what it is:
- Moved code folds into one "Moved N lines" row in its old place, with a band to where it went. Code that moved and also changed stays open, in purple.
- A rename highlights only the name that changed.
- Code that was only reformatted is drawn quiet and grey, so a real edit next to it stands out.
- Each block is labelled moved, moved & edited, renamed, reformatted, extracted or inlined. Each file header has a sem N menu listing that file's changes, and the Semantic diff tab lists every change in the review by name, for example
rate -> taxRate. A row in either one jumps to the change.
It reads TypeScript and TSX, JavaScript, Python, Go, Rust, Java, C#, PHP, Ruby, Kotlin and Swift. The work happens in your browser, and no code leaves your computer for it. Other files, and anything that takes longer than about three seconds, keep the normal diff. Turn it off with Show moved & renamed code in the diff display options, or turn off the whole feature with Settings → Analysis → Semantic changes.
Power Up (Settings → Semantic diffs) is an optional second look by a model, for changes the engine could not label on its own, such as code extracted into a new function. It is off until you add a key for one of its two models. When it is on, the code in question goes to the model you chose. You can turn down a link it draws.
The Inbox PR page now draws semantic diffs too, with the same switch in its diff options.
Talk through a review comment with your agent
When the Inbox is running, a comment in the review window can go straight to your agent as a conversation. Type
@in the comment box to pick a connected agent and send it now, or leave comments as before and use Send or Send all in the new Threads tab. Send all goes to the agent as one review, with each comment as its own thread.Replies show under the lines they are about, with Queued, Delivered and Read, a reply box, and Resolve. If the code changes under a thread, the thread stays on the lines that took its place and shows the old code. If the code moved, the thread follows it. Each conversation is an ordinary Inbox thread, and Open the review of … in that thread's header opens the review again with its threads in place.
The first comment goes to the agent that opened the review (Claude Code, Pi and OpenCode). Without a running Inbox, the comment box works as it did.
Code review in the Inbox, now in Settings
Settings → Capabilities → Code review is now shown to everyone. It is off until you turn it on, and the Inbox does not offer it in a pop-up. If you already had it on, it stays on. Turning it on gives you:
- Reviews in the sidebar: your agents' reviews and your open GitHub and GitLab pull requests in one list, with a project filter. Type
/in a reply to ask an agent for a review, then approve it, send feedback to the agent, or post it on the pull request. - The Pull requests board , as a grid or a table, Open or Merged, with bulk actions. It now follows the project chosen in Reviews, and its running checks mark turns while checks run.
- PR pages with the same file tree as the review window and semantic diffs. Your unsent comments and Viewed ticks stay until a new commit lands, even when someone adds a label or a comment. When you send feedback on a pull request you opened yourself, the agent makes the change and pushes it to the branch. On a teammate's pull request it still changes nothing unless you ask.
- Hide for a pull request (row menu in Reviews, the PR page bar, the board's tile and select mode) and for a whole repository (its header on the board). Hidden pull requests leave Reviews, the board and every count, and nothing is done on GitHub or GitLab. Each Hide has Undo, and a Hidden fold at the end of Reviews lists them with Show again. A hidden pull request stays hidden through new commits and comments until you show it again.
- Set risk rules : describe in your own words what makes a pull request risky, and an agent ranks each open pull request High, Medium or Low against them, with one sentence why. It runs only once you have written rules.
Code review in the Inbox is separate from
plannotator review, which works the same with the switch on or off.#3626, #3610, #3613, #3609, #3627, #3612, #3628, #3653, #3622, with earlier work in #2640 and #2694
Fixed: a linked machine stayed "asleep" after Tailscale came back
Two faults on the far machine kept a linked machine unreachable:
- An Inbox that started while Tailscale was not running never published its link for other machines, and never tried again. It now checks for Tailscale after 30 seconds, then less and less often, up to every five minutes, and publishes the link as soon as Tailscale runs. While the link is up, it checks every ten minutes that Tailscale still points at it.
- After an Inbox crashed or stopped while Tailscale was off, the mapping it left behind pointed at a port where nothing listened. The next Inbox refused it as someone else's mapping. The Inbox now remembers the mappings it made and points its own dead ones at the new run. A mapping it did not make, or one in use, is never touched.
Typing on long threads
On a heavy page, such as a list of about 550 threads or a thread of about 600 messages, every key in the reply box did work that grew with the page, so holding Backspace could fall seconds behind. Each key now does a fixed, small amount of work. Chrome's undo also takes back a whole run of typing again instead of one letter at a time, and a pick from the
/,$or@list is its own undo step. That last part is for Chrome and other Chromium browsers; Safari is listed under Known issues. A/,$or@list now opens only when you type, not when you delete back into a trigger.Routines
For people who use Routines:
- Agents can make routines.
plannotator routine create|list|get|update|on|off|run|deletecovers every field of the editor. The Inbox has a built-in/create-routineskill that teaches an agent how. A routine an agent makes arrives off, and only you turn it on the first time. When you ask for it yourself with/create-routine, that request counts as your approval, and the routine is made on. - Edit and Runs tabs on each routine. Runs lists the newest 20 runs, each one a link to that point in the thread. The Edit tab shows how the last run went, in red when it did not start or did not finish.
- Filter the list by routine. The list's Filter has a Routine group: "Routine threads" and "Other threads".
- A one-time intro to Routines, with No thanks and Turn on , shown once to people who have sent messages in the Inbox on three different days.
- Two fixes from @rudycelekli: rescheduling a one-time routine while its run was getting ready no longer runs the old time and marks the new one Done (#3545), and two windows editing the same routine no longer undo each other's changes or bring back a deleted routine (#3552).
Playback speed for videos and recordings
Videos and recordings in the Inbox have a speed menu: 1x, 1.2x, 1.5x, 1.7x and 2x. The speed you pick applies to every video and recording you open in that tab until you close it. On a video, the "1x" chip sits in the line under the film, so it never covers the browser's own controls. On a phone, the menu opens as a sheet.
By @MaxKless in #3534, their first contribution, finished in #3582 with their commits kept
Fixes from
@rudycelekli sent twelve fixes, each with a test that failed before it:
- Last commit on a branch with one commit now shows that commit. Before, it showed nothing on a clean checkout, or your uncommitted edits. #3547
- Before the first commit , Uncommitted changes and Since base now include files you have staged with
git add. #3551 - Staging
row[1].txtfrom the review tree no longer also stagesrow1.txt. Stage and unstage now take the file name literally. #3544 - A submodule change shows as its normal one-line pointer change whatever your
diff.submodulesetting is. #3542, related to #3533 from @luwanglin - OpenCode Ask AI reports a prompt that OpenCode rejects, such as an unknown model, instead of waiting for a reply that never comes (#3548), and no longer starts a second
opencode servewhen it is stopped during startup (#3543). - Linked documents in plan review and annotate open in the order you clicked them, and a note you add while the next file loads is kept. #3550
- Restoring an annotate draft no longer drops an older note when a new one arrives from the same source. #3546
- An MP4 you upload to the Inbox keeps its length and size, and an audio-only MP4 shows as a recording, as it does when an agent attaches it. #3549
- The two routine fixes listed under Routines (#3545, #3552), and a fix to how CI picks the browser tests for a change when a path has unusual characters (#3541).
Ten of them landed together in #3624, with each commit and its authorship kept.
Additional Changes
- Your Inbox rules reach Claude Code sessions the Inbox starts. The rules under Prompts → Inbox ("Rules for your agents") reached sessions you started in a terminal, but a session started from the Inbox only got them after a compaction. They now come with its first wake. #3594
- Pick an OpenCode agent at launch. With OpenCode picked in To, the model menu has an Agent column: Default, build, plan and any primary agents you made. The thread's start line names it, and a reply that starts OpenCode again keeps it. #3621
- Contents for short documents. A Markdown document opened in the Inbox shows its Contents rail from two headings, not four. #3621
- Remove a link from a Board card. Each link in an opened card has a quiet ×. The card's history says what was removed. #3621
- Groundwork with no visible change: card parts for host apps in
@plannotator/ui, and Inbox work that stays off. #3572, #3579, #3581, #3586, #3587, #3569, #3570, #3584 - Test upkeep: #3608
Known issues
- Python docstrings. A change inside a docstring can be labelled "reformatted" in a semantic diff, so it is drawn quiet and grey although the words changed.
- Semantic diffs on a phone. The moved and renamed bands show without their labels, and the switch to turn them off is not offered there.
- Comments in a folded moved block. Commenting on lines inside a folded "Moved N lines" block opens the fold only when the comment sits on the old side's hidden lines. A comment that starts inside the block and ends outside it leaves the block folded.
- The file tree's search box shows what you type in lower case. The search itself is not affected.
- Undo after a pick in Safari. In the reply box, one undo right after picking from the
/,$or@list empties the box. Redo brings it back. Chrome is not affected. - Opened lines can move on a pull request page. If you open hidden lines in a file during the first few seconds, before the moved and renamed notes have arrived for the files above it, those lines shift by a few rows when the notes arrive. Nothing is lost; scroll back to them. Opening lines after the notes have drawn is not affected.
- An expand arrow may need a second click while a file's header still says "reading…". This is most common in Safari, and also happens in Chrome on the first click after a pull request opens.
Install / Update
macOS / Linux:
curl -fsSL https://plannotator.ai/install.sh | bashWindows:
irm https://plannotator.ai/install.ps1 | iexClaude Code Plugin: The install script above also updates the plugin when
claudeis on your PATH. Otherwise, in a terminal:claude plugin marketplace update plannotator claude plugin update plannotator@plannotator --scope userThen restart Claude Code. Inside Claude Code, run
/plugin marketplace update plannotator, then open/plugin→ Installed → plannotator → Update now.Pi:
pi update npm:@plannotator/pi-extensionOpenCode: Re-run the install script above. It also clears the OpenCode 2 plugin cache.
What's Changed
- Inbox: internal groundwork, off in #3569
- UI frame: card parts for host apps in #3572
- Inbox: internal groundwork, off in #3570
- UI frame: card grid gap by size; the focus ring's colour in the docs in #3579
- UI frame: card rows and a visible row focus in #3581
- Inbox: playback speed menu for videos and recordings (1x to 2x) by @MaxKless in #3534
- Inbox: playback speed menu under the film, a sheet on a phone (finishes #3534 by @MaxKless, with their commits) in #3582
- Inbox: internal groundwork, off in #3584
- UI frame: card rows keep their title in narrow lists in #3586
- UI frame: plain names in the card example in #3587
- Claude Code: a session the Inbox starts gets your Inbox rules on its first wake in #3594
- Routines: Edit and Runs tabs on a routine in #3596
- Code review redesign: file tree, two panes, semantic diffs, image diffs, minimap, launch pad, live review threads; Code Tour removed (carries #3324, #3331, #3332, #3337, #3338, #3340, #3342, #3347, #3349, #3353, #3357, #3360, #3361, #3389, #3391, #3394, #3408, #3413, #3417, #3428) in #3383
- Inbox:
plannotator routinecommands and the/create-routinebuilt-in skill in #3601 - Fix a flaky selection bar browser test in #3608
- Inbox: a one-time Routines intro after three days of use in #3604
- Code review: fixes from the 0.29.0 hands-on QA in #3605
- Inbox typing on long threads: no per-key page-wide work; Chrome undo per typing run again in #3603
- Reviews: the risk dialog is titled Set risk rules in #3612
- Report rejected OpenCode Ask AI prompts instead of waiting for a reply by @rudycelekli in #3548
- Keep OpenCode Ask AI startup from spawning a duplicate server after disposal by @rudycelekli in #3543
- Review: Expand all stays on from commit to commit; Cmd/Ctrl-click jumps to one clear definition in #3618
- Board: show the selected segment in dark theme in #3622
- Claude Code: open behind the guard's early-run rule at the tool's run step in #3619
- Filter routines in the Inbox list in #3615
- Inbox: publish the link for other machines once Tailscale runs; re-point a dead mapping the Inbox made in #3614
- Fix browser slice selection for Git-quoted paths by @rudycelekli in #3541
- Preserve submodule pointer hunks in Git reviews by @rudycelekli in #3542
- Stage and unstage review filenames literally by @rudycelekli in #3544
- Keep a rescheduled Inbox routine from being marked done by its old run by @rudycelekli in #3545
- Keep distinct external comments when restoring annotate drafts by @rudycelekli in #3546
- Preserve audio and video metadata when people upload to the Inbox by @rudycelekli in #3549
- Keep linked document navigation ordered and preserve pending edits by @rudycelekli in #3550
- Include staged files in working-tree reviews before the first commit by @rudycelekli in #3551
- Preserve concurrent changes when editing Inbox routines by @rudycelekli in #3552
- Ten fixes from @rudycelekli, merged together in #3624
- Inbox: hide a pull request from Reviews and the PR board in #3610
- Show the first commit in Last commit reviews by @rudycelekli in #3547
- Show the Code review switch in Settings to everyone; never show its offer in #3626
- Board: same surface as the list beside it; running checks turn in #3628
- Inbox: Contents for short documents, remove a card link, OpenCode's agent at launch in #3621
- A pick from the skill or @ list is its own undo step in #3632
- Release batch: Code review switch, board surface, Inbox small fixes, undo after a pick in #3634
- PR board: follow Reviews' project filter; Hide repository in #3613
- Inbox: the PR page's file list is the code review tree in #3609
- Inbox window: draw diffs with the vendored diff library fork in #3625
- File tree: arrow keys work after a search; 44 px All files rows on a phone in #3627
- Inbox PR page: semantic diffs (moved and renamed code) in #3630
- Reviews: name the filtered project when everything in it is hidden; leave select mode after a bulk hide in #3653
- Inbox PR page: an expand arrow used before a file's moved and renamed note arrives no longer leaves its header on "reading…" in #3656
New Contributors
Contributors
@rudycelekli sent twelve fixes across code review, annotate, OpenCode Ask AI, Inbox uploads and Routines (#3541 to #3552). Each one came with a test that failed before the fix, most of them against a real Git repository: the first commit in Last commit reviews, staged files before the first commit, file names with brackets, submodule pointers, rejected OpenCode prompts, a duplicate OpenCode server, linked document order, annotate drafts, uploaded video details, and two races in Routines.
@MaxKless built the playback speed menu for Inbox videos and recordings (#3534), with keyboard and screen reader support and tests, and recorded it in Chrome, Safari and on a phone. It ships in #3582 with their commits kept. First contribution.
Thanks also to @luwanglin, who asked for code review to cover submodules in #3533. #3542 makes the submodule pointer show the same way under every Git setting; reviewing inside a submodule is still open there.
The new review tree and diffs are built on Pierre's
@pierre/treesand@pierre/diffslibraries.Full Changelog :
v0.28.67...v0.29.0 -
🔗 HexRaysSA/plugin-repository commits sync repo: +5 releases, -2 releases rss
sync repo: +5 releases, -2 releases ## New releases - [btf2ida](https://github.com/nightshift-labs-ai/btf2ida): 0.1.24 - [cfiscope](https://github.com/nightshift-labs-ai/cfiscope): 0.1.21 - [ida-bochs-binaries](https://github.com/hexrayssa/ida-bochs-binaries): 2.0.2, 1.0.7 - [memlens](https://github.com/nightshift-labs-ai/memlens): 0.3.29 ## Changes - [btf2ida](https://github.com/nightshift-labs-ai/btf2ida): - removed version(s): 0.1.0 - [memlens](https://github.com/nightshift-labs-ai/memlens): - removed version(s): 0.3.4
-
- November 17, 2026
-
🔗 smol-machines/smolvm smolvm v1.35.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
- Keep a restored machine's local image on its storage disk instead of mounting the capturing host's archive by @BinSquare in #2163
- Update quinn-udp to 0.5.16 for RUSTSEC-2026-0538 by @BinSquare in #2165
- Count every symlink with one mode in the agent rootfs digest so a Mac checkpoint restores on Linux by @BinSquare in #2162
- Carry guest traffic in 64 KB frames over the gateway link so downloads use a quarter of the CPU by @BinSquare in #2168
- Pin libkrun 518949b4 and libkrunfw 0fae3853, rebuilt for every platform by @BinSquare in #2169
- Reserve tmpfs for concurrent RAM captures and sweep abandoned checkpoint scratch at serve start by @BinSquare in #2173
- Let a packed image's branch take the deferred checkpoint save and say when the VM died mid-save by @BinSquare in #2174
- Integrate and validate Docker Engine, automatic ports, and nested Rosetta support by @BinSquare in #2172
- Run x86_64 images in containers Docker starts inside a Rosetta machine, keeping their PID by @BinSquare in #2093
- Serve the Docker Engine API from smolvm, every container a machine by @BinSquare in #2114
- Publish the ports a machine starts listening on, with --auto-ports by @BinSquare in #2136
- Give engine containers user-defined networks, so Docker Compose stacks run by @BinSquare in #2115
- Let engine containers reach the Docker socket, so Testcontainers and Dev Containers work by @BinSquare in #2116
- Branch engine containers from a warm base when many of one image run by @BinSquare in #2117
- Publish engine container ports on the address each one names by @BinSquare in #2119
- Give engine containers a volume for each VOLUME their image declares by @BinSquare in #2120
- Move images in and out of the engine: save, load, push, commit, import, export by @BinSquare in #2121
- Run --network container: containers in that container's machine by @BinSquare in #2122
- Give engine networks IPv6 by @BinSquare in #2123
- Run the Docker API on demand with independent workload supervisors by @BinSquare in #2175
- Fix Buildx volume permissions and macOS restart stalls by @BinSquare in #2178
- Improve default macOS shared-volume write performance by @BinSquare in #2179
- engine: speed up macOS Buildx with automatic overlayfs snapshots by @BinSquare in #2181
- Run the guest keep-alive init as root while workloads and execs keep the image user and its supplementary groups. by @BinSquare in #2004
- engine: fix multi-stage Buildx builds containing deleted files by @BinSquare in #2183
- Scrub injected credential values from what a credential host sends back by @BinSquare in #2180
- Re-authorize a restored checkpoint's credential bindings from the CLI, and refuse a start that could not inject them by @BinSquare in #2182
- Sweep a deleted machine's pause-operation lock along with its fork-operation lock by @connorburgess in #2184
- Let machine update set and remove labels, in any machine state by @josmo in #2143
- Leave the Docker Engine API opt-in so installing or upgrading smolvm never switches the user's Docker context by @BinSquare in #2186
- Bump every workspace crate and the nix flake to 1.35.0 by @BinSquare in #2185
- fix(network): retain OS-allocated local TCP listeners by @kumanday in #2112
- Retry a checkpoint part the object store refuses with a transient error by @BinSquare in #2191
- fix(shim): preserve foreground helper exit statuses by @hfiguera in #2190
- Delete the image seed builder when a CLI start is interrupted, and reap builders whose owner exited (#2083) by @rdslw in #2188
- Honor SMOLVM_DATA_DIR and --state-dir on macOS by @BinSquare in #2193
- Map a mounted host directory to the workload user again, not the keep-alive init's root, so a non-root workload can write to it by @josmo in #2189
- Open the Nix flake bump from main and run its required attribution check, so the bump PR can merge by @BinSquare in #2194
- Bind the port forward tests' ports before using them, instead of picking a free port and binding it again later by @BinSquare in #2195
- engine: use an on-demand native Buildx builder by @BinSquare in #2196
- perf(engine): reduce container lifecycle overhead by @BinSquare in #2198
- perf(engine): improve streaming output throughput by @BinSquare in #2200
- perf(engine): bound log tail reads and stream binary payloads by @BinSquare in #2201
- Compile the auto ports test's port helper only on Unix, where its one caller runs by @BinSquare in #2199
- Keep an image's files under /run when a container starts by @BinSquare in #2203
- Leave the Docker context alone when an engine with its own state directory is set up, and remove its registration by name by @BinSquare in #2202
- Stop a workload supervisor on SIGTERM and when its engine state is deleted, whoever holds the warm base lock by @BinSquare in #2204
- Start a display without a host GPU, check the host GPU before a --gpu start, and finish stop and delete around a process the kernel will not let exit by @BinSquare in #2210
- Allow ARM cloud checkpoints to return to macOS by @BinSquare in #2216
- Refuse a staged sync entry whose parent leads outside the mount through a symlink, so a guest cannot delete host files by @BinSquare in #2242
- Serve at most eight workload log connections, closing the oldest, so a guest cannot exhaust host threads by @BinSquare in #2243
- Bump libkrun so a resumed macOS machine releases the memory its guest frees and keeps it out of checkpoints by @BinSquare in #2244
- Trim the guest's disks before a capture, so deleted files leave the checkpoint and the host disk by @BinSquare in #2245
- Forget a host's learned addresses when a running machine's allow list is left with no hosts by @josmo in #2142
- Point exec and cp on a paused machine at resume, not at a start that refuses it by @connorburgess in #2167
- Bump libkrun so restored macOS machines keep later writes in checkpoints and qcow2 discards free host disk space by @BinSquare in #2248
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.3 -
🔗 tintinweb/pi-subagents v0.23.2 release
New
- Partial README translations in Simplified Chinese, Japanese and Korean (
README.zh-CN.md,README.ja.md,README.ko.md). They cover the intro, Features, Install, Quick Start and the/agentscommand, and link to the English README for everything else. A language switcher sits at the top of each README.
Fixes
- The conversation viewer honors
tui.altScreen.top/tui.altScreen.bottom(#438). The fullscreen observer's scroll-to-top and jump-to-latest keys, and the jump-to-latest divider label, now resolve through your keybindings. Before, a remap inkeybindings.jsonleft the observer on the stockCtrl+Home/Ctrl+End.Home/Endstill work as aliases, andCtrl+Home/Ctrl+Endnow also scroll in the windowed viewer.
QA
- Automated: 2546 tests passed, including 95 scripted end-to-end tests (real pi sessions, scripted model).
- Live: the end-to-end suite against a real model (92 tests passed). It covers foreground and background spawn with
get_subagent_result, Explore dispatch, workflow fan-out, and structured output.
Thanks @glyh.
Full details in CHANGELOG.md.
- Partial README translations in Simplified Chinese, Japanese and Korean (
-
🔗 tintinweb/pi-subagents v0.25.0 release
What changes for existing users
general-purposecan now spawn subagents of its own, matching Claude Code (#448). SetmaxSubagentDepthto1to turn nesting off; an ejectedgeneral-purpose.mdwithoutallowed_subagentskeeps the old behavior./agents→ Settings writes~/.pi/agent/subagents.jsonunless the project already has.pi/subagents.json; Tab switches the target (#391, #419).
New
/agents→ Settings tags each row with the file that sets it, resets a row with Delete, and filters as you type.
Fixed
- The Settings number editor refuses values that loading would drop on restart.
- Finished nested subagents no longer outlive their parent across a session switch.
get_subagent_resultshows when a saved result finished (#436).- A leftover schedule lock no longer freezes pi for 5 seconds (#247, #266).
QA
- 2657 tests passed (96 scripted e2e); live e2e against a real model: 93 passed.
Thanks @danieltwagner, @xh123637, @EndUser123, @jyn514, @ChakornK.
Full details in CHANGELOG.md.
-
🔗 tintinweb/pi-subagents v0.24.0 release
What changes for existing users
- Nested spawns are refused once 10 nested subagents are running (#427). Set
maxConcurrentNestedto0to restore unbounded nesting. - FleetView rows show each agent's own tokens , the selection is marked
❯, and●marks the view in front (#446).
New
maxConcurrentNestedcaps running nested subagents (default10) (#427).- FleetView lists nested subagents under their parent , with mouse support in fullscreen mode (#446).
showModelnames the model and thinking level on fleet rows (#447).
QA
- 2590 tests passed (95 scripted e2e); live e2e against a real model: 92 passed.
Thanks @zane668, @WinPooh32.
Full details in CHANGELOG.md.
- Nested spawns are refused once 10 nested subagents are running (#427). Set
-
🔗 tintinweb/pi-subagents v0.26.1 release
Patch release — three fixes.
⚠️ Note — a resumed agent keeps the model and thinking level it ran with (#462). Editing
model:orthinking:in its file no longer changes them on resume.Fixed
- Resuming an old agent no longer switches it to your current model (#462). Once cleaned up, a resumed agent ran on the parent's model and thinking level; it now resumes on the ones it ran with.
@agentmentions no longer send the working directory twice (#459). The<cwd>section no longer repeats in the clone's system prompt.- Subagents that delegate now see what each agent they can spawn does (#457). The nested
Agenttool lists each allowed agent's description and tools, like the main session's.
Thanks @hazydream, @zane668, @sjdhome, @WinPooh32.
Full detail in CHANGELOG.md.
-
🔗 tintinweb/pi-subagents v0.26.0 release
What changes for existing users
- A workflow starts only when you ask for one (#451). "Use 10 agents to …" now runs parallel
Agentcalls; say "use a workflow" or name a saved workflow to run one. agent({ schema })is validated strictly against draft-07 (#455). Schemas with unknown keywords (prefixItems,x-*) or a non-draft-07$schemaare refused before the agent starts.
New
- Workflow progress in FleetView and the inspector: a progress bar, active phases, each agent's tool calls, and full prompt/outcome (#455).
- Workflows report why an
agent()call failed viaagentError(label), the journal, and<failures>in the completion notification (#439, #444 — thanks @woksin, @Swarneil1905). workflowToolExposure: "skill"moves the workflow script reference into aworkflow-authoringskill, saving about 4k tokens per session.workflowToolExposure: "deferred"keepsSubagentWorkflowout of the tool spec until pi'stool_searchloads it (#434, #437 — thanks @M1racleShih).
Changed
- Workflow scripts behave as Claude Code's do: strict mode, copied return values,
pipeline()stops an item onnull, plussetTimeout,disallowedToolsand case-insensitiveeffort. See Coming from Claude Code.
Fixed
Thanks @woksin, @Swarneil1905, @M1racleShih, @cgngtr.
Full details in CHANGELOG.md.
- A workflow starts only when you ask for one (#451). "Use 10 agents to …" now runs parallel
-
🔗 smol-machines/smolvm smolvm v1.35.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
- Release a paused branch child's VM lock so the memory pressure guard can resume it by @BinSquare in #2157
- Keep a restored machine's local image on its storage disk instead of mounting the capturing host's archive by @BinSquare in #2163
- Update quinn-udp to 0.5.16 for RUSTSEC-2026-0538 by @BinSquare in #2165
- Count every symlink with one mode in the agent rootfs digest so a Mac checkpoint restores on Linux by @BinSquare in #2162
- Carry guest traffic in 64 KB frames over the gateway link so downloads use a quarter of the CPU by @BinSquare in #2168
- Pin libkrun 518949b4 and libkrunfw 0fae3853, rebuilt for every platform by @BinSquare in #2169
- Reserve tmpfs for concurrent RAM captures and sweep abandoned checkpoint scratch at serve start by @BinSquare in #2173
- Let a packed image's branch take the deferred checkpoint save and say when the VM died mid-save by @BinSquare in #2174
- Integrate and validate Docker Engine, automatic ports, and nested Rosetta support by @BinSquare in #2172
- Run x86_64 images in containers Docker starts inside a Rosetta machine, keeping their PID by @BinSquare in #2093
- Serve the Docker Engine API from smolvm, every container a machine by @BinSquare in #2114
- Publish the ports a machine starts listening on, with --auto-ports by @BinSquare in #2136
- Give engine containers user-defined networks, so Docker Compose stacks run by @BinSquare in #2115
- Let engine containers reach the Docker socket, so Testcontainers and Dev Containers work by @BinSquare in #2116
- Branch engine containers from a warm base when many of one image run by @BinSquare in #2117
- Publish engine container ports on the address each one names by @BinSquare in #2119
- Give engine containers a volume for each VOLUME their image declares by @BinSquare in #2120
- Move images in and out of the engine: save, load, push, commit, import, export by @BinSquare in #2121
- Run --network container: containers in that container's machine by @BinSquare in #2122
- Give engine networks IPv6 by @BinSquare in #2123
- Run the Docker API on demand with independent workload supervisors by @BinSquare in #2175
- Fix Buildx volume permissions and macOS restart stalls by @BinSquare in #2178
- Improve default macOS shared-volume write performance by @BinSquare in #2179
- engine: speed up macOS Buildx with automatic overlayfs snapshots by @BinSquare in #2181
- Run the guest keep-alive init as root while workloads and execs keep the image user and its supplementary groups. by @BinSquare in #2004
- engine: fix multi-stage Buildx builds containing deleted files by @BinSquare in #2183
- Scrub injected credential values from what a credential host sends back by @BinSquare in #2180
- Re-authorize a restored checkpoint's credential bindings from the CLI, and refuse a start that could not inject them by @BinSquare in #2182
- Sweep a deleted machine's pause-operation lock along with its fork-operation lock by @connorburgess in #2184
- Let machine update set and remove labels, in any machine state by @josmo in #2143
- Leave the Docker Engine API opt-in so installing or upgrading smolvm never switches the user's Docker context by @BinSquare in #2186
- Bump every workspace crate and the nix flake to 1.35.0 by @BinSquare in #2185
- fix(network): retain OS-allocated local TCP listeners by @kumanday in #2112
- Retry a checkpoint part the object store refuses with a transient error by @BinSquare in #2191
- fix(shim): preserve foreground helper exit statuses by @hfiguera in #2190
- Delete the image seed builder when a CLI start is interrupted, and reap builders whose owner exited (#2083) by @rdslw in #2188
- Honor SMOLVM_DATA_DIR and --state-dir on macOS by @BinSquare in #2193
- Map a mounted host directory to the workload user again, not the keep-alive init's root, so a non-root workload can write to it by @josmo in #2189
- Open the Nix flake bump from main and run its required attribution check, so the bump PR can merge by @BinSquare in #2194
- Bind the port forward tests' ports before using them, instead of picking a free port and binding it again later by @BinSquare in #2195
- engine: use an on-demand native Buildx builder by @BinSquare in #2196
- perf(engine): reduce container lifecycle overhead by @BinSquare in #2198
- perf(engine): improve streaming output throughput by @BinSquare in #2200
- perf(engine): bound log tail reads and stream binary payloads by @BinSquare in #2201
- Compile the auto ports test's port helper only on Unix, where its one caller runs by @BinSquare in #2199
- Keep an image's files under /run when a container starts by @BinSquare in #2203
- Leave the Docker context alone when an engine with its own state directory is set up, and remove its registration by name by @BinSquare in #2202
- Stop a workload supervisor on SIGTERM and when its engine state is deleted, whoever holds the warm base lock by @BinSquare in #2204
- Start a display without a host GPU, check the host GPU before a --gpu start, and finish stop and delete around a process the kernel will not let exit by @BinSquare in #2210
- Allow ARM cloud checkpoints to return to macOS by @BinSquare in #2216
- Refuse a staged sync entry whose parent leads outside the mount through a symlink, so a guest cannot delete host files by @BinSquare in #2242
- Serve at most eight workload log connections, closing the oldest, so a guest cannot exhaust host threads by @BinSquare in #2243
- Bump libkrun so a resumed macOS machine releases the memory its guest frees and keeps it out of checkpoints by @BinSquare in #2244
- Trim the guest's disks before a capture, so deleted files leave the checkpoint and the host disk by @BinSquare in #2245
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.2 -
🔗 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.6 -
🔗 Simon Willison Running the full server-side Datasette Python app in the browser with service workers and Pyodide rss
Datasette Lite is my port of the Datasette Python application to run directly in the browser using WebAssembly and Pyodide. I've released a complete rewrite of Datasette Lite using service workers, and it's now almost indistinguishable from the real server-side application.
You can now do all of the following, using a carefully crafted URL to lite.datasette.io:
- Load client-side Datasette to browse any SQLite database, JSON file, CSV file or SQL script
- Select a released version of Datasette to load from PyPI
- Load a specific commit, tag, or branch name from the Datasette GitHub repository
- Pick from over 100 versions of SQLite to use with Datasette
- Install additional Datasette plugins from PyPI or URLs to wheel files, including JavaScript visualization tools
The ability to load specific Datasette references, plugins, and SQLite versions makes this a fantastic tool for linking to demos of work-in-progress features or bug reproductions, without needing to spin up a full web server to serve that demo.
As an example, consider the following URL:
Follow that link and, after a short loading screen, you'll find yourself on a page that looks like this:

That's Datasette running the new datasette-maplibre plugin, loading up a database of GeoJSON shapes of countries and displaying both a combined map and individual boundary maps in a table.
Let's break down that URL to see what it's doing:
https://lite.datasette.io/ ?install=datasette-maplibre &url=https://.../demo.db &metadata=https://.../metadata.yml #/demo/capitals_and_countries%23map=0/4.2/180&color=continentThe
?install=datasette-maplibreinstalls that additional plugin from PyPI. You can pass&install=...as many times as you like to load more plugins.&url=https://.../demo.dbloads that SQLite database from the provided URL. These URLs need to have open CORS headers - I host files like this in Gists, because they provide an easy way to get open CORS headers on a web-hosted file.&metadata=https://.../metadata.ymlloads this metadata.yml file. The metadata file adds HTML descriptions to various tables, and to the Datasette homepage. Visit that homepage here for a guided tour of the other features of that plugin, all defined in the metadata file.#/demo/capitals_and_countries%23map=0/4.2/180&color=continentis a fragment hash that turns into a location within Datasette - here it's loading the/demo/capitals_and_countriesSQL view, then appending another fragment hash to it (%23is a URL-encoded#) which tells the map plugin to zoom to a certain location and to set the color of the shapes on the map based on thecontinentcolumn in the data.That URL is doing a lot of work! I wrote more about this trick for building URL-addressable software in URL-addressable Pyodide Python environments last year.
The full set of supported URL arguments is described in the Datasette Lite README.
I've already started using Datasette Lite as part of the Datasette development process. Here's a recent issue describing a pagination bug - I posted a comment there demonstrating the old, broken behavior and the new fix using links to Datasette Lite:
Demo of the bug: https://lite.datasette.io/?ref=1.0a42&sql=https://gist.github.com/simonw/75ececf61d50e6e8d50f0c150150ee81#/data/scores?_size=2&_sort=score - click next and the second page is empty.
Here's that same page with the bug fixed (running on 1.0a43): https://lite.datasette.io/?ref=1.0a43&sql=https://gist.github.com/simonw/75ececf61d50e6e8d50f0c150150ee81#/data/scores?_size=2&_sort=score
How this works, using service workers Datasette Lite is not a new project. I launched the first version back in 2022, originally as a bit of a joke (running server-side apps in the browser is pretty funny) but one that quickly started proving its value. The problem with that initial version is that it was a hack. It worked by running Datasette in a Pyodide web worker, simulating requests through that stack, then injecting the resulting HTML back into the top level page using innerHTML. This worked for basic Datasette, but meant that any feature that used JavaScript failed to work, because script tags in innerHTML don't execute, and the web worker tricks it used failed to load additional JavaScript or CSS files. The new version takes a completely different approach based on Service Workers. These allow JavaScript to intercept HTTP requests for new pages and resources and serve them from client-side code instead. Datasette Lite registers a service worker for the entire lite.datasette.io domain. The parent page then creates an iframe that sends requests for Datasette pages to URLs that look like this: /app/aa94e6851595/ # the homepage (HTML) /app/aa94e6851595/data/places # a table page (HTML) /app/aa94e6851595/-/static/navigation-search.js # (JavaScript) /app/aa94e6851595/-/static/app.css # (CSS) Those are regular Datasette URLs, but with a /app/aa94e6851595/ prefix. What's that about? The /app/<session>/ prefix is necessary because of multiple tabs. Consider the URL above, which loads the demo instance with the datasette-maplibre plugin. That URL defines a full, custom Datasette instance. You might have that one running in a tab, then one of my other demo links running in another. The service worker for lite.datasette.io is shared between all of those tabs. If it routed to a single instance of Datasette then every tab would share that underlying instance, no matter what plugins or other settings their URL attempted to configure. Instead, the parent page generates a random session ID and uses it as a prefix for all of the subsequent hidden asset and page loads. The service worker can then use that session ID to route those requests back through the parent page to a web worker running a dedicated Datasette instance for that particular session. (We still need a web worker because Pyodide in a service worker would not be able to maintain state beyond around 30 seconds, depending on the browser. There are a lot of moving parts here!) I had Claude Fable 5.2 generate several SVG diagrams to help explain this. Here's my favorite of those, now embedded in the Datasette Lite README: This system started life back in May as an AI research spike generated using Claude Opus 4.8. It wasn't until November (and Claude Fable 5.2) that I felt familiar enough with how it all works to confidently ship it to production! Bonus feature: pick your version of SQLite I added this feature last night as an off-shoot of investigating a potential bug in SQLite. Datasette is meant to work against any released version of SQLite since 3.25 (released in September 2018). There have been 87 further releases since then. Being able to fire up Datasette against a specific version of SQLite is really useful for demonstrating new SQLite features and debugging weird issues. In the past I've used various tricks to get different SQLite versions running with Python on my Mac, but it's not a trivial process. WebAssembly is perfect for this. I can load up a custom SQLite build entirely in my browser, test it there, then discard it when I close my tab. datasette/pysqlite3-wasm-wheels is my new repository which contains WebAssembly compiled Python wheels for pysqlite3 for 163 different SQLite versions. Each version gets a file with a name like this: pysqlite3-0.6.2-3.54.1-cp314-cp314-pyemscripten_2026_0_wasm32.whl That's for SQLite 3.54.1, the most recent version. Datasette Lite now takes a special ?sqlite= URL parameter, which will accept a version number like 3.54.1, resolve the path to the corresponding wheel file, then fetch that wheel and install it into the Pyodide environment and configure Datasette to use it. Once I'd built the wheels, I decided to have Claude Fable 5.2 build me ">https://datasette.github.io/pysqlite3-wasm-wheels/?versions=3.54.1,3.54.0&sql=select+json_object(%27a%27%2C+(select+json_array(1%29%29%29) for comparing a SQL query across any selected versions of SQLite. Here's an example showing how select json_object('a', (select json_array(1))) differs between SQLite 3.54.0 and 3.54.1: This should work for every other Python app, too
Nothing about how Datasette Lite works is unique to Datasette. Almost any Python application should be able to pull the same trick - running entirely in the browser using WebAssembly and Pyodide, as a cheap way to provide preview environments, demonstrate features, and recreate bugs.
C and Rust extensions used to be a blocker for this kind of thing, but any good coding agent can compile those to Pyodide-compatible WebAssembly now. You can even publish them to PyPI as of PEP 783 in April 2026.
One catch is databases. SQLite is no problem at all, but running PostgreSQL or MySQL in WebAssembly, while possible, is still a path less trodden.
I'd love to see WebAssembly preview environments like these become a common pattern across the Python ecosystem.
For Hacker News: Full server-side Datasette Python app in the browser with service workers
You are only seeing the long-form articles from my blog. Subscribe to /atom/everything/ to get all of my posts, or take a look at my other subscription options.
-
🔗 3Blue1Brown (YouTube) How to compress text to 1 bit per character | Information theory, part 3 rss
Arithmetic codes and how they elucidate this trilogy's title Channel career fair: https://3b1b.com/talent New store items! https://3b1b.com/store Early views for supporters: https://3b1b.com/support
Other resources you may enjoy.
On Arithmetic Codes:
https://jacobfilipp.com/DrDobbs/articles/DDJ/1991/9102/9102a/9102a.htm
https://www.nayuki.io/page/reference-arithmetic-coding
On Asymmetric numeral systems:
https://arxiv.org/abs/0902.0271
https://demonstrations.wolfram.com/DataCompressionUsingAsymmetricNumeralSystems/
https://arxiv.org/pdf/2201.01741v2
https://arxiv.org/pdf/2510.13867
Ilya Sutskever, An Observation on Generalization https://www.youtube.com/watch?v=AKMuA_TVz3A&t=24s
A bit on prequential coding: https://yidingjiang.github.io/blog/post/curriculum/
Timestamps: 0:00 - The absurdity of Shannon’s estimate 6:27 - From text to real numbers 16:57 - Is this Shannon’s limit? 20:26 - Reframing pretraining 22:41 - Arithmetic codes in action 27:29 - Reflections on “Compression is Intelligence” 36:30 - Three ways to support
Secret Enscreen Vlog: https://youtu.be/hoX3IiKXT-M
These animations are largely made using a custom Python library, manim. See the FAQ comments here: https://3b1b.co/faq#manim
Music by Vincent Rubinetti. https://vincerubinetti.bandcamp.com/album/the-music-of-3blue1brown https://open.spotify.com/album/1dVyjwS8FBqXhRunaG5W5u
3blue1brown is a channel about animating math, in all senses of the word animate. If you're reading the bottom of a video description, I'm guessing you're more interested than the average viewer in lessons here. It would mean a lot to me if you chose to stay up to date on new ones, either by subscribing here on YouTube or otherwise following on whichever platform below you check most regularly.
Mailing list: https://3blue1brown.substack.com Twitter: https://twitter.com/3blue1brown Bluesky: https://bsky.app/profile/3blue1brown.com Instagram: https://www.instagram.com/3blue1brown Reddit: https://www.reddit.com/r/3blue1brown Facebook: https://www.facebook.com/3blue1brown Patreon: https://patreon.com/3blue1brown Website: https://www.3blue1brown.com
-
🔗 3Blue1Brown (YouTube) Encoding the encyclopedia on a rod rss
Full video: https://youtu.be/qbsb9DpdZ6s
-
🔗 @binaryninja@infosec.exchange Want to spend your summer in Florida working on Binary Ninja? We're accepting mastodon
Want to spend your summer in Florida working on Binary Ninja? We're accepting applications for the Vector 35 Summer Internship Program 2027! If you're interested, check out the details and application instructions here: https://binary.ninja/students/internship-2027.html
-
🔗 Hex-Rays Blog IDA 9.5: Introducing Native UEFI Firmware Support rss
-
🔗 gildas-lormeau/single-file-cli v2.27.0 release
SingleFile CLI 2.27.0
New features
-
New option
--load-deferred-content-expand-viewport: expand the browser viewport to the height of the document while loading deferred content, and restore it before the page is read. By default, the page is only made to believe it is that tall. This option loads the content of pages that measure the viewport in a way the emulation does not reach (e.g. an element sized with thevhunit). No zoom-out is applied unless--load-deferred-content-min-zoom-factoris set. A page that does not react to the restored size is saved with the elements it sized from the tall viewport.single-file https://www.example.com/gallery page.html --load-deferred-content-expand-viewport -
The unused CSS rules of the stylesheets found in shadow roots are now removed, they were always saved whole. On a Reddit thread with 240 comments, the saved page goes from 394 MB to 21 MB (gildas-lormeau/SingleFile#1514).
-
The deferred content is now also loaded on a page that keeps the document at the size of the window and scrolls an inner element. Such a page was saved with its first rows only.
-
An SVG file referenced by a
useelement is inlined in the page, the image was lost before.
CLI fixes and improvements
- Updated single-file-core to 1.14.1:
- a stylesheet containing
:is()or:where()with an empty argument list no longer makes the save fail with "Cannot read properties of null (reading 'data')" (gildas-lormeau/SingleFile#2058 by @alekssmitt) - with
--selected-elements-selector, the selected content is no longer saved as a blank page when it is displayed through the slots of web components (gildas-lormeau/SingleFile#2060 by @FvH01)
- a stylesheet containing
Co-authored by Claude (Claude Code)
-
-
🔗 backnotprop/plannotator v0.28.67 release
Follow @plannotator on X for updates
Missed recent releases? Release | Highlights
---|---
v0.28.66 | Pick several threads and archive or snooze them at once, combine picked threads into one; Tidy follows your own words, rows take their tag's colour; filter and search by tag, files an agent's message names open beside the thread, swipe rows on phone or iPad; list can show archived threads, Antigravity and Orca use the Inbox; T3 Codex threads get replies, Open in lists JetBrains IDEs, Routines: run a saved prompt on a schedule
v0.28.65 | Take back a reply your agent has not received yet, over Tailscale, Plannotator opens only for your own account, tag a linked machine's threads; one tag across machines, T3 Code threads get the Inbox with no setup, long threads open on slow connections
v0.28.64 | Installs and updates download a smaller, compressed copy, a Videos filter on the Artifacts page, GitLab comments on a whole file get their own thread, pull request pictures and videos show in the Inbox
v0.28.63 | Pair Grok Bot and other cloud agents from Settings, Hermes Agent, OpenClaw and Muse Code can use the Inbox, add a thread to Priority to keep it on top, tag threads, and find each tag in the sidebar, Pull requests board as a table, with bulk Merge
v0.28.62 | Agents started from the Inbox now work on Windows, pick a model and effort when you start an agent, rules for your agents, written in your own words, post a thread's decisions on its pull request, the Inbox loads faster on a slow connection
v0.28.61 | Updates now update the Claude Code plugin too, an agent's chosen face shows on every icon of it, filter the Inbox list by pull request state, Modern dark shows section bands and the Reply button, one conversation no longer shows as two agents
v0.28.60 | Click a word to highlight it, a one-time Themes dialog, Settings → Rows rebuilt, tell your agent how you want your rows, starred threads as pills above the list, a pill for new messages out of view, a half-circle face picker with ten Glass colours, a new phone sidebar and reply box
v0.28.59 | A quieter Agents section in the sidebar, machine names only when agents run on more than one machine, agent icons that are always gently alive and lean toward your pointer
v0.28.58 | Start Codex from New message, an Agents section in the sidebar, start an agent in a folder on any drive, play audio attachments and comment at a moment, Claude Code's Plannotator tools work on Windows
v0.28.57 | Pin artifacts, and see every artifact on one page, filter the list by project, date or agent, a thread shows its pull requests and their state, choose what the sidebar shows, and in what order, Ask AI starts from Side in the selection bar
v0.28.56 | Questions can show trade-offs and a prototype to try, a thread with many big pictures no longer crashes the tab, Escape closes New message and keeps your draft, read threads stop being bold and keep their place, agent messages that name no thread start a new 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 InboxWhat's New in v0.28.67
TL;DR
- New: Drag threads to Priority, Archive or Quiet, or combine them
- New: Mention another thread in your reply
- New: Linear links show hover cards; add your key in Settings
- New: Agent icons made from the project name
- Changed: Pick any tag colour; turning a tint off keeps it
- Fixed: A linked computer's pictures, pages and files now open
- Fixed: Pull request cards say why they could not load
- Fixed: A review that can't load shows an error with Retry
v0.28.67 is a short Inbox release. You can now drag a thread row to sort it, hold it over another thread to combine the two, or drop it in your reply to mention it. Tags get a full colour picker, Linear links get hover cards, and a thread that lives on a linked computer now shows its pictures and opens its pages and nearby files. Two fixes protect you: the script in an HTML attachment can no longer move the Inbox to another thread, and a failed settings save can no longer empty
config.json. The release has 30 PRs. One of them carries the Linear hover cards by @Raj1v, their first contribution.Drag a thread to sort it, combine it or open it
On a computer, you can now pick up a thread row and drop it somewhere. While you carry it, three places show over the list: Priority at the top, and Archive and Quiet · Mark read at the bottom. A drop runs the same action as the row menu, with the same toast and Undo. Several picked rows move together, with one toast and one Undo. A place that cannot take the rows turns grey and says why, for example "Already in Priority" or "Already read", and a drop there changes nothing. Quiet still asks before it sets a question aside. If you cancel that warning, your picked rows stay picked.
Hold a row over the middle of another row for half a second to combine them. The row under the pointer reads "Combine with this thread". When you let go, the Combine dialog opens with both threads picked. It never combines on its own.
With Keep thread panel open on (in the list's ⋮ menu) and no thread open, the empty panel takes a dropped row and opens that thread.
Dragging needs a mouse, a trackpad or a pen with a fine pointer. Touch never drags: on a phone, the row's sheet and its swipe do the same things. An iPad with only its Pencil no longer announces rows as draggable, and connecting or removing a trackpad updates the rows at once.
Mention another thread in your reply
You can point your agent at another thread from the reply box. Drag a row onto the box, choose Mention in reply in the row's menu (also on a phone's row sheet), or paste a thread's link. The thread's title goes in as a token, and Backspace removes it whole. Several picked rows become several mentions. The sent message shows each mention as a link that opens the thread, and the mentioned thread itself does not change. Your agent gets each thread's title and id at the spot where you put it, and a short list of the threads you mentioned after your words.
Tag colours: any colour, and off keeps it
A tag's right-click menu in the sidebar now has two rows. Highlight rows is a checkbox that turns the tag's tint on or off at once. Color opens a picker in place, with quick swatches, your recent colours, a colour square, a hue strip and a Hex field. Turning a tag's highlight off keeps its colour, so turning it on again brings the same colour back. New tags go through all twelve swatches before any colour repeats.
A tinted row follows the colour you picked in every theme. On each built-in theme, its text is never harder to read than on that theme's plain row.
Linear hover cards
A
linear.app/…/issue/ENG-123link in the Inbox now shows a hover card, as GitHub and GitLab links do. It shows the issue's team, title, state, author, priority, project, labels, assignee, description, attached pull requests, the latest comment and Open in Linear. A bareENG-123in a message becomes a link whenENGis one of your workspace's team keys.To see details, paste a Linear personal API key in Settings → Accounts → Linear. Cards work right after you save it, with no restart. The key is kept in a private file in Plannotator's data folder, never in
config.json, and goes only to Linear. IfLINEAR_API_KEYis set and no key is saved, the row says "Using LINEAR_API_KEY". Nothing is fetched until you hover or tap a card.#3146, with the hover cards from #3063 by @Raj1v, closing #3120, which they also opened
Files on a linked computer open from here
When you look at a thread that lives on a linked computer, its files now work from this one:
- Markdown pictures show , and a link to a file next to it opens in the pane.
- An HTML page opens in its own tab , with its stylesheets and pictures. In the viewer beside the thread, the page's folder loads too, and a link to a page next to it opens in the pane. Large pages open as well.
- Open in shows only what works from here. The editors, Default app and Finder are not offered for another computer's file, so the "No attachment" errors are gone. Copy path copies that computer's path, and a picture still opens in a new tab.
Both computers need this version. An older linked computer still refuses these reads, and the picture stays broken as before.
Pull request cards say why they could not load
When the Inbox cannot get a pull or merge request from
ghorglab, the card in a thread and the link hover card now say which problem it is, with one next step. Before, they could only say "The Inbox did not answer."- gh isn't installed: a link to install it, and Try again.
- gh isn't signed in: the
gh auth login --hostname github.comcommand with Copy, and Try again. A refusedGH_TOKENis named. - gh didn't answer in 8 seconds, or GitHub asked for a short break (rate limited).
- gh can't see this pull request: Open on GitHub.
glab gets the same words for GitLab. A sign-in command only ever names github.com, gitlab.com, a host your CLI already knows, or your project's own host, never a look-alike host that a link named. Try again right after you sign in works at once.
Two safety fixes
- An HTML attachment's own script can no longer move the Inbox. Before, a script inside an attached HTML page could send the Inbox window to any thread with no click. Now only your own click on a link is followed. An HTML page from outside the project also gets no network in the viewer, as it already did when served by address. Annotate's HTML viewer gets the same protection. #3469
- A failed settings save can no longer empty
config.json. When the safe write (a temp file, then a rename) failed, Plannotator wrote straight intoconfig.json, and a full disk or a crash could leave it empty, so the next save lost every other setting. Now the old file is never touched: the save fails with the existing warning and your settings stay. On Windows, a save waits about two seconds for a program that holds the file.state.jsongets the same protection. #3473
Additional Changes
- The thread's title shows in its header bar , with its subject after it in a muted colour. A title cut short is a button: click or tap it to read the whole title. #3528
- Agent icons from the project name. Settings → Rows → Agent icons has a new choice, From the project name : a coloured tile with the project's letters, with the agent's mark as a small badge. It changes only agents with no face you picked.
plannotator inbox rows set agent-icons=projectsets it from a terminal. The default is unchanged. #3503 - The routine editor saves by itself. For people who turned on Routines: typing saves after a short pause, and the header says "Saving…", "Saved" or "Couldn't save · retrying". A new routine's draft is kept until it has a name and a prompt, even after a reload. Run once now saves first. The tip on the sidebar's and list's resize edges no longer covers a routine's name. #3558
- Docs: the README covers guided reviews and annotating a live site, shows the Workspaces picture in Sharing, and folds the long uninstall text. The HTML viewer's guide for host apps covers a host that loads the bridge by URL. #3554, #3524, #3531
- Code review shows an error with Retry when the diff cannot load, instead of a sample diff with no decision buttons. If the review server answered with an error, you can still send a note or close the review. #3573, for #940 reported by @digitalmaster, with diagnosis from @cschanhniem
- Groundwork with no visible change: page frame parts in
@plannotator/uifor host apps, and more of the thread pane work. #3540, #3562, #3528 - Test and CI upkeep: #3561, #3491, #3559, #3535, #3565
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
- README: the Workspaces picture in Sharing; uninstall details fold away in #3524
- A failed settings save can no longer empty config.json in #3473
- CI: a docs-only PR skips the unit, DOM, package, smoke and Semgrep steps in #3491
- Inbox: Linear hover cards and the Linear key in Settings → Accounts (includes #3063 by @Raj1v) in #3146
- HTML attachments: a page's own script cannot move the Inbox; no network for pages from outside the project (port of #2511) in #3469
- HTML viewer docs: a host that loads the bridge by URL puts the load's key on the bridge's tag in #3531
- Pull request cards say why gh or glab could not answer in #3093
- Update lock tests: do not depend on how long the machine has been up in #3535
- Inbox: agent icons from the project name in #3503
- Open in: show only what works for a linked machine's file in #3536
- README: guided reviews and live site annotation in #3554
- Open a linked machine's HTML attachment in its own tab, with its folder in #3538
- Inbox: mention a thread in a reply (drag a row, row menu, pasted link) in #3526
- Inbox tag colors: a two-dimensional picker, and rows that follow the pick in #3553
- Inbox: the thread's title in its header bar, and thread pane groundwork (no visible change) in #3528
- UI frame: a reusable page screen for @plannotator/ui in #3540
- Inbox: drag threads to the list edges, onto another thread, and onto the empty panel in #3537
- Shared stream e2e (WebKit): wait for the takeover until the script runs out in #3559
- Inbox: a linked computer's Markdown pictures and the files next to it open here in #3557
- Inbox drags follow-ups: keep picks on a cancelled Quiet drop; drag help follows the device's pointers in #3560
- UI frame: follow-ups (author kind none, compared row name, README) in #3562
- Inbox: open a linked computer's large sibling page; document the window-only costs in #3563
- AGENTS.md: no AI attribution in commits, tags, release notes or PR bodies in #3565
- Inbox routines: the editor saves by itself and says so in #3558
- Inbox: internal groundwork, off in #3527
- Inbox: internal groundwork, off in #3556
- Inbox: internal groundwork, off in #3574
- Inbox: fixes from the release check: mention undo and editing, Linear key messages, small drag and tag colour fixes in #3576
- Run only what a PR's change can affect in PR CI in #3561
- Code review: show an error with Retry instead of the demo diff when the diff fails to load in #3573
New Contributors
Contributors
@Raj1v asked for Linear hover cards in the Inbox (#3120) and then built them (#3063): the card, its Linear states, and bare
ENG-123identifiers that become links. Their commit ships with its authorship kept inside #3146, which adds the Settings row for the Linear key. First contribution.Thanks also to @digitalmaster, who reported the code review failure in #940, and @cschanhniem, who traced its cause there.
Full Changelog :
v0.28.66...v0.28.67 -
🔗 HexRaysSA/plugin-repository commits sync repo: +1 plugin, +2 releases rss
sync repo: +1 plugin, +2 releases ## New plugins - [revengai](https://github.com/revengai/plugin-ida) (3.29.0, 3.28.0) -
🔗 Filip Filmar DDR3 memory for a TxHDL design, with a controller we did not write rss
The Vreteno RISC-V processor originally executed out of 4 KiB of block RAM. In contrast, the Alinx AX7A200 FPGA board provides one gigabyte of external DDR3 SDRAM. Designing a custom DDR3 PHY and memory controller requires extensive calibration circuitry. Rather than rewriting this complex infrastructure, we integrated the open-source UberDDR3 controller into a TxHDL SoC design as a foreign module. This post describes foreign module integration, board simulation with Micron memory models, and synthesis status.
-
- November 16, 2026
-
🔗 IDA Plugin Updates IDA Plugin Updates on 2026-11-16 rss
-
🔗 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.5 -
🔗 @HexRaysSA@infosec.exchange A few of our team members will be in Tokyo at mastodon
A few of our team members will be in Tokyo at @codeblue_jp on 17 & 18 November, ready to talk about all things IDA.
Want to meet up? Email us at marketing@hex-rays.com and we’ll help you find us.
-
🔗 SparkFun Tutorials How to Build a Remote GNSS CORS rss
How to Build a Remote GNSS CORS a Available online at:
What's a CORS?
For high precision GNSS to work you need a base/rover system. In the simplest terms this means you need a GNSS receiver sitting stationary and transmitting its corrections every second up to the internet. A CORS, or continuously operating reference station, is a field hardened GNSS receiver to maximize uptime. These reference stations are scattered over large swathes of land, generally positioned 30 to 50km apart to provide rovers in the area with the most precise correction data with as few 'holes' in the coverage map as possible.
Example CORS station VITH in St. Thomas
GNSS reference stations installed by the National Geodetic Survey, or by US states who set up their own corrections networks for their transportation and surveying crews can cost more than $50,000 a site. This project, the SparkFun CORS, is a demonstration of how to deploy a very reliable, remotely monitored station for around $2,000.
It goes without saying, but we do not claim to have the same accuracy or efficacy of the NGS - they rule! We provide this information as a potential starting point for municipalities or other organizations that are looking to move to high precision GNSS without needing to subscribe to a for-profit corrections provider.
Where can I get corrections today?
States with Free CORS
Free state CORS/RTK networks:
- Alabama — AL CORS
- Arizona — AZCORS
- Arkansas — ARDOT RTN
- California — CRTN
- Connecticut — ACORN
- Florida — FPRN
- Indiana — InCORS
- Iowa — IaRTN
- Kentucky — KYCORS
- Maine — MaineDOT CORS
- Massachusetts — MaCORS
- Michigan — MDOT CORS (MSRN)
- Minnesota — MnCORS
- Mississippi — GCGC RTN
- Missouri — MoDOT RTN
- New York — NYSNet
- Ohio — ODOT VRS
- Oregon — ORGN
- Vermont — VECTOR
- West Virginia — WVRTN
- Wisconsin — WISCORS
This is only a partial list. There are lots of additional free networks including UNAVCO and country-wide networks such as CentipedeRTK in France.
If you're lucky and live in a state or area where there is a free or low cost corrections network then use it! If you are a municipality or county unlucky like we are in a state that doesn't have a network, then keep reading about how you can set up your own CORS!
SparkFun CORS
A CORS is all the associated bits that enable a reference station to be robustly connected to the internet for long periods of time. If you can install your base station in a protected, climate controlled office or outbuilding, do it! The goal of this tutorial is to demonstrate a mid-grade CORS station capable of being installed in semi-remote areas where no power or internet (WiFi or ethernet) is available. You can spend tens of thousands of dollars on bulky, power hungry equipment but we wanted to show that you don't need to.
Above is the SparkFun CORS at the end of our parking lot. There are four parts:
- The antenna is located at the top of the light post.
- The solar panel shown is 30W but was later changed to 100W.
- The cabinet houses the battery, solar charger, low-voltage disconnect, base station, and cellular modem.
- The grounding wire for lightning suppression.
Below is a list of parts used on this project:
Description | Cost
---|---
SXM-E | $1,200
RUT241 LTE Modem | $190
1m SMA Extension Cable | $5
Tello SIM card | $3
Metal Enclosure w/ Hardware | $105
Cam Lock Replacement | $7
Cable glands | $8
100W Solar Panel | $52
Large Panel Mounting Bracket | $120
10AWG Solar Wiring | $18
MPPT Charger | $20
50Ah Battery | $90
Battery Harness + Fuse | $5
RV Pipe Heater | $14
DC Thermostat | $6
Low Voltage Disconnect | $21
Lightning Arrestor | $20
1m SMA Extension Cable | $5
Grounding Rod | $30
Square U Bolts | $20
NMO Antenna Mount | $10
5/8" Rod 2" | $10
|
Total | $1,959The core of a CORS is the reference station that monitors the GPS signals and generates corrections. Most GNSS receivers have the capability to be told the exact location the device is located. From that point on, any differences that are detected in the received GNSS signals are attributable to perturbations (think turbulence) in the ionosphere and atmosphere in general. Those differences are turned into corrections that, when broadcast to a rover, allow the rover to enter into an RTK Fix with accuracies that can be below 10mm in horizontal accuracy.
We chose the SXM-E reference station as its mosaic-X5 receiver is the Cadillac for precision, while being extremely configurable, reasonably compact, with reasonable power consumption.
For a video tutorial on how to set up the SXM-E, including antenna installation and how to run a 24 hour survey to establish the location of the antenna down to the millimeter, check out this video. We found NMO Antenna Mounts to be a handy 5/8" compatible bracket for pole mounting. 4" u-bolts were used to fasten the hardware to the square light pole.
Housing
We chose a ~$100 painted steel cabinet that measures 16 x 12 x 8". In retrospect, this is too small. We should have opted for a larger enclosure but the allure of snugly fitting a 50Ah battery into this enclosure was initially too great. That said, the grated ventilation system of this cabinet works very well and helps keep bugs and mother nature out while keeping the SXM-E within its operating temperature of −20°C to +85°C.
We re-used some of the packaging foam to create a boat shaped pad for the battery to rest in.
Note that the enclosure dimensions are not necessarily the usable internal dimensions. Our cabinet came with a handy shelf bracket installed on the back wall. Unfortunately the shelf and bracket system sat so proud that it had to be forcibly removed (ground out) to allow for enough room for the battery to fit. If I were to do it again, I would use a larger ~24x20x10" cabinet.
The cabinet required a fair amount of modification to allow for the u-bolt mounting hardware (four holes), SMA connectors, and the installation of glands to allow for various water-tight cable connections.
Holes made for connections:
- 2 x 9mm glands for +/- solar wires
- 1 x 7mm hole for cellular SMA extension cable
- 1 x 7mm hole for GNSS SMA extension cable
- 4 x 1/2" holes for u-bolt fasteners
Originally we had intended to install the GNSS antenna directly on the top of the cabinet. This would allow the overall CORS to be more compact but the sloped roof of the enclosure would make getting the antenna into a vertical position very challenging. Additionally, the sky-view blocking aspect of the light pole meant we needed to mount the antenna further up. If you do consider antenna mounting to the cabinet roof opt for an enclosure that has a flat roof and waterproof accordingly.
Shown above, to prevent damage to the reference station in the case of a lightning strike, a grounding rod and tie line were run to the housing.
Above, in this original setup you can see the ground tie connected to the lightning arrester in the upper right corner. As my co-worker pointed out: "This is a very bad idea." If lighting where to strike, it would send the lightning through the ground wire inside the enclosure.
Here is the lightning arrester properly located on the outside of the enclosure: the GNSS antenna cable routes to the lightning suppressor, the ground wire has its shortest path to ground, and the arrestor is connected to an SMA extension cable that mounts to the enclosure wall that, in turn, connects to the SXM-E's mosaic-X5 GNSS receiver.
Power
I thoroughly recommend LiFePO4 chemistry batteries. Lithium Iron Phosphate (aka LFP) batteries have most of the benefits of their higher-energy-density LiPo cousins with the additional benefit of being very safe and hardy in robust environments. I have put 12V equivalent LiFePO4 battery packs through thousands of cycles, across three winters without heating and four summers in the Colorado sun, only to test the capacity of the battery and see that it remains at 80% of its badge capacity! Because of this, LiFePO4 was a natural match for our CORS test station.
The first step was calculating worst case scenario for lack of solar. Between the LTE modem and the SXM-E base station, our system power draw was about 4.5W average. Use your favorite calculator or chatbot to aid in the battery size, solar panel size, and solar panel angle. But our initial calculations put us at 30W for a solar panel (assuming an MPPT charger) and a 50Ahr battery. This setup was slated to last us 640Wh / 4.5W = 142h or six days if no sun was available, and charge the battery from dead in about 3 to 5 days depending on the time of year.
Above we have the 30W panel with the small panel mounting bracket. This combination was originally attractive for its compactness and low-cost. Unfortunately the panel was not large enough to escape the death spiral.
Pro Tip: When deploying a solar powered, self-contained system, start from a dead battery. It's natural to want to charge your battery fully then deploy your system thinking all will work fine. But if your charger is malfunctioning, or your battery is not quite up to its badge rating, or a bird causes a mess and degrades your solar panel's performance, you won't discover your system is slowly dying for many weeks or months. By starting from death, you can check that the system will be capable of digging itself out, from a power perspective.
I didn't intend to deploy our CORS with a dead battery but by installing the electronics one day and getting delayed installing the solar by a few days, it was a happy accident. Well, happy if we mean our base station failed from day one.
During the red highlighted phase, the station was deployed and would work for a few hours, but once night came the station would go offline due to loss of power. The frustrating part was that the station would not come back when the sun came up the next day. What in the world was going on? It's BMS lockout!
Above we see two discharge curves: LiFePO4 versus a lead-acid based battery. The run time in hours is not representative of any one CORS, rather, the graph is to demonstrate how the respective chemistries will behave during a cut-off scenario.
Every lithium based battery has a battery management system (BMS) to prevent the cells from dangerous and damaging edge cases such as over current, over voltage, or under voltage. In our case, the 12V battery has a BMS that disconnects the batteries via a MOSFET switch. Whereas classic lead-acid based 12V batteries (SLAs, AGMs, etc. all behave similarly) will output a lower and lower voltage (11V, 10V, 8V, etc), lithium based batteries with a BMS will lower their output voltage to a point, say 11.5V at which the BMS turns off the pack and the battery will read 0.0V. The BMS will not 'unlock' the pack until the load is fully disconnected. In the case of our CORS, the BMS was locking out at 0.0V but the load (the cellular modem and base station) continued to pull on the battery even when the sun was fully out. This was a type of lock-out death we had not anticipated. Luckily, this is a common issue!
Above we see the new wiring harness complete with MPPT charger and low-voltage- disconnect. The charger is connected to the solar panel wires using wire nuts. The small bare pair of wires connect to the SXM-E's screw terminals, the polarized plug powers the RUT241 modem. An LVD simply disconnects the downstream system when the voltage drops below a programmable threshold, and turns on the downstream system when the available voltage is above another programmable threshold. We set our LVD to cut off at 11.8V (~5% capacity remaining) and turn back on at 12.8V. This approach allows us to draw down the battery considerably without triggering the BMS disconnect. There is a chance that we have a terrible snowstorm that drives the system to LVD cutoff, then perhaps through self-discharge the battery enters BMS lockout, but this is unlikely. I've tested LiFePO4 batteries after a year of being on the shelf and tested their capacity to find only a 2% capacity loss! LiFePO4s are pretty amazing. A few days sitting in a low state shouldn't lead to a low-voltage cut-off.
Above we can see a report of the USACOLNIW2 station up time over a series of days. While I'm still not a proponent of anything blockchain, Onocoy does serve as an excellent, free station monitoring service. This quickly showed us the LVD was working! The station was dying at night, sure, but it was turning back on and charging during the day! We hit our second wall: The solar charging system was not large enough to charge the battery sufficiently to allow the system to run longer and longer over a series of good solar days.
The solution was to upgrade to a larger 100W panel, bracket, and wiring. It's frustrating that the mounting bracket is twice the cost of the panel. But considering the weight of the panel and the wind speeds around Boulder, CO, this much more substantial mounting hardware gives us peace of mind that the heavier solar panel won't fall damaging anything or anyone!
The panel change increased the cost of the project by ~5% but the improvements were immediately obvious, shown above as a steady green bar. After the installation of the new 100W panel, and with only a few hours of winter daylight left to charge the battery, the station was charged enough to survive the night and continue to improve over the coming days. Dig-out from death is a success!
Now let's talk battery heaters for a minute. The internet abounds with warnings to never charge your LiFePO4 battery when the cell temperature is below 0C (32F). My experience differs slightly: I have fully discharged and charged multiple batteries through Colorado winters without temperature control or sensing of the pack. After over 1000 cycles (more than 3 years), the capacity tested at 80%. Not bad!
However, for the benefit of this tutorial we wanted to test out battery heating. Shown above, our original design of the CORS battery pack included a stick-on RV pipe heating pad adhered to the bottom of the battery connected to a thermostat. The idea was to turn on the heater to allow the battery to heat itself when the temperature dropped below 3C (~37F). This heat would keep the battery warm while providing the SXM-E residual warmth to keep it above its lower -20C operating threshold.
When the station failed initially due to BMS and charging issues, the thermostat and heater were disconnected. The additional system complexity was not worth the marginal improvement to the battery lifespan. We have found the combination of insulation foam on the bottom of the cabinet, residual heat from the SXM-E itself, and strong Colorado sun tend to keep the battery at a good charging temperature when the sun is out. If you are very concerned about it, go for it! Our design heated the battery even at night which is silly. We recommend adding a light sensitive switch so that heating is only enabled when the solar output is high enough that the battery is actually charging.
Cellular Data Link
A reference station doesn't do much good unless it's pushing corrections to an NTRIP caster. To get the data to the internet we could have used SparkFun's local WiFi but that wouldn't provide a reasonable demonstration to users who are deploying a self-contained station.
In order of lowest cost and complexity:
- If you've got ethernet, use it! It's the lowest power and most dependable. Also, PoE is supported.
- If you've got WiFi, use it! It's free.
- If you've got cellular coverage, it will cost a bit each month ($10-$20), but it will work.
- If you're really remote, there's HugesNet, Viasat, Starlink, or Iridium. These provide satellite based internet but can cost anywhere from $50 to thousands of dollars per month and require considerably more power.
We originally tried to use SIMO, a ~$120 cellular hotspot marketed with 1GB of free data for life. Shown above, this is the small gray plastic device sitting on top of the battery. This would ostensibly remove the need for a monthly cellular account. However, we found that every 10 minutes, like clockwork, the SIMO would disconnect from the casters for a few seconds then promptly reconnect. While we could have troubleshot why this was occurring, it was assumed that SIMO was doing some sort of reasonable throttling that the casters would not like. 1GB a month is not enough data (more below) and the SIMO was not really built for this so we switched to the RUT241 and have been duly impressed.
The RUT241 is a cellular modem with ethernet, WiFi, and remote monitoring. Above we see the RUT241 connected over WiFi to the SXM-E. Eventually we got rid of the WiFi antenna and directly connected the SXM-E over ethernet; this cut down on complexity and reduced power consumption.
Note in the photo above the RUT241 has two cellular SMA connectors: one connected to a large flat antenna and another connected to an SMA extension cable. We were concerned the enclosure would cut down on cellular reception so the primary antenna is connected over the SMA extension to an external antenna while the secondary antenna is kept inside the enclosure. We found that reception was superb but you may want both antennas externally mounted for additional reception.
The amount of data a reference station can generate varies a lot based on a multitude of factors. MSM4 is the more compact, slightly less precise format for RTCM messages where as MSM7 is larger and more precise. If you have a relatively basic base station receiver (say a ZED-F9P) capable of only L1 and L2 frequencies, with a portion of low-elevation satellites removed from the corrections output, then you can easily drop down under ~800 bytes per second. Unfortunately this still leads to nearly 2GB per month. Alternatively, if you want to participate in networks like Onocoy, and are rewarded based on the 'quality' of the data and number of satellites in view, this can substantially increase the data being pushed to the caster over the cellular connection. And because of the SXM-E's superb reception, you can expect many thousands of bytes per second.
Reasons for increasing data:
- An advanced receiver that can receive multiple L1/L2/L5 frequencies will output far more correction data than an L1 only capable GNSS receiver.
- Outputting the more precise, but larger format MSM7 formatted corrections messages will output more data than the equivalent MSM4 formatted RTCM.
- A high-quality, high-sensitivity receiver and GNSS antenna will sense more satellites, and hence output a lot more corrections than a low-quality receiver with sky-view obstructions. Every additional satellite detected linearly expands the amount of data to transmit.
- A receiver that reports every satellite, even low to the horizon poor quality ones will add to the data transmitting vs reporting only high quality, high signal satellites.
- A receiver reporting corrections for all constellations (GPS/GLONASS/Galileo/BeiDou) will generate far more data than a base station reporting corrections for only the GPS constellation.
And just because we're weird, we want to simultaneously cast to three casters: RTK2Go, Emlid, and Onocoy. We love RTK2Go but it experiences outages when we least expect it so Emlid serves as a nice backup. And we use Onocoy both as an uptime monitor and because it's technically generating funny money. We will report back if we're ever successful in turning the Ono coin into something tangible (i.e., beer). Now we could have used RTKLIB's Stream Server (STRSVR) to send only one copy of corrections over the cellular network and then have a server re-broadcast to the three casters but this was deemed overly complex; it's easier to pay the $20 a month to push more data.
One especially nice feature of the RUT241 is the ability to remotely tunnel into the system. This allows us to remotely connect to the SXM-E as if we were connected over a USB cable to both monitor and configure the settings. This has been extremely handy. The downside is that there is no free lunch: Teltonika charges a monthly fee (about $5 as of writing) for this access. Now that the station is up and running, we will probably let the subscription lapse and purchase a month's access only when we need to modify or troubleshoot something which should be very rare.
You can also tunnel into the cellular modem itself and view data usage statistics. Note the small print at the bottom; these are estimates that may differ from the cellular provider, but they give us some insight into the daily usage. If this is to be believed, we're transmitting between 10 and 15GB per month.
The easiest/lowest priced data we've found was Tello. Your mileage may vary, but $18 a month is not terrible. Getting their SIM and using it with the RUT241 was very easy. Again, we're rare in that we need 20GB per month. If you filter out low-elevation satellites, turn off corrections from constellations that your rovers don't care about (perhaps Galileo and BeiDou), turn off frequencies that are not needed (GPS L5 is a good candidate), and push to a single caster, you should be able to reduce your data usage per month considerably.
Further Improvements
The SparkFun CORS is operating very well. Check out the current status on Onocoy and RTK2Go. We hope to have a fairly boring next couple of years. If we learn anything else we'll update this tutorial along the way.
1) As stated earlier, a larger cabinet would be the first improvement. Currently any maintenance or modifications require the entire cabinet to be emptied. However, now that we know what we're doing, there would be far fewer changes after-the-fact so perhaps the smaller cabinet is acceptable.
2) The cold-rolled steel is very sturdy, but a pain to drill. There are knock- outs but they were deemed too large to use. Finding a better way to leverage the built-in knockouts would require less drilling.
3) The MC4 connectors on the 100W solar panel required sending larger diameter wire through two glands and then connecting them using wire nuts to the MPPT charger. This works but is cumbersome. Perhaps MC4 bulkhead connectors could be used, but these connectors are too bulky to be used inside the enclosure. Perhaps there's a solution using an SAE connector to connect the wires to the charger.
4) Given infinite time and money it would be interesting to build a much larger cabinet instrumented in a way to allow for much more granular data gathering. Measuring and reporting the power consumption, battery voltage, and data flows would allow us to potentially reduce the solar panel, battery size, and tailor the cellular data rates.
Thanks for reading!
learn.sparkfun.com | CC BY-SA 3.0 | SparkFun Electronics | Niwot, Colorado
-
🔗 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.
-
🔗 Rust Blog Enabling the parallel frontend on nightly rss
TL;DR: We are enabling the parallel frontend of the Rust compiler on nightly by default, to find remaining issues in preparation for its stabilization.
Context
The Rust compiler has been using multiple threads to compile code in its "backend" part (using LLVM) for a long time. However, its "frontend" part (which includes type checking and borrow checking) has been executing sequentially, on a single thread, which of course limits the performance of the compiler. If you are interested in a more in-depth explanation of parallelism in the Rust compiler, see this previous post.
The compiler frontend actually had support for running in parallel for a long time, but it was not enabled by default due to various issues. Three years ago, we made it possible to opt into the parallel frontend on the nightly channel, with the plan to stabilize it in 2024. Clearly, we did not achieve that goal, but work on the parallel frontend was still slowly progressing in the meantime.
Last year, Vadim Petrochenkov, together with several other contributors, started a coordinated effort to finally get the parallel frontend over the finish line. Since then, many long-standing issues were fixed, and its performance was improved. Now we are at a point where we would like to make it widely available. But before that, we want to find out if people encounter issues with it in the wild, which is why we are enabling it by default only on the nightly channel. Once we will be confident enough that it is working well, we want to stabilize it.
The parallel frontend has been enabled on the nightly channel by default since
nightly-2026-11-14.Benefits
The primary benefit of enabling the parallel frontend is, of course, faster compilation of Rust programs.
We benchmarked the parallel frontend in our benchmark suite, which measures the duration to compile the leaf crate in a crate graph. As usual, the results were varied. In some benchmarks, the parallel frontend barely helped. In others, for example when performing a
cargo checkof thenalgebra,cargoordieselcrates, the compilation was almost three times faster, using 8 threads.In the table below, you can find the aggregated wall-time mean change for the real-world benchmarks in our suite, when building a single crate from scratch across several configurations, compared to the same build using a sequential frontend.
Frontend threads / Profile|
check|clippy|debug|opt
---|---|---|---|---
2| -21.95 %| -20.74 %| -14.2 %| -12.51 %
4| -37.99 %| -36.01 %| -29.14 %| -23.67 %
8| -44.23 %| -41.76 %| -36.1 %| -27.88 %It is clear that the parallelization is not perfect, and we definitely plan to invest more effort into improving its performance. Nevertheless, with 8 threads, it can make the end-to-end compilation time of
cargo check~2x faster for several crates that we tested, which is still quite an improvement.The performance benefits for incremental rebuilds are much more modest, and also very hard to compare, because the performance of rebuilds depends on what was changed and how were the codegen units laid out. In our benchmark suite, we saw a mean improvement of 3-5% for incremental rebuilds. But we currently do not have great benchmarks for this use-case, so your results might vary.
We can also zoom in on an individual crate. Here is a chart of how the wall- time scales when compiling the
nalgebra 0.33crate, for a full non- incremental build (full), full incremental build (incr-full) and an incremental rebuild (incr-patched) across several build configurations:
What is interesting to note is that enabling the parallel frontend can actually also make the backend faster, for reasons explained here.
It is important to note that all benchmark results presented above measured only the compilation of a single crate. When compiling a whole crate graph, your CPU cores might already be saturated because of backend (LLVM) parallelism or by Cargo compiling multiple crates in parallel. So the final performance effect will vary heavily based on the workload that you are running, and on the number of cores that you have available.
We also benchmarked
cargo checkend-to-end (checking the whole crate graph) on thecargocrate itself on a machine with 8 CPU cores. With 8 threads, it resulted in a ~15% end-to-end improvement:- 36.7s with 1 frontend thread
- 35.1s with 2 frontend threads
- 31.9s with 4 frontend threads
- 30.8s with 8 frontend threads
As can be seen from the results above, when the CPU cores are already saturated with parallel crate compilation and LLVM, the positive effect of the parallel frontend is reduced.
Tuning the thread count
At the start, the nightly toolchain will default to the parallel frontend using only
2threads. This is a conservative choice that should still allow us to find potential issues while not increasing memory usage a lot at the same time.If you want to test out the performance with different thread counts, you can override the number of threads used for the frontend using the
--jobs- frontendcompiler flag. It can be specified either in theRUSTFLAGSenvironment variable, or you can put it into a.cargo/config.tomlfile:[build] rustflags = ["-Zunstable-options", "--jobs-frontend=8"]Currently, the performance of the parallel frontend will likely not scale very well above ~8 threads, but you can try it on your workload to test what happens. Note that using higher thread counts will likely lead to higher memory usage of the compiler, and in extreme cases it might cause you to run out of memory.
Limitations and known issues
Due to the used parallelism, the produced order of diagnostics might not be deterministic when using the parallel frontend.
In some situations, the generated binary might also not be reproducible, though we currently consider these cases bugs, and we would like to identify them and fix them.
There are currently some known issues related to the reproducibility of the Rust compiler when using the parallel frontend, which are being worked on.
How do I opt out?
To reiterate: this is only being enabled on nightly for now. If you are using the stable toolchain, you will still be using the sequential frontend by default.
If you want to disable the parallel frontend on the nightly channel, pass
-Zunstable-options --jobs-frontend=1torustc, either via theRUSTFLAGSenvironment variable, or with the.cargo/config.tomlconfiguration file:[build] rustflags = ["-Zunstable-options", "--jobs-frontend=1"]If you have to do this for some reason, please do tell us why on GitHub or on Zulip. We would especially like to know about any compiler crashes that you encounter, or the produced binaries not being reproducible when the parallel frontend is enabled.
What's next?
Over the next few months, we will be monitoring GitHub and Zulip for any reported issues about the parallel frontend. Once we have enough confidence that it is working well, and there are no major issues, we would like to move forward and finally stabilize it.
We would also like to improve its performance, and make more things parallel. So far, a lot of the work on the parallel frontend has been focused on making it work correctly, rather than tuning its performance down to the last percent. We thus expect that we might still be able to make further performance improvements to it.
We would also like to make more parts of the frontend actually parallel, as some parts are currently still sequential even if parallelism is enabled. There is some ongoing work on this. Last year, we had a Google Summer of Code project focused on enabling parallel macro expansion and name resolution, and there is also an open pull request for parallelizing the lowering of the Abstract Syntax Tree (AST) to the High-Level Intermediate Representation (HIR). More work remains to be done on this front.
-
- November 15, 2026
-
🔗 IDA Plugin Updates IDA Plugin Updates on 2026-11-15 rss
IDA Plugin Updates on 2026-11-15
New Releases:
Activity:
- augur
- 48574c40: Merge pull request #19 from 0xdea/dependabot/github_actions/actions-d…
- f1e77ab2: ci: bump taiki-e/install-action
- 4a8a77d6: ci: run dependabot on fridays
- f89691ba: chore: allow unwrap, expect, panic, and indexing in tests via clippy.…
- b5a81475: chore: enable cargo lints and deny their warnings in ci
- b8a10ecc: refactor: clean up the output directory with DropGuard and require Ru…
- ffxiv_bossmod
- 5481bdd6: slight fixes
- ee5b04a4: Merge pull request #815 from Nonunon/pandaemonium-normal
- 322eb773: fix clock range
- c58c248d: cleanup
- 4b09a37f: waowoawowoa
- 48551fe7: Add P9N Kokytos module
- 2f1d9d57: Add P10N Pandaemonium module
- aa674090: Add P7N Agdistis module
- 1de76b93: Add P5N Proto-Carbuncle module
- 513b7835: Add P11N Themis module
- 6f10e9c9: Add P8N Hephaistos module
- 31c1ea23: Add P4N Hesperos module
- fd4d09a4: Add P3N Phoinix module
- 247ff846: Add P12N Athena module
- cbfe3790: Add P6N Hegemone module
- 28e19aca: Add P2N Hippokampos module
- haruspex
- 5b948022: Merge pull request #23 from 0xdea/dependabot/github_actions/actions-d…
- 1ec46656: ci: bump taiki-e/install-action
- 00c73592: ci: run dependabot on fridays
- 18088414: chore: allow unwrap, expect, panic, and indexing in tests via clippy.…
- 2bd7e459: chore: enable cargo lints and deny their warnings in ci
- 03c730eb: refactor: clean up the output directory with DropGuard and require Ru…
- ida-sigmaker
- ida_rpc
- c81777ea: Update minor fixes
- rhabdomancer
- 1ee5adbf: Merge pull request #23 from 0xdea/dependabot/github_actions/actions-d…
- e6b4fa05: ci: bump taiki-e/install-action
- 31083c3c: ci: run dependabot on fridays
- a655503f: chore: allow unwrap, expect, panic, and indexing in tests via clippy.…
- a3293dbd: chore: enable cargo lints and deny their warnings in ci
- 5c50ead7: docs: update the cmd.exe call count without the ARM64EC marker
- 28a13dba: refactor: use str::trim_prefix and require Rust 1.100
- augur
-
🔗 @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
-



























