๐Ÿก


  1. November 20, 2026
    1. ๐Ÿ”— gchq/CyberChef v11.6.0 release

      11.6.0

    2. ๐Ÿ”— earendil-works/pi v1.6.0 release

      New Features

      • GPT-6.2 Astra and GPT-6.2 Sol : both models are available on the openai, azure, and openai-codex providers, and GPT-6.2 Sol is now the default model for all three. See Providers.

      Breaking Changes

      • Extension components: render() now returns readonly string[], and Container returns the same cached array while its children are unchanged. Extensions that modify render output in place, including super.render() in a Container subclass or an embedded component's output, must copy it first (#9549)

      Added

      • Added GPT-6.2 Astra and GPT-6.2 Sol to the openai, azure, and openai-codex providers. Both reject reasoning effort none and minimal, so thinking level off is unavailable. Azure serves them with a 1.05M context window; Codex serves GPT-6.2 Sol with 500K and GPT-6.2 Astra with 272K
      • Added qwen4-max-preview to the Qwen Token Plan Individual providers (#12259)
      • Added deepseek-v4.1-flash and deepseek-v4.1-flash-1017 to the Qwen Token Plan Individual providers, and per-plan key variables QWEN_TOKEN_PLAN_TEAM_API_KEY, QWEN_TOKEN_PLAN_TEAM_CN_API_KEY, QWEN_TOKEN_PLAN_INDIVIDUAL_API_KEY, and QWEN_TOKEN_PLAN_INDIVIDUAL_CN_API_KEY; the shared QWEN_TOKEN_PLAN_API_KEY and QWEN_TOKEN_PLAN_CN_API_KEY still work (#11773)
      • Added a transcript notice when OpenAI drops reasoning items from a request, such as OpenAI dropped 2 reasoning items: prefix_mismatch (details in session) after compaction on GPT-6.2. Like the Anthropic thinking notice, it is shown when showCacheMissNotices is on and only when more items are dropped than in the previous response. Both notices now name the reasons

      Changed

      • Qwen Token Plan providers now use the current gateways (token-plan.maas.qwencloudapi.com international, token-plan.maas.qianwenaiapi.com China), and qwen-token-plan and qwen-token-plan-cn are named "Qwen Token Plan Team" and "Qwen Token Plan Team CN". Provider IDs are unchanged, and the old aliyuncs.com hosts still work (#11773)
      • Updated undici to 8.12.4 for security advisories GHSA-mqg3-3v4r-cm32, GHSA-7xg3-fphp-28hg, GHSA-5rm8-gv32-r954, GHSA-9v6h-8rgp-m69f, GHSA-3g9m-rv3r-w5w2, and GHSA-r4pc-4jcp-7pqc (#12200)
      • The default model for the openai, azure, and openai-codex providers is now GPT-6.2 Sol (gpt-6.2-sol) instead of GPT-6.1 Sol, at the same price
      • The find tool's path patterns are now relative to the search directory, like grep's glob: src/*.ts finds src/a.ts but no longer pkg/src/a.ts; use **/src/*.ts to match at any depth. Patterns without / still match file names at any depth (#12066)
      • The llama.cpp extension now connects to http://127.0.0.1:9931 by default, the current llama-server default port, instead of port 8080 (#12001 by @julien-c)
      • Anthropic message threads are now on by default for any provider whose baseUrl is on api.anthropic.com, not only the anthropic provider (#11987)
      • The resume command printed on exit is now on its own line after To resume this session:, so it can be selected with a triple-click (#12237)

      Fixed

      • Fixed read storing a note that the current model does not support images, which was replayed to the model as stale text after switching to a vision model. The image is still replaced with a placeholder per request for models without image input, and the read result now shows the warning in the TUI only, also when collapsed (#12131)
      • Fixed MCP tools loaded by tool_search being dropped on resume and /reload when an extension deactivates only its own tool at session_start, as pi-web-access and pi-subagents do in toolActivation: "auto" mode (#11996)
      • Fixed the standalone binary failing to resolve extension npm dependencies whose entry point is declared in package.json main or exports (for example shiki, yaml, graceful-fs), including imports made from inside other dependencies (#12012)
      • Fixed the find tool returning no results for patterns starting with ./, such as ./src/*.ts (#12020)
      • Fixed pi exiting with an uncaught AbortError when a read tool call is cancelled while the file is being opened (#11956)
      • Fixed pi exiting with an uncaught AbortError when the session picker cancels loading after skipping a .jsonl file that is not a session, and fixed such files staying open (#11956)
      • Fixed /share crashing pi when the GitHub CLI fails to start
      • Fixed pi update on Windows managed installs failing with "Could not verify managed Pi" when an older system Node.js comes before the installer's standalone Node.js on PATH (#12048)
      • Fixed /export HTML showing raw terminal hyperlink escape codes around links in custom tool output; links are now clickable (#12003)
      • Fixed the bash tool returning no output, with a footer like [Showing lines 3-2 of 2], when the output ends in one line longer than about 100KB, such as a grep match in a minified file; it now shows the end of that line (#12062)
      • Fixed provider errors reading "Connection closed." not triggering automatic retries (#12064)
      • Fixed /resume sometimes selecting an unrelated session while the list reloads after deleting or renaming a session (#12106)
      • Fixed Groq Qwen models failing with 400 Unexpected message role; OpenAI-compatible providers other than OpenAI now receive system messages (the system prompt and mid-conversation system messages) with the system role (#10741)
      • Fixed enabledModels/--models warnings such as No models match pattern "github-copilot/nope" being written over the interactive TUI on every /new, /resume and /fork, which left stale lines in fullscreen mode. The warnings are now shown once at startup, in the chat in interactive mode and on stderr in other modes; RPC mode no longer repeats them on stderr for each new_session, switch_session or fork (#11264)
      • Fixed the find tool matching path patterns through folders above the search path: with the project in ~/src/app, src/**/*.ts returned every .ts file in the project (#12066)
      • Fixed pi crashing with RangeError: Maximum call stack size exceeded when rendering a very large edit diff, for example after editing a file with a multi-megabyte line, and again on every resume of that session (#8036)
      • Fixed pressing Esc during a batch of tool calls leaving the calls that had not started yet without a result in the session; they now get an "Operation aborted" result (#9986)
      • Fixed an unreadable CHANGELOG.md (pi's own or an extension package's) printing Warning: Could not parse changelog over the interactive TUI; it now shows no changelog notes (#11264)
      • Fixed problems found when replacing the session with /new, /resume, /fork or RPC new_session, switch_session and fork never being shown, for example a project extension that fails to load after /resume into another project, or an enabledModels pattern that matches nothing after a settings change. Interactive mode now shows them in the chat and print, JSON and RPC modes write them to stderr; a problem already reported is not repeated. SDK hosts can call the new AgentSessionRuntime.takeUnreportedDiagnostics() at startup and after each replacement to get each diagnostic once
      • Fixed RPC new_session, switch_session, fork and clone running extension session_start and resources_discover handlers twice for the new session. RPC clients now also receive events emitted by session_start handlers, such as entry_appended for entries they append (#10470)
      • Fixed an exception thrown by an extension's pi.events handler being printed with console.error over the interactive TUI. It is now reported like other extension errors: in the chat in interactive mode, as extension_error in RPC mode and as Extension error (...) in print mode. Errors from a handler that fails after its session was replaced are dropped (#11264)
      • Fixed AgentSession.reload() not emitting session_start to extensions when the SDK host bound them with bindExtensions({}), after it had already emitted session_shutdown. Extensions that start work in session_start, such as the MCP extension connecting its servers, stayed stopped after a reload
      • Fixed --mode json dropping events emitted by extension session_start handlers, such as entry_appended for entries they append, at startup and after an extension replaces the session
      • Fixed Could not restore model <provider>/<model>. Using <fallback> being shown only at interactive startup. Resuming or forking into a session whose model no longer exists or has no login switched to another model without notice, and print, JSON and RPC modes never showed it. It is now reported in every mode, at startup and after /resume, /fork and RPC switch_session or fork
      • Fixed git and npm output, such as Cloning into ... or added 12 packages, being drawn over the interactive TUI when pi installed or refreshed packages during /reload, /new, /resume and /fork, including temporary -e git: and -e npm: packages. In interactive mode their output is now captured, and a failed install reports the end of it. Until the TUI starts, each install is announced as Installing &lt;source&gt;... on stderr instead of showing git and npm output. git and ssh can no longer prompt in interactive mode: a package that needs a typed password or passphrase fails with a hint to set up a credential helper or ssh agent, or to run pi install &lt;source&gt; once from the shell. pi install and pi update keep live output (#11264)
      • Fixed fullscreen scrolling in long sessions saturating a CPU core by re-rendering the whole transcript on every wheel event (#9549)
      • Fixed search in /login, /logout, /scoped-models and /resume keeping the highlight on the row scrolled to before typing, so Enter picked whichever entry landed there instead of the best match; a query now highlights the top match, as /model does (#12245, #12246 by @acmerfight)
      • Fixed exiting pi, pi config and the --resume and other startup pickers dropping terminal output still queued in stdout, such as the resets that turn off mouse tracking and Kitty keyboard reporting; the shell could then print mouse and key reports as text. pi now waits up to one second for queued output before exiting or continuing (#12133)
      • Fixed moving the cursor in a search field with Left, Right, Home or End moving the highlight back to the first entry in /login, /logout, /model, /scoped-models, /resume, /settings, the per-model settings model picker and pi config (#12245)
      • Fixed llama.cpp decision classifiers ignoring the image input that llama.cpp reports, such as Clef with its mmproj; models.classify() now sends their images to /v1/systemone (#12282)
      • Fixed kill -TSTP from outside pi stopping it without restoring the terminal, which left mouse tracking and the Kitty keyboard protocol on at the shell prompt and turned mouse movement into garbage input. pi now suspends as with Ctrl+Z and redraws on fg (#12283 by @haoqixu)
      • Fixed changing the thinking level on the openai-codex provider invalidating the prompt cache on GPT-6 models (#12269)
      • Fixed unscoped syntax-highlighted text inheriting the terminal foreground and becoming unreadable on contrasting tool cards (#11092)
      • Fixed /copy saying "No agent messages to copy yet." after Esc during a tool call or after a provider error; it now copies the previous answer. RPC get_last_assistant_text skips the same messages (#12119, #12121 by @acmerfight)
      • Fixed pi.exec reporting exit code 0 for commands ended by a signal, such as a timeout, an abort or a crash; it now reports 128 + the signal number, like a shell (143 for SIGTERM, 137 for SIGKILL) (#12088, #12089 by @acmerfight)
      • Fixed GitHub Copilot Gemini and Kimi models (gemini-4-argon, gemini-4-carbon, gemini-3.8-flash, kimi-k3) ignoring the thinking level, and Copilot usage always reporting 0 reasoning tokens (#12110 by @DenielC1)
      • Fixed provider errors that report only a Node socket error code, such as read ECONNRESET, write EPIPE, or connect ETIMEDOUT, not triggering automatic retries (#12128)
      • Fixed OpenAI rejecting requests with a 400 error when a tool's schema contains a node without a type (such as items: {} or Type.Unknown()); such tools are now sent in non-strict mode (#12049)
      • Fixed Mistral Large 4 tool calls stalling for minutes; Mistral models no longer receive strict tools unless compat.supportsStrictMode is set (#12148)
      • Fixed non-strict Anthropic tool schemas not telling the model that extra arguments are forbidden (#12067)
      • Fixed GitHub Copilot models on the Responses API (GPT, Grok, MAI-Code) filling omitted optional tool arguments with empty strings or invented values (#12286)
      • Fixed the OpenAI Codex WebSocket 60-minute connection limit failing the turn when it hit mid-stream, for example during long thinking; the request is now retried on a fresh connection (#12124)
      • Fixed the openai-codex provider getting almost no prompt cache hits for the system prompt on GPT-6.2 models (#12273)
      • Fixed the openai-codex provider ignoring a model's maxTokens
      • Fixed fullscreen Kitty images disappearing after a full redraw such as a window resize (#12010)
      • Fixed text after a multi-row inline image in Markdown drawing over the image (#12017)
      • Fixed Kitty and iTerm2 images covering overlays drawn over them (#11584)
      • Fixed Enter on a Tab path menu for an absolute path (look at /tmp/fi) or a slash command argument menu (/open /tm) submitting the prompt instead of accepting the completion (#12309, #12312 by @acmerfight)

      Removed

      • Removed the retired deepseek-v3.2 and deepseek-v4-flash from the Qwen Token Plan Team providers; use deepseek-v4-flash-0731 or deepseek-v4.1-flash (#11773)
    3. ๐Ÿ”— New Music Releases Rammstein - Live in Mexico City rss

      Rammstein - a new release is available:

      • 2026-11-20: Live in Mexico City (Live)

      Amazon: Canada | Deutschland | France | United Kingdom | United States

      Visit muspy for more information.

    4. ๐Ÿ”— New Music Releases Trivium - Crown in the Grave rss

      Trivium - a new release is available:

      • 2026-11-20: Crown in the Grave (Album)

      Amazon: Canada | Deutschland | France | United Kingdom | United States

      Visit muspy for more information.

    5. ๐Ÿ”— New Music Releases Thy Catafalque - XIII: Sรกrga erdo rss

      Thy Catafalque - a new release is available:

      • 2026-11-20: XIII: Sรกrga erdo (Album)

      Amazon: Canada | Deutschland | France | United Kingdom | United States

      Visit muspy for more information.

  2. November 19, 2026
    1. ๐Ÿ”— HexRaysSA/plugin-repository commits sync repo: +3 releases, -1 release rss
      sync repo: +3 releases, -1 release
      
      ## New releases
      - [cfiscope](https://github.com/nightshift-labs-ai/cfiscope): 0.1.23
      - [kflow](https://github.com/nightshift-labs-ai/kflow): 0.0.8
      - [memlens](https://github.com/nightshift-labs-ai/memlens): 0.3.31
      
      ## Changes
      - [memlens](https://github.com/nightshift-labs-ai/memlens):
        - removed version(s): 0.3.6
      
    2. ๐Ÿ”— backnotprop/plannotator v0.29.1 release

      Follow @plannotator on X for updates

      Missed recent releases? Release | Highlights
      ---|---
      v0.29.0 | A redesigned code review window with two panes, a file tree, image diffs and a minimap, semantic diffs for moved and renamed code, talk through a review comment with your agent, Code review in the Inbox is a switch in Settings, hide a pull request or a repository, playback speed for videos, plannotator routine commands and a /create-routine skill
      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

      What's New in v0.29.1

      TL;DR

      • New: Start the Inbox's agents in Rex, each in its own tab, on a Mac or on a Linux or FreeBSD server
      • New: Search inside the list's Filter menu when a section is long
      • New: Start a thread from a pull request's page in Reviews
      • New: /picture-it, a built-in skill that asks an agent for one page of pictures explaining a change
      • New: Questions that propose a change show it as Now and After
      • New: Threads side by side, a switch in Settings (off by default)
      • New: Status marks for every agent in the sidebar, a switch in Settings (off by default)
      • New: Tag a project, and filter the list and the Board by that tag
      • Changed: Play a sound now rings for every agent message by default; "when an agent asks you" keeps the old behaviour
      • Changed: The "N new" bar stays at the top of the list and says what came
      • Changed: On a computer where the Inbox has never run, nothing starts it until you run plannotator inbox, and Claude Code gets no Inbox tool until then
      • Fixed: In code review, the symbol hover card closed while the pointer was in it
      • Fixed: Your Inbox rules and reminder never reached sessions that connect over MCP
      • Fixed: Invisible or faint text in several built-in themes

      v0.29.1 is mostly an Inbox release, with a round of fixes to the code review window that v0.29.0 introduced. Agents the Inbox starts can now run as tabs in Rex, the list's filter gets a search field, and a pull request's page can start a thread. On a computer where the Inbox has never run, it now stays off until you run it. The release has 56 PRs. Fifteen come from outside contributors: fourteen fixes from @rudycelekli, merged together in #3658, and one from @sx4im.

      The Inbox turns on only when you run it

      On a computer where the Inbox has never run, nothing starts it on its own any more. Claude Code gets no plannotator_inbox tool and no Inbox reminder, and a background start by a plugin or an agent's Inbox call answers with one line instead:

      The Plannotator Inbox is off on this computer. plannotator inbox --open turns it on. If you are an agent, ask the person in the chat instead, and turn it on only if they ask you to.

      The Inbox turns on when you run plannotator inbox yourself (bare, --no- open or --open; /plannotator-inbox runs --open), or when your agent runs plannotator inbox --open from the Inbox setup prompt. That first --open also connects the agents it finds, within half a minute.

      If you have already run the Inbox on this computer, nothing changes: the first time Plannotator checks after the update, it sees that the Inbox ran here and records that once. One edge: a Claude Code session that already had the plugin loaded before you first turned the Inbox on needs one restart to get the tool, because a session decides at its start whether it has it.

      #3729

      Start agents in Rex

      Rex is a terminal server with sessions, tabs and panes. The Inbox can now start its agents there instead of in the background.

      Settings โ†’ Agents โ†’ Start new agents in has two choices: In the background (the default) and Rex. The row shows while Rex is running on this computer, or while Rex is already the choice. With Rex picked, a New message, or a reply that starts a session, opens a new tab named for the agent, in a Rex session the Inbox keeps for that project. The agent runs its ordinary interactive command there and keeps running after the Inbox closes. Rex's app is not brought to the front when a tab opens. Your message never goes on a command line; the agent receives it as its first turn through its own Inbox connection.

      • Claude Code, Pi and OpenCode can start in Rex. Codex always starts in the background, and so does every routine run, so a routine does not open a tab per run.
      • Where it lives. An agent in a Rex pane shows "Rex ยท session / tab" on its hover card, in the To picker and in its spoken name. This includes agents you started in Rex yourself, while Rex is the setting.
      • Show in Rex on the agent's menu moves Rex's app to that agent's tab. It needs Remote Control turned on in Rex's settings; if it is off, the Inbox says so.
      • Status marks. An agent in Rex gets a mark on its icon when its pane reports that it is working, waiting on you, done or failed.
      • Stop closes that agent's own tab in Rex and nothing else. Open in Terminal is not offered for an agent in Rex, because it would start a second process on the same session.
      • When Rex is not there, or does not open a tab, the agent starts in the background and the run line says why. A reply to an agent that stopped starts it again in a new tab, as the same session.

      Rex also runs as a server on Linux and FreeBSD, with no app on that machine and apps attaching from other computers. The Inbox finds such a server in the places Rex's manual gives, and starts agents there without an app. Show in Rex then asks the Rex apps attached to that server. For an agent on a linked machine, Show in Rex goes through the machine link to the Inbox beside that Rex. A click made on another computer never moves a Mac's own Rex app.

      The Inbox only talks to Rex through its existing socket, owned by your user. It never starts a Rex server, never types into a pane and never reads what a pane shows.

      #3606, #3693, for #3303 from @tommyent

      Search the list's filter

      When a section of the list's Filter menu has more than eight rows, a Search filters field sits at the top of the menu. Typing narrows every section at once (Agent, Project, Tag, Pull request, Routine and the rest), bolds the matching part of each row and ignores case and accents. A section with no match goes away, and a row you already ticked stays so you can untick it.

      The arrow keys move through the rows while the field keeps focus, Enter ticks a row and leaves the menu open, and Escape clears the field before it closes the menu. On a phone the field sits under the sheet's title, and opening the menu with a tap does not raise the keyboard. With short lists the menu is the same as before.

      #3620

      Start a thread from a pull request

      On a pull request's page in Reviews, when no thread is about that pull request yet, the Review thread section offers Start a thread. The page turns into an empty thread for the pull request in place: its header line with title, branch, changes and checks, one line ("Ask anything about this pull request. Your first message starts the thread."), and the reply box. The reply box's To control lists this computer's live agents in the pull request's project, then a new session of each agent.

      Nothing is made until you press Send. Your words come first in the message, and the pull request's details follow under a fold, "Sent with: this PR's details", which shows exactly what the agent received. From then on the pull request's row in Reviews and its page open that thread. Closed and merged pull requests, stacks of several pull requests, and pull requests outside a project do not get the button.

      #3629

      Picture it

      /picture-it is a new built-in skill, first among the built-ins in the reply box's / list. It asks the agent for one self-contained HTML page that explains what you are discussing, mostly drawings with short labels: for a code change, what changed and why. The skill tells the agent to take file names, lines and numbers from the code or the thread, to make the page read at phone width and take your Inbox theme, and not to change code while it makes the page. The agent sends the page back in the same thread as an attachment.

      The Inbox also recognises a page made this way from a mark in its head, and records which attachment it is. Nothing in the window uses that yet.

      #3723

      Before and after on a question card

      A question that proposes a change, to words, a screen, code or a setting, can now show it. The agent writes Where:, Before: and After: lines, and the Inbox draws them as a quiet Now and After pair: removed words struck through on a red tint, added words on a green tint. A line that changes almost entirely is shown whole instead of marked word by word. A value can be a picture, and two pictures sit side by side on a wide card. Each choice can carry its own After:, so a question about three wordings shows three versions.

      The agent tool's instructions, plannotator inbox --help before-after and the plannotator skill teach agents the format. Plan review, annotate and older Inboxes show these lines as plain text, and a question without them looks exactly as before.

      #3714

      Threads side by side

      Settings โ†’ General โ†’ Appearance โ†’ Threads side by side is a new switch, off by default. Turned on, a thread's right-click menu offers Open to the side , and you can drag a thread next to the open one. The change applies at once in every open Inbox window, with no reload. Turned off, the Inbox works exactly as it does today. A phone always shows one thread, so the row is not shown there. If you had turned on the hidden preview in config.json (inboxSplitView), the switch is already on.

      The panes themselves were also improved: Escape closes only the pane you are in, closing a pane by keyboard moves focus to the pane that is left, a column holds at most two panes, and the panes you are not in have a stronger grey header. When the window narrows and a pane steps aside, a toast says so, and the pane comes back when the window widens.

      #3719

      Agent status marks

      Show agent status (Settings โ†’ General โ†’ Appearance, under Sidebar, and in the list's โ‹ฎ menu) puts a status mark on every agent in the sidebar's Agents list, not only on agents in Rex. It is off by default. A mark shows when an agent is working, when it waits on a prompt where it runs ("Waiting for your permission in the agent" or "Waiting for your answer in the agent"), and when a thread waits on you. An agent at rest draws nothing. Marks show only in the Agents list, never on thread rows or the Board. A mark that could stay on "Waiting for your permission in the agent" when a prompt was answered within a second was fixed before release.

      Permission and question prompts are reported by Claude Code (questions, and permission prompts for Bash on Claude Code 2.1.326 and later), OpenCode 2, Pi and Oh My Pi.

      One part of this applies with the setting off: an agent that does not report when it is working (Codex, T3 Code, Antigravity and cloud agents, for example) is no longer called "Idle". Its hover card says "Doesn't say when it's working".

      #3710, #3735

      Tag a project

      A project's โ‹ฏ menu has Add tag , with the same tag list as a thread's menu. Picking a tag in the list's Filter then keeps threads that have the tag and threads in a project that has it, and the Board's tag filter does the same. This lets you see, say, every Work project together. Nothing looks different until you tag a project. Tags on a linked machine's project are kept on that machine.

      #3697

      Play a sound: for every agent message

      Play a sound (Settings โ†’ General, under "When an agent sends you something") now has a choice: when an agent asks you (the behaviour until now) and for every agent message , which is the new default. With the default, a plain reply, a new thread or a question from an agent rings the bell. Either way it rings only while no Inbox tab is in front, once for a burst of messages within 30 seconds, and never for your own messages or for snoozed threads. If you had turned the sound off, it stays off.

      #3695

      The new-messages bar

      The "N new ยท Show" bar above the list now stays at the top while you scroll, and says what came on one line, for example Claude Code replied in โ€œCheckout redesignโ€ ยท Show or 2 replies from Claude Code and Codex ยท Show. In a project or filter view, news from elsewhere gets a second line with Show all. The bar arriving no longer moves the rows you are reading. The floating New pill now shows only after you press Show, for rows that landed out of view.

      #3616

      Code review: the symbol hover card

      Moving the pointer from a symbol into its hover card ("8 references") often closed the card a moment later, with the pointer still in it. It now stays open until the pointer leaves the card. The hover underline and hand cursor now show only on names that can open a card, so comments, keywords and ; no longer look clickable. The card's footer is one line: "Click to jump ยท โŒ˜ click for all references" (Ctrl+click on other systems).

      #3728, #3732

      Code review fixes

      • Lines no longer move under you when semantic notes arrive. Once you start reading (scroll, click, type or jump to a file), a file's moved and renamed notes that arrive later are offered in its header ("1 moved", one click shows them) instead of redrawing the file at a new height. Files below the view still get their notes as they arrive. #3674
      • Semantic diffs on a slow connection. The first download of the engine and of each language could hit the three-second limit and fail the file. A language's first answer now gets 30 seconds. Lines you open stay where they are, and with the semantic switch off no file header shows a semantic note. A comment on any old-side line inside a folded "Moved N lines" block now opens the block. #3662
      • Expand arrows. A mouse click on an expand arrow or on the "N unmodified lines" label sometimes did nothing, mostly in Safari, because the row was redrawn during the press. The click now always opens the lines. #3666
      • Two Git settings no longer change what a review reads. With diff.relative=true, a review started in a subdirectory showed only that subdirectory, and expanding, staging and unstaging broke. With log.showSignature=true, a signed commit's short SHA and subject were read wrong. Every review Git command now turns both off. #3664
      • File tree. Escape in an empty search box moves focus to the tree's current row instead of the page. A renamed file's tooltip reads old โ†’ new. On the Inbox PR page, switching between Changes and All files keeps focus on the switch. #3663
      • A review job that ends at once no longer shows Running forever. If a Guided Review or agent review finished (or failed) before the window had read the answer to its own start request, that late answer set it back to Running until a reload. A finished job now stays finished, and one that fails at once shows Failed. #3747
      • Review agent instructions say in plain words that missing tests are a finding only when a change adds non-trivial logic with no test coverage at all. #3703

      Your Inbox rules reach MCP sessions

      Sessions that connect to the Inbox over MCP, such as every session T3 Code starts, only ever saw the built-in server instructions. The rules and reminder under Prompts โ†’ Inbox reached sessions started from a terminal but not these. The MCP server now adds your rules for all agents, then your reminder, after its built-in lines, and follows the same reminder switch. How much room they get depends on the client: Claude Code 2.1.296 and later keeps more than older Claude Code and other Claude apps, and other clients get the terminal path's limit. Rules and reminder are each sent whole or left out whole, never cut. Settings โ†’ Prompts shows the count against Claude Code's room and a "Not sent to โ€ฆ" note when your text is too long for some agents. A change applies to the next session, with no restart.

      By @sx4im in #3567, closing #3555 from @stjepanvrbic

      Fixes from

      Fourteen fixes from @rudycelekli, merged together in #3658 with each pull request's commits and authorship kept:

      • Paired cloud agents sawcomputer_asleep while the computer was awake. The Inbox now pings its relay connection and replaces one that stopped answering. A follow-up keeps the connection through a slow, large upload, such as a video sent to a phone. #3636, closing #3577 from @kyletruong
      • Oh My Pi: /new, resume and fork move the Inbox connection to the new session, so replies reach it (#3644, closing #3564 from @omederos), and a session switch resets plan mode and closes the open plan review (#3650).
      • Less repeated work on list and status reads. Each session's restart check is worked out once per response. #3637, part of #3623 from @Arobotmaster
      • Pull request stacks rank the forge's default branch as trunk ahead of an older branch named main (#3639), and an open pull request stays in its stack through five merged layers (#3641).
      • Bulk actions: a failed later batch of a bulk hide or show no longer undoes the batches that went through (#3640), and a bulk merge confirmation resets when a picked pull request's head, base or machine changes (#3649).
      • Linked machines: a linked machine's Board is read again after its first read fails (#3646), and a Reviews read in flight is dropped when that machine is unlinked (#3647).
      • Review diffs: removed lines such as ---- or --- x count in a file's +/โˆ’, the same in the file tree, the file header and stack cards (#3642); paths with leading or trailing spaces are kept (#3643); and blank context lines read correctly whatever your diff.suppressBlankEmpty setting (#3651).
      • Comment boxes stay open when Escape only closes an input method's candidate list. #3648

      Theme contrast

      Some text in the built-in themes was hard or impossible to read.

      • Invisible text in Simple and Neutral. Text on red buttons, such as the Inbox's confirm button, the "This review was replaced" banner and the remove ร— on attachments, was the same red as the button, or nearly. It is now near-white.
      • Pale accent text in Simple, Neutral and Quantum Rose light now reads at 4.5:1.
      • Faint grey text in light themes. Muted text in light themes such as Min, Material, Solarized, Tokyo Night, One Light, Rosรฉ Pine, Vitesse and the Everforest themes is darker, to at least 4.5:1. In six of them the body text is darkened too, so it still reads stronger than the grey. Dark modes are unchanged.

      #3706

      Which version of an attachment you are viewing

      When an attachment opened beside a thread has changed since it was sent, the line above it now says which version is on screen, for example "Viewing the current file (edited 5:51 PM). Claude Code sent an earlier version at 3:41 PM." with View sent version , or "Viewing the version Claude Code sent at 3:41 PM." with View current file. Full screen's chip uses the same sentence and link.

      #3704

      Additional Changes

      Known issues

      • Rex on Linux and FreeBSD has been tested against a stand-in for Rex's server, not a real one.
      • Threads side by side: narrowing the window does not fold the docked sidebar, so fewer panes fit than could, and Tab moves through panes in the order they were opened, not the order they sit on screen.
      • Code review: clicking the header of a file with opened lines still folds them back.

      Install / Update

      macOS / Linux:

      curl -fsSL https://plannotator.ai/install.sh | bash
      

      Windows:

      irm https://plannotator.ai/install.ps1 | iex
      

      Claude Code Plugin: The install script above also updates the plugin when claude is on your PATH. Otherwise, in a terminal:

      claude plugin marketplace update plannotator
      claude plugin update plannotator@plannotator --scope user
      

      Then restart Claude Code. Inside Claude Code, run /plugin marketplace update plannotator, then open /plugin โ†’ Installed โ†’ plannotator โ†’ Update now.

      Pi:

      pi update npm:@plannotator/pi-extension
      

      OpenCode: Re-run the install script above. It also clears the OpenCode 2 plugin cache.

      What's Changed

      • File tree: Escape focus, rename tooltip, focus after switching lists in #3663
      • Reconnect the Inbox when a relay socket stops answering by @rudycelekli in #3636
      • Reuse restart judgments in Inbox thread and status responses by @rudycelekli in #3637
      • Prefer the forge's default branch when grouping PR stacks by @rudycelekli in #3639
      • Keep successful entries when a later bulk hide or show fails by @rudycelekli in #3640
      • Keep an open PR attached through five merged stack layers by @rudycelekli in #3641
      • Count patch-marker-like lines in review hunks by @rudycelekli in #3642
      • Preserve whitespace in Git review paths by @rudycelekli in #3643
      • Move the Inbox wake when Oh My Pi switches sessions by @rudycelekli in #3644
      • Retry a linked Board after its first read fails by @rudycelekli in #3646
      • Discard linked Reviews reads when their machine is unlinked by @rudycelekli in #3647
      • Keep comment composers open on an IME Escape by @rudycelekli in #3648
      • Refresh bulk merge confirmation when its target changes by @rudycelekli in #3649
      • Restore plan mode when Oh My Pi changes sessions by @rudycelekli in #3650
      • Read Git hunks that omit blank context prefixes by @rudycelekli in #3651
      • Fourteen fixes from @rudycelekli, merged together in #3658
      • Review: pin diff.relative and log.showSignature off in review Git commands in #3664
      • Review: a click on an expand arrow always opens the lines in #3666
      • Inbox: Start a thread from a PR's page, an empty thread in place in #3629
      • Semantic diffs: opened lines stay put, switch off and on, slow links in #3662
      • Inbox: where an agent lives in Rex, Open in Rex, Show in Rex in #3606
      • Internal: move shared Inbox types in #3682
      • CI: internal change in #3677
      • Semantic diffs: notes that land after you started reading are offered, not swapped in in #3674
      • Internal: move question answer code in #3686
      • Internal: name a list row rule in #3688
      • Inbox server: internal change in #3678
      • Mobile: internal work in #3679
      • Mobile: internal work in #3681
      • Inbox: search the list filter when a section is long in #3620
      • Relay: internal change in #3680
      • Inbox: send your Inbox rules and reminder to MCP sessions by @sx4im in #3567
      • Mobile: internal work in #3684
      • Mobile: internal work in #3685
      • Mobile: internal work in #3699
      • Mobile: internal work in #3701
      • Review instructions: say plainly when missing tests are a finding in #3703
      • Inbox: the version line says which version you are viewing in #3704
      • Mobile: internal work in #3694
      • Inbox list: the N new bar sticks; the New pill shows only after Show in #3616
      • Fix blank text and faint light muted text in the built-in themes in #3706
      • Mobile: internal work in #3708
      • Inbox: tag a project, and let the filter pick the tag in the list and on the Board in #3697
      • Inbox: status marks for every agent, behind a setting in #3710
      • Show a proposed change on a question card: Where, Now and After in #3714
      • Fix a flaky test: a grammar download that never ends in #3722
      • Inbox sound: ring for every agent message, or only when an agent asks in #3695
      • Mobile: internal work in #3713
      • Inbox: a Settings switch for thread panes (off by default) in #3719
      • Review: keep the symbol hover card open while the pointer is in it in #3728
      • Rex on any server: Linux and FreeBSD servers, starts with no app, Show in Rex from other computers in #3693
      • Review: a one-line footer on the symbol hover card in #3732
      • Picture it: the /picture-it skill and the page mark in #3723
      • Agent status: a prompt set and cleared between two looks reaches the window in #3735
      • The Inbox turns on only when you run it in #3729
      • Review: a finished job stays finished when its launch answer arrives late in #3747

      Contributors

      @rudycelekli sent fourteen fixes this time, across the relay connection, Oh My Pi, pull request stacks, bulk actions, linked machines, review diffs and comment boxes (#3636 to #3651). They landed together in #3658 with each commit and its authorship kept. Two of them close reported issues: the dead relay socket and Oh My Pi's /new.

      @sx4im made the MCP server carry your Inbox rules and reminder, sized to what each client keeps of its instructions, with a count and notes in Settings โ†’ Prompts (#3567).

      Thanks also to the people whose reports shaped this release:

      • @stjepanvrbic reported that Inbox rules and the reminder never reached sessions connecting over MCP (#3555)
      • @kyletruong measured an idle Inbox losing its relay connection after about an hour and never reconnecting, leaving paired cloud agents with computer_asleep (#3577)
      • @omederos found that a session started with /new in Oh My Pi did not get Inbox replies, and traced it to the session switch event (#3564)
      • @Arobotmaster reported thread-list latency that depended on the session (#3623)
      • @tommyent asked for the Inbox to say where each agent runs (#3303), which the Rex work answers for agents in Rex

      Full Changelog : v0.29.0...v0.29.1

    3. ๐Ÿ”— smol-machines/smolvm smolvm v1.35.5 release

      What's Changed

      • docs: say that virtiofs DAX is off on arm64 hosts and SMOLVM_MOUNT_DAX does nothing there by @BinSquare in #2087
      • Add smolvm docker: one command starts a Docker engine in a managed machine and points docker at it by @BinSquare in #2089
      • Share the home directory with the smolvm docker machine at the same path by @BinSquare in #2090
      • Resolve host.docker.internal to the host from smolvm docker containers by @BinSquare in #2091
      • Fix a port race in the leader-exit test by @BinSquare in #2096
      • Remove smolvm docker by @BinSquare in #2095
      • Hand supplied credential values to a running embedded machine at once by @BinSquare in #2097
      • Pin libkrunfw with UDP kept inside a TSI guest, and test it by @BinSquare in #2099
      • Publish ports below 1024 on macOS, add IPv6 loopback to live-forwarded ports, and lift the 64-mapping cap by @BinSquare in #2092
      • Return idle guest memory to the host within two minutes and cap new machines at half the host's RAM by @BinSquare in #2094
      • Install a root-owned agent-rootfs when root runs install.sh by @rdslw in #2082
      • Announce a changed file to the guest once per change by @BinSquare in #2102
      • Answer guest DNS from a host cache that coalesces bursts and resends lost queries by @BinSquare in #2098
      • Keep every disk chain under the branch depth limit: fold restored checkpoint layers and frozen-source chains by @BinSquare in #2103
      • Exec sessions: commands the node owns, resumable after a dropped connection by @BinSquare in #2101
      • Let a guest hold tens of thousands of connections on virtio-net and free their host sockets promptly by @BinSquare in #2104
      • Scope the usage journal to the test's own thread by @BinSquare in #2106
      • Pin libkrun 526be460 and libkrunfw f290c62b, rebuilt for every platform by @BinSquare in #2109
      • Build the agent rootfs as non-root on hosts with user namespaces again by @BinSquare in #2107
      • Answer a start missing the mediated interceptor with 400, not 500 by @BinSquare in #2108
      • Run tests that need a released file lock free at once in their own process by @BinSquare in #2110
      • Pin libkrun 9df62257 and libkrunfw 7f4d4950, rebuilt for every platform by @BinSquare in #2113
      • Stop resetting virtio-net connections a server closes first by @BinSquare in #2118
      • Upgrade rusqlite to 0.41 for the patched bundled SQLite (RUSTSEC-2026-0459) by @BinSquare in #2128
      • Keep a host memory reserve VMs cannot take and charge branch children for growth by @BinSquare in #2127
      • Ask before stopping a machine on delete, so a refused or declined delete leaves it running by @connorburgess in #2131
      • Prepare SmolVM v1.34.1 for release by @BinSquare in #2135
      • Bring a soft open-file limit above kern.maxfilesperproc down to the cap on macOS, so the limit raise_nofile_limit reports is the one in force by @connorburgess in #2132
      • Leave no data directory behind when exec, status or stop name a machine that does not exist by @connorburgess in #2129
      • Warn when --block-private keeps a named host unreachable by @BinSquare in #2146
      • Register Rosetta itself as the x86_64 interpreter when the host answers its start-up ioctl by @BinSquare in #2148
      • Make a mounted host directory belong to the workload user so a non-root workload can write to it by @BinSquare in #2149
      • Record the image platform on the machine so a Rosetta machine can be created from an amd64 image by @BinSquare in #2147
      • Bump libkrun so a Rosetta machine runs amd64 programs directly and a macOS machine stops promptly by @BinSquare in #2150
      • Keep a cache disk's chain on its shared base when compaction shortens it by @BinSquare in #2145
      • Satisfy Rust 1.100's needless_bool lint in connect_in_progress on Windows by @BinSquare in #2154
      • Bound branch admission and reported capacity by the VM slice's memory limit, not just host free memory by @BinSquare in #2152
      • Stop throttling the VM slice and reclaim it from the pressure guard instead by @BinSquare in #2153
      • Release a paused branch child's VM lock so the memory pressure guard can resume it by @BinSquare in #2157
      • Keep a restored machine's local image on its storage disk instead of mounting the capturing host's archive by @BinSquare in #2163
      • Update quinn-udp to 0.5.16 for RUSTSEC-2026-0538 by @BinSquare in #2165
      • Count every symlink with one mode in the agent rootfs digest so a Mac checkpoint restores on Linux by @BinSquare in #2162
      • Carry guest traffic in 64 KB frames over the gateway link so downloads use a quarter of the CPU by @BinSquare in #2168
      • Pin libkrun 518949b4 and libkrunfw 0fae3853, rebuilt for every platform by @BinSquare in #2169
      • Reserve tmpfs for concurrent RAM captures and sweep abandoned checkpoint scratch at serve start by @BinSquare in #2173
      • Let a packed image's branch take the deferred checkpoint save and say when the VM died mid-save by @BinSquare in #2174
      • Integrate and validate Docker Engine, automatic ports, and nested Rosetta support by @BinSquare in #2172
      • Run x86_64 images in containers Docker starts inside a Rosetta machine, keeping their PID by @BinSquare in #2093
      • Serve the Docker Engine API from smolvm, every container a machine by @BinSquare in #2114
      • Publish the ports a machine starts listening on, with --auto-ports by @BinSquare in #2136
      • Give engine containers user-defined networks, so Docker Compose stacks run by @BinSquare in #2115
      • Let engine containers reach the Docker socket, so Testcontainers and Dev Containers work by @BinSquare in #2116
      • Branch engine containers from a warm base when many of one image run by @BinSquare in #2117
      • Publish engine container ports on the address each one names by @BinSquare in #2119
      • Give engine containers a volume for each VOLUME their image declares by @BinSquare in #2120
      • Move images in and out of the engine: save, load, push, commit, import, export by @BinSquare in #2121
      • Run --network container: containers in that container's machine by @BinSquare in #2122
      • Give engine networks IPv6 by @BinSquare in #2123
      • Run the Docker API on demand with independent workload supervisors by @BinSquare in #2175
      • Fix Buildx volume permissions and macOS restart stalls by @BinSquare in #2178
      • Improve default macOS shared-volume write performance by @BinSquare in #2179
      • engine: speed up macOS Buildx with automatic overlayfs snapshots by @BinSquare in #2181
      • Run the guest keep-alive init as root while workloads and execs keep the image user and its supplementary groups. by @BinSquare in #2004
      • engine: fix multi-stage Buildx builds containing deleted files by @BinSquare in #2183
      • Scrub injected credential values from what a credential host sends back by @BinSquare in #2180
      • Re-authorize a restored checkpoint's credential bindings from the CLI, and refuse a start that could not inject them by @BinSquare in #2182
      • Sweep a deleted machine's pause-operation lock along with its fork-operation lock by @connorburgess in #2184
      • Let machine update set and remove labels, in any machine state by @josmo in #2143
      • Leave the Docker Engine API opt-in so installing or upgrading smolvm never switches the user's Docker context by @BinSquare in #2186
      • Bump every workspace crate and the nix flake to 1.35.0 by @BinSquare in #2185
      • fix(network): retain OS-allocated local TCP listeners by @kumanday in #2112
      • Retry a checkpoint part the object store refuses with a transient error by @BinSquare in #2191
      • fix(shim): preserve foreground helper exit statuses by @hfiguera in #2190
      • Delete the image seed builder when a CLI start is interrupted, and reap builders whose owner exited (#2083) by @rdslw in #2188
      • Honor SMOLVM_DATA_DIR and --state-dir on macOS by @BinSquare in #2193
      • Map a mounted host directory to the workload user again, not the keep-alive init's root, so a non-root workload can write to it by @josmo in #2189
      • Open the Nix flake bump from main and run its required attribution check, so the bump PR can merge by @BinSquare in #2194
      • Bind the port forward tests' ports before using them, instead of picking a free port and binding it again later by @BinSquare in #2195
      • engine: use an on-demand native Buildx builder by @BinSquare in #2196
      • perf(engine): reduce container lifecycle overhead by @BinSquare in #2198
      • perf(engine): improve streaming output throughput by @BinSquare in #2200
      • perf(engine): bound log tail reads and stream binary payloads by @BinSquare in #2201
      • Compile the auto ports test's port helper only on Unix, where its one caller runs by @BinSquare in #2199
      • Keep an image's files under /run when a container starts by @BinSquare in #2203
      • Leave the Docker context alone when an engine with its own state directory is set up, and remove its registration by name by @BinSquare in #2202
      • Stop a workload supervisor on SIGTERM and when its engine state is deleted, whoever holds the warm base lock by @BinSquare in #2204
      • Start a display without a host GPU, check the host GPU before a --gpu start, and finish stop and delete around a process the kernel will not let exit by @BinSquare in #2210
      • Allow ARM cloud checkpoints to return to macOS by @BinSquare in #2216
      • Refuse a staged sync entry whose parent leads outside the mount through a symlink, so a guest cannot delete host files by @BinSquare in #2242
      • Serve at most eight workload log connections, closing the oldest, so a guest cannot exhaust host threads by @BinSquare in #2243
      • Bump libkrun so a resumed macOS machine releases the memory its guest frees and keeps it out of checkpoints by @BinSquare in #2244
      • Trim the guest's disks before a capture, so deleted files leave the checkpoint and the host disk by @BinSquare in #2245
      • Forget a host's learned addresses when a running machine's allow list is left with no hosts by @josmo in #2142
      • Point exec and cp on a paused machine at resume, not at a start that refuses it by @connorburgess in #2167
      • Bump libkrun so restored macOS machines keep later writes in checkpoints and qcow2 discards free host disk space by @BinSquare in #2248
      • Preserve local-image machines across export and restore by @Vishv07 in #1980
      • Preserve packed network restrictions and apply overrides atomically by @Vishv07 in #2006
      • Clone the case-sensitive layers image instead of formatting a new one by @BABTUNA in #1713
      • Preserve staged files when an interactive output pipe closes by @connorburgess in #2164
      • Diagnose unsupported macOS virtualization without masking other failures by @Bnjoroge1 in #1323
      • Allow disk growth before first boot by @BinSquare in #2211
      • Expose machine files and harden engine storage workflows by @BinSquare in #2206
      • Close failed port-forward tunnels and reap reply readers by @BinSquare in #2214
      • Fix Docker container name filtering by @BinSquare in #2225
      • Speed up and isolate first-use disk template expansion by @BinSquare in #2229
      • Fix Docker networking and persistent VM lifecycle by @BinSquare in #2234
      • Serialize overlay remounts so concurrent prepares don't race by @Liamso in #2166
      • Fix interactive stream stalls and idle wakeups by @BinSquare in #2250
      • Report Docker container resources from guest kernel accounting by @BinSquare in #2228
      • Preserve image index digests for Docker image lookup by @BinSquare in #2224
      • Hold back the growth already promised to running branch children when admitting a branch by @BinSquare in #2205
      • Share local images with managed Kubernetes and recover filesystem notifications by @BinSquare in #2219
      • fix(engine): stop polling idle Docker event streams by @BinSquare in #2251
      • fix(checkpoint): retain booted rootfs after app updates by @BinSquare in #2253
      • Preserve container sessions and discover local apps by @BinSquare in #2254
      • Build a restored checkpoint over the most similar tree the node has, not only a recorded ancestor by @BinSquare in #2255
      • Clean up disconnected sessions when guest input is blocked by @BinSquare in #2256
      • chore(nix): bump flake to 1.35.3 by @github-actions[bot] in #2249
      • Add machine credentials refresh, which hands a running machine new credential values from this shell without a restart by @BinSquare in #2257
      • Approve the Nix flake bump PR's held checks, so a release's bump can merge by @BinSquare in #2258
      • Let the Nix package keep the guest rootfs's links, and build the flake in CI by @BinSquare in #2261
      • Bump libkrun so a Windows guest rewrite keeps a file's owner and a share can serve a default owner by @BinSquare in #2262
      • Let a host mount name the guest owner of its files (-v HOST:GUEST:uid=N[,gid=N]) by @BinSquare in #2260
      • Keep pack and OCI layer extraction from touching anything outside the layer by @BinSquare in #2264
      • Reuse a pack's extraction only for the artifact it came from, and key bundled libraries by SHA-256 by @BinSquare in #2266
      • Load a pack's own libraries only when they came from the executable running by @BinSquare in #2267
      • Serve only the host on the guest agent's vsock listeners by @BinSquare in #2268
      • Keep host loopback closed to gateway flows under --block-private by @BinSquare in #2269
      • Pin libkrun at the share-confinement fixes by @BinSquare in #2271
      • Add on-demand SSH and SFTP for seamless environment access by @BinSquare in #2272
      • Preserve image-backed containers across VM pause and resume by @BinSquare in #2274
      • Expose checkpoint reader requirements before local offload by @BinSquare in #2277
      • Keep pod volume copies private to the VMM and honor read-only volume mounts by @BinSquare in #2270
      • Support POSIX ACLs on a machine's ext4 disks by @BinSquare in #2276
      • Keep guest root ownership consistent across hosts by @BinSquare in #2279
      • Preserve guest permissions when installing the runtime by @BinSquare in #2281
      • Preserve PAX filenames and links containing newlines by @BinSquare in #2283
      • Relocate checkpoint mounts without losing ownership by @BinSquare in #2284
      • chore(nix): bump flake to 1.35.4 by @github-actions[bot] in #2263
      • Preserve machine ownership across lifecycle and transfer operations by @BinSquare in #2289
      • Preserve workload dependencies during transfers by @BinSquare in #2290
      • Unpack image layers whose entries use absolute paths by @BinSquare in #2291

      New Contributors

      Full Changelog : v1.34.0...v1.35.5

    4. ๐Ÿ”— exe.dev Rex-on-exe rss

      Using Rex to Access exe

      If youโ€™re one of the โ€œlucky fewโ€ whoโ€™s running Rex as their daily shell, adding exe.dev hosts to Rex is easy. Create a new vm with ssh exe.dev new, and then, from inside a Rex terminal, run:

      rex server install ssh://<your-vm-name>.exe.xyz
      

      This installs the Rex server on your exe VM. After that, you can connect using the ssh:// URLs, and youโ€™re all set.

      With that out of the way, it's kind of fun to look under the hood to see how it all works.

      What's All the Fuss About?

      In an agentic world, what's old is new again, and many of us are doing work on remote machines rather than our laptops. Some of the reasons for this are:

      • VMs isolate agents
      • VMs facilitate parallelism
      • We can do "dev-is-prod" in VMs by developing and deploying on the same machine

      Working on remote machines kinda stinks, without rich affordances. If you SSH to a remote machine and you close your laptop, your session will drop, taking all of its state with it. This is not a new problem. Tailscale abstracts away the network so that your session doesn't drop. mosh introduces a terminal synchronization protocol and is resilient to drops. Eternal Terminal is similar to Mosh. tmux and screen virtualize your sessions, so you can reconnect to them. zmx, tmate, dtach, atch, abudco, reptyr... so many options in this space. Perhaps the most common approach is tmux , but it comes with one major downside: you have to use tmux, and now things as simple as splitting your terminal into two panes become Ctrl-B ", and who's got time for all that?

      Rex splits up the problems nicely. The Rex server runs on the remote machine, and manages multiple sessions (which in their terminology contain windows, which contain blocks, which are terminals). The Rex server listens locally on a Unix socket. The protocol is HTTP. If the server is killed, all its sessions go with it. That's not supposed to happen very often. This Unix socket is forwarded over SSH to your Mac, where the client app runs. The client app displays whatever sessions are available. The state lives on the Rex server on the remote machine, so when you create a split from the command line on your Linux machine, it is reflected in the client app.

      How Rex works. On the Mac, Rex.app connects to a local Unix socket
(~/Library/Application Support/rex/ssh/69b715b2โ€ฆ.sock), which an ssh -N -L
process forwards over ssh to the Linux machine. There, the sshd session (a
child process of sshd) connects to the same socket,
/run/user/1000/rex/server.sock, where the rex server listens. The rex server
runs two blocks, top and bash, whose processes are its children, and Rex.app
shows the same two blocks.

      If you (or your agent) want to do some advanced trickery, Rex ships with an llms.txt which you can pull out with something like curl -s --unix-socket /run/user/$(id -u)/rex/server.sock http://rex/llms.txt. It explains the protocols at quite some length and enables giving your session to an agent.

      Session Persistence, Terminals, Apples, and Oranges

      There are several interwoven concerns at play when doing session persistence. Different tools solve different subsets of the problems. The table below highlights which tools solve which bits of the problem. I'm delighted that Rex is trying to solve many of the problems in one tool, rather than forcing me to cobble together solutions from multiple. Here at exe, we've felt many of the same problems and it's no surprise that exe- scroll and our Mac, iOS, and web apps share similar underpinnings (e.g., ghostty for terminal emulation and a unix socket on the server).

      I want to highlight "good for agents" in the table below: When the pi coding agent came on the scene, I realized that tmux wasn't just a terminal multiplexer. It was a CLI (tmux capture-pane, tmux send-keys) to let an agent manipulate a terminal session.

      As you look through the table, note how much SSH is doing. I think there's a lot of space for more approaches to auth and connectivity; SSH is showing its age. I'm particularly excited about systems like tailcat and iroh and web-based solutions. There are enough dimensions here that you can combine tools to get great experiences, but not all bundling combinations have been tried yet.

      | Plain SSH| SSH over Tailscale| Mosh| tmux| dtach| Terminal apps| Rex| exe- scroll| exe.dev apps
      ---|---|---|---|---|---|---|---|---|---
      Auth| SSH| Tailscale identity| SSH| Unix socket| Unix socket| n/a| Unix socket via SSH or Tailscale| Unix socket| HTTP cookies or SSH
      Transport| TCP| WireGuard (UDP)| TCP to initiate, then UDP| Unix socket| Unix socket| Local pty| SSH or Tailscale| Unix socket| HTTPS or SSH
      Process model| 1/connection| 1/connection| 1/session| 1 process, N terminals| 1/session| 1 app process, N terminals| 1/machine, N terminals| 1/terminal| exe-scroll
      Switching networks| No| Yes| Yes| Partly1| Partly1| n/a| Yes| Yes| Yes
      Multiple clients to same terminal| No| No| No| Yes| Yes| n/a| Yes| Yes| Yes
      Outlives the connection| No| Yes| Yes2| Yes| Yes| n/a| Yes| Yes| Yes
      Scrollback after reconnect| No| No| No| Yes| No| n/a| Yes| Yes| Yes
      Splits| n/a| n/a| n/a| Yes| n/a| Yes| Yes| n/a| n/a
      Native affordances| Yes| Yes| Partly3| No| n/a| Yes| Yes| n/a4| Yes
      Good for agents| Partly5| Partly5| No| Yes6| No| No| Yes| Yes| Yes
      Scriptable| Partly7| Partly7| No| Yes| No| n/a| Yes| Yes| Not sure
      Speculative local echo| No| No| Yes| No| No| n/a| No| No| No
      Viewing remote port| Yes| Yes| No| n/a| n/a| n/a| Yes| n/a| Yes

      1. Reattach
      2. Same client only
      3. No scrollback
      4. Via the apps
      5. One-off commands
      6. send-keys and capture-pane
      7. Commands only

      One Last Thing

      Vincent was kind enough to record a demo; check it out!

    5. ๐Ÿ”— The Pragmatic Engineer The Pulse: What can we learn from the Railway hack? rss

      Hi, this is Gergely with a bonus, free issue of the Pragmatic Engineer Newsletter. In every issue, I cover Big Tech and startups through the lens of senior engineers and engineering leaders. Today, we cover one out of four topics from last week 's issue of The Pulse . Full subscribers received the article below 7 days ago. If you 've been forwarded this email, you can subscribe here .

      Over the past two weeks I've talked with several CTOs and founders at infra companies, and in those circles, it's an open secret that companies are being targeted by what looks like Chinese attackers, using abliterated AI models (those with no safeguards). These attackers seem to only want AI model keys; most likely to sell at discounted rates. "Popping" an infra company and accessing thousands of AI keys can be profitable, so it's economical to spend heavily on offensive abliterated models.

      Cloud provider Railway was one of the several infra providers that was hacked two weeks ago, with customer secrets leaked. The company has released a very detailed postmortem, which is the most in-depth description of how such an attack happens and how fast attackers adapt.

      At a high level, this is what happened:

      • Phase #1: Several unsuccessful exploit attempts. On 18 Oct, the attacker created dummy Railway accounts and tried unsuccessfully to get into the company's systems. The attacks are blocked, but the attacker did not give up.
      • Phase #2: Get Railway 's monorepo code (5 steps in 11 hours). The steps:
        • Attacker finds a vulnerability so they can read files on Railway's build system
        • -> steals build credentials
        • -> tries the credentials on several internal systems
        • -> accesses a Temporal cluster that stores build histories
        • -> finds Railway's monorepo as a build history and downloads it
      • Phase #3: Gain SSH access to Railway 's cloud environment (4 steps in 10 hours):
        • Scans the downloaded code; tries using old endpoints
        • -> Gets a short-lived cloud credential by exploiting a misconfigured OpenID Connect binding in the deploy pipeline
        • -> Uses the short-lived credential to pull a long-lived cloud credential
        • -> Finds an SSH key with the long-lived cloud credential
      • Phase #4: Get access to customers ' AI provider keys (3 steps in 3 hours):
        • With cloud access, they query the production database and access encrypted environment variables. The attacker filters for AI provider keys
        • -> Figures out that there's a key management service that can decrypt the keys, which the attacker has access to with their access to the cloud environment
        • -> Calls the key management service to decrypt customer secrets (AI provider keys)

      Let's visualize how the attack unfolded:

      altVisualizing the attack on Railway

      I talked with Railway founder and CEO Jake Cooper, who said the attack was especially frustrating because at one point, they were only minutes behind the attacker: it was down to 1-8 minutes that the attack could unfold in the way it did because Railway's team was alerted to their build system's credentials being probed on internal systems eight minutes after the attacker started in phase #2. Railway revoked credentials the attacker used to download the monorepo just one minute after the attacker used them:

      altFrustrating: in phase #2, Railway's team got close to stopping the attack

      What makes attacks by abliterated AI models different

      Railway's summary is the first in-depth account of how an attack from an offensive AI model plays out, and there are several noteworthy details:

      From the attacker's side:

      • Stolen code can be exploited within hours by an AI model. If a human got access to Railway's monorepo, it would have likely taken days or weeks for them to figure out the weaknesses to launch further attacks at. But with AI models, all this is sped up: six hours after downloading the code, the attacker figured out a plan to get access to the AI provider keys, and knew where to look from then on.
      • Abliterated AI models are like bloodhounds: relentless in chasing their goal. The offensive AI model just kept going and going, trying to get access to ever more systems with the sole goal of accessing AI provider keys. It's hard to imagine such durability by a human in keeping going through hoop after hoop to finally get access to AI keys!
      • Attackers never give up, not even after all doors and windows are sealed shut. Railway evicted the attacker and revoked all the paths they used to get in. But the attacker returned and probed for new weaknesses the same night!

      From the defender's point of view:

      • Storing hashes of customer secrets is a very smart approach. As soon as Railway discovered the breach, they sent over the hashes of AI provider keys to all AI providers, so those providers could cancel them to avoid the attacker draining customer accounts. Hashing allowed Railway to send the keys without knowing them, and for providers to revoke them immediately.
      • Defenders are handicapped by models ' capabilities. Attackers have access to abliterated AI models, while the models Railway has for defense - from the likes of OpenAI and Anthropic - refuse to engage in cybersecurity activity, including defensive work. Railway had no access to Project Glasswing during the incident, which would have allowed removal of some restrictions. As of today, Railway does have access, but many infra companies don't have that privilege.
      • Railway decided to move to a new build system, instead of patching the existing one. Once Railway realized that its build infra was how the attacker gained entry, they shut down all builds. This was a problem for customers, given they needed to re-deploy builds with rotated keys! Railway decided to move every customer to an unreleased build system, and not attempt to patch the existing one. Fortunately for Railway, they had the new build system nearly ready to go!

      During such an attack, the vendor often has to very quickly choose between "bad" and "worse" decisions. Railway faced a couple of these:

      • To simply notify customers that their API keys were leaked, or immediately notify vendors like Anthropic and OpenAI, sending over API key hashes? Railway did the latter at the risk of upsetting some customers, and even causing unaffected customers' services to stop working until they created and set up a new API key. The trade-off was that this limited overall financial damage.
      • Should Railway have allowed builds to happen after revoking the attacker's build system credentials? Allowing customers to do builds would have meant less service disruption, but the attacker could have returned via a slightly different path and stolen the rotated keys. Railway decided to bite the bullet by halting builds and rebuilding its build system in a matter of hours.

      Lessons from this incident

      I'm impressed by how much Railway has reflected on the structural problems that made it easier for the attacker to succeed, and how the company fixed them:

      • Builds should not run on shared machines. The whole attack started with the attacker being able to attack the build's isolation boundary (the sandbox on the VM), and getting access to the build machine's environment. Since that build machine ran several customers' builds, it had credentials that were valuable to the attacker. Railway has now rebuilt its build stack so that each build gets its own throwaway virtual machine - which is a much stronger boundary than a sandbox on a VM.
      • Add fine-grained access control for all internal secrets. Assume that an attacker will appear within your trust boundary and try to use secrets to get access to internal services. After the attack, Railway rebuilt its CI system to separate out sensitive components, with fine-grained access control. Getting access to important and sensitive credentials now requires 2FA, and even biometrics.
      • Assume that attackers have full access to your source code. The attacker was able to come up with a better plan of attack only after getting access to Railway's source code. Securing all of your source code is very hard - and might not even be possible in the context of social engineering attacks via an employee. So, design security as if attackers already have full source code access.
      • Decommission old, unused systems. The attacker probed credentials on Railway's old systems, and although they didn't get far, they could have found more weaknesses. Following this attack, Railway has shut down old, unused systems.
      • Increase logging and alerting. Even if you do all of the above, an attacker could get access to your systems in unexpected or novel ways. As and when this happens, ensure that you will be alerted for unusual usage patterns, like some services being accessed with invalid or old credentials, unusual internal network activity, etc.
      • It 's essential to respond to suspicious activity within minutes, not hours or days later. Attackers with AI are much faster at hopping between systems than we've been used to seeing. Defenders have the advantage that they can spot unusual patterns; after all, an attacker is fumbling around inside an unfamiliar system. But you need to act fast to evict an attacker inside your system!

      **Seeking to gain from competitors ' problems: what goes around, comes

      around**

      There's an unwritten rule among software vendors that you don't turn competitors' outages into a sales pitch to try and poach their customers for yourself.

      But Northflank evidently didn't get this memo. On the day of Railway's outage, the market rival published a blog post titled "How to migrate off Railway." The article started by linking to Railway's security incident disclosure, and explained how to safely migrate to Northflank. In the article, Northflank also boasted about its security capabilities:

      "Security controls also include BYOC, workload isolation, network security, and envelope encryption, helping teams manage infrastructure access and reduce exposure."

      The article reads like a naked attempt to grab customers from Northflank's rival, stating: "Railway got hacked, come on over to Northflank, which is a platform that cares about security."

      Any engineering teams that decided to take the offer ended up getting hacked not once, but twice. Nine days after Railway's hack, Northflank got hacked in a near-identical way. From Northflank's incident summary:

      "The first known decryption of [customer AI] secrets occurred between 02:39 UTC and 03:08 UTC on 30 October. Northflank received its first security platform alert at 11:43 UTC, and our engineers responded within minutes. The exploit was patched within 60 minutes of notification, and customers were notified within two hours.

      Some customers have reported unauthorised use of AI secrets. Please rotate all secrets now, both integration secrets and project secrets, even if you haven't seen suspicious activity. We recommend starting with AI provider keys, cloud provider credentials, payment provider keys, private keys, and database and other service credentials.

      We also recommend reviewing your provider logs for unusual activity. If you have seen unexpected AI usage or spend, contact your AI providers directly, such as OpenAI and Anthropic."

      So, Northflank took nine hours to detect that customer secrets had been stolen, 11 hours to notify customers, and - unlike Railway - they did not proactively notify AI providers to revoke the keys. Objectively, this is a worse response than Railway's, yet it was Northflank that tried to capitalize on the security outage.

      In this particular context, companies would do better to help other players in the market, rather than dunk on their competitors, and indeed, Railway's CEO texted Northflank to offer support and information about their attack. At first glance, this might appear a bit counter-intuitive to help rivals, but Jake Cooper realized what Northflank's leadership seems to have missed: that it's bad for all infra providers if many of them get hacked because customers will stop trusting all infra providers! It's in the interest of providers to collaborate on this matter and harden their own security. Once they do so, then companies win the market based on features, pricing, and innovation.

      Plus, it's just a very short-sighted way of doing business to try to capitalize on novel security incidents, especially as Northflank seems to have been worse at dealing with the breach than the competitor they went after!

      I have no affiliation with Railway or Northflank and struggle to see why Northflank did not remove the article about Railway's security incident article. One guess would be that it's a sign the business isn't exactly thriving, and that they're ready to try anything to keep things afloat.


      Read the full issue of The Pulse this is from, or check out this week 's The Pulse. This week's issue covers:

      1. Anthropic: the largest-ever IPO. The leading AI frontier lab raised $107B with its IPO, and around 600 early employees could see gains of $100M or more. It's absolutely incredible for a startup that is only five-and-a-half years old.
      2. Is Amazon 's writing culture collapsing because of AI? A former Amazon software engineer sees signs that written artifacts - the 'six-pager' documents the company uses to promote good decision making - are increasingly AI-generated and AI-read, and warns it's not a positive development.
      3. Meta struggles to understand devs & reverses Conductor shutdown. Meta shuttered the AI coding harness Conductor after acquiring it, but is now reversing its decision - possibly after learning that a rival harness, T3 Code, is getting four times the usage of the latest Gemini model. Oops!
      4. Is AI making us pay off decades of tech debt? The industry is currently on a speedrun of vulnerabilities being uncovered and patched or exploited. One way of looking at it could be that we're on a speedrun to pay off decades of tech debt.
    6. ๐Ÿ”— Console.dev newsletter Sponsor: WarpBuild rss

      WarpBuild - Braintrust, Raycast and Jane Street run CI on WarpBuild. Get started with $50 in free credits.

      Visit WarpBuild

    7. ๐Ÿ”— Console.dev newsletter Kiri rss

      Docker Desktop alternative.

      What we like: Single, Docker-compatible daemon (CLI, Compose, buildx). Performance optimized with a small memory footprint. Includes networks, volumes, k8s. Dev tools like auto-HTTPs endpoints with publicly sharable URLs. Supports macOS, Windows, Linux.

      What we dislike: Non-native UI, unlike something like Orbstack (which is macOS only). โ€œMachinesโ€ are containers with filesystem access, not true VMs.

    8. ๐Ÿ”— Console.dev newsletter Jiff rss

      Datetime library for Rust.

      What we like: Understands timezones natively and handles daylight sayings. Built-in handling of common date operations like durations, differences, calculations, geo regions. Uses Rust-native formatting and display options, including friendly formats.

      What we dislike: Shows you how complex dates and times actually are, but that probably means fewer bugs!

    9. ๐Ÿ”— Console.dev newsletter Sponsor: Coresignal rss

      Agentic B2B search for builders

      Visit Coresignal

    10. ๐Ÿ”— @binaryninja@infosec.exchange Binary Ninja is in Japan! We're attending TenguCon and CODE BLUE this week. If mastodon

      Binary Ninja is in Japan! We're attending TenguCon and CODE BLUE this week. If you're around, make sure to come say hi to the team!

  3. November 18, 2026
    1. ๐Ÿ”— IDA Plugin Updates IDA Plugin Updates on 2026-11-18 rss

      IDA Plugin Updates on 2026-11-18

      New Releases:

      Activity:

      • apiscout
        • eb2e94ea: DB builder: refuse DEF files of the other bitness, parser follow-ups
        • 42efe485: DB builder: check DEF files against named exports, review follow-ups
        • 616d09ef: DB builder: name exports by ordinal only from DEF files (#7)
        • eb8de9b0: Merge pull request #63 from danielplohmann/fix/ida-view-not-opened
        • 66c698aa: IDA plugin: open the results view from a timer
        • 8ac70a58: Merge pull request #61 from danielplohmann/ci/release-process
        • 0519a86c: ci: adopt the shared release process for v3.0.0
        • 2fb89f70: Merge pull request #60 from r0ny123/refactor/repo-layout
        • 070f283e: Merge pull request #59 from r0ny123/feat/min-confidence-default
        • df558b4d: Move the Binary Ninja plugin folder to plugins/binja_scout
        • 74577494: Move the IDA and Ghidra plugins to plugins/
        • 309e43ce: Run the DB builder as a module, vendored pefile in _vendor
        • 3846483c: scan: drop hits with a confidence below 20 by default
        • 20487906: Merge pull request #58 from r0ny123/feat/plugin-load-addresses
        • 1783ca87: Merge pull request #57 from r0ny123/fix/review-followups
        • 1f57e269: Merge pull request #56 from r0ny123/feat/symbols-keyed-speed
        • 4ad4e54e: Merge pull request #54 from r0ny123/feat/api-hashes
        • 9d507ad1: Merge pull request #53 from r0ny123/feat/explain-match
        • 9086bf2b: Merge pull request #52 from r0ny123/feat/hit-confidence
      • augur
        • a8ef7a00: docs: render workflow badges with shields.io
        • 639af045: docs: host documentation on docs.rs instead of github pages
      • haruspex
        • 98f2f5c1: docs: render workflow badges with shields.io
        • caf2934c: docs: host documentation on docs.rs instead of github pages
      • oh-my-pi
        • 57771ae5: chore: bump version to 19.0.0
        • 2421bdb9: chore: bump version to 19.0.0
        • 003818b5: chore: bump version to 19.0.0
        • 028f1d6b: chore: bump version to 19.0.0
        • 8bb17f25: chore: bump version to 19.0.0
        • 47c5a9bf: chore: bump version to 19.0.0
      • rhabdomancer
        • 1599926a: docs: render workflow badges with shields.io
        • 7b8e6a72: docs: host documentation on docs.rs instead of github pages
    2. ๐Ÿ”— exe.dev Hey Shelley, Fix My Monitor rss

      Earlier this year, I was on the hunt for a new monitor. My old one was a 27โ€ 4K (Dell U2720Q). I wanted something slightly bigger and ideally 5-6K. After doing a bit of research, I realized that my options were fairly limited. The Apple Pro Display XDR was pretty but 4x my budget. The Apple Studio Display was 5K and 27โ€, so it didnโ€™t fit the bigger screen requirement. The Dell U3224KB was 2.5x my budget.

      But then I lucked out and found a brand new Dell U3224KB for ~$1,100 on Facebook Marketplace. I was so excited when I plugged it in, but then I realized it had a manufacturing issue where these lights would just continuously cycle on and off. I think the intent was for them to turn on when my hand was near them, but theyโ€™d turn off for a few seconds and then turn right back on. It was almost like a perpetual notification coming in and distracting me from my work. I stopped using the monitor for a few months.

      The touch buttons along the bottom edge of the Dell U3224KB, all lit: a
phone button, volume down and volume up in white, and microphone mute and
camera off in red.

      Any reasonable person would have tried to contact Dell support and have them fix the issue. But the thought of going through their website and figuring out how to chat with them and not having the original receipt just didnโ€™t feel like a good use of time. So I just continued using my laptop and feeling sad about my purchase.

      A few weeks ago, I saw that people were using agents to reverse-engineer and remove cruft from their smart TVs. That gave me the idea of asking Shelley to fix my monitor. After giving it access, I spun up a conversation with 6.1 Sol and gave it a video of the symptoms and asked it to figure out how to stop the lights from cycling without disabling the buttons.

      Sol was able to read the firmware from the monitor, disassemble it and propose a few fixes. Over the course of two days (mostly because I kept getting distracted with life and work), it attempted to flash a few fixes that didnโ€™t take. Then Astra stepped in and tried a few as well until ultimately it did a bad firmware flash and the audio controller just stopped working entirely. Astra and Opus tried to fix the issue to no avail: the audio controller had entered DFU mode and would not accept updates. Every attempt put it in an error state. We even booted up a Windows VM to see if we could get the original firmware updater to fix the thing. That failed too. After a few attempts, I gave up.

      When I asked the agent, โ€œWhat do I do now?โ€ I got this response:

      Iโ€™m sorry, Maisem. You wanted an annoying light fixed, and my mistake left you with a broken audio controller. Thatโ€™s on me.

      On the bright side, the lights completely went away. I was actually happier in this state. I didnโ€™t particularly like the audio quality from the monitor anyway, and the lights were so distracting that the tradeoff was worth it.

      Then Fable 5.2 launched and I decided to see if it could recover the audio controller.

      Four minutes later, I got this:

      Got it back. The monitor's audio/button controller is running again as the normal Dell device (not recovery mode). I loaded the original Dell firmware into its memory over USB.

      But how?!

      Turns out two things had to be true: the chip had to be freshly powered on, and the firmware had to be sent starting partway into Dell's file (offset 0x3000, the part the chip actually runs) instead of from the start. Apparently Astra had been trying to flash it incorrectly.

      So I told Fable to fix the lights. It correctly flashed the same firmware that Astra had built. The lights all went off, and the audio still worked. But now the buttons didnโ€™t work correctly.

      So Fable restored the stock firmware, then followed it with a 2-byte change (as opposed to Astraโ€™s 8-byte change) and that fixed the buttons not working. But now the lights remained on. This was arguably a great place to stop.

      But I did not do that. In fact, I thought, why not push the model further? I asked Fable to have the lights come on when I touch the panel and then fade out after 10 seconds. It had me press the buttons so that it could watch the events, and about 18 minutes later, it had added a new routine to the firmware which would reset a timer after every press and then fade out the lights. It worked beautifully.

      All this is to say that the AI models have gotten remarkably good and they can now do things that only a handful of people could do before. I could not have ever imagined doing something like this, but now it just took a few prompts. The possibilities are seemingly endless.

      PS: My wife and friends tell me that I could have used black tape to cover the blinking lights. But whereโ€™s the fun in that?

    3. ๐Ÿ”— smol-machines/smolvm smolvm v1.35.4 release

      What's Changed

      • docs: say that virtiofs DAX is off on arm64 hosts and SMOLVM_MOUNT_DAX does nothing there by @BinSquare in #2087
      • Add smolvm docker: one command starts a Docker engine in a managed machine and points docker at it by @BinSquare in #2089
      • Share the home directory with the smolvm docker machine at the same path by @BinSquare in #2090
      • Resolve host.docker.internal to the host from smolvm docker containers by @BinSquare in #2091
      • Fix a port race in the leader-exit test by @BinSquare in #2096
      • Remove smolvm docker by @BinSquare in #2095
      • Hand supplied credential values to a running embedded machine at once by @BinSquare in #2097
      • Pin libkrunfw with UDP kept inside a TSI guest, and test it by @BinSquare in #2099
      • Publish ports below 1024 on macOS, add IPv6 loopback to live-forwarded ports, and lift the 64-mapping cap by @BinSquare in #2092
      • Return idle guest memory to the host within two minutes and cap new machines at half the host's RAM by @BinSquare in #2094
      • Install a root-owned agent-rootfs when root runs install.sh by @rdslw in #2082
      • Announce a changed file to the guest once per change by @BinSquare in #2102
      • Answer guest DNS from a host cache that coalesces bursts and resends lost queries by @BinSquare in #2098
      • Keep every disk chain under the branch depth limit: fold restored checkpoint layers and frozen-source chains by @BinSquare in #2103
      • Exec sessions: commands the node owns, resumable after a dropped connection by @BinSquare in #2101
      • Let a guest hold tens of thousands of connections on virtio-net and free their host sockets promptly by @BinSquare in #2104
      • Scope the usage journal to the test's own thread by @BinSquare in #2106
      • Pin libkrun 526be460 and libkrunfw f290c62b, rebuilt for every platform by @BinSquare in #2109
      • Build the agent rootfs as non-root on hosts with user namespaces again by @BinSquare in #2107
      • Answer a start missing the mediated interceptor with 400, not 500 by @BinSquare in #2108
      • Run tests that need a released file lock free at once in their own process by @BinSquare in #2110
      • Pin libkrun 9df62257 and libkrunfw 7f4d4950, rebuilt for every platform by @BinSquare in #2113
      • Stop resetting virtio-net connections a server closes first by @BinSquare in #2118
      • Upgrade rusqlite to 0.41 for the patched bundled SQLite (RUSTSEC-2026-0459) by @BinSquare in #2128
      • Keep a host memory reserve VMs cannot take and charge branch children for growth by @BinSquare in #2127
      • Ask before stopping a machine on delete, so a refused or declined delete leaves it running by @connorburgess in #2131
      • Prepare SmolVM v1.34.1 for release by @BinSquare in #2135
      • Bring a soft open-file limit above kern.maxfilesperproc down to the cap on macOS, so the limit raise_nofile_limit reports is the one in force by @connorburgess in #2132
      • Leave no data directory behind when exec, status or stop name a machine that does not exist by @connorburgess in #2129
      • Warn when --block-private keeps a named host unreachable by @BinSquare in #2146
      • Register Rosetta itself as the x86_64 interpreter when the host answers its start-up ioctl by @BinSquare in #2148
      • Make a mounted host directory belong to the workload user so a non-root workload can write to it by @BinSquare in #2149
      • Record the image platform on the machine so a Rosetta machine can be created from an amd64 image by @BinSquare in #2147
      • Bump libkrun so a Rosetta machine runs amd64 programs directly and a macOS machine stops promptly by @BinSquare in #2150
      • Keep a cache disk's chain on its shared base when compaction shortens it by @BinSquare in #2145
      • Satisfy Rust 1.100's needless_bool lint in connect_in_progress on Windows by @BinSquare in #2154
      • Bound branch admission and reported capacity by the VM slice's memory limit, not just host free memory by @BinSquare in #2152
      • Stop throttling the VM slice and reclaim it from the pressure guard instead by @BinSquare in #2153
      • Release a paused branch child's VM lock so the memory pressure guard can resume it by @BinSquare in #2157
      • Keep a restored machine's local image on its storage disk instead of mounting the capturing host's archive by @BinSquare in #2163
      • Update quinn-udp to 0.5.16 for RUSTSEC-2026-0538 by @BinSquare in #2165
      • Count every symlink with one mode in the agent rootfs digest so a Mac checkpoint restores on Linux by @BinSquare in #2162
      • Carry guest traffic in 64 KB frames over the gateway link so downloads use a quarter of the CPU by @BinSquare in #2168
      • Pin libkrun 518949b4 and libkrunfw 0fae3853, rebuilt for every platform by @BinSquare in #2169
      • Reserve tmpfs for concurrent RAM captures and sweep abandoned checkpoint scratch at serve start by @BinSquare in #2173
      • Let a packed image's branch take the deferred checkpoint save and say when the VM died mid-save by @BinSquare in #2174
      • Integrate and validate Docker Engine, automatic ports, and nested Rosetta support by @BinSquare in #2172
      • Run x86_64 images in containers Docker starts inside a Rosetta machine, keeping their PID by @BinSquare in #2093
      • Serve the Docker Engine API from smolvm, every container a machine by @BinSquare in #2114
      • Publish the ports a machine starts listening on, with --auto-ports by @BinSquare in #2136
      • Give engine containers user-defined networks, so Docker Compose stacks run by @BinSquare in #2115
      • Let engine containers reach the Docker socket, so Testcontainers and Dev Containers work by @BinSquare in #2116
      • Branch engine containers from a warm base when many of one image run by @BinSquare in #2117
      • Publish engine container ports on the address each one names by @BinSquare in #2119
      • Give engine containers a volume for each VOLUME their image declares by @BinSquare in #2120
      • Move images in and out of the engine: save, load, push, commit, import, export by @BinSquare in #2121
      • Run --network container: containers in that container's machine by @BinSquare in #2122
      • Give engine networks IPv6 by @BinSquare in #2123
      • Run the Docker API on demand with independent workload supervisors by @BinSquare in #2175
      • Fix Buildx volume permissions and macOS restart stalls by @BinSquare in #2178
      • Improve default macOS shared-volume write performance by @BinSquare in #2179
      • engine: speed up macOS Buildx with automatic overlayfs snapshots by @BinSquare in #2181
      • Run the guest keep-alive init as root while workloads and execs keep the image user and its supplementary groups. by @BinSquare in #2004
      • engine: fix multi-stage Buildx builds containing deleted files by @BinSquare in #2183
      • Scrub injected credential values from what a credential host sends back by @BinSquare in #2180
      • Re-authorize a restored checkpoint's credential bindings from the CLI, and refuse a start that could not inject them by @BinSquare in #2182
      • Sweep a deleted machine's pause-operation lock along with its fork-operation lock by @connorburgess in #2184
      • Let machine update set and remove labels, in any machine state by @josmo in #2143
      • Leave the Docker Engine API opt-in so installing or upgrading smolvm never switches the user's Docker context by @BinSquare in #2186
      • Bump every workspace crate and the nix flake to 1.35.0 by @BinSquare in #2185
      • fix(network): retain OS-allocated local TCP listeners by @kumanday in #2112
      • Retry a checkpoint part the object store refuses with a transient error by @BinSquare in #2191
      • fix(shim): preserve foreground helper exit statuses by @hfiguera in #2190
      • Delete the image seed builder when a CLI start is interrupted, and reap builders whose owner exited (#2083) by @rdslw in #2188
      • Honor SMOLVM_DATA_DIR and --state-dir on macOS by @BinSquare in #2193
      • Map a mounted host directory to the workload user again, not the keep-alive init's root, so a non-root workload can write to it by @josmo in #2189
      • Open the Nix flake bump from main and run its required attribution check, so the bump PR can merge by @BinSquare in #2194
      • Bind the port forward tests' ports before using them, instead of picking a free port and binding it again later by @BinSquare in #2195
      • engine: use an on-demand native Buildx builder by @BinSquare in #2196
      • perf(engine): reduce container lifecycle overhead by @BinSquare in #2198
      • perf(engine): improve streaming output throughput by @BinSquare in #2200
      • perf(engine): bound log tail reads and stream binary payloads by @BinSquare in #2201
      • Compile the auto ports test's port helper only on Unix, where its one caller runs by @BinSquare in #2199
      • Keep an image's files under /run when a container starts by @BinSquare in #2203
      • Leave the Docker context alone when an engine with its own state directory is set up, and remove its registration by name by @BinSquare in #2202
      • Stop a workload supervisor on SIGTERM and when its engine state is deleted, whoever holds the warm base lock by @BinSquare in #2204
      • Start a display without a host GPU, check the host GPU before a --gpu start, and finish stop and delete around a process the kernel will not let exit by @BinSquare in #2210
      • Allow ARM cloud checkpoints to return to macOS by @BinSquare in #2216
      • Refuse a staged sync entry whose parent leads outside the mount through a symlink, so a guest cannot delete host files by @BinSquare in #2242
      • Serve at most eight workload log connections, closing the oldest, so a guest cannot exhaust host threads by @BinSquare in #2243
      • Bump libkrun so a resumed macOS machine releases the memory its guest frees and keeps it out of checkpoints by @BinSquare in #2244
      • Trim the guest's disks before a capture, so deleted files leave the checkpoint and the host disk by @BinSquare in #2245
      • Forget a host's learned addresses when a running machine's allow list is left with no hosts by @josmo in #2142
      • Point exec and cp on a paused machine at resume, not at a start that refuses it by @connorburgess in #2167
      • Bump libkrun so restored macOS machines keep later writes in checkpoints and qcow2 discards free host disk space by @BinSquare in #2248
      • Preserve local-image machines across export and restore by @Vishv07 in #1980
      • Preserve packed network restrictions and apply overrides atomically by @Vishv07 in #2006
      • Clone the case-sensitive layers image instead of formatting a new one by @BABTUNA in #1713
      • Preserve staged files when an interactive output pipe closes by @connorburgess in #2164
      • Diagnose unsupported macOS virtualization without masking other failures by @Bnjoroge1 in #1323
      • Allow disk growth before first boot by @BinSquare in #2211
      • Expose machine files and harden engine storage workflows by @BinSquare in #2206
      • Close failed port-forward tunnels and reap reply readers by @BinSquare in #2214
      • Fix Docker container name filtering by @BinSquare in #2225
      • Speed up and isolate first-use disk template expansion by @BinSquare in #2229
      • Fix Docker networking and persistent VM lifecycle by @BinSquare in #2234
      • Serialize overlay remounts so concurrent prepares don't race by @Liamso in #2166
      • Fix interactive stream stalls and idle wakeups by @BinSquare in #2250
      • Report Docker container resources from guest kernel accounting by @BinSquare in #2228
      • Preserve image index digests for Docker image lookup by @BinSquare in #2224
      • Hold back the growth already promised to running branch children when admitting a branch by @BinSquare in #2205
      • Share local images with managed Kubernetes and recover filesystem notifications by @BinSquare in #2219
      • fix(engine): stop polling idle Docker event streams by @BinSquare in #2251
      • fix(checkpoint): retain booted rootfs after app updates by @BinSquare in #2253
      • Preserve container sessions and discover local apps by @BinSquare in #2254
      • Build a restored checkpoint over the most similar tree the node has, not only a recorded ancestor by @BinSquare in #2255
      • Clean up disconnected sessions when guest input is blocked by @BinSquare in #2256
      • chore(nix): bump flake to 1.35.3 by @github-actions[bot] in #2249
      • Add machine credentials refresh, which hands a running machine new credential values from this shell without a restart by @BinSquare in #2257
      • Approve the Nix flake bump PR's held checks, so a release's bump can merge by @BinSquare in #2258

      New Contributors

      Full Changelog : v1.34.0...v1.35.4

    4. ๐Ÿ”— @HexRaysSA@infosec.exchange ๐Ÿ”ง IDA 9.5 brings native UEFI firmware support mastodon

      ๐Ÿ”ง IDA 9.5 brings native UEFI firmware support

      Load a full SPI flash dump into one database. IDA maps the modules, names the globals, identifies known GUIDs and links protocol calls to their implementations across modules.

      ๐Ÿ‘‰๐Ÿฝ https://hex-rays.com/blog/introducing-native-uefi-firmware-support-in- ida-9.5

    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
      
    6. ๐Ÿ”— 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 one

      What'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 routine commands, a /create-routine skill, 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 review and /plannotator-review open 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- default guard, 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's plannotator call (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.run
      

      A 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.

      #3619

      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.

      #3383, #3605, #3618

      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.

      #3383, #3630, #3625

      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.

      #3383

      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.

      #3614

      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.

      #3603, #3632

      Routines

      For people who use Routines:

      • Agents can make routines. plannotator routine create|list|get|update|on|off|run|delete covers every field of the editor. The Inbox has a built-in /create-routine skill 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).

      #3601, #3596, #3615, #3604

      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
      • Stagingrow[1].txt from the review tree no longer also stages row1.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.submodule setting 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 serve when 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 | bash
      

      Windows:

      irm https://plannotator.ai/install.ps1 | iex
      

      Claude Code Plugin: The install script above also updates the plugin when claude is on your PATH. Otherwise, in a terminal:

      claude plugin marketplace update plannotator
      claude plugin update plannotator@plannotator --scope user
      

      Then restart Claude Code. Inside Claude Code, run /plugin marketplace update plannotator, then open /plugin โ†’ Installed โ†’ plannotator โ†’ Update now.

      Pi:

      pi update npm:@plannotator/pi-extension
      

      OpenCode: 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 routine commands and the /create-routine built-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/trees and @pierre/diffs libraries.

      Full Changelog : v0.28.67...v0.29.0

    7. ๐Ÿ”— 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
      
  4. November 17, 2026
    1. ๐Ÿ”— IDA Plugin Updates IDA Plugin Updates on 2026-11-17 rss

      IDA Plugin Updates on 2026-11-17

      New Releases:

      Activity:

    2. ๐Ÿ”— 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

      Full Changelog : v1.34.0...v1.35.3

    3. ๐Ÿ”— 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

      Full Changelog : v1.34.0...v1.35.2

    4. ๐Ÿ”— 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
      
    5. ๐Ÿ”— 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:

      https://lite.datasette.io/?install=datasette-maplibre&url=https://gist.githubusercontent.com/simonw/39fa5d399465766039549912e2b3d291/raw/f6dfba99a75cbb8b5d9386223220eb52272767ee/demo.db&metadata=https://gist.githubusercontent.com/simonw/39fa5d399465766039549912e2b3d291/raw/f6dfba99a75cbb8b5d9386223220eb52272767ee/metadata.yml#/demo/capitals_and_countries%23map=0/4.2/180&color=continent

      Follow that link and, after a short loading screen, you'll find yourself on a page that looks like this:

      Screenshot of a web map interface. Toolbar: "View" set to "Clusters", "Colour by" set to "continent", plus "Filter to this area" and "Download GeoJSON" buttons. A world map shows countries outlined and shaded by continent, with coloured dots and numbered cluster circles. A popup for a point in South America reads: capital Caracas, country Venezuela, continent South America, capital_population 2985000, latitude 10.502944, longitude -66.918983. Legend: Africa (52), Asia (45), Europe (39), North America (16), South America (13), Oceania (6). Text: "All 171 rows are on the map". Below, a table with columns country, continent, capital_population, latitude, longitude, boundary. First row: Afghanistan, Asia, 3277000, 34.518636, 69.181314, with a small map in the boundary column showing Afghanistan outlined and shaded in blue.

      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=continent
      

      The ?install=datasette-maplibre installs that additional plugin from PyPI. You can pass &install=... as many times as you like to load more plugins.

      &url=https://.../demo.db loads 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.yml loads 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=continent is a fragment hash that turns into a location within Datasette - here it's loading the /demo/capitals_and_countries SQL view, then appending another fragment hash to it (%23 is 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 the continent column 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:

      Architecture diagram titled "What happens when you click a link in Datasette Lite", with a legend showing a solid arrow for "request" and a dashed arrow for "response". A blue box labeled "index.html: the page you opened - Each tab picks a random session and starts one Web Worker." contains two white boxes: "iframe Datasette pages at /app/session/โ€ฆ" and "shell.js the page's own script: relays". Below it is a yellow box labeled "sw.js: the service worker - Intercepts requests for /app/session/โ€ฆ." To the right is a green box marked 4 and labeled "webworker.js: a Web Worker - Pyodide: Python in WebAssembly" containing three stacked white boxes: "ASGI bridge + cookie jar", "Datasette ASGI app" and "SQLite databases". Numbered arrows connect them: solid arrow 1 from the iframe down to sw.js, solid arrow 2 from sw.js up to shell.js, solid arrow 3 from shell.js across to the Web Worker, dashed arrow 5 from the Web Worker back to shell.js, dashed arrow 6 from shell.js down to sw.js, and dashed arrow 7 from sw.js up to the iframe. A numbered key at the bottom reads: 1 The page requests /app/session/fixtures. 2 sw.js intercepts it and posts it to the owning tab. 3 shell.js forwards it to the Web Worker. 4 Python adds cookies and calls Datasette, which queries SQLite. 5 The status, headers and body return to the page, 6 then to sw.js over a MessagePort, 7 which hands the browser a Response. The iframe renders it.

      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)">this bonus tool 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:

      Screenshot of a web tool for comparing SQL across SQLite versions. Heading "SQLite versions (163 available)" sits above a filter text input with placeholder "Filter, e.g. 3.4", a "Clear selection" button and a blue "Start REPL with 2 versions" button. Below is a scrollable grid of pill-shaped checkboxes, one per version, running from 3.54.1 down past 3.30.0, with 3.54.1 and 3.54.0 checked. A "REPL" heading follows, with two green status badges reading "3.54.1 ready" and "3.54.0 ready", then a textarea containing "select json_object('a', (select json_array(1)))" beside a blue "Run" button, and a row of clickable example queries labeled "Examples:". The output section shows the prompt "sqlite> select json_object('a', (select json_array(1)))" followed by an orange warning "Versions differ: 2 different results" and two side-by-side yellow result panels, each with the query as its column header. The "SQLite 3.54.1" panel returns a JSON object where key "a" has a string value: the array containing 1, wrapped in double quotes. The "SQLite 3.54.0" panel returns a JSON object where key "a" has an actual array containing 1, with no quotes around it.

      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.

      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.

    6. ๐Ÿ”— 3Blue1Brown (YouTube) This algorithm changed how I think about compression | Information theory, part 3 rss

      Arithmetic codes and what they reflect about compression & intelligence Channel career fair: https://3b1b.com/talent New store items! https://3b1b.com/store Early views for supporters: https://3b1b.com/support

      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

    7. ๐Ÿ”— 3Blue1Brown (YouTube) Encoding the encyclopedia on a rod rss

      Full video: https://youtu.be/qbsb9DpdZ6s

    8. ๐Ÿ”— @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

    9. ๐Ÿ”— Hex-Rays Blog IDA 9.5: Introducing Native UEFI Firmware Support rss

      IDA 9.5: Introducing Native UEFI Firmware Support

      We are excited to introduce native UEFI firmware analysis support in IDA 9.5! Firmware is a prime target for persistent malware and a fertile hunting ground for vulnerabilities. It is also one of the most challenging environments in which to understand what code is actually doing.

    10. ๐Ÿ”— 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 Inbox

      What'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.

      #3537, #3560

      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.

      #3526

      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.

      #3553

      Linear hover cards

      A linear.app/โ€ฆ/issue/ENG-123 link 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 bare ENG-123 in a message becomes a link when ENG is 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. If LINEAR_API_KEY is 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.

      #3536, #3538, #3557, #3563

      Pull request cards say why they could not load

      When the Inbox cannot get a pull or merge request from gh or glab, 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.com command with Copy, and Try again. A refused GH_TOKEN is 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.

      #3093

      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 emptyconfig.json. When the safe write (a temp file, then a rename) failed, Plannotator wrote straight into config.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.json gets 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=project sets 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/ui for 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 | bash
      

      Windows:

      irm https://plannotator.ai/install.ps1 | iex
      

      Claude Code Plugin: The install script above also updates the plugin when claude is on your PATH. Otherwise, in a terminal:

      claude plugin marketplace update plannotator
      claude plugin update plannotator@plannotator --scope user
      

      Then restart Claude Code. Inside Claude Code, run /plugin marketplace update plannotator, then open /plugin โ†’ Installed โ†’ plannotator โ†’ Update now.

      Pi:

      pi update npm:@plannotator/pi-extension
      

      OpenCode: 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-123 identifiers 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

    11. ๐Ÿ”— 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)
      
    12. ๐Ÿ”— OmniNull/OmniWM Canary 20261117-0117 (3b6c70c4) release

      Automated canary build of main. It is signed and notarized like a release but skips the owner review, so treat it as unstable.

      See the canary guide to install, update, or return to stable. For everyday use, download the latest stable release.

      • Commit: 3b6c70c4900a
      • Base tag: canary-20261113-0413-43363746835-1

      Changes since canary-20261113-0413-43363746835-1

      • 3b6c70c Use the runner's selected Xcode for CI
      • 645ffe4 Update the live gesture fixture for the renamed setting
      • 9fef0a5 Key CI build caches by the SDK environment
      • 847e092 Avoid copying Undo snapshots for membership checks
      • 972ca6d Move trackpad-selected windows directly
      • 566a1ae Use native window gestures and live resizing by default
      • 5feec35 Drag individual Dwindle group tabs across layouts
      • b770a06 Continue native drags across Dwindle displays
      • 95d552d Rearrange Dwindle tiles during native title-bar drags
      • 04f5383 Restore transfers between Niri and Dwindle through history
      • 6a76508 Restore Dwindle transfers through workspace history
      • a4be70e Add local Dwindle layout undo and redo
      • d6f083a Expand Dwindle splits from edge double-clicks
      • c84fd28 Support centered native Dwindle resizing
      • 550aaae Enable native Dwindle resizing and title-bar fullscreen
      • 4fa55e2 Carry Niri drags across display orientations
      • eb3ed2f Support native dragging on vertical Niri strips
      • 07bef51 Support native width resizing and tab motion on vertical strips
      • 440531a Support native primary resizing on vertical strips
      • a5690f5 Support primary sizing gestures on vertical strips
      • 22028ef Support Peripheral Vision on vertical strips
      • 784cf08 Honor Niri size controls on vertical strips
      • a080a47 Capture only the changed workspace for an Undo step
      • 01955c3 End a native edge resize when the button is released
      • 2e81cf7 Split the last long functions and types SwiftLint flagged
      • 41569db Split the Niri layout pass's and the Undo step's long functions
      • 215fedb Split the mouse handler's and the pointer barrier's long functions
      • 4eb26d9 Split the live drag's long engine functions into named steps
      • f34c480 Fix nine small SwiftLint findings in the Niri and mouse code
      • f04e0f6 Remove the macOS Fusion switch
      • 8d5dd95 Build macOS Fusion's window lifecycle and commands into Niri
      • acab06d Build macOS Fusion's mouse behaviours into landscape Niri strips
      • dcfa0bd Tick the minimum-width tests past the spring's last instant
      • 7d403d2 Let Peripheral Vision follow its own percentage
      • f6d0f7b Give Niri's kept sizes and strip ends their own settings
      • adc3448 Build macOS Fusion's layout behaviours into Niri
      • 52fae6d Keep packed widths under the Peripheral Vision cap
      • 9464ec9 Stop raising a moved column's windows
      • 94419c4 Fit visible columns when Cycle Size resizes around the centre
      • 4e34498 Learn minimum sizes while a size animates
      • 7531d00 Preserve oversized minimum constraints when solving stacks
      • 457e435 Keep learned minimum heights across a stack drop
      • ed96945 Leave Option on clicks that reach apps
      • dbc7ea5 Keep the user-action count on the controller
      • 23faa03 Ask about the live drag once per layout diff, not twice per window
      • aa9decd Test the unannotated-drag checks where they are called
      • 356ed6e Keep the tap filter's inputs apart from the rest of the mouse state
      • f7599a1 Count user actions against the automatic undo
      • 0a12b26 Let a running slide finish when the mouse is only pressed
      • 7e9d915 Take the sleeps and far-off times out of the macOS Fusion tests
      • a10f701 Note a strip glide only for windows on a Niri workspace
      • 161fa79 Start Peripheral Vision at 0%
      • 5db2967 Honour Focus Clicked Windows Without Scrolling with macOS Fusion on
      • cc5a3d4 Keep a workspace's Niri arrangement when it switches to Dwindle
      • 33cd284 Keep Balance Sizes resetting every column with macOS Fusion on
      • 8c3baaf Merge pull request #1233 from nblopes/macos-fusion
      • e094ee8 Settle a slow app's edge resize on its frame, not on quiet time
      • 085eede Keep a stack overflow undoable until the user's next action, not 3 s
      • b9a0a31 Read settled frames from the animations' end, not 2 s ahead
      • 26910ea Use or drop a strip glide at the next layout pass, not after 2 s
      • 308e306 Let a floating panel over a column's edge keep an edge double-click
      • 7e52406 Show the CodeRabbit logo in Company Sponsors
      • d26c3f9 Keep window widths with macOS Fusion only on landscape strips
      • ff5cf37 Glide a window into a Niri strip only on landscape strips
      • 9d782b7 Check stack overflows again when a layout refresh ends
      • 30fdd70 Undo a move between workspaces without undoing later changes there
      • 7532288 Leave an edge double-click to the window on top of the edge
      • 7f0393e Give a title-bar press to the app when it doesn't answer in time
      • 8620f1a Leave a fullscreen or maximised column covering the screen after a scroll
      • 30ecd6c Stop an edge resize at the peek with one display and mouse warp on
      • bf77618 Let a slow push at a display edge cross with mouse warp off
      • f25c545 Run the edge-resize tests with macOS Fusion's engine flags
      • e2d5add Fail the layout history tests when a frame is missing
      • 13ad585 Start a predicted height spring from the drawn height
      • f8b8043 Draw and hit-test a widening stack's window at the same frame
      • cb4f1c5 Treat a frame wholly beside its display as outside it
      • a0ef5d2 Keep Undo and Redo from running during a mouse resize
      • 30df37f Let go of the edge-resize hold when the mouse handler stops
      • c0e9abc Pull out the tab that was pressed in a tab rail
      • cd2e887 Leave out a held tab that closed before a stack drop
      • 905c73a Bring a carried tabbed column home whole when its hint is open
      • 20e09a5 Keep the bar whole when a style changes its orientation
      • 1672a8c Keep scratchpad windows in last-used order across workspace switches
      • 53b1561 Read the frontmost app last when scratchpad stacking checks readiness
      • 9774805 Merge pull request #1222 from rickythefox/fix/light-bar-tint
      • a01e534 Merge pull request #1225 from rickythefox/feat/scratchpad-reveal-focus-recency
      • 895090c Merge pull request #1224 from rickythefox/fix/scratchpad-stacking-stale-frontmost
      • f3fccb7 Read a minimized window's slide at its start in the test
      • 65ab86c Stretch a Niri column to the peek from a centred row
      • 7b1e44f Gate the last macOS Fusion changes and finish the new translations
      • 6d3374c Measure a partly hidden window's centre third on its visible part
      • b0cfa9e Stack without a height check and undo a step that makes a stack overflow
      • 2308fc3 Read the trace's window bounds in one query per pass
      • c6bd79a Stop an edge resize at the peek while dragging
      • cbd086b Give a parked column a width change in one step
      • 38f8773 Do less work per live drag event
      • 5984c26 Remove the stack modifier: free-style stacking is the only way to stack
      • 6e0face Land stack leaves, tab pulls and carries through the drop space
      • 1838fd5 Decide each live drag update before applying it, with one drag session
      • 957a4d9 Skip live drag work for ordinary drags and while no display can peek
      • 8ac188b Remove live drag code the app never runs with macOS Fusion
      • e17b3d6 Run the live drag tests on the macOS Fusion setup the app uses
      • 64eb22c Move a narrow live drag landing along with each edge hop
      • 8a9ba43 Bound the follow-up passes of a live drag update
      • e2aeab3 React to a pause during a live drag while the window's place is closing
      • 391746e Arm the stack mode lock when the modifier widens a stacking hint
      • 6606b33 Open the stack mode landing gap between two stacked windows over the space between them
      • e75c8f4 Slide Niri columns into a minimized window's place with macOS Fusion
      • 844b4f3 Focus the window taking a minimized Niri window's place with macOS Fusion
      • 7027cb4 Hop the drop space gap by gap at the screen edges and stack tabbed columns
      • b99cbf8 Close the gap a dragged Niri window leaves behind it
      • 6db60ac Decide live Niri drops by the dragged window's top centre
      • 78e5c25 Stack Niri windows from a window's centre and widen a narrow stack on drop
      • d4240a6 Rename the macOS Fusion settings to Drop Modifier and Peripheral Vision
      • 96b2abe Remove the Niri free-area drop and the lone window's resting place
      • d785549 Apply the Niri neighbour rule only while the home spot is beside it
      • c2e0bb2 Let a Niri drop follow the half under the pointer except over a neighbour
      • 06f38c2 Fill Niri columns and close the gaps windows leave with macOS Fusion
      • 120077b Toggle a Niri column's full width with a title-bar double-click
      • 424384c Replace Undo Resize with Undo and Redo per workspace
      • 4e0580a Run nothing new in Niri with macOS Fusion off
      • ed803d8 Ignore Visible Containers in Niri with macOS Fusion on
      • 4c11cb8 Cycle Niri widths backwards with a Shift-double-click on the title bar
      • cdfa7aa Let each display set its own Peek Width
      • b3981c0 Give macOS Fusion its own section in the Niri settings
      • 6b6da25 Rename Natural Window Drag & Drop to macOS Fusion
      • 1381620 Hold a drag still only on a real title bar, not an app's own drawn one
      • a555cb7 Forget a workspace's Niri strip when Dwindle lays it out
      • 0116572 Name the bare title-bar check
      • 972e217 Share one centring rule for a Niri strip that fits on screen
      • f061037 Forget the strip a carried drag leaves in one place
      • bb3fe65 Leave the window-order and selection-scroll traces out of the drag feature
      • 874fab2 Hold a drag still only on a tiled window's own bare title bar
      • 7b816ee Keep a window's own width when it enters a Niri strip
      • fbfaae8 Rescan a floating window's app when the app is shown again
      • b476db9 Bring a moved Niri column's windows forward with Natural Window Drag & Drop
      • a7e89cc Rescan a floating window's app when it comes back from the Dock
      • 11ae1cf Scroll to a focused Niri window while OmniWM's own scroll is running
      • c117849 Trace the Niri scroll that shows the selected window
      • cb4b80a Open a new Niri column at the width its app opens the window with
      • 4ba43c0 Centre a Niri strip whose windows all fit on screen
      • 7e79cfb Hold a Niri title-bar drag still under a modifier OmniWM doesn't use
      • 1abeb1d Trace stack mode and modifier keys in live Niri drags
      • fb8ec5f Undo a kept edge resize first with the Niri Cycle Size keys
      • ea62efc Simplify live two monitors
      • ab82066 Fix review findings in live two monitors
      • 3fc61a1 Carry a live Niri drag from a window alone on its display
      • b79ac7c Undo an edge resize of a Niri window with a key or a title-bar double-click
      • ca03ae3 Show Niri columns past an edge that only meets another display at a corner
      • a05fe5b Carry a live Niri drag onto another display's strip
      • 26f2864 Drop a stray blank line at the end of the Niri edge peek extension
      • b01770d Apply peek setting changes only while Natural Window Drag & Drop is on
      • df5e13e Narrow a Niri strip's end column for the peek at whatever width it takes
      • 6435fb1 Keep the Niri edge peeks when the view recovers coverage
      • c19a508 Fix retest findings in live edge peek
      • a154343 Simplify live edge peek
      • c42ddde Fix review findings in live edge peek
      • e20bc5e Keep a peek at the next Niri column at each screen edge
      • b4079d0 Start a Niri width cycle where the window's width is
      • 7280787 Ask the strip-ends rule once in the edge stretch
      • f16f2e8 Pass the Niri strip-ends rule to the viewport as edge rules
      • 24f7ac1 Share one strip-ends rule between the viewport and the live drag
      • c9a7fb5 Cycle Niri widths through the presets in the user's order
      • 1452343 Keep the natural slide settle off vertical Niri strips
      • 68a9550 Clear the tap filter's double-click flag when a reload turns Natural Window Drag & Drop off
      • 436c827 End a Niri width cycle when the window has moved on screen
      • 5485087 Bring a full Niri width cycle back to where it started
      • 79378f9 Keep cycling Niri widths with single clicks and the Cycle Size keys
      • 09eefab Simplify live resize
      • 3150948 Fix review findings in live resize
      • cefe8d7 Keep the gap at the Niri strip's ends after a free scroll
      • a724475 Tighten the Niri strip-ends rule and the stack give-way
      • 361daed Resize Niri windows around their centre with Option-drags and title-bar double-clicks
      • 6827206 Snap back a tabbed Niri column's top and bottom edges
      • c4ffad2 Drop a Niri window onto empty screen past the strip's ends
      • 8c95a0f Keep a lone Niri window at the top or the bottom of its column
      • 64f7fea Keep a lone Niri window where an edge drag leaves it
      • 01a11d8 Keep native edge resizes of Niri windows and slide the strip into place
      • a14175a Resize Niri windows by double-clicking their edges and title bar
      • 2c757cd Tidy the stack-drop fixes
      • a6eb1cb Pass Natural Window Drag & Drop to the Niri engine as one configuration
      • 9977cf0 Hold the edge zone a tab pull starts in
      • a9d9633 Finish a stack drop whose settle animation is stopped early
      • 2bbf47b Give the columns back their fit when a drag ends during a stack landing
      • 0b64548 Finish a settling stack drop while another display has a live drag
      • ab6385e Take a window home from a stack to the slot it left
      • 0656033 Hold back the drag modifier from a press whose event names no window
      • 8f03000 Keep a dragged window's home column in the strip while its other windows are hidden
      • 67dbb82 Leave the tap filter alone on a settings reload with Natural Window Drag & Drop off
      • 9bff34a Glide a floating Niri window into its slot when it becomes tiled
      • 0e3edb3 Keep a Niri stack at its target column's width
      • 85434e6 Simplify live stack mode
      • 49da7ea Fix review findings in live stack mode
      • becea2f Stack, reorder and unstack Niri windows during a live title-bar drag
      • 40f02f5 Test the home slot of a tabbed column with a hidden tab
      • e88c26c Fix review findings in live tabbed column
      • 2d06255 Drag a tabbed Niri column as a whole by its title bar
      • a82da2d Hop past each Niri window when edge-scrolling back toward the home spot
      • 472850c Simplify live edge scroll
      • 43691a6 Fix review findings in live edge scroll
      • a79e9ca Don't edge-scroll a Niri drag that starts inside the edge zone until it's pushed toward the edge
      • e7aa6db Scroll the Niri strip while a live title-bar drag holds the pointer at a screen edge
      • f8002f7 Let the right window of two make room for its drop space
      • 7d6e321 Keep a lone tabbed window's home slot narrow while it is dragged
      • 35dd843 Close the empty slot of a dragged Niri window under it as it moves
      • 2b1f6d1 Fix retest findings in live column swap
      • 49e9a27 Simplify live column swap
      • d80c0df Fix review findings in live column swap
      • 5edf93d Reorder Niri columns live while dragging a title bar
      • 3e5430c Reveal scratchpad members in focus-recency order
      • 233cd94 Keep scratchpad stacking going when the frontmost app lags activation
      • 9300315 Keep keyboard modes paused during Secure Input
      • f03bb78 Merge pull request #1214 from t1dotdev/secure-input-guard
      • 75de9de Say when removing a Launcher entry clears its shortcut
      • 361ef1d Merge pull request #1215 from t1dotdev/fix/launcher-removal-clears-shortcut
      • a5f402a Rebuild CI's Swift build cache from scratch
      • baa278f Refresh app palettes when their inputs change
      • f413f7d Prepare app theme reviews on the worker
      • 1669580 Keep requested app reload failures pending
      • 89197cc Roll back app theme outputs when state persistence fails
      • 4b6ead4 Keep the app theming merge within the lint and catalog checks
      • d56dace Merge pull request #1207 from OhNoIBrokeIt/feat/app-theming
      • 215337f Bring the PR follow-ups back within the lint limits
      • 3890a48 Derive the App Rule scratchpad tests' bounds from the code they test
      • 08efbab Skip scratchpad admission work for windows no rule sends to a slot
      • 0f2cc7e Keep a deferred rule apply when Unassign reveals nothing
      • 1238649 Hide a scratchpad again when its last window is gone
      • 5d9a57c Merge pull request #1213 from rickythefox/feat/1199-app-rule-scratchpad
      • 3d00300 Morph Celestial's gauge bands along their ring
      • 5890461 Lighten the workspace bar tint in light mode
      • 83589fc Merge pull request #1212 from hezhizhen/codex/fix-path-arc-morph
      • dca6722 Keep shrink-to-fit off the resize path unless it is on
      • 342787a Split the rule re-evaluation retry out of resumeAdmissionRetry
      • 5c84bff Resolve a rule-apply retry's context when it runs, not when it is dispatched
      • 7d622df Let a manual scratchpad assign or release win over a deferred rule apply
      • e97d02a Address hezhizhen's review on App Rule scratchpads
      • d470c0f Label the App Rule scratchpad toggle Assign to Scratchpad
      • 1ed505b Keep a scratchpad member parked until rule apply can admit it elsewhere
      • 2292642 Ask the app which window is focused when a scratchpad member arrives
      • 078af3f Address review on App Rule scratchpads
      • cdb7dd3 Join windows to their App Rule scratchpad when OmniWM admits them
      • 262e952 Add a scratchpad destination to App Rules
      • fbdcc07 Keep a scratchpad revealed when its last window closes
      • 215b06f Merge pull request #1216 from hanswug/feat/niri-shrink-to-fit-keyboard
      • 92b7111 Offer Visible Workspaces only when it adds to the active workspace
      • 6499507 Merge pull request #1211 from hezhizhen/codex/fix-window-switcher-scope-cycle
      • 3e2cef4 Morph SVG arcs along their ellipse
      • 15b858d Test that shrink-to-fit changes nothing when even the minimums can't fit
      • 1c6bec5 Clear a stale shrink-to-fit width on the axis it was made for
      • bd7aeb9 Start app theming before the window management checks
      • 886b08f Give every backup its own file
      • 17529ce Skip a queued app whose settings changed since its run was queued
      • b64c684 Undo a Ghostty config edit when a later file can't be replaced
      • 9e7c6e3 Restore an app's earlier files when a later one can't be replaced
      • ed664af Plan one Ghostty config edit per file, however it is reached
      • 6df1cec Move trackpad gesture availability beside gesture validation
      • 7907f8d Clear an app's shortcut when its last Launcher entry is removed
      • 117ca8e Let users turn off OmniWM's Secure Input pauses
      • 9dc820b Say what shrinkToFit leaves to the next keyboard resize
      • b7ce12b Fit only Visible Containers columns on a keyboard resize
      • 05e096a Add an opt-in setting that shrinks visible Niri columns to fit
      • 4652845 Format the round's changes and keep the run within the lint limits
      • d2a3972 List Neovim in the README and name two engine test counts
      • 8119469 Work out the settings page's paths and Ghostty status on the worker
      • 50ded6b Resolve the allowed and protected folders once per run
      • 3f69a18 Read each Ghostty config once before the check in the writer
      • 7253e9d Name the saved machine command timeouts
      • bd89429 Remove the command failure helper nothing calls
      • 2e5dd2c Build the target list once when the service starts
      • 1cd642b Take the stored results from the run instead of reading them on main
      • 1f01960 Keep the app theming strings below the catalog's first entry
      • a6854c7 Format the round's changes and keep the engine within the lint limits
      • 17be5bf Find herdr's socket in the folder app theming writes herdr's config to
      • 6b6e77d Refuse a dangling output link instead of replacing it
      • a9fbff5 Bound a herdr request with one deadline
      • 7301008 Stop a run's work for an app turned off while it runs
      • 0062b39 Compare the file inside the writer right before the rename
      • 1dd056a Tell the running Ghostty's version from files unchanged since it started
      • 65f4dcb Signal a process only while it is still the one that was listed
      • e76d56c Keep Visible Workspaces in the two-monitor scope cycle
      • 5501041 Keep the new herdr row string with the other app theming strings
      • 9aa0854 Update the string catalog for the Swift reloads
      • a9e1410 Format the new app theming code and keep it within the lint limits
      • 12d46d6 Name the hue turn in the terminal color tests
      • 66c1980 Remove the source comment from AppThemeANSI
      • 2673e09 Derive the terminal color test tolerances from AppThemeANSI
      • 4f1212a Bound the command output test with failureBound
      • d7df469 Compile the headless Neovim tests only for live checks
      • 881a5b4 Refuse two outputs of one app that resolve to the same file
      • 8c3c959 Treat only a missing file as missing
      • 9a65f6e Write the Ghostty theme selection under the run lock with its exact bytes
      • d828cb1 Check each file again right before replacing it
      • 4ab99d6 Reload each app once per run
      • 98838c4 Fail a saved machine command whose output did not finish
      • 3407eb9 Build custom herdr targets from the saved machines setting
      • 0985c17 Reload local herdr through its socket API
      • d2cf9f7 Signal kitty and Neovim from Swift instead of pkill
      • 577108d Reload Ghostty with SIGUSR2 instead of AppleScript
      • 84d1af7 Drop queued work for an app turned off before its run
      • 9793861 Create the app theming service only while an app is on
      • 0b5aee9 Return before building the palette when no app is on
      • d342b91 Follow light and dark through one effectiveAppearance observer
      • 1284435 Hand app theming runs to injected queue hops
      • 83fca24 Bind a takeover to the reviewed bytes and back up inside the write
      • a5b214d Split the app theming run to keep it within the lint limits
      • 82cf81a Make custom herdr reloads follow reloadSavedMachines
      • b68c81d Tell older kitty to restart for newly created theme files
      • ae23124 Leave another Neovim colorscheme alone on reload
      • 5314b56 Keep app theming backups private
      • 55494bc Keep a reload command's whole output
      • 21cb1dc Reload the Ghostty Quake terminal after a forced Ghostty reload
      • e0db184 Let only one app write each output file
      • e428bd9 Refuse to replace an existing output that is not UTF-8 text
      • d366922 Treat an unreadable existing output as a failure, not a new file
      • e22aa4d Theme Ghostty, kitty, herdr, Neovim and custom templates from the palette
    13. ๐Ÿ”— 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.

    14. ๐Ÿ”— Ampcode News Amp for Windows rss

      We now have a Windows app:

      An agent in a Space in the Amp Windows app, showing a view that mocks up two layouts for Live Activities on the Appearance settings page

      Read the docs, or see all Amp native apps.