🏡


  1. November 19, 2026
    1. 🔗 hacker news ida pro references New comment by linkregister in "LLM assisted reverse engineering" rss

      I wonder if Radare would work well with LLMs. I never had the patience to learn how to use it before good LLMs appeared. Ghidra's decompiler, Hopper's mach-O support, and IDA Pro's Windows symbols support were always good enough for me.

    2. 🔗 Works in Progress The trouble with serendipity rss

      Saloni Dattani explores accidental discoveries in history, and comes away learning that scientists ' lives were messier than she expected.

      This is a column: a lighter piece from the Works in Progress extended universe, designed to be enjoyed inprint. If you'd like to opt out of columns, or any other section, you can do so here.


      People love accidental discoveries. Penicillin's discovery by Alexander Fleming is a classic example. Fungal spores wafted in through an open window, fell onto a plate of bacterial colonies, and dissolved them. Another is Louis Pasteur's discovery of a chicken cholera vaccine, the second vaccine ever developed. After Pasteur left a broth overexposed to oxygen, it went stale. But he ran out of fresh broth, so used it anyway to study the effects of an infection, and found, surprisingly, that it protected the chickens. Or how about the discovery of X-rays? Wilhelm Rontgen was working with a cathode ray tube in a dark room when he suddenly noticed a screen glowing nearby, even though he'd wrapped the tube in cardboard.

      Subscribe now

      Though they're great stories, I've come to believe none of them happened that way. Rontgen had his notes burned after his death, and the story is just a hypothesis. Pasteur was extremely secretive as well, and forbade his family from making his notes and letters public after his death. His grandson, however, did, and after poring over their contents, historians have found that the key experiments were done deliberately by Pasteur's then-assistant Émile Roux while Pasteur was away for his daughter's wedding.

      And what about Fleming? His first paper describing penicillin in 1929 never says where the spores came from. Of course, it's hard to see how he could have known, given they would have been microscopic. But Fleming first told the window story in an interview in 1945, sixteen years after his first report, and his colleagues testified the window was 'seldom if ever opened'. They weren't able to replicate the discovery as he described, either: penicillin would have needed to be present on the plate before the bacteria grew, because it blocks bacteria from building their cell walls, rather than killing them once they've grown.

      Subscribe to print

      Several people have tried to work out what really happened. Fleming's would-be biographer Ronald Hare made dozens of attempts and found just one reliable way to reproduce the discovery that fit the facts. The spores, he argues, were an unusually productive strain; came from the lab of a fungal researcher on the floor below, rather than the window; settled on the plate roughly when Fleming seeded it with bacteria; Fleming forgot to incubate it; and all this happened during a cold spell in the summer that let the mold grow before the bacteria. Hare noted how much more serendipitous this sequence of events was: 'the odds against the occurrence of the phenomenon become almost astronomical', though he ultimately believed it. While writing this column, I read through many of his notes and letters archived at the Wellcome Library and have come to agree with his view: Hare was exceedingly careful in corroborating the events from multiple people and sources from the time.

      Part of the reason I find the popular stories fascinating is because it's jarring to realize how little they're based on. I do expect some stories of accidental discovery will survive the test of time. In medicine, for example, it's fairly common to test a drug for one disease and find, unexpectedly, that it works for another: colchicine was used for centuries to treat gout before it was found effective against cardiovascular disease, and sildenafil (Viagra) was being tested for angina when its more famous effect was noticed. Side effects are difficult to predict.

      Subscribe now

      But I wonder why the popular versions have survived so long. Maybe they're more enjoyable? They're certainly easier to recount than the other explanations, which are convoluted. A fungal spore floating through an open window to reveal a world-changing antibiotic is a far better dinner party story than a meandering one involving several more coincidences you've probably already forgotten. Or the stories make scientists feel just like us: anyone can stumble upon a discovery, and then the challenge is merely to... spend years turning it into something useful?

      'Chance favors only the prepared mind', as Pasteur put it. I think there's something to it: the brilliance of these scientists isn't necessarily in their initial discoveries, but in seeing their potential and doing something with them. Edward Jenner, for example, wasn't the first to notice that cowpox infections protected against smallpox, but he documented it thoroughly and popularized the method, spreading smallpox vaccination worldwide.

      But what bothers me is that calling these discoveries accidents is sometimes the opposite of reality. Pasteur and Roux, for example, carried out hundreds of experiments to find reliable methods to create new vaccines - the popular framing is actively misleading and diminishes their work.

      My friend Niko McCarty recently dug into other famously serendipitous discoveries in biology, such as those of green fluorescent protein and nanopore sequencing, and explained they came from systematic trial and error. He also describes the idea of 'engineered serendipity': in optogenetics, for example, 'the key breakthrough came about because the inventors wrote down the exact requirements they were looking for [...] and then enumerated , or wrote down, all the ways they could possibly imagine to make this happen'. It makes me wonder if learning how they really happened could help understand how to make more discoveries systematically.

      Yet I'm still left with questions. Why credit chance events instead of hard work? Why hide or burn your notebooks?

      Messiness, mistakes, and privacy come to mind. But here's another theory: competition and rivalry. Gerald Geison, a historian of Pasteur, suggests the method he ultimately used to develop chicken cholera vaccines was 'remarkably simple' and could be applied to other diseases too: 'had he revealed immediately the method of attenuation through exposure to ordinary air, Pasteur might have faced a host of competitors in the search for other vaccines'. Pasteur was probably the best-paid scientist in France at the time, and sold his inventions commercially. His secrecy might have been rational: patents weren't allowed on medicines in France then, so keeping the method secret would have helped him maintain his monopoly on producing them. Pasteur was so cagey that he didn't allow his collaborators to take notes, took his notebooks with him when he traveled, and published his methods (without much detail) only months after announcing his discoveries.

      Subscribe to print

      Meanwhile, Wilhelm Rontgen, who discovered X-rays and had his notes burned after his death, had been in a long dispute with another scientist, Philipp Lenard. Lenard had spent years researching cathode rays before him, and shared his methods and discharge tube with Rontgen. Once Rontgen became famous, Lenard accused him of having robbed him of the discovery. That dispute, historians suggest, could have motivated the note- burning, but it's hard to know without being able to read them. (Incidentally, Émile Roux, too, had his notes burned periodically, and it's only because Pasteur's were released that we know what happened at all.)

      Science seems like it should be above the messiness. It's an institution we've built to guard against our biases. But it's also just people - who forget, hide their notebooks from their colleagues, burn their papers, and spend years fighting over who deserves credit. It's shaped by rivalries, incentives, obsessions, and years of unglamorous work, most of which is forgotten. That, to me, makes it far more interesting than a story about an open window.


      Saloni Dattani is an editor at Works in Progress.

    3. 🔗 hacker news ida pro references New comment by TuxSH in "LLM assisted reverse engineering" rss

      Don't use REA, you can just use IDA MCP (HexRaysSA/ida-mcp) with IDA Pro.

      Ask it to create an IDB from the binary, then ask a broad question like "reverse engineer the entire binary" or "reverse engineer the [whatever] subsystem"

    4. 🔗 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

    5. 🔗 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.

    6. 🔗 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!

    7. 🔗 Console.dev newsletter Sponsor: Coresignal rss

      Agentic B2B search for builders

      Visit Coresignal

    8. 🔗 @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!

    9. 🔗 anthropics/claude-code v2.1.328 release

      What's changed

      • Added auto mode for Claude Opus 4.6 and Sonnet 4.6 on Amazon Bedrock, Google Cloud's Agent Platform, Microsoft Foundry and Claude apps gateway; interactive sessions with no permission mode start in it
      • Added "onFailure": "block" for mcp_tool hooks, as for command and HTTP hooks: a hook whose call fails blocks the action
      • Added a warning when a message from a session that skips permission prompts may be held and dropped by a cloud session
      • Added a notice in /status and claude doctor when an OpenTelemetry exporter has no endpoint and its data would likely be lost
      • Added CLAUDE_CODE_DISABLE_DEFERRED_TOOL_RESUME, which lets a host stop claude -p --resume and --continue from running a tool call that a hook deferred
      • Added support for apps that embed Claude Code to switch on the policy plugin's allowManagedModsOnly option; an admin's managed settings still win
      • Added a startup warning to the Claude apps gateway when a policy's maxEffortLevel is not a valid effort level
      • Self-hosted runner: Added --repository-folder to name the folder that sessions use for a repository at --capacity 1, in place of its path under the base folder, which can't be a symbolic link
      • Self-hosted runner: Added a start-up warning when the host's settings.json sets a default permission mode that sessions ignore
      • Self-hosted runner: Added --hook-label to claude self-hosted-runner orchestrator, to hand chosen session labels to the spawn-runner hook
      • Self-hosted runner: Added --metadata key=value to claude --environment, to label a session for the spawn-runner hook
      • Self-hosted runner: Added claude_code_self_hosted_orchestrator_session_queue_wait_by_reason_seconds to the orchestrator's /metrics, so a re-opened session's wait can be told from a new one's
      • Self-hosted runner: Added an orchestrator metric, claude_code_self_hosted_orchestrator_sessions_given_up_total, that counts by cause how often Anthropic gave up starting a runner for a session
      • Fixed Bash commands in zsh stopping with a "not found" error at a word that starts with =, such as echo ==== or [ a == b ]; =cmd no longer expands to a command's path
      • Fixed automatic compaction reusing the session's earlier system prompt instead of rebuilding it the way /compact does
      • Fixed markdown rendering freezing on some very long or malformed input
      • Fixed rare screen freezes
      • Fixed Esc often being lost at a permission prompt or question when you typed straight after it; in terminals that send Alt as Esc and a key, an unused Alt or Option key now declines there
      • Fixed a paste or a terminal's reply being typed into the prompt when a slow connection cut it in two
      • Fixed saving a scheduled task erasing the project's other saved tasks when the scheduled tasks file can't be read, on third-party providers or with telemetry or feature flags turned off
      • Fixed a scheduled task with a typo in the project's scheduled tasks file being deleted the next time that file was saved
      • Fixed a case where a resumed cloud session could lose its compaction summary or recent messages when a message was saved late
      • Fixed the token counts on the spinner and for subagents counting a retried reply twice, missing replies that were not streamed, and standing still while Claude thinks
      • Fixed the error shown when usage credits run out mid-response, which named a rate limit
      • Fixed auto mode failing every turn outside Claude Desktop with CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS set behind a gateway rejecting betas, on Bedrock, Agent Platform, Foundry or Claude apps gateway
      • Fixed CLAUDE_STREAM_IDLE_TIMEOUT_MS not lengthening the 5-minute connection limit on gateways, custom base URLs and cloud providers
      • Fixed some Claude Desktop sessions on third-party providers, other than scheduled tasks, ending for good with "Prompt is too long" after large tool results; the largest are now left out
      • Fixed MCP tools whose input schema starts with anyOf, oneOf or allOf going missing on third-party providers or with telemetry or feature flags turned off
      • Fixed an MCP tool with an invalid input schema failing requests on third-party providers or with telemetry or feature flags turned off; the tool is now left out and Claude is told why
      • Fixed effort being turned off for a subagent's model for the session if Bedrock, Google Cloud's Agent Platform or Foundry refused its progress summary's effort setting (regression in 2.1.327)
      • Fixed Code Mode stopping a script when a permission prompt outside auto or bypass mode, a plan approval or a question stayed open for ten minutes
      • Fixed Code Mode scripts in auto and bypass-permissions modes failing to call an MCP server that had connected while the previous script was running
      • Fixed Code Mode scripts not running in the background in auto or bypass permissions mode in a session chosen in the claude --resume picker
      • Fixed Code Mode losing a loaded skill, hook context or a note typed with a permission approval when resuming a session in which one reply ran several scripts
      • Fixed Claude not being told that a Code Mode script was cut off when the session was resumed from the picker or in a mode that asks for permission
      • Fixed Code Mode silently using undefined for top-level variables that an earlier failed script never set
      • Fixed Code Mode scripts not being told when a failing command's long output was cut
      • Fixed Code Mode refusing valid scripts that start with a { block
      • Fixed Code Mode refusing scripts that use both a top-level await and a top-level return
      • Fixed an @-mentioned small file not being attached in Code Mode after a script had read or written it
      • Fixed Code Mode offering write() and edit() to read-only subagents that can't call them
      • Fixed Claude starting a turn by itself in Code Mode when Esc was followed by a command such as /model
      • Fixed Claude in Code Mode not being told to run workflows only when you ask, or the workflow size you set in /config
      • Fixed Remote Control repeating the same disconnect message, and telling you to retry a session that can't reconnect
      • Fixed a waiting permission prompt being lost, and its answer ignored, when a remote session restarted while the service was slow
      • Fixed cloud sessions resuming a cleared conversation after a rewind followed by /clear
      • Fixed a remote session losing a turn's tool calls and results when its runner or worker was lost after a dropped model stream had been retried
      • Fixed cloud and Remote Control sessions that just started, or have an @ in their title, being unreachable in cross-session messaging from a session with Remote Control on
      • Fixed Claude being told that cloud sessions can never reply; it now learns when a reply can come and how else to get the result
      • Fixed /diff, the Changes pane of Remote Control sessions and the diff beside an edit leaving out committed work after a command moved into another repository
      • Fixed Remote Control not showing a running workflow's agents when a session run by an IDE extension or other SDK app is opened over an hour after the workflow last made progress
      • Remote Control: Fixed an idle Desktop or VS Code session showing as running after Remote Control is turned on
      • Fixed the model saying background agents were still running after an SDK interrupt had stopped them
      • Fixed Send now in the desktop app and SDK hosts telling Claude that a stopped web search found no results
      • Fixed Cmd+letter being typed into the prompt in terminals that report Cmd
      • Fixed Ctrl+click opening a link twice in GNOME Terminal, side mouse buttons acting as clicks, and the first wheel notch in the other direction being ignored after a pause, in fullscreen mode
      • Fixed Shift+Enter in Konsole outside tmux and ssh, and Alt shortcuts on non-Latin keyboard layouts in terminals that speak the kitty keyboard protocol
      • Linux: Fixed pasting in other apps freezing while Claude Code is suspended with Ctrl+Z, when xclip or wl-copy is installed
      • Linux: Fixed Ctrl+V missing the clipboard image, pasting an old one or hanging
      • Fixed text copied in fullscreen mode including the quote bar, losing spaces at line wraps when a drag scrolled upward, or missing words under the "Jump to bottom" pill
      • Fixed an image path pasted into a ! command becoming an attachment
      • Fixed Ctrl+C showing no exit warning while the ? shortcuts list is open
      • Fixed Ctrl+R search in fullscreen mode and the /theme color editor picking the wrong row when keys arrive together, and keys being dropped there and in the search of /config and /plugin
      • Fixed wrong or missing colors inside GNU screen
      • Fixed many background notifications cutting into the top border of open dialogs in fullscreen mode
      • Fixed a message to a background agent showing a long file path in place of a pasted image
      • Fixed /goal removing a skill's Stop hook, or ending early on another hook's result, when both had the same wording
      • Fixed /bug saying cancelled after the report was sent
      • Fixed Esc not dismissing the transcript share question for Pro and Max users
      • Fixed /hooks losing your place when going back
      • Fixed /export writing a file named .txt when the name was left empty
      • Fixed /terminal-setup in Zed replacing a symlinked keymap.json with a plain file
      • Fixed /install-github-app adding a code review workflow when asked to update the existing workflow file
      • Fixed /plugin reopening a skill, or closing the open page, when a slow save or removal finished after you went back
      • Fixed /plugin asking to uninstall the wrong plugin, or ignoring Esc, after leaving a plugin while a change was still running
      • Fixed typing and arrow keys not working on the /plugin Installed tab after a search with no results or a click on the tab row
      • Fixed holding Enter in /plugin turning off several installed plugins
      • Fixed the /usage plugin total stopping at 2,000 tokens on 1M context models, and low token estimates in /usage and /plugin when no model is picked
      • Fixed Esc on the Bedrock access keys step closing /login instead of going back
      • Fixed /exit and Ctrl+D describing running work differently, and /exit warning about a workflow that had stopped
      • Fixed Claude calling an artifact private after reading one in a shared folder or publishing to another organization's, and saying only named people can open one when its folder's people can too
      • Fixed a plugin's toast sometimes showing another plugin's text
      • Fixed a mod saved just after a turn began sometimes reloading mid-turn instead of at the turn's end
      • Fixed one malformed OTEL_RESOURCE_ATTRIBUTES entry dropping the variable's other labels from metric points, events, and spans. Now only that entry is left off
      • Fixed agent hooks running past their timeout while compacting after a request was refused as too large
      • Fixed a crash at startup when FORCE_COLOR is set to a negative number
      • Fixed a crash in secret masking when the machine is almost out of memory
      • Fixed the Bash sandbox on Linux renaming .git/HEAD after each command when the branch name is not valid UTF-8
      • Self-hosted runner: Fixed all running sessions being stopped when a proxy or web filter answered a poll with HTTP 200 and a body such as {}; the runner now retries such a poll
      • Self-hosted runner: Fixed deletion of a kept clone's objects or refs, and of commits that existed only there, after a temporary disk error; that start now fails instead
      • Fixed self-hosted runners stopping when their token ran out on a host whose clock is slow or was set back
      • Self-hosted runner: Fixed sessions with Anthropic-managed git losing git access to GitHub after a script or hook in the session ran claude again
      • Fixed self-hosted runners with Anthropic-managed git being unable to fetch or push where the machine's git config sets http.proactiveAuth
      • Self-hosted runner: Fixed a runner that exited without telling the server when setup failed after it had registered; it now deregisters with a reason, and an on-demand runner reports the failed start
      • Self-hosted runner: Fixed archiving or requeueing a session not taking effect while it waited for another session to prepare the same repository (--capacity above 1)
      • Self-hosted runner: Fixed a session with a damaged .claude.json failing every later start under --trust-workspace false; it now starts on defaults, with MCP servers turned off there on again
      • Self-hosted runner: Fixed a failed start's message losing the words that say what failed when a checkout hook or git printed a lot
      • Fixed the self-hosted runner skipping its post-session hook when a disk stalled for a few seconds; on a dead disk a session's end can take 25 seconds longer by default
      • Fixed self-hosted runners: a session that resumes in a new Claude config directory no longer loses its task list
      • Fixed Claude not being told when a self-hosted session starts without one of its repositories, and why
      • Self-hosted runner: Fixed --correlation-id of claude --environment not reaching the spawn-runner hook
      • Fixed the self-hosted runner setup wizard's key rotation advice, which now warns that revoking a key stops the sessions running under it
      • Improved claude -p and SDK sessions to fetch managed-settings plugins that have their own git repository, in the background, for a later session
      • Improved how soon managed-settings plugins from a git marketplace load on a fresh machine in claude -p, SDK and Claude Desktop sessions; a short run may exit up to 30 seconds later
      • Improved the time to resume large sessions
      • Improved memory use when resuming a session with many images
      • Improved memory use and response time in long SDK and desktop sessions that run slow commands or tools
      • Improved Code Mode's speed in auto and bypass-permissions modes by removing a 0.75 second pause after most scripts
      • Improved prompt caching for new Code Mode sessions that have MCP servers, and Claude is now told when a server is still connecting and when the list of servers changes
      • Improved Code Mode's token use with shorter tool descriptions
      • Improved Code Mode to show the command a script is running, and its output, while it runs
      • Improved Code Mode edits: an edit that changes nothing no longer stops a script, and Claude is told where a failed edit matches or comes closest
      • Improved Code Mode: Claude is now told which tool calls were still running when a script failed
      • Improved how Claude starts dev servers in Code Mode's auto and bypass modes: Claude is told to run them as background tasks that show in /tasks
      • Windows: Improved Code Mode by telling Claude that scripts' shell commands run in Git Bash and that PowerShell aliases run instead of functions with the same name
      • Improved starting several in-process teammates at once: far fewer now fail with "Lock file is already being held"
      • Improved the computer use approval dialog: it now shows each app's level of access and plainer warnings
      • Improved cross-session messaging: Claude now explains that Remote Control is off when a cloud session or another computer is not listed
      • Improved claude -p text output to say on stderr when a message from another session is held or dropped, and how to allow it
      • Improved Claude's answers on who can open an artifact it published: Claude is now told to check the artifact again instead of repeating the last publish's answer
      • Improved resumed self-hosted runner sessions: Claude now checks whether its earlier work is still there, and says what is missing
      • Changed plan mode and Bash prompts for Opus 4.6 and Sonnet 4.6 on third-party providers to use and offer auto mode, as on newer models; disableAutoMode turns both off
      • Changed Code Mode to no longer run UserPromptSubmit hooks, managed ones included, on scripts' output; to redact that output, use a PostToolUse hook with updatedToolOutput
      • Changed /code-review on most models to report only bugs and CLAUDE.md violations; run /simplify for reuse, simplification and efficiency cleanups
      • Changed /code-review to mark each finding Important, Pre-existing or Nit on most models, and to end each summary with a suggested fix; a clean review's list now reads "Code review found no issues."
      • Changed deniedMcpServers entries of the form claude.ai <name> to apply to that connector in cloud and self-hosted runner sessions too
      • Changed managed PostToolUse hooks to no longer fire for calls refused before they ran: no log entry, rewrite, block or stop there; PostToolBatch gets most, not marked as refused
      • Changed /bug to ask Yes or No before sending, so repeated Enters no longer send a report or open GitHub
      • Changed subagents in claude -p, the Agent SDK, desktop and VS Code to wait for their own subagents by default when CLAUDE_CODE_FORK_SUBAGENT=0 is set
      • Changed claude -p with CLAUDE_CODE_FORK_SUBAGENT=0 to count a background subagent and those it waits for against one 10-minute wait; raise CLAUDE_CODE_PRINT_BG_WAIT_CEILING_MS for longer chains
      • Changed a shell command rewritten by a PermissionRequest hook to a sandbox-excluded command to run outside the sandbox
      • Changed the Claude in Chrome welcome screen and /chrome to say that Claude Code asks before Claude acts on a site, unless your permission mode or a rule in /permissions answers
      • Changed Claude Desktop and Agent SDK sessions on third-party providers or with telemetry or feature flags off to end the turn when closed with a question open, instead of continuing without an answer
      • Changed pasted text to be marked for Claude as pasted, on third-party providers or with telemetry or feature flags turned off
      • Changed subagent progress summaries in terminal sessions on the Anthropic API to be written by the default small fast model from short notes, also with telemetry off, using far fewer tokens
      • Changed how a sandbox that can't start is reported, unless sandbox.failIfUnavailable is set: the next sandboxed Bash command is refused and says that the sandbox is off for the session
      • Changed /list-agents to show its list to you alone; Claude lists sessions itself when needed
      • Self-hosted runner: Changed the built-in gh api to be off by default where settings guard Claude's GitHub tools by name; --use-anthropic-gh true turns it on
      • Self-hosted runner: Changed a claude that a wrapper script runs before the session's own claude is up, or after it has ended, to have no Anthropic-managed git
      • Self-hosted runner: Changed CLAUDE_RUNNER_SESSION_UUID and CLAUDE_CODE_REMOTE_SESSION_UUID to both be set for the session and its checkout, post-session and spawn-runner hooks
      • Changed self-hosted runners at --capacity 1 to refuse a session earlier when the path of a repository it pushes to is a symbolic link
      • [VSCode] Added a notice when a message from another session is held, with a link to the settings file that can allow it
      • [VSCode] Fixed the permission prompt cutting off its No button, reply field or title when the panel is low or a command, URL or description is long
      • [VSCode] Fixed failed or blocked tool calls showing no reason or a reason cut short, and Glob and Grep counting an error as results
    10. 🔗 hacker news ida pro references New comment by teravor in "LLM assisted reverse engineering" rss

      for LLMs, IDA Pro works better than Ghidra in my experience.

      you can also steer the LLM into doing tedious but correct things like injecting code, hijacking functions, intercepting data etc to gain an understanding of what's going on if straight up disassembly doesn't appear to be going in the right direction.

      have the LLM periodically write reports on all its findings and then wipe the context and reset this time with the report at hand.

  2. November 18, 2026
    1. 🔗 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?

    2. 🔗 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

    3. 🔗 @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

    4. 🔗 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
      
    5. 🔗 backnotprop/plannotator v0.29.0 release

      Follow @plannotator on X for updates

      Missed recent releases? Release | Highlights
      ---|---
      v0.28.67 | Drag threads to Priority, Archive or Quiet, or onto another thread to combine them, mention another thread in your reply, Linear hover cards, pick any tag colour, a linked computer's pictures and files open here, pull request cards say why they could not load
      v0.28.66 | Pick several threads and archive or snooze them at once, combine picked threads into one; Tidy follows your own words, rows take their tag's colour; filter and search by tag, files an agent's message names open beside the thread, swipe rows on phone or iPad; list can show archived threads, Antigravity and Orca use the Inbox; T3 Codex threads get replies, Open in lists JetBrains IDEs, Routines: run a saved prompt on a schedule
      v0.28.65 | Take back a reply your agent has not received yet, over Tailscale, Plannotator opens only for your own account, tag a linked machine's threads; one tag across machines, T3 Code threads get the Inbox with no setup, long threads open on slow connections
      v0.28.64 | Installs and updates download a smaller, compressed copy, a Videos filter on the Artifacts page, GitLab comments on a whole file get their own thread, pull request pictures and videos show in the Inbox
      v0.28.63 | Pair Grok Bot and other cloud agents from Settings, Hermes Agent, OpenClaw and Muse Code can use the Inbox, add a thread to Priority to keep it on top, tag threads, and find each tag in the sidebar, Pull requests board as a table, with bulk Merge
      v0.28.62 | Agents started from the Inbox now work on Windows, pick a model and effort when you start an agent, rules for your agents, written in your own words, post a thread's decisions on its pull request, the Inbox loads faster on a slow connection
      v0.28.61 | Updates now update the Claude Code plugin too, an agent's chosen face shows on every icon of it, filter the Inbox list by pull request state, Modern dark shows section bands and the Reply button, one conversation no longer shows as two agents
      v0.28.60 | Click a word to highlight it, a one-time Themes dialog, Settings → Rows rebuilt, tell your agent how you want your rows, starred threads as pills above the list, a pill for new messages out of view, a half-circle face picker with ten Glass colours, a new phone sidebar and reply box
      v0.28.59 | A quieter Agents section in the sidebar, machine names only when agents run on more than one machine, agent icons that are always gently alive and lean toward your pointer
      v0.28.58 | Start Codex from New message, an Agents section in the sidebar, start an agent in a folder on any drive, play audio attachments and comment at a moment, Claude Code's Plannotator tools work on Windows
      v0.28.57 | Pin artifacts, and see every artifact on one page, filter the list by project, date or agent, a thread shows its pull requests and their state, choose what the sidebar shows, and in what order, Ask AI starts from Side in the selection bar
      v0.28.56 | Questions can show trade-offs and a prototype to try, a thread with many big pictures no longer crashes the tab, Escape closes New message and keeps your draft, read threads stop being bold and keep their place, agent messages that name no thread start a new 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

    6. 🔗 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
      
  3. 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. 🔗 anthropics/claude-code v2.1.327 release

      What's changed

      • Added a confirmation before /install-github-app changes a repository
      • Added claude mcp add-json <name> - to read the server's JSON from stdin, so tokens can stay off the command line; not available inside a Claude Code session
      • Added a line when a resumed session's earlier messages can't be loaded
      • Added a list in /status of broken agent, skill, command and output style files, keybinding errors, an unavailable sandbox, ignored permission settings and hook matchers that never match
      • Added a note in /config when other settings override a row
      • Added x-claude-code-managed-settings-checksum to the gateway hint headers; sent where managed settings set CLAUDE_CODE_GATEWAY_HINT_HEADERS=1, including where they already do
      • Added support for naming a session's billing group with the attributionProject setting, for Claude apps gateways that set admin.billing_group_tag
      • Added /tui classic as the name for the non-fullscreen renderer; /tui default still works
      • Remote Control: Fixed stopping the server in worktree mode deleting a running session's git-ignored files, such as .env
      • Fixed self-hosted runners with --use-anthropic-git-proxy deleting a non-empty directory named by GIT_CONFIG_GLOBAL at startup: the runner now keeps it, ignores the variable and warns
      • Fixed claude mcp add and claude mcp remove with project scope deleting other top-level keys from .mcp.json, such as $schema or another tool's servers
      • Fixed /export overwriting an existing file without asking: the dialog now asks, and /export <name> keeps the file and says to run /export
      • Fixed a command you had allowed still running after you pressed Stop, when the approval arrived after a restart, in cloud and self-hosted runner sessions with no feature flags loaded
      • Fixed Enter closing /teleport's load error screen
      • Fixed a click followed by Enter in /plugin installing or disabling a plugin
      • Fixed a half-typed ! command running on an extra Enter after the usage limit menu
      • Fixed some --disallowedTools rules with parentheses in their content
      • Fixed auto mode ignoring some wildcard PowerShell allow rules that name a script with .\, such as PowerShell(.\scripts\build.ps1 *)
      • Fixed a running Code Mode script in auto mode getting permission prompts and denials once Claude started a second script that auto mode also allowed
      • Changed some pre-started background sessions to be discarded after an account change
      • Changed a workflow paused at a usage limit in the terminal to stay paused after a login, until the earlier login returns or you type a prompt
      • Fixed a nested claude with its own token being refused by forceLoginOrgUUID: commands that don't get the session's token no longer get its CLAUDE_CODE_OAUTH_SCOPES; set it on any that need it
      • Fixed headless sessions losing stored messages on resume when a message was sent again with the same UUID after the process was killed
      • Fixed cases where a session resumed after an empty reply or a killed command lost an answer, or brought back a rewound prompt, after another crash or a move to the background
      • Fixed a remote session forgetting messages sent after Stop was pressed during a restart, if Claude Code then crashed
      • Fixed tasks created after /clear being lost, and cleared tasks coming back, when a cloud or self-hosted runner session with no feature flags loaded resumed later
      • Fixed a compaction right after a reply cut at the output token limit losing that reply's tool call and its result
      • Fixed a settings change from /config and similar commands failing to save with no warning; a line under the prompt now says so
      • Fixed /rewind closing without a word when some files could not be restored
      • Fixed pasted images being dropped when the prompt starts with a file path such as /tmp/a.txt
      • Fixed agents passed with --agents being lost once plugins loaded or reloaded
      • Fixed a plugin's agent being dropped when resuming a session from the --resume picker
      • Fixed Claude Code refusing to start when https_proxy or HTTPS_PROXY is a bare host:port and neither its input nor its output is a terminal (the desktop app, an SDK, cron)
      • Fixed Claude Code on Linux sometimes returning to the shell while restarting itself at startup, such as after the first sign-in to a Claude apps gateway or when turning on Code Mode
      • Fixed claude -p hanging before its first request when the fetch of a model's settings stalled, such as at a proxy; it now goes on without them after 10 seconds
      • Fixed the screen staying blank or frozen after a brief out-of-memory error
      • Fixed a rare display fault that could freeze the screen or end the session
      • Fixed cloud sessions breaking when a program left thousands of connections open to the session's network proxy
      • Fixed a turn hanging when a mod's $.model.complete or $.model.classify call met a usage limit: the call now gets the API's error at once; mods should handle that error
      • Fixed stalls on a compaction reply with thousands of unclosed tags and on some very long WebFetch URLs; WebFetch now refuses a URL over 2,000 characters before any permission prompt
      • Fixed a message with thousands of @ mentions stalling before Claude replies; only the first 100 mentions are now looked up as files
      • Fixed the prompt freezing after rejecting a write to a very large file; a rejected write now shows a short preview
      • Fixed a crash when a burst of keys reached the search box in /plugin
      • Fixed a false crash report and exit code when a suspended session resumes, or at exit, where a Linux security policy blocks a process from signalling itself
      • Fixed remote MCP servers staying disconnected after a longer outage such as a VPN drop: most servers on other machines reached by hostname over https are now retried in the background for about a day
      • Fixed Edit refusing with "File has not been read yet" after a compaction on unchanged files outside the project that Claude had already read in full
      • Fixed Grep repeating or skipping results when paging with head_limit and offset; content and count results are now sorted by file path
      • Fixed Read failing on Jupyter notebooks that contain an output of an unknown type
      • Fixed NotebookEdit removing the notebook file's final newline
      • Fixed the Read tool reporting 512KB instead of the real size when a file of 10 MB or more is too large to read at once
      • Fixed the Bash tool's diff of changed files not naming files that are binary, too large or too many to show
      • Fixed artifact publishes failing with "the source file changed between approval and publish" when a synced or remote-backed folder had only changed the file's timestamp
      • Fixed a new artifact that you approved being refused in a cloud scheduled task's session, in organizations that require approval of each new artifact
      • Fixed a new artifact being refused after an app built on the Agent SDK approved it, in organizations that require approval of each new artifact
      • Fixed /artifacts showing part of your list, or "No artifacts yet", when a request for more of the list failed: it now tries again, then warns if it can't load the whole list
      • Fixed in-process agent teammates on a different model from the lead compacting at the lead's context limit and on the wrong model; they now use their own limit and model, at that model's rate
      • Fixed a finished subagent resuming on the model and effort of a sibling subagent that messaged it
      • Fixed the main conversation not being told a background agent had finished when the subagent that started it ended by itself without reading the result, outside auto mode
      • Fixed Claude reporting a background agent as still running when it had waited 30 seconds or more on a permission prompt in the desktop app, on the web and in the SDK
      • Fixed Claude not being told in auto mode when a background agent's reply to a follow-up message was dropped, and reduced repeat wake-ups there from agents waiting on background commands
      • Fixed the desktop app, Claude Code on the web and VS Code showing a raw task notification as a subagent's prompt after its background task woke it
      • Fixed messages sent from another session with "later" priority joining the running turn, instead of waiting for it to end, in Remote Control and Claude Desktop sessions
      • Fixed messages to cloud and Remote Control sessions being reported as failed with a stale address after a timeout or rate limit; Claude now says when a message may have arrived
      • Fixed cloud sessions giving no error when a UserPromptSubmit hook blocks a message sent while Claude works
      • Fixed failing hooks showing nothing: SubagentStop in background agents, SessionEnd at /clear and /resume, and CwdChanged and FileChanged in fullscreen
      • Fixed a Stop hook that failed to run being shown as having reported a problem
      • Fixed focus view keeping a finished reply hidden while a Stop hook was running
      • Fixed Claude getting a long managed PostToolUse hook output twice when a mod added context to the tool call
      • Fixed /model listing the wrong models in some terminal sessions when a project's .claude/settings.json sets ANTHROPIC_BASE_URL to an LLM gateway
      • Fixed /statusline writing to ~/.claude/settings.json when CLAUDE_CONFIG_DIR points to another folder
      • Fixed claudeMdExcludes patterns on Windows not matching a path whose drive letter is written in the other case
      • Fixed claude agents and claude rm refusing to remove a fully pushed session ("The worktree has unpushed commits") when its worktree has a file or folder named HEAD at the top level
      • Fixed long ListAgents results hiding most sessions on accounts with many cloud or Remote Control sessions: long lists now come in pages
      • Fixed slow turns in resumed sessions for organizations with tens of thousands of connector tool permissions
      • Self-hosted runner: Fixed claude -p started by a session's script or hook waiting out rate limits, because it inherited the session's own retry setting
      • Fixed the spend limit menu reporting a changed limit when the server refused it
      • Fixed a second x on a task's details in /tasks stopping the next task too
      • Fixed Esc being ignored on a permission prompt that had just appeared
      • Fixed lists that load their rows late sometimes ignoring Enter and the arrow keys
      • Fixed /autofix-pr holding the keyboard after Esc while it stopped the cloud session; the dialog now closes at once, and a stop that fails is reported afterwards with a link
      • Fixed a blank screen and stray mouse codes in the shell after quitting with ctrl+c just after ← opens the agents view
      • Fixed Ctrl+C right after the trust question leaving the terminal in fullscreen
      • Fixed the shell flashing on screen when ← opens the agents view in fullscreen mode
      • Fixed terminal display faults: most scrambled scrollback in Ghostty on resize, link addresses hidden in Windows Terminal under old tmux and in VTE 0.50.0, and no selection highlight with 16 colors
      • Fixed some garbled rows in tmux with allow-passthrough on inside kitty, Ghostty or iTerm2
      • Fixed /mcp saying no servers were configured after one was added during a session or declined; it now says what to do
      • Fixed /hooks leaving out hooks given by --settings
      • Fixed the / menu listing a row for each skill of the same name, though every row ran the first
      • Fixed /teleport showing no message when the chosen session failed to resume
      • Fixed n and N in transcript search skipping matches
      • Fixed cancelling a transcript search (ctrl+o, then /) in a long session landing far from where the search started
      • Fixed up and down losing the cursor's column over a short or blank line
      • Fixed Tab in shell mode filling in a file name after &&, ; or |, where a command goes
      • Fixed the selected session leaving the screen in claude --resume and /resume when branch names or folder paths are long
      • Fixed the MCP tool list in /mcp and /plugin losing your place when going back from a tool
      • Fixed /resume listing one session fewer than the window has room for, and a 'Resend your message' hint after most spend caps, where resending can't help
      • Fixed an MCP server's long question being cut off after one row, text fields hiding long pastes with no sign, and a doubled divider line in /plugin's options and /login's Bedrock and Vertex steps
      • Fixed the "+N lines" count being too high for command output with links or colors, and the transcript's ? help hiding how to exit in a short window
      • Fixed Ctrl+C twice not closing /chrome from its browser list
      • Fixed a number and Enter typed too early at an agent's plan approval in screen reader mode causing the next number to be dropped too
      • Fixed Claude trying to read design system token files that do not exist when starting a deck or design
      • Fixed exit not saying that a worktree was kept
      • Fixed /hooks help naming input fields that do not exist
      • Fixed question dialogs naming ctrl+g after the external editor key was rebound
      • Fixed two sign-in error messages that pointed to the Claude subscription option on computers where forceLoginMethod is set to console
      • Fixed /config saying the dialog was dismissed instead of "Set theme to …" after changing the theme
      • Bug fixes and reliability improvements
      • Improved the speed of a session's first Bash command: shell start-up files may now run before it's approved, even if it's refused; set CLAUDE_CODE_DISABLE_SHELL_HEAD_START=1 to turn this off
      • Improved commits on newer models and in PowerShell: Claude is now told not to commit files that likely contain secrets
      • Improved sandboxed shell commands: Claude now sees when a command exempt from the sandbox stayed in it because its permission check relied on the sandbox
      • Improved the refusal for shell commands with no rm that the dangerous rm check can't parse, so Claude can resend harmless ones in plain syntax instead of giving up
      • Improved resuming very long sessions: a transcript read that ends early is now retried once, so messages are lost less often
      • Improved subagent answers that hit the output token limit twice: they now more often come back whole or say up front that they are partial
      • Improved long replies on unrecognized models: a reply cut at 32,000 output tokens now continues with a limit of 128,000
      • Improved the reminder about a completed subagent after compaction: if Claude can't read the agent's output file, it is now told to ask the agent with SendMessage
      • Improved the warning shown when an API key and an Anthropic profile are both set: it now says which one is in use and how to switch to the profile
      • Improved /plugin: the question before removing a marketplace now says that its plugins' settings and saved data are deleted, and a marketplace's page no longer shows another marketplace's error
      • Windows: Improved start-up time with no Git Bash and no pwsh on PATH by checking PowerShell's standard install locations at once; System32's powershell.exe now wins over one earlier on PATH
      • Improved startup time on Windows when PATH points to Git for Windows' bin folder, by starting git.exe directly instead of through its launcher
      • Windows: Improved PowerShell tool speed by up to about half a second per command
      • Improved how soon the Bash tool's diff of changed files is ready in auto and bypass permissions modes
      • Improved speed of the Bash permission check on very deeply nested missing paths on macOS and Linux, and of secret masking on very long text with a URL
      • Improved transcript search to find text in edits and written files
      • Improved speed of reading large PNG images, and the quality of the JPEG sent in their place
      • Improved the Artifact tool to read an uploaded file by the address the artifact's page shows; other forms still fail, most with a message that says to read uploads one per call, by id
      • Improved the Artifact tool to ignore prompt, limit and label on some calls that do not use them instead of failing the call
      • Improved MCP server pages in /mcp: local, remote and agent servers share one layout, menus end in Back, and actions are no longer numbered outside screen reader mode; use the arrow keys and Enter
      • Improved narrow terminals: /status, forms and detail screens lay out better, /model and /effort fit at about 40 columns, and key hints such as ←/→ to adjust stay
      • Improved /install-github-app: the repository, secret and API key steps use the standard list and keys, with shorter messages, a spinner and clearer errors
      • Improved /desktop: the download question is a standard list instead of y/n
      • Changed ExitWorktree to ask before removing a worktree that may hold unsaved work; refused in don't-ask mode or with nobody to answer, unless an allow rule, auto or bypass permissions mode allows it
      • Changed claude mcp add --scope project to stop, instead of overwriting the file, when .mcp.json lists its servers at the top level with no mcpServers key
      • Changed the arrow keys on most permission prompts to stop at No instead of wrapping around; a number past the last answer moves to No
      • Changed path checks to refuse some symbolic links
      • Changed what counts as inside a working directory, so some paths now ask for permission
      • Changed permissions.blockReadsOutsideWorkingDirectories to ask about more Bash commands in bypass and auto modes, and to deny some in auto mode
      • Changed permissions.blockReadsOutsideWorkingDirectories to refuse more Bash commands that name a path under a Read or Edit deny rule, where it used to ask
      • Changed auto mode's notice about falling back to billed classifier requests to say that an upcoming release removes the fallback; each action it would have checked will be asked about or denied
      • Changed auto mode to ignore more allow rules that run any package, like Bash(pnpm dlx *), and path or version forms of ones it already ignored (/usr/bin/npm run:*); the safety check decides those
      • Changed /sandbox and most /config value lists to be unnumbered outside screen reader mode; use the arrow keys and Enter
      • Changed Bash commands whose variables expand to very long text to be denied, with a message that says to use shorter values or a file
      • Changed the PowerShell tool to ask before one more command, even under a rule naming it; if nothing answers, it's refused unless a whole-tool rule, auto mode or bypass permissions mode allows it
      • Changed a subagent resumed by a sibling's message to follow the session's permission settings; it may now ask, or be refused where nobody can answer
      • Changed --worktree with a relative --add-dir beside the launch folder to give the Bash sandbox that folder, not one beside the worktree
      • Changed some --worktree starts with a relative --add-dir above the launch folder, such as .., to give the Bash sandbox, and a --bg session, only the worktree
      • Changed Claude in Chrome to refuse uploading some credential files; attach those to the page yourself
      • Changed artifact approval in organizations that require it for each new artifact: an artifact that only a plugin created or allowed can be refused
      • Changed sessions with nobody to ask to refuse a new artifact at once, with no permission prompt, in organizations that require approval of each one
      • Changed the Artifact tool to refuse calls once settings turn Artifacts off, in sessions already running too
      • Changed the Artifact publish prompt to stop offering "don't ask again" in subagents and after a background task result, someone else's message or a compaction
      • Changed claude plugin eval to keep its deny rules over a plugin's permission hook, and to flag calls the hook let through
      • Changed MCP server logs to record the mode, action, and field names of elicitation requests and hook answers, not their full contents
      • Changed most prompts to ignore answers other than Esc for a moment after resuming with fg
      • Changed Code Mode to no longer refuse to start when an installed mod hooks tool calls; an administrator can still keep Code Mode off in managed settings
      • Changed subagents launched without a model to stay on the model they started on when resumed, including after /model
      • Changed the first subagent on a model to wait up to 1.5 seconds (10 in claude -p) for that model's settings from Anthropic, instead of starting without them
      • Changed restarted background subagents, and turns that start by themselves, to wait for plugins to load
      • Changed prompt history to leave out most launch prompts of sessions that another Claude Code session started, such as claude --bg run by Claude
      • Changed subagent progress summaries in terminal sessions on Amazon Bedrock, Google Vertex AI and Microsoft Foundry to be written from short notes, not the whole conversation, using far fewer tokens
      • Changed non-interactive (-p) mode to run fewer git commands before the first request
      • Changed first-run setup to skip terminal setup in remote VS Code, Cursor and Devin Desktop sessions, where it cannot change settings
      • Changed fullscreen text selection to leave out the glyph of system, thinking and inbound message lines
      • Changed Anthropic-hosted cloud sessions to ignore more of a repository's flag and plugin delivery settings; its CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC now acts at most as DISABLE_TELEMETRY
      • [VSCode] Added "Claude Code: Add to Chat" to the Explorer's right-click menu, which @-mentions the selected files and folders in the chat
      • [VSCode] Fixed the permission prompt not showing the reason that a PreToolUse hook gives when it asks for confirmation (#85950)
      • [VSCode] Fixed long tool and file names being cut off in a permission prompt's title
      • [VSCode] Fixed a terminal session's diff showing the previous proposed edit after you typed in it and Claude edited the same file again
      • [VSCode] Fixed Escape also stopping Claude's response when it closes the feedback or "Build a custom style" dialog, the @-mention menu, the model, mode or "+" menu, or another popup
      • [VSCode] Improved speed when Claude makes several edits in a row: queued edits share one wait for new problems; a problem may be reported with a later edit
      • [VSCode] Improved @-mention file search speed in large workspaces when rg is on your PATH; results now rank much as in the terminal, with less tolerance for typos
      • [VSCode] Improved startup: the model picker is ready at once in folders opened for the first time, empty windows and worktrees, except on third-party providers
      • [VSCode] Changed a chat edit's diff to stay open and keep asking for approval when a terminal session in the same window sends a prompt
      • [VSCode] Removed unused tools from the IDE connection (openFile, saveDocument, getOpenEditors and related)
    3. 🔗 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

    4. 🔗 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

    5. 🔗 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
      
    6. 🔗 Simon Willison Running the full server-side Datasette Python app in the browser with service workers and Pyodide rss

      Datasette Lite is my port of the Datasette Python application to run directly in the browser using WebAssembly and Pyodide. I've released a complete rewrite of Datasette Lite using service workers, and it's now almost indistinguishable from the real server-side application.

      You can now do all of the following, using a carefully crafted URL to lite.datasette.io:

      • Load client-side Datasette to browse any SQLite database, JSON file, CSV file or SQL script
      • Select a released version of Datasette to load from PyPI
      • Load a specific commit, tag, or branch name from the Datasette GitHub repository
      • Pick from over 100 versions of SQLite to use with Datasette
      • Install additional Datasette plugins from PyPI or URLs to wheel files, including JavaScript visualization tools

      The ability to load specific Datasette references, plugins, and SQLite versions makes this a fantastic tool for linking to demos of work-in-progress features or bug reproductions, without needing to spin up a full web server to serve that demo.

      As an example, consider the following URL:

      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: This system started life back in May as an AI research spike generated using Claude Opus 4.8. It wasn't until November (and Claude Fable 5.2) that I felt familiar enough with how it all works to confidently ship it to production! Bonus feature: pick your version of SQLite I added this feature last night as an off-shoot of investigating a potential bug in SQLite. Datasette is meant to work against any released version of SQLite since 3.25 (released in September 2018). There have been 87 further releases since then. Being able to fire up Datasette against a specific version of SQLite is really useful for demonstrating new SQLite features and debugging weird issues. In the past I've used various tricks to get different SQLite versions running with Python on my Mac, but it's not a trivial process. WebAssembly is perfect for this. I can load up a custom SQLite build entirely in my browser, test it there, then discard it when I close my tab. datasette/pysqlite3-wasm-wheels is my new repository which contains WebAssembly compiled Python wheels for pysqlite3 for 163 different SQLite versions. Each version gets a file with a name like this: pysqlite3-0.6.2-3.54.1-cp314-cp314-pyemscripten_2026_0_wasm32.whl That's for SQLite 3.54.1, the most recent version. Datasette Lite now takes a special ?sqlite= URL parameter, which will accept a version number like 3.54.1, resolve the path to the corresponding wheel file, then fetch that wheel and install it into the Pyodide environment and configure Datasette to use it. Once I'd built the wheels, I decided to have Claude Fable 5.2 build me ">https://datasette.github.io/pysqlite3-wasm-wheels/?versions=3.54.1,3.54.0&sql=select+json_object(%27a%27%2C+(select+json_array(1%29%29%29) for comparing a SQL query across any selected versions of SQLite. Here's an example showing how select json_object('a', (select json_array(1))) differs between SQLite 3.54.0 and 3.54.1: This should work for every other Python app, too

      Nothing about how Datasette Lite works is unique to Datasette. Almost any Python application should be able to pull the same trick - running entirely in the browser using WebAssembly and Pyodide, as a cheap way to provide preview environments, demonstrate features, and recreate bugs.

      C and Rust extensions used to be a blocker for this kind of thing, but any good coding agent can compile those to Pyodide-compatible WebAssembly now. You can even publish them to PyPI as of PEP 783 in April 2026.

      One catch is databases. SQLite is no problem at all, but running PostgreSQL or MySQL in WebAssembly, while possible, is still a path less trodden.

      I'd love to see WebAssembly preview environments like these become a common pattern across the Python ecosystem.

      For Hacker News: Full server-side Datasette Python app in the browser with service workers

      You are only seeing the long-form articles from my blog. Subscribe to /atom/everything/ to get all of my posts, or take a look at my other subscription options.

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

    8. 🔗 3Blue1Brown (YouTube) Encoding the encyclopedia on a rod rss

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

    9. 🔗 @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

    10. 🔗 Works in Progress How should armies fight? rss

      This is a column: a lighter piece from the Works in Progress extended universe, designed to be enjoyed inprint. If you'd like to opt out of columns, or any other section, you can do so here.


      Occasionally a book gets the next war right. In 1937, Heinz Guderian argued in Achtung - Panzer! that tanks should concentrate in armored formations, that those formations were best controlled by radio, and that their purpose was to break through enemy lines and fight beyond them. In 1940, Guderian used a German tank corps to punch through French defenses and trap almost two million Allied soldiers.

      Jack Watling may have written another book like that. Watling, a British military analyst who works closely with the Ukrainian general staff, published The Arms of the Future in 2023. It argues that three forces define war today: the reach of sensors, the range of weapons, and the precision of munitions. All three are improving and have made the way armies previously fought impossible.

      Sensors come in many forms. They include cameras mounted on consumer drones, commercial satellites and ground surveillance radars. Some listen: an acoustic sensor carried by a single soldier can identify a tank from ten kilometers away. Others use lasers to detect heartbeats or electronic emissions to locate a soldier making a phone call.

      Once the sensors have found a target, modern munitions can destroy it from much further away. Eighty years ago, heavy artillery firing at sixteen kilometers missed by an average of fifty meters. In tests today, heavy artillery firing at seventy kilometers misses by an average of just two meters. Other weapons like rocket artillery and kamikaze drones regularly hit targets at twice that range.

      This is a problem for the way modern militaries, including Western ones, fight. Generals try to combine surprise and concentration: secretly assembling a large group of soldiers and tanks and quickly overpowering the enemy. But both are impossible if a radar operator can spot vehicles assembling from fifty kilometers away and artillerymen start hitting them minutes later.

      Already, grouping vehicles in Ukraine within a few tens of kilometers of the front line often gets them destroyed. As sensors and munitions improve, this 'gray zone' keeps growing, reaching far into what used to be the rear. The countryside, traditionally the place where generals like to maneuver, has become extremely dangerous: any concentration of forces is detected and then destroyed from a distance. How, then, should armies fight?

      The first option soldiers have is to make themselves not worth shooting. They can do this by dispersing and hardening - digging deep holes and sitting in them. This is a great tactic when defending, but ensures that any attack they mount will be piecemeal and bloody.

      Their second option is to withdraw to the places where cameras cannot see them and shells struggle to kill them: cities. To the modern soldier, the urban environment is like a warren of tunnels, full of shelters that preserve mobility. They require specialized troops to attack, and even then, fighting is difficult. But an army that ignores the countryside will soon find itself surrounded and cut off, and sitting in a city doesn't solve the problem of attacking the enemy.

      Their third option, and Watling's preference, is to try to restore movement and surprise by fighting the sensors themselves. The ideal army of the future combines small groups of highly mobile soldiers that target enemy sensors and deploy their own with heavy artillery that support them from further back and specialized assault units that fight over cities and other strongpoints. The hope is not to revive the long offensives of Guderian's tanks but to create a brief window in which troops can assemble and take a single objective without being spotted and destroyed.

      The Arms of the Future came out three years ago. Since then, the war in Ukraine has evolved along the lines Watling predicted. Most Ukrainian soldiers live underground, sometimes for months at a time and hundreds of meters from the nearest friendly unit. They avoid movement whenever possible and, when forced to hold ground, prefer towns and cities, as they did at Pokrovsk and Kostyantynivka. A Ukrainian battalion commander tells Watling: 'I don't need reinforcements, I need buildings to fight from.' The attacking Russians, who have no holes to sit in, no cities to shelter in, and can neither concentrate nor achieve surprise, are suffering astonishing losses.

      That doesn't mean successful attacks have become entirely impossible. Some Ukrainian units, like the Third Assault Brigade, are learning to fight as Watling would want, targeting enemy sensors before grouping together and rushing forward. These attacks appear to be working, and may keep the battlefield moving for a while. But they will succeed only as long as they manage to keep blinding the enemy. If the cameras keep improving and the shells keep flying, that too may stop being an option.


      Pieter Garicano is an editor at Works in Progress.

      Subscribe now

    11. 🔗 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.

    12. 🔗 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

    13. 🔗 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)
      
    14. 🔗 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.

    15. 🔗 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.

  4. November 16, 2026
    1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-11-16 rss

      IDA Plugin Updates on 2026-11-16

      Activity:

    2. 🔗 anthropics/claude-code v2.1.326 release

      What's changed

      • Added support for turning on Code Mode while agent teams are enabled; if you already turned it on, sessions with teams on now start in Code Mode
      • Added a startup warning when an --allowedTools, --disallowedTools or --tools value has an entry that doesn't look like a complete rule
      • Added a message explaining why MCP servers stop loading when an administrator adds managed-mcp.json during a session
      • Added a row to /status that says when your provider or an environment variable such as DISABLE_TELEMETRY turns features off
      • Added a note in /plugin and claude plugin list when a malformed plugin.json field such as author or homepage is ignored
      • Added Ctrl+O to show hidden startup notices
      • Added a hint in the empty prompt that says what to do after a request fails
      • Added an esc to stop footer hint in a subagent's view where Esc would stop it
      • Added OTEL_RESOURCE_INCLUDE_HOST to include host.name and host.id in OpenTelemetry resource attributes (off by default)
      • Added overflowX="scroll" on a mod's Box, and maxLines and wrap="clip" on its Text
      • Fixed cp of a file being refused when only its source was covered by an Edit deny rule
      • Fixed Bash commands that delete or overwrite files (find -delete, cat a > b, sort -o) being summed up in the transcript as a search or a read
      • Fixed a misleading "Dangerous rm operation" warning in the Bash permission prompt on some commands with no rm that Claude Code can't read reliably
      • Fixed background sessions losing the LLM gateway your shell exported after a crash, after a reopen from another folder, or when the background service lacks it: they now stop before any model request
      • Fixed the background service ending your own processes, such as an SSH login, when a process number on its list had been reused by another user's process
      • Fixed rules added in /permissions or at a main-conversation tool prompt, and /add-dir folders, looking saved when the settings file couldn't be written; the terminal now warns and names it
      • Fixed a failed MCP headersHelper, or one not run in an untrusted folder, making other sessions start without that server, for most servers with no stored OAuth refresh token
      • Fixed managed settings with certain key names stopping Claude Code from starting or affecting other managed files
      • Fixed settings files with values nested thousands of levels deep crashing Claude Code or applying only some of the time; values past 64 levels are now dropped with a warning
      • Fixed a settings file saved with an error mid-session being skipped silently; a warning now names the file
      • Fixed the subagent model set in managed settings not applying in Claude Desktop's Code tab; it now overrides your own, as in a terminal, unless those settings also pick a provider or gateway
      • Fixed sandboxed commands failing to start on Linux when the home or config directory is reached through a symlink into /net and sandbox settings deny reads of it
      • Fixed empty placeholder files, including .git/config.lock, sometimes being left in the project on Linux when Claude Code was stopped during a sandboxed command
      • Fixed Up then Enter answering Yes at the folder trust prompt shown under an already trusted parent folder
      • Fixed an extra Enter at the end of setup accepting the offer to make auto mode the default
      • Fixed a message typed over the startup auto mode offer being lost, and its Enter accepting the offer
      • Fixed a note typed on a permission prompt being sent to Claude after Tab had hidden it
      • Fixed PreToolUse hooks in managed settings leaving no OpenTelemetry tool_decision event or permission_denials entry when they refused a direct tool call
      • Fixed letters typed over /sandbox or a delete question in /permissions moving the selection
      • Fixed resumed sessions losing recent turns after a crash when the previous turn ended with an empty reply
      • Fixed resumed sessions losing earlier conversation history when Claude Code ran low on memory
      • Fixed a re-sent file overwriting Claude's changed copy in Remote Control and cloud sessions on Linux with no feature flags loaded: the copy moves to a .kept- folder, or the new file isn't saved
      • Fixed a background session being killed and its request lost when you opened, stopped or removed the older session whose conversation it had resumed
      • Fixed claude purge hiding its prompts when stdout is redirected, where one unseen Enter could delete a project's data; they now show on the terminal
      • Fixed the spend limit menu removing the monthly limit without asking when Backspace and Enter were pressed as it opened
      • Fixed /rewind restoring only some files after running /branch twice while a slow backup copy was still running
      • Fixed /rewind saying "No code changes" when a shell command changed files it can't restore; a turn whose changes weren't tracked now reads "Code changes unknown"
      • Fixed /rewind: Esc now cancels its summary, its list shows more than one past prompt in fullscreen, and a long prompt no longer hides its warning about losing later file changes
      • Fixed Ctrl+C or Ctrl+D twice in /skills quitting Claude Code and dropping changes; it now saves and closes the panel
      • Fixed the usage limit menu erasing your draft and opening while you were typing
      • Fixed pasted text and images being dropped when ↑ recalls a draft cleared with Esc Esc
      • Fixed an edited typed answer to Claude's question sending the old text when you moved on without pressing Enter
      • Fixed going back to a question you answered from its list putting the cursor on the first option, where Enter replaced your answer
      • Fixed /feedback and /bug sending the report when you typed a space on the confirmation screen, and losing the typed report after Ctrl+O or Ctrl+Z
      • Fixed a prompt typed after --add-dir, --allowedTools or another list option being dropped without a message
      • Fixed /plan <description> ignoring the description when plan mode was already on
      • Fixed valid PDFs being dropped from the conversation after the API rejected a different PDF read in the same batch
      • Fixed a session ending after a single failed memory allocation while drawing the screen
      • Fixed compaction on Bedrock, Vertex and Foundry, and with telemetry turned off, sometimes replying to one of your messages instead of summarizing, or leaving Claude's last reply out of the summary
      • Fixed image-heavy sessions on Vertex AI getting stuck on a 400 error about the request size exceeding a 30 MB limit, instead of compacting and retrying
      • Fixed an error when max_tokens exceeded the model's limit: Claude Code now retries the request with the maximum the Anthropic API reports
      • Fixed grep in the Bash tool silently skipping some text files
      • Fixed a crashed Node or Python hook showing only the first line of its stack trace; the error is now shown, and Ctrl+O shows up to 10,000 characters of the output
      • Fixed /goal clear or a new /goal not sticking when typed while Stop hooks were running and background work was still in progress
      • Fixed the automatic session recap being sent after a reply billed to usage credits; /recap still works
      • Fixed auto mode staying on its local classifier, which counts toward usage, because of a stale saved value, such as one from an older Claude Code
      • Fixed "Sign in with your Console account" in /login replacing your Claude subscription login when the browser sign-in used your Claude plan instead of a Console organization
      • Fixed /login ending on "Login successful" while an approved ANTHROPIC_API_KEY was still used; it now says requests still use the key
      • Fixed "Not logged in" staying after turning on the API key in /config; "Not logged in", /login and /status now name an unused ANTHROPIC_API_KEY
      • Fixed claude auth logout leaving credentials behind, and token refresh failing, when only a Console profile's credentials are on a drive that rejects folder timestamps
      • Fixed a past conversation resumed from agent view being sent on the background service's sign-in when the service doesn't have the terminal's API key or token
      • Fixed model requests failing on a one-off authentication error (401) in Claude Desktop's Code tab: they are now sent once more first
      • Fixed forceLoginOrgUUID and forceRemoteSettingsRefresh startup errors telling you to sign in again when a network block page (HTTP 403) was the cause
      • Fixed claude auth login not showing a pasted sign-in code, so a wrong paste couldn't be seen or corrected before Enter
      • Fixed /login and claude setup-token showing nothing after you submit a pasted code; they now show "Finishing sign-in…"
      • Fixed Esc doing nothing while the first-run sign-in waits for the browser or a pasted code; it now goes back one screen
      • Fixed /logout in fullscreen mode exiting without leaving the logged-out message on screen
      • Fixed the shell prompt being drawn over the last screen after quitting with Ctrl+C or Ctrl+D at a sign-in or first-run step
      • Fixed Ctrl+C twice doing nothing on the first-run theme choice, and freezing the terminal on setup screens or a background session at its startup question
      • Fixed your OFF answer to the updated terms being replaced when keys were typed while it was saving, at startup and in /privacy-settings
      • Fixed the /privacy-settings toggle sometimes saving the opposite of what the screen showed on a quick double press, changing your setting on keys pressed after Esc, and not saying when a save failed
      • Fixed /privacy-settings saving your choice on the wrong account after signing in to a different account in another terminal
      • Fixed /privacy-settings saying "set to true" when you picked OFF right after ON
      • Fixed skills and slash commands failing to load in Code Mode under auto mode when an inline ! command needs approval; Claude is now asked to run it
      • Fixed background subagents started in Code Mode failing when they preload a skill with an inline ! command
      • Fixed mods being unable to use Bash, Read and other tools through $.tool.call and $.tool.check in Code Mode
      • Fixed parallel MCP tool calls reading another call's saved result when two long results arrived in the same millisecond (#105138)
      • Fixed tool search sometimes loading another MCP server's tool when asked for a tool by its exact name; you may be asked again for that tool
      • Fixed MCP prompts disappearing when two servers have nearly identical names
      • Fixed a tool call to an MCP server that an SDK host had just removed reconnecting to it, or reporting that it needs authentication
      • Fixed Claude not being told that a remote MCP server's question was declined when the server then failed the tool call
      • Fixed MCP tools with a root anyOf or oneOf showing Claude only the first branch's form of an argument; text such as 42 can now arrive as a number where another branch takes one
      • Fixed Claude not being told when an approved MCP resource tool was unavailable after a cloud session's worker was replaced
      • Fixed /mcp not showing why a local (stdio) MCP server failed to start
      • Fixed Esc doing nothing while an MCP server reconnects: Esc, or Ctrl+C pressed twice, now closes the wait and the reconnect continues in the background
      • Fixed Enable in /mcp showing no progress for a slow server, and a second Enter disabling it again
      • Fixed claude mcp add-json answering most mistakes with "Invalid configuration: : Invalid input"; it now says what to change
      • Fixed the Ctrl+C hint on a background MCP task's question saying "cancel" when the second press leaves the question to answer later
      • Fixed pressing c to copy an MCP sign-in URL leaving a stray c in the paste field
      • Fixed Tab and Shift+Tab not moving between fields in an MCP server's input form, and a required field there keeping its tick after being emptied
      • Remote Control: Fixed a session disconnecting mid-reply when the server was briefly unavailable
      • Remote Control: Fixed the QR code in /remote-control being cut off in short terminal windows such as 80×24
      • Remote Control: Fixed terminal sessions showing as idle on your phone while background subagents were still running; Stop on your phone or the web now ends them together with the turn
      • Fixed Remote Control showing a session as running while it waited on a prompt that can only be answered in the terminal, and as idle when turned on while a tool was running
      • Fixed a reply in a remote session running again after a restart when Stop had been pressed while Claude Code was restarting
      • Fixed Stop in cloud and self-hosted runner sessions sometimes waiting for slow MCP servers to connect before taking effect
      • Fixed files Claude sends from cloud and Remote Control sessions failing at once when a proxy answers an upload with its own HTTP 502, 504 or 520 to 524; the upload now gets a second try
      • Fixed claude.ai chats and Cowork tasks sometimes not sending a file after you chose "Send it" at the check for secret keys
      • Fixed claude.ai chats and Cowork tasks asking about a plugin file only because it holds a Word, Excel or other zip-type file; such files are now read for secret keys first
      • Fixed claude self-hosted-runner asking for new tokens nonstop when a refreshed token was already due, such as when the machine's clock runs ahead
      • Fixed /autofix-pr reporting a run as cancelled when its cloud session could not be stopped; it now links the session so you can stop it
      • Fixed /teleport hiding a session from its list in narrow terminals
      • Fixed artifact publishing refusing files in a background session's temporary folder
      • Fixed subagents whose disallowedTools lists Artifact still being offered artifact tools in some cloud sessions
      • Fixed Claude calling a just-published artifact private when people with access to its folder can open it
      • Fixed the terminal not showing an artifact's link after Claude publishes or updates it
      • Fixed the main conversation of a terminal session waiting in silence for a background subagent that another subagent had messaged: it's now told which agent the subagent reports to
      • Fixed background agents being told you refused their tool call when a session ended by Ctrl+C twice at the exit dialog, or after an interface crash
      • Fixed Up and Esc moving the main conversation's queued messages into the prompt box of a subagent or teammate you are viewing
      • Fixed the agent rows under the prompt showing an agent as busy after its turn ended: the row now says what it is waiting on, and /tasks names the subagent behind each background command
      • Fixed stopped and failed agents looking like running ones in the agent rows under the prompt, or showing "Done" when run in parallel, and a stopped agent's last command still showing "Running…"
      • Fixed an opened background agent showing a normal spinner while its requests were being retried
      • Fixed the "background agents launched" line stopping at two when Claude starts three or more agents in one reply
      • Fixed every earlier turn's "done" line showing "1 shell still running" while a background task ran
      • Fixed subagent tool counts in auto mode including the call that delivers the agent's final report
      • Fixed the welcome header outside fullscreen mode showing the session's model while viewing a subagent or teammate that runs on a different model
      • Fixed images pasted while viewing a background agent arriving as the text [Image #1]
      • Fixed long background agent and background command results wrapping under the bullet instead of lining up with their text
      • Fixed claude --worktree showing nothing while a slow worktree is set up
      • Fixed the worktree exit dialog counting a new folder as one uncommitted file
      • Fixed workflow resume telling Claude every finished agent would be reused after a call failed; Claude is now told how many results were reused and where reuse stopped
      • Fixed a hang on malformed glob patterns in settings, plugin marketplace entries and Grep file filters
      • Fixed plugin and marketplace requests waiting forever when ALL_PROXY is the only proxy set and the proxy never answers; they now fail after 25 seconds
      • Fixed the / menu, /skills and /plugin repeating rows and losing the cursor when two skills or commands in one place share a name
      • Fixed search in /resume, /plugin, /permissions and /config ignoring IME input, dictation and fast typing
      • Fixed the cursor disappearing after clearing a search on the /plugin Installed tab
      • Fixed a mod's Text with wrap="truncate-end" losing rows on the terminal when it holds a line feed
      • Fixed /model showing your saved model as "Default (recommended)": Default now names your plan's default model, and choosing it in the terminal switches you back to that default
      • Fixed a first skill, command or agent created during a session not being found right away
      • Fixed /clear --help and other built-in commands running at an idle prompt instead of showing usage; added /help <command>
      • Fixed a half-written reply sitting frozen with no spinner while Claude Code retried after a mid-response server error
      • Fixed the API retry notice sitting at "Retrying in 0s" during the next attempt, now "retrying…", and the "will retry in" countdown freezing when a reply stalled or with Reduce motion on
      • Fixed the transcript dropping a few rows, or the prompt jumping up, as a reply started streaming
      • Fixed a line of a long list or code block going missing from scrollback, and text jumping a row, while a response streams
      • Fixed a long queued message hiding Claude's reply while it streams, and erasing it from scrollback in the classic renderer
      • Fixed fullscreen text jumping when a reply finishes while you're scrolled up or after answering an Edit or Write prompt, and losing your place or jumping turns when resizing
      • Fixed the fullscreen transcript going blank when searching or jumping far back, and freezing partway through a fast scroll, in long sessions
      • Fixed the pinned prompt in fullscreen showing an older question while a reply streams, and being copied with the reply when you drag a selection past the top
      • Fixed the screen going blank and dropping keys after picking a model in /model, and /model <alias> and /effort <level> briefly hiding the prompt and dropping letters typed right after
      • Fixed the screen scrambling after /tui default in a long conversation, or when the tui setting changed in another window (#94879)
      • Fixed the screen freezing for seconds when showing long newly created files in the permission prompt and the Ctrl+O transcript
      • Fixed some very long Bash or PowerShell commands freezing the session for seconds
      • Fixed Shift+Enter or Option+Enter pressed right after a paste sending the prompt instead of adding a new line
      • Fixed Up, Down, End and mouse clicks putting the cursor on the wrong row of a prompt that wraps
      • Fixed undo (Ctrl+_) losing the last words typed when pressed after deleting a line or word
      • Fixed code or a diff pasted into a prompt losing its indentation in the transcript, and a pasted diff's added lines showing as removed
      • Fixed [Image #N] landing in the middle of a word when typing right after pasting, and a pasted image not being sent after deleting its placeholder and pasting it back with Ctrl+Y
      • Fixed asterisks disappearing from your own prompts in the transcript, such as src/**/*.ts or 2*3*4
      • Fixed claude -p showing nothing in the terminal while it retried an overloaded or failing API request, or when it failed with its text output redirected or captured
      • Fixed Windows paths in Claude's responses losing the backslash before folders like .claude or _build
      • Fixed bold text showing as raw ** in Japanese, Chinese and Korean replies when it starts or ends with punctuation
      • Fixed /memory opening a read-only file with no warning that changes may not save
      • Fixed Claude editing ~/.claude/keybindings.json, which has no effect in Claude Desktop, when asked to change a shortcut there
      • Fixed Claude saying that an administrator can turn on Claude in Chrome when your organization's policy disables it, in apps that provide its tools such as Claude Desktop's Code tab
      • Fixed the suggested next prompt sometimes being a bare tag, such as <signal type="empty" />
      • Fixed long command output ending mid-line in the expanded view with no sign it was cut; it now names the saved file
      • Fixed collapsed tool lines reading "Ran" or "Called" while still asking permission, and "Running…" or "Reading…" again when a panel opened after a call was stopped or refused
      • Fixed failed, blocked or refused commands looking like passing ones in a collapsed tool line: it now shows "· 1 failed" or says they did not run
      • Fixed the "done" line showing after a turn that failed or was refused at a permission prompt
      • Fixed failed or refused skill and agent calls still showing "Initializing…"
      • Fixed /btw showing only a lead-in such as "Let me check that file." with no notice when the model tried to use a tool (#90314)
      • Fixed long /btw answers looking finished and ignoring PgUp, PgDn, Home, End and the mouse wheel
      • Fixed /resume search saying "No sessions match" for older sessions that exist, and a typed number opening a session instead of searching
      • Fixed pressing Ctrl+R again in fullscreen prompt search not moving to the next older match
      • Fixed Tab not completing file names without a slash in shell mode (!), and completed paths with spaces or shell characters not being quoted
      • Fixed a rebound chat:submit key doing nothing while the slash command or @ file menu was open
      • Fixed holding Esc over typed text opening Rewind after the text was cleared
      • Fixed Esc over typed text cancelling a pending /loop
      • Fixed "Esc again to clear" staying on screen after a second Esc would no longer clear the prompt
      • Fixed typing landing in the wrong place in a question's note after going back to it or editing it in an external editor
      • Fixed the "paste again to expand" hint hiding the mode and "esc to interrupt" after a paste was sent or deleted
      • Fixed "paste again to expand" hiding the middle of a paste longer than 10,000 characters in fullscreen mode, and a prompt collapsing while you type past that length
      • Fixed the arrow keys and q not working in a pager that claude --help is piped to, as in claude --help | less
      • Fixed Claude Desktop's Code tab blaming the internet connection when a certificate's signature couldn't be verified
      • Fixed Web Search showing nothing while its request was being retried
      • Fixed desktop notifications not being sent inside tmux (with allow-passthrough on), or to iTerm2 over SSH, on the default setting
      • Fixed /copy and /export saying "copied to clipboard" over SSH when the terminal may not have copied anything
      • Fixed /usage-credits saying "Request sent to your admin" when the request was refused; people who have billing access themselves are now pointed to the usage settings page
      • Fixed the transcript share question for Pro and Max users staying open after the next message, /clear or /resume
      • Fixed an upgrade hint appearing under an old usage limit message after the limit had reset
      • Fixed the effort level notice reappearing after every permission prompt or dialog, and the usage limit warning and other notices not appearing while the context warning showed
      • Fixed /tui default saying it had switched back to the classic renderer when a setting kept fullscreen on; after a /tui that can't switch, Claude Code now says what keeps the renderer
      • Fixed a new account's first session using a different renderer from later ones
      • Fixed Reduce motion and Show tips in /config applying only to the current folder
      • Fixed typing and spinners redrawing the whole pane in tmux 3.7
      • Fixed Option+T typing † instead of toggling thinking over SSH from iTerm2 when Option isn't set as Meta
      • Fixed /terminal-setup not naming the tmux settings that Shift+Enter needs, and promising Shift+Enter in Windows Terminal before 1.25, where it sends the prompt
      • Fixed Program Status Protocol (OSC 7501) terminals showing a finished turn after idle compaction, or no status for background sessions opened with claude agents, claude attach or --resume
      • Fixed terminals that support the Program Status Protocol (OSC 7501) not seeing Claude Code as waiting on you while the folder trust prompt is open (#105801)
      • Fixed the terminal progress bar showing Claude as working while it waited for your answer or was suspended with Ctrl+Z, and disappearing in Ghostty after 15 seconds while Claude was still working
      • Fixed fullscreen giving no sign that a permission prompt or question was waiting while you were scrolled up
      • Fixed the fullscreen tool group headline naming a finished or queued call instead of the running one
      • Fixed finished tool groups in fullscreen counting a search or listing also as a shell command, and the tool timer there counting time at a permission prompt or queued behind another command
      • Fixed a multi-line shell command filling the screen in fullscreen while it runs
      • Fixed ! shell commands showing no output for their first three seconds
      • Fixed a running command showing no output or timer when its collapsed row was clicked open in fullscreen mode
      • Fixed the jump-to-bottom pill disappearing in fullscreen while more of the reply was still below
      • Fixed the prompt disappearing in short fullscreen windows while a survey or notice showed above it
      • Fixed the custom status line disappearing and the screen jumping on Ctrl+C, in ! shell mode and while pasting an image
      • Fixed a custom status line keeping its old width, folder and session name after a terminal resize, /cd or /rename (#107291)
      • Fixed "esc to interrupt" missing beside a custom status line and showing while Esc would go to a panel or footer item
      • Fixed mouse escape codes being typed into the shell after exiting fullscreen mode
      • Fixed the Ctrl+Z message printing over the prompt box outside fullscreen
      • Fixed claude logs painting over and mixing with what was already in the terminal
      • Fixed the spinner tip flashing back and the screen bouncing as a reply finished
      • Fixed the "Reading 1 file…" line blinking out and the prompt jumping when a tool call finished streaming
      • Fixed the claude --resume session preview being garbled and not scrolling in fullscreen mode
      • Fixed Esc not leaving the "Connect to your IDE automatically?" question in /ide, where Ctrl+C twice quit Claude Code
      • Fixed first-run terminal setup saying nothing about what it changed or could not set up
      • Fixed /status showing installation warnings twice
      • Fixed the footer's PR badge showing the previous branch's pull request after switching branches
      • Fixed the "Pushed to" summary naming the fetched branch when a command fetched or pulled first, and "Merged PR" or "Closed PR" showing when gh refused the action and the exit code was hidden
      • Fixed URLs that wrap over several lines not being clickable in terminals with link support that Claude Code doesn't recognize, and labeled links in the Rex terminal
      • Fixed the Ctrl+O transcript hinting Ctrl+B to background a command in fullscreen, where it pages up, and showing no sign that Claude is still working
      • Fixed the Ctrl+R search, the model picker, plan approval, question previews, background shell output and /plugin install choices being cut off in short fullscreen windows
      • Fixed the /context grid, API errors such as "Credit balance too low", "Waiting for API response" and retry notices, "esc to interrupt" and "Interrupted" being cut off or jumbled in narrow terminals
      • Fixed wide tables breaking apart in plans and subagent prompts, cutting short words in half beside a long cell, and showing stray words and blank rows when drawn as label and value lists
      • Fixed code keywords, added diff lines, the slow-reply spinner and "thinking" being hard to read in some themes and terminals
      • Fixed code in diffs and file previews being invisible when the theme and the terminal background differ
      • Fixed the unused part of /usage bars looking full in the light and ANSI themes
      • Fixed the /effort slider ignoring mouse clicks in fullscreen mode
      • Fixed text being drawn out of place after skin-tone or joined emoji, symbols such as ✌ and ☝, and Hindi, Tamil and other Indic vowel signs in terminals that draw them wider
      • Fixed joined emoji pushing rows out of place in GNU screen
      • Fixed the last item of JSON lists and right-aligned numbers losing their indent in command and tool output
      • Fixed diffs numbering "No newline at end of file" as a line of code, which shifted the line numbers after it
      • Fixed long single-line messages showing "(0 lines hidden)" instead of how much text is hidden
      • Fixed notebook edits showing no tool row when Claude left out the cell type or deleted a cell, and showing @undefined when inserting a cell at the top
      • Fixed the "Switch model?" and "Change effort level?" questions showing no key hints
      • Fixed the ? shortcuts list running its columns together in narrow terminals and being cut off at the bottom in short fullscreen windows
      • Fixed leftover hint text in screen reader mode on macOS and Linux after closing the /permissions search when the rule list was taller than the terminal
      • Improved Bash permission checks: some commands now ask first, or are refused where no one can answer
      • Improved permission checks in Code Mode; more sandboxed commands now ask or are refused
      • Improved the messages shown when Code Mode can't be turned on, so they say what you can do
      • Improved Bash sandbox protections on macOS, Linux and WSL
      • Changed edits in a session's mods folder to ask more often, and sandboxed commands to write to fewer folders; if every edit asks, remove any link there to an unreadable or network path
      • Improved Claude's sandbox instructions on Linux to explain that a server is reachable only from the command that started it
      • Improved how secrets are masked in push notifications from Remote Control and cloud sessions
      • Improved /logout and claude auth logout in the terminal to retry revoking the login, and to say where to revoke it if the server doesn't confirm
      • Improved Remote Control: replies from claude remote-control, Claude Desktop and VS Code sessions now stream to your phone or browser as they are written
      • Improved typing, streaming and resize responsiveness, especially in long sessions
      • Improved response time after reading or editing files, most noticeably on Windows
      • Improved idle CPU use: an idle session now wakes the machine less often
      • Improved CPU use when more than 20 subagents are running: token counts of background agents whose transcript isn't open now update every 5 seconds
      • Windows: Improved the speed of a session's first Bash command by about a second
      • Improved response time of the first message after /compact in git repositories
      • Improved response time in Claude Desktop for messages queued while Claude finishes a reply
      • Improved time to first response in Claude Desktop's new sessions: the first turn no longer waits up to 500 ms for local MCP servers whose tools load on demand
      • Improved how a PreToolUse hook's updatedInput is kept when more than one hook answers a tool call; the rewrite now runs in more cases
      • Improved the error when a PreToolUse hook exits 127, saying its check may not have run
      • Improved hook failures, blocks and timeouts in the transcript: failures are now red instead of grey, a hook that stops Claude is yellow, and the reason is shown under them
      • Improved the folder trust prompt, at launch and in /cd, to name the project settings files Claude Code will load; at launch it also marks files that run commands
      • Improved the folder trust prompt to say why Claude Code exited
      • Improved the message in non-interactive runs and background agents when a permission check fails with an error, so it names the cause
      • Improved Claude in Chrome permission requests from a terminal session over Remote Control: on claude.ai they now name the site Claude wants to act on, also when it is already allowed
      • Improved MCP tool errors in cloud sessions: when a call through the session's proxy is cut off after it was sent, Claude is told that the outcome is unknown
      • Improved /update-config in the terminal to use about 13,000 tokens of context instead of 93,000, and a rejected settings edit to quote only the changed settings
      • Improved Program Status Protocol (OSC 7501) reports: background commands, monitors and MCP tasks are listed, and a session waiting on them shows as working instead of done
      • Improved Monitor: when a watch expires with no events and its command wrote to stderr, Claude is now told so and told which file holds the output
      • Improved Claude in Chrome: a long browser_batch call now has 150 seconds to answer, up from 90, so fewer finished results are lost
      • Improved /doctor to share findings as it works instead of staying silent until the full report
      • Improved the error for a settings or .mcp.json file with broken JSON: it now gives the line and column
      • Improved commands that are off for your provider, sign-in or an environment variable such as DISABLE_TELEMETRY to say why instead of "Unknown command"
      • Improved the CERT_SIGNATURE_FAILURE connection error to name a possible cause after a CA renewal and what IT can change
      • Improved the message shown when a team's pooled group budget is used up: it now says when the budget resets
      • Improved the error shown when the API refuses a Console sign-in: it now says to run /login instead of pointing to an admin setting
      • Improved sign-in prompts: pasting a verification code or a web address now says what to do instead, and the prompt stays so you can paste the right code (#97)
      • Improved the /login screen: the code goes in a proper text field, a rejected code says why under it, and pasting in a short window scrolls the field into view
      • Improved /design-login, /install-github-app and MCP sign-in screens to match /login; the first two now mask the pasted code
      • Improved the Claude apps gateway sign-in screens: the sign-in address is a link and c copies it
      • Improved /plugin Discover and marketplace lists: they fit short windows with the cursor and key hints on screen, and Home, End, PgUp, PgDn, the mouse wheel and clicks now work
      • Improved /plugin Marketplaces and Add marketplace: a compact list, a clearer remove confirmation, a clear text field and shorter errors when adding fails
      • Improved /plugin Installed tab: Home, End, PgUp, PgDn and clicks now work, and hidden rows are counted
      • Improved /plugin Errors and Stats tabs: long errors no longer fill the screen, uninstalling from an error asks first, and long skill names no longer break the table
      • Improved claude plugin, mcp, update, doctor and auth logout output on a terminal to mark success, failure and warnings the same way (piped output keeps its old form)
      • Improved wording across the terminal: /plugin, /mcp, sign-in, setup, settings, the agent view, /teleport, Remote Control, update messages, spinner tips, /powerup and claude --help
      • Improved key hints in many dialogs and the ? lists: they show the keys that work, in one order and wording, and fit narrow windows; deeper screens in /hooks and /permissions say Esc goes back
      • Improved text fields in /add-dir, /export, /permissions, /feedback, /install-github-app and Bedrock and Vertex setup: one look, long text wraps, and a refused value can be corrected in place
      • Improved dialogs, panels and the transcript: errors, warnings and confirmations in many dialogs start with ✘, ⚠ or ✔, and loading lines, status rows, counts and durations look and read more alike
      • Improved long menus such as /permissions, /resume and /model to say how many rows are above and below, and the / and @ menus to count hidden rows outside fullscreen and screen reader mode
      • Improved list navigation: more lists wrap at both ends, checkbox lists in slash commands take Home and End, and /permissions says when a search finds nothing
      • Improved the pickers in agent view to take Home, End and paging
      • Improved agent view and the agent rows under the prompt to mark the selected row with the same pointer and color as other lists
      • Improved the footer after Ctrl+C stops background agents: it now offers ↓ to resume subagent while a stopped subagent is listed
      • Improved fullscreen mode: the prompt's borders now show how many lines of a long prompt are out of view
      • Improved /autocompact and /scroll-speed with a slider that shows every value, takes Home, End and (in fullscreen) clicks, and fits narrow terminals
      • Improved on/off settings to read on / off in /config, /memory and auto mode setup
      • Improved the send-now hint under queued messages: it now says "Queued" and no longer looks like part of your message
      • Improved terminal setup to list every change before making it
      • Improved alignment and spacing in /btw, /help, /scroll-speed, the settings error dialog and dialogs that suggest a plugin or setting
      • Changed terminal and VS Code sessions in organizations with the Claude Code + Cowork HIPAA configuration to start in auto mode by default; disableAutoMode turns it off
      • Changed terminal and VS Code sessions with no mode set to start in auto mode, not Manual mode, when your organization's policy hasn't loaded
      • Changed a managed-mcp.json added mid-session so it may apply at the next check; restart open sessions for it to apply in full
      • Changed Code Mode's $ shell helper to refuse some values with an error; nothing runs
      • Changed auto mode to stop some shell commands that ran before
      • Changed some Bash commands on macOS that ran before to ask or be refused
      • Changed a hook's "decision": "block" to hold in more cases, so a hook that always prints one may start blocking calls
      • Changed sessions that start in auto by default to take a server-managed defaultMode once settings load, or Manual if settings fail with no stored copy and policy fails or requires it
      • Changed auto mode for organizations with the Claude Code + Cowork HIPAA configuration: on a direct Anthropic API connection, the server-side classifier now checks actions, as for other organizations
      • Changed the Bash sandbox to keep its state in some cases during a session, until you run /sandbox or /cd; Bash may ask first
      • Changed sandboxed commands on macOS, Linux and WSL to no longer write to some sensitive home folders by default; some can be allowed with sandbox.filesystem.allowWrite in user or managed settings
      • Changed the Bash sandbox to set aside unexpected entries in a repository's .git folder after a command
      • Changed the Bash sandbox on Linux and WSL to create some missing --add-dir folders before each sandboxed command, so commands that create them can fail, skip, or land inside them
      • Changed commands that a permission hook or SDK host rewrites while approving to stay in the sandbox if the original was checked as sandboxed; the approver can add dangerouslyDisableSandbox: true
      • Changed claude mcp serve to ignore sandbox.excludedCommands
      • Changed /rewind on macOS, Linux and WSL to leave some files untouched and report them as skipped when the sandbox is on
      • Changed the Bash sandbox to ask before some lines that set environment variables when auto-allow is off; unattended runs can refuse them
      • Changed Claude's file tools to refuse writes to Claude Code's sign-in files, such as .credentials.json
      • Changed the Bash permission check to ask before more commands reach Claude Code's sign-in files
      • Changed some file tools to refuse some device and process files
      • Changed some cp and mv commands to ask first
      • Changed some tool calls in bypass permissions mode to ask for approval, or be denied where no one can be asked
      • Changed the Bash permission check to ask about some commands with very long values it can't finish checking, or to refuse them where a deny rule may apply or no one can answer
      • Changed subagents isolated in a worktree to refuse, in any repository, some git commands in Bash that can rewrite branches shared with your checkout; sessions are not affected
      • Changed ExitWorktree to refuse removing a worktree while a background subagent or shell command may still be running in it, unless Claude passes discard_changes
      • Changed the computer use macOS permissions panel to ignore j and k; the arrow keys and Ctrl+P/Ctrl+N still move the selection
      • Changed the PowerShell tool to ask before some more commands; unattended runs refuse them unless an allow rule, auto mode or bypass permissions mode allows them
      • Changed the PowerShell tool to ask about some more commands, even in bypass permissions mode, and to refuse some of them
      • Changed some malformed PowerShell commands to be denied
      • Changed some PowerShell tool commands that define a function named like a built-in command to be refused, so Claude can rename it
      • Changed auto mode to ignore some wildcard shell allow rules, such as ones that name no program or that start with $HOME, so the safety check decides those commands
      • Changed auto mode to judge wildcard allow rules whose program is a Windows backslash path, so those calls can be blocked; exact rules keep their allow; we plan to restore rules that start with .\
      • Changed a managed autoMode.environment list without "$defaults" to replace every built-in entry in Claude Desktop and Agent SDK apps too; add "$defaults" or copy the sensitive-target ones
      • Changed --add-dir and /add-dir in local terminal sessions to show the trust prompt for a folder you have not trusted yet; claude --bg refuses such a folder
      • Changed self-hosted runners under --trust-workspace false to ignore more repository settings; set such values in user or managed settings
      • Changed how permission answers over Remote Control and on self-hosted runners save "always allow" choices
      • Changed enabled plugins that were refused for a malformed plugin.json display field: they now load, with their hooks and MCP servers; administrators should check the plugins they deploy
      • Changed how allowedHttpHookUrls and httpHookAllowedEnvVars apply to hooks from managed settings
      • Changed HTTP hooks to ignore Content-Length and Transfer-Encoding in their headers setting; the request's length comes from its body
      • Changed plugin uninstall to also delete the files extracted from the plugin's MCP bundles (.mcpb, .dxt), unless another plugin uses the same bundle
      • Changed some worktree sessions to skip some plugin settings; a notice names what was skipped
      • Changed /plugin uninstall, remove and switch questions to lists answered with the arrow keys and Enter, or Esc to cancel; y, n and u no longer answer them
      • Changed automatic compaction in plan mode to use the model answering you, such as Opus with opusplan, so it can cost more
      • Changed Cowork cloud sessions to hold an organization's OpenTelemetry export until the first turn; a session that gets no message now sends nothing, so claude_code.session.count can fall
      • Changed Claude's messages to a session on another machine to be refused when your session uses an API key, auth token, profile or workload identity beside a saved claude.ai login
      • Changed --bare sessions on an unapproved API key: moving one to the background is now refused in most setups, and claude --bare --bg exits with an error if the background service lacks the key
      • Changed "Continue automatically at usage limit" to stop with a notice, sending nothing, when your login changes or ends during the wait
      • Remote Control: Changed how it connects through a proxy: requests now use a CONNECT tunnel, so a proxy that refuses CONNECT stops Remote Control with an error
      • Remote Control: Changed the session debug logs written under --verbose to go to ~/.claude/child-logs/
      • Self-hosted runner: Changed Linux and macOS sessions with no gh to get a built-in gh api by default, via Anthropic, which adds their GitHub sign-in, if any; --use-anthropic-gh false turns it off
      • Changed agent view so that quitting with Ctrl+C twice, Ctrl+D twice or /exit after pressing ← in an empty conversation ends that session, instead of leaving it running for 5 minutes
      • Changed --await-initialize to be refused with --bg or --worktree --tmux, which never read the initialize request, instead of starting without the fields it carries
      • Changed worktree creation, /teleport and IDE checkouts to run git with a stricter PATH; a git filter or helper may need its full path
      • Changed the card for approving a subagent's plan to two choices, "Yes, and switch to default (ask each time) for this session" and "No", chosen with the arrow keys and Enter (typed text moves to No)
      • Changed the /claude-api skill to build agents on Managed Agents by default, unless you want to host the agent loop yourself
      • Changed /usage in fullscreen mode to show plan limit bars before session cost for subscribers; /cost still starts with cost
      • Changed the wording of some messages that claude subcommands print; JSON output is unchanged
      • Changed first-run setup to preselect the "Auto (match terminal)" theme instead of Dark mode
      • Changed fullscreen /cd to refuse "Yes" while its trust prompt doesn't fit, with a line saying to make the window taller
      • Removed the tmux notice that said the mouse wheel needs set -g mouse on in fullscreen; the wheel scrolls without it
      • Removed the spinner tip that suggested /clear 30 minutes into a running turn
      • [VSCode] Added a claudeCode.promptSuggestions setting that turns prompt suggestions off
      • [VSCode] Fixed "Rewind code to here" in a forked conversation sometimes undoing one turn too many and deleting files created in that turn
      • [VSCode] Fixed the Sandbox dialog creating empty files and folders in the home directory and the project's .git folder while the sandbox is off
      • [VSCode] Fixed the saved sign-in being lost on some networks
      • [VSCode] Fixed sign-in ending when a verification code, a web address or a code from another sign-in attempt is pasted; the panel now says what to paste instead
      • [VSCode] Fixed the sign-in screen showing briefly each time a panel or window opened while signed in to Console without an API key
      • [VSCode] Fixed the usage-limit banner's "Request more" button for Team and Enterprise members coming back after each press without sending anything, after you signed in again during a session
      • [VSCode] Fixed /ide in a second Claude Code session silently losing the editor connection back to the first session; the newest connection now wins and the displaced session shows how to switch back
      • [VSCode] Fixed saved memories not being listed in the Memory dialog, or RAM use growing without end, when the memory folder held symlink loops, and a hang when it held a named pipe
      • [VSCode] Fixed a running command's live output stopping after one failed read
      • [VSCode] Fixed "Open in Terminal" showing only the shell's error when claude could not be started: in bash, zsh, fish and Git Bash, a notice now explains why and links to the install guide
      • [VSCode] Fixed the panel showing no "Open artifact" link after Claude publishes an artifact
      • [VSCode] Fixed the prompt suggestion hiding the "attach selected text" hint while the chat panel is unfocused
      • [VSCode] Fixed buttons with no visible border in the high-contrast themes, and the dark welcome art on the sign-in screen in Light High Contrast
      • [VSCode] Improved Edit and Write speed: no wait for new problems on files that are not open in a tab when the editor has been reporting none for such files
      • [VSCode] Changed a running command's live output in the chat to look like the command card's OUT row
      • [VSCode] Changed the text of extension errors in event listeners, views and activation to stay out of the editor's own error telemetry
    3. 🔗 HexRaysSA/plugin-repository commits sync repo: +1 release rss
      sync repo: +1 release
      
      ## New releases
      - [kflow](https://github.com/nightshift-labs-ai/kflow): 0.0.5
      
    4. 🔗 @HexRaysSA@infosec.exchange A few of our team members will be in Tokyo at mastodon

      A few of our team members will be in Tokyo at @codeblue_jp on 17 & 18 November, ready to talk about all things IDA.

      Want to meet up? Email us at marketing@hex-rays.com and we’ll help you find us.

    5. 🔗 Works in Progress Don’t put all your eggs in one city rss

      Dan Wang explores why America and China both draw their strength from many rival cities, not one dominant capital.

      This is a column: a lighter piece from the Works in Progress extended universe, designed to be enjoyed inprint. If you'd like to opt out of columns, or any other section, you can do so here.


      Vienna has five times more people than Graz, Austria's second city. London is four times, Seoul six times, and Paris seven times larger than their countries' next largest cities. These primate cities are the singular political, cultural, and financial centers of their countries, hosting the overwhelming concentration of the national elite.

      Washington, DC and Beijing are awesomely powerful entities. Yet Beijing is not China's largest city - that's Shanghai - while DC does not rank among even the top five metro areas of the United States. The political center of both countries sometimes struggles to assert itself against other national hubs. That tension imbues the United States and China with productive friction. It is part of the reason that they are superpowers that have been able to combine social dynamism with jealous states.

      Earlier this summer, I visited a few comedy shows in Shanghai. Performers have to submit their scripts beforehand so that censors can expurgate any routine that carries a whiff of political commentary. But they will permit jokes on regional stereotypes. I listened to stand-up comedians make fun of Shanghainese, who worship money while henpecked husbands are governed by formidable women. I heard them say that folks from Liaoning and other northeastern provinces became conniving drunks after the local economy collapsed, but they are redeemed by humor and loyalty. Everyone appreciated the idea that people in the northern metropolis of Beijing can hold forth beautifully on any topic - though that is all they can do.

      Subscribe now

      This comedy reveals a deeper point: China is made up of distinctive macro regions. China's central government has for millennia tried to impose its will on the entire nation. Though top leader Xi Jinping wields more governance instruments than any former emperor, central authorities still have to contend with the ambitions of different regions. New investments do not end up in Beijing by default. They also go toward the southwestern mountain zone centered around Sichuan and Chongqing, the coastal provinces of Fujian and Guangdong, the populous heartland of Hubei and Hunan, and around a half dozen other macro zones.

      Read more

    6. 🔗 SparkFun Tutorials How to Build a Remote GNSS CORS rss

      How to Build a Remote GNSS CORS a Available online at:

      What's a CORS?

      For high precision GNSS to work you need a base/rover system. In the simplest terms this means you need a GNSS receiver sitting stationary and transmitting its corrections every second up to the internet. A CORS, or continuously operating reference station, is a field hardened GNSS receiver to maximize uptime. These reference stations are scattered over large swathes of land, generally positioned 30 to 50km apart to provide rovers in the area with the most precise correction data with as few 'holes' in the coverage map as possible.

      alt
text

      Example CORS station VITH in St. Thomas

      GNSS reference stations installed by the National Geodetic Survey, or by US states who set up their own corrections networks for their transportation and surveying crews can cost more than $50,000 a site. This project, the SparkFun CORS, is a demonstration of how to deploy a very reliable, remotely monitored station for around $2,000.

      It goes without saying, but we do not claim to have the same accuracy or efficacy of the NGS - they rule! We provide this information as a potential starting point for municipalities or other organizations that are looking to move to high precision GNSS without needing to subscribe to a for-profit corrections provider.

      Where can I get corrections today?

      States with Free
CORS

      States with Free CORS

      Free state CORS/RTK networks:

      This is only a partial list. There are lots of additional free networks including UNAVCO and country-wide networks such as CentipedeRTK in France.

      If you're lucky and live in a state or area where there is a free or low cost corrections network then use it! If you are a municipality or county unlucky like we are in a state that doesn't have a network, then keep reading about how you can set up your own CORS!

      SparkFun CORS

      Metal housing attached to a light post in a parking
lot

      A CORS is all the associated bits that enable a reference station to be robustly connected to the internet for long periods of time. If you can install your base station in a protected, climate controlled office or outbuilding, do it! The goal of this tutorial is to demonstrate a mid-grade CORS station capable of being installed in semi-remote areas where no power or internet (WiFi or ethernet) is available. You can spend tens of thousands of dollars on bulky, power hungry equipment but we wanted to show that you don't need to.

      Above is the SparkFun CORS at the end of our parking lot. There are four parts:

      • The antenna is located at the top of the light post.
      • The solar panel shown is 30W but was later changed to 100W.
      • The cabinet houses the battery, solar charger, low-voltage disconnect, base station, and cellular modem.
      • The grounding wire for lightning suppression.

      Below is a list of parts used on this project:

      Description | Cost
      ---|---
      SXM-E | $1,200
      RUT241 LTE Modem | $190
      1m SMA Extension Cable | $5
      Tello SIM card | $3
      Metal Enclosure w/ Hardware | $105
      Cam Lock Replacement | $7
      Cable glands | $8
      100W Solar Panel | $52
      Large Panel Mounting Bracket | $120
      10AWG Solar Wiring | $18
      MPPT Charger | $20
      50Ah Battery | $90
      Battery Harness + Fuse | $5
      RV Pipe Heater | $14
      DC Thermostat | $6
      Low Voltage Disconnect | $21
      Lightning Arrestor | $20
      1m SMA Extension Cable | $5
      Grounding Rod | $30
      Square U Bolts | $20
      NMO Antenna Mount | $10
      5/8" Rod 2" | $10
      |
      Total | $1,959

      The core of a CORS is the reference station that monitors the GPS signals and generates corrections. Most GNSS receivers have the capability to be told the exact location the device is located. From that point on, any differences that are detected in the received GNSS signals are attributable to perturbations (think turbulence) in the ionosphere and atmosphere in general. Those differences are turned into corrections that, when broadcast to a rover, allow the rover to enter into an RTK Fix with accuracies that can be below 10mm in horizontal accuracy.

      We chose the SXM-E reference station as its mosaic-X5 receiver is the Cadillac for precision, while being extremely configurable, reasonably compact, with reasonable power consumption.

      SparkPNT SXM-E Reference Station next to a
quarter

      For a video tutorial on how to set up the SXM-E, including antenna installation and how to run a 24 hour survey to establish the location of the antenna down to the millimeter, check out this video. We found NMO Antenna Mounts to be a handy 5/8" compatible bracket for pole mounting. 4" u-bolts were used to fasten the hardware to the square light pole.

      Housing

      Empty metal cabinet
enclosure

      We chose a ~$100 painted steel cabinet that measures 16 x 12 x 8". In retrospect, this is too small. We should have opted for a larger enclosure but the allure of snugly fitting a 50Ah battery into this enclosure was initially too great. That said, the grated ventilation system of this cabinet works very well and helps keep bugs and mother nature out while keeping the SXM-E within its operating temperature of −20°C to +85°C.

      Open cabinet with foam pan on
bottom

      We re-used some of the packaging foam to create a boat shaped pad for the battery to rest in.

      Note that the enclosure dimensions are not necessarily the usable internal dimensions. Our cabinet came with a handy shelf bracket installed on the back wall. Unfortunately the shelf and bracket system sat so proud that it had to be forcibly removed (ground out) to allow for enough room for the battery to fit. If I were to do it again, I would use a larger ~24x20x10" cabinet.

      Metal cabinet on its side with a u-bolt sticking out the
back

      The cabinet required a fair amount of modification to allow for the u-bolt mounting hardware (four holes), SMA connectors, and the installation of glands to allow for various water-tight cable connections.

      Holes made for connections:

      • 2 x 9mm glands for +/- solar wires
      • 1 x 7mm hole for cellular SMA extension cable
      • 1 x 7mm hole for GNSS SMA extension cable
      • 4 x 1/2" holes for u-bolt fasteners

      Metal cabinet attached to the light post with a solar
panel

      Originally we had intended to install the GNSS antenna directly on the top of the cabinet. This would allow the overall CORS to be more compact but the sloped roof of the enclosure would make getting the antenna into a vertical position very challenging. Additionally, the sky-view blocking aspect of the light pole meant we needed to mount the antenna further up. If you do consider antenna mounting to the cabinet roof opt for an enclosure that has a flat roof and waterproof accordingly.

      Concrete light post pedestal with a sledge hammer leaning on
it

      Shown above, to prevent damage to the reference station in the case of a lightning strike, a grounding rod and tie line were run to the housing.

      Battery with SIMO cellular hot spot on top with a bunch of
wires

      Above, in this original setup you can see the ground tie connected to the lightning arrester in the upper right corner. As my co-worker pointed out: "This is a very bad idea." If lighting where to strike, it would send the lightning through the ground wire inside the enclosure.

      Lightning suppressor connected to the bottom of a metal housing with
antenna cables
attached

      Here is the lightning arrester properly located on the outside of the enclosure: the GNSS antenna cable routes to the lightning suppressor, the ground wire has its shortest path to ground, and the arrestor is connected to an SMA extension cable that mounts to the enclosure wall that, in turn, connects to the SXM-E's mosaic-X5 GNSS receiver.

      Power

      LiFePO4 battery with heat pad
disconnected

      I thoroughly recommend LiFePO4 chemistry batteries. Lithium Iron Phosphate (aka LFP) batteries have most of the benefits of their higher-energy-density LiPo cousins with the additional benefit of being very safe and hardy in robust environments. I have put 12V equivalent LiFePO4 battery packs through thousands of cycles, across three winters without heating and four summers in the Colorado sun, only to test the capacity of the battery and see that it remains at 80% of its badge capacity! Because of this, LiFePO4 was a natural match for our CORS test station.

      SXM-E power draw
measurement

      The first step was calculating worst case scenario for lack of solar. Between the LTE modem and the SXM-E base station, our system power draw was about 4.5W average. Use your favorite calculator or chatbot to aid in the battery size, solar panel size, and solar panel angle. But our initial calculations put us at 30W for a solar panel (assuming an MPPT charger) and a 50Ahr battery. This setup was slated to last us 640Wh / 4.5W = 142h or six days if no sun was available, and charge the battery from dead in about 3 to 5 days depending on the time of year.

      SparkPNT CORS with smaller solar
panel

      Above we have the 30W panel with the small panel mounting bracket. This combination was originally attractive for its compactness and low-cost. Unfortunately the panel was not large enough to escape the death spiral.

      Pro Tip: When deploying a solar powered, self-contained system, start from a dead battery. It's natural to want to charge your battery fully then deploy your system thinking all will work fine. But if your charger is malfunctioning, or your battery is not quite up to its badge rating, or a bird causes a mess and degrades your solar panel's performance, you won't discover your system is slowly dying for many weeks or months. By starting from death, you can check that the system will be capable of digging itself out, from a power perspective.

      I didn't intend to deploy our CORS with a dead battery but by installing the electronics one day and getting delayed installing the solar by a few days, it was a happy accident. Well, happy if we mean our base station failed from day one.

      Graph showing the base station failing to connect to the
internet

      During the red highlighted phase, the station was deployed and would work for a few hours, but once night came the station would go offline due to loss of power. The frustrating part was that the station would not come back when the sun came up the next day. What in the world was going on? It's BMS lockout!

      A graph comparing pack voltage over
time

      Above we see two discharge curves: LiFePO4 versus a lead-acid based battery. The run time in hours is not representative of any one CORS, rather, the graph is to demonstrate how the respective chemistries will behave during a cut-off scenario.

      Every lithium based battery has a battery management system (BMS) to prevent the cells from dangerous and damaging edge cases such as over current, over voltage, or under voltage. In our case, the 12V battery has a BMS that disconnects the batteries via a MOSFET switch. Whereas classic lead-acid based 12V batteries (SLAs, AGMs, etc. all behave similarly) will output a lower and lower voltage (11V, 10V, 8V, etc), lithium based batteries with a BMS will lower their output voltage to a point, say 11.5V at which the BMS turns off the pack and the battery will read 0.0V. The BMS will not 'unlock' the pack until the load is fully disconnected. In the case of our CORS, the BMS was locking out at 0.0V but the load (the cellular modem and base station) continued to pull on the battery even when the sun was fully out. This was a type of lock-out death we had not anticipated. Luckily, this is a common issue!

      Wiring harness with a charger, LVD and a few
connectors

      Above we see the new wiring harness complete with MPPT charger and low-voltage- disconnect. The charger is connected to the solar panel wires using wire nuts. The small bare pair of wires connect to the SXM-E's screw terminals, the polarized plug powers the RUT241 modem. An LVD simply disconnects the downstream system when the voltage drops below a programmable threshold, and turns on the downstream system when the available voltage is above another programmable threshold. We set our LVD to cut off at 11.8V (~5% capacity remaining) and turn back on at 12.8V. This approach allows us to draw down the battery considerably without triggering the BMS disconnect. There is a chance that we have a terrible snowstorm that drives the system to LVD cutoff, then perhaps through self-discharge the battery enters BMS lockout, but this is unlikely. I've tested LiFePO4 batteries after a year of being on the shelf and tested their capacity to find only a 2% capacity loss! LiFePO4s are pretty amazing. A few days sitting in a low state shouldn't lead to a low-voltage cut-off.

      A graph showing the station connecting then disconnecting at regular
intervals

      Above we can see a report of the USACOLNIW2 station up time over a series of days. While I'm still not a proponent of anything blockchain, Onocoy does serve as an excellent, free station monitoring service. This quickly showed us the LVD was working! The station was dying at night, sure, but it was turning back on and charging during the day! We hit our second wall: The solar charging system was not large enough to charge the battery sufficiently to allow the system to run longer and longer over a series of good solar days.

      A larger 100W solar panel shown attached to the light
post

      The solution was to upgrade to a larger 100W panel, bracket, and wiring. It's frustrating that the mounting bracket is twice the cost of the panel. But considering the weight of the panel and the wind speeds around Boulder, CO, this much more substantial mounting hardware gives us peace of mind that the heavier solar panel won't fall damaging anything or anyone!

      A connection graph showing the base station staying connected over multiple
days

      The panel change increased the cost of the project by ~5% but the improvements were immediately obvious, shown above as a steady green bar. After the installation of the new 100W panel, and with only a few hours of winter daylight left to charge the battery, the station was charged enough to survive the night and continue to improve over the coming days. Dig-out from death is a success!

      LiFePO4 battery with fuse and heat
pad

      Now let's talk battery heaters for a minute. The internet abounds with warnings to never charge your LiFePO4 battery when the cell temperature is below 0C (32F). My experience differs slightly: I have fully discharged and charged multiple batteries through Colorado winters without temperature control or sensing of the pack. After over 1000 cycles (more than 3 years), the capacity tested at 80%. Not bad!

      However, for the benefit of this tutorial we wanted to test out battery heating. Shown above, our original design of the CORS battery pack included a stick-on RV pipe heating pad adhered to the bottom of the battery connected to a thermostat. The idea was to turn on the heater to allow the battery to heat itself when the temperature dropped below 3C (~37F). This heat would keep the battery warm while providing the SXM-E residual warmth to keep it above its lower -20C operating threshold.

      LiFePO4 battery with heat pad
disconnected

      When the station failed initially due to BMS and charging issues, the thermostat and heater were disconnected. The additional system complexity was not worth the marginal improvement to the battery lifespan. We have found the combination of insulation foam on the bottom of the cabinet, residual heat from the SXM-E itself, and strong Colorado sun tend to keep the battery at a good charging temperature when the sun is out. If you are very concerned about it, go for it! Our design heated the battery even at night which is silly. We recommend adding a light sensitive switch so that heating is only enabled when the solar output is high enough that the battery is actually charging.

      Cellular Data Link

      A reference station doesn't do much good unless it's pushing corrections to an NTRIP caster. To get the data to the internet we could have used SparkFun's local WiFi but that wouldn't provide a reasonable demonstration to users who are deploying a self-contained station.

      In order of lowest cost and complexity:

      • If you've got ethernet, use it! It's the lowest power and most dependable. Also, PoE is supported.
      • If you've got WiFi, use it! It's free.
      • If you've got cellular coverage, it will cost a bit each month ($10-$20), but it will work.
      • If you're really remote, there's HugesNet, Viasat, Starlink, or Iridium. These provide satellite based internet but can cost anywhere from $50 to thousands of dollars per month and require considerably more power.

      Cabinet with a battery and pile of electronics and wires including a SIMO
cellular hot
spot

      We originally tried to use SIMO, a ~$120 cellular hotspot marketed with 1GB of free data for life. Shown above, this is the small gray plastic device sitting on top of the battery. This would ostensibly remove the need for a monthly cellular account. However, we found that every 10 minutes, like clockwork, the SIMO would disconnect from the casters for a few seconds then promptly reconnect. While we could have troubleshot why this was occurring, it was assumed that SIMO was doing some sort of reasonable throttling that the casters would not like. 1GB a month is not enough data (more below) and the SIMO was not really built for this so we switched to the RUT241 and have been duly impressed.

      Cabinet showing the SXM-E connected to a RUT241 cellular
modem

      The RUT241 is a cellular modem with ethernet, WiFi, and remote monitoring. Above we see the RUT241 connected over WiFi to the SXM-E. Eventually we got rid of the WiFi antenna and directly connected the SXM-E over ethernet; this cut down on complexity and reduced power consumption.

      Note in the photo above the RUT241 has two cellular SMA connectors: one connected to a large flat antenna and another connected to an SMA extension cable. We were concerned the enclosure would cut down on cellular reception so the primary antenna is connected over the SMA extension to an external antenna while the secondary antenna is kept inside the enclosure. We found that reception was superb but you may want both antennas externally mounted for additional reception.

      The amount of data a reference station can generate varies a lot based on a multitude of factors. MSM4 is the more compact, slightly less precise format for RTCM messages where as MSM7 is larger and more precise. If you have a relatively basic base station receiver (say a ZED-F9P) capable of only L1 and L2 frequencies, with a portion of low-elevation satellites removed from the corrections output, then you can easily drop down under ~800 bytes per second. Unfortunately this still leads to nearly 2GB per month. Alternatively, if you want to participate in networks like Onocoy, and are rewarded based on the 'quality' of the data and number of satellites in view, this can substantially increase the data being pushed to the caster over the cellular connection. And because of the SXM-E's superb reception, you can expect many thousands of bytes per second.

      Reasons for increasing data:

      • An advanced receiver that can receive multiple L1/L2/L5 frequencies will output far more correction data than an L1 only capable GNSS receiver.
      • Outputting the more precise, but larger format MSM7 formatted corrections messages will output more data than the equivalent MSM4 formatted RTCM.
      • A high-quality, high-sensitivity receiver and GNSS antenna will sense more satellites, and hence output a lot more corrections than a low-quality receiver with sky-view obstructions. Every additional satellite detected linearly expands the amount of data to transmit.
      • A receiver that reports every satellite, even low to the horizon poor quality ones will add to the data transmitting vs reporting only high quality, high signal satellites.
      • A receiver reporting corrections for all constellations (GPS/GLONASS/Galileo/BeiDou) will generate far more data than a base station reporting corrections for only the GPS constellation.

      And just because we're weird, we want to simultaneously cast to three casters: RTK2Go, Emlid, and Onocoy. We love RTK2Go but it experiences outages when we least expect it so Emlid serves as a nice backup. And we use Onocoy both as an uptime monitor and because it's technically generating funny money. We will report back if we're ever successful in turning the Ono coin into something tangible (i.e., beer). Now we could have used RTKLIB's Stream Server (STRSVR) to send only one copy of corrections over the cellular network and then have a server re-broadcast to the three casters but this was deemed overly complex; it's easier to pay the $20 a month to push more data.

      The mosaic-X5 configuration page within the Teltonika remote management
system

      One especially nice feature of the RUT241 is the ability to remotely tunnel into the system. This allows us to remotely connect to the SXM-E as if we were connected over a USB cable to both monitor and configure the settings. This has been extremely handy. The downside is that there is no free lunch: Teltonika charges a monthly fee (about $5 as of writing) for this access. Now that the station is up and running, we will probably let the subscription lapse and purchase a month's access only when we need to modify or troubleshoot something which should be very rare.

      Bar graph showing the daily data
sent

      You can also tunnel into the cellular modem itself and view data usage statistics. Note the small print at the bottom; these are estimates that may differ from the cellular provider, but they give us some insight into the daily usage. If this is to be believed, we're transmitting between 10 and 15GB per month.

      Tello prices for 20GB per
month

      The easiest/lowest priced data we've found was Tello. Your mileage may vary, but $18 a month is not terrible. Getting their SIM and using it with the RUT241 was very easy. Again, we're rare in that we need 20GB per month. If you filter out low-elevation satellites, turn off corrections from constellations that your rovers don't care about (perhaps Galileo and BeiDou), turn off frequencies that are not needed (GPS L5 is a good candidate), and push to a single caster, you should be able to reduce your data usage per month considerably.

      Further Improvements

      The SparkFun CORS is operating very well. Check out the current status on Onocoy and RTK2Go. We hope to have a fairly boring next couple of years. If we learn anything else we'll update this tutorial along the way.

      1) As stated earlier, a larger cabinet would be the first improvement. Currently any maintenance or modifications require the entire cabinet to be emptied. However, now that we know what we're doing, there would be far fewer changes after-the-fact so perhaps the smaller cabinet is acceptable.

      2) The cold-rolled steel is very sturdy, but a pain to drill. There are knock- outs but they were deemed too large to use. Finding a better way to leverage the built-in knockouts would require less drilling.

      3) The MC4 connectors on the 100W solar panel required sending larger diameter wire through two glands and then connecting them using wire nuts to the MPPT charger. This works but is cumbersome. Perhaps MC4 bulkhead connectors could be used, but these connectors are too bulky to be used inside the enclosure. Perhaps there's a solution using an SAE connector to connect the wires to the charger.

      4) Given infinite time and money it would be interesting to build a much larger cabinet instrumented in a way to allow for much more granular data gathering. Measuring and reporting the power consumption, battery voltage, and data flows would allow us to potentially reduce the solar panel, battery size, and tailor the cellular data rates.

      Thanks for reading!


      learn.sparkfun.com | CC BY-SA 3.0 | SparkFun Electronics | Niwot, Colorado

    7. 🔗 backnotprop/plannotator v0.28.66 release

      Follow @plannotator on X for updates

      Missed recent releases? Release | Highlights
      ---|---
      v0.28.65 | Take back a reply your agent has not received yet, over Tailscale, Plannotator opens only for your own account, tag a linked machine's threads; one tag across machines, T3 Code threads get the Inbox with no setup, long threads open on slow connections
      v0.28.64 | Installs and updates download a smaller, compressed copy, a Videos filter on the Artifacts page, GitLab comments on a whole file get their own thread, pull request pictures and videos show in the Inbox
      v0.28.63 | Pair Grok Bot and other cloud agents from Settings, Hermes Agent, OpenClaw and Muse Code can use the Inbox, add a thread to Priority to keep it on top, tag threads, and find each tag in the sidebar, Pull requests board as a table, with bulk Merge
      v0.28.62 | Agents started from the Inbox now work on Windows, pick a model and effort when you start an agent, rules for your agents, written in your own words, post a thread's decisions on its pull request, the Inbox loads faster on a slow connection
      v0.28.61 | Updates now update the Claude Code plugin too, an agent's chosen face shows on every icon of it, filter the Inbox list by pull request state, Modern dark shows section bands and the Reply button, one conversation no longer shows as two agents
      v0.28.60 | Click a word to highlight it, a one-time Themes dialog, Settings → Rows rebuilt, tell your agent how you want your rows, starred threads as pills above the list, a pill for new messages out of view, a half-circle face picker with ten Glass colours, a new phone sidebar and reply box
      v0.28.59 | A quieter Agents section in the sidebar, machine names only when agents run on more than one machine, agent icons that are always gently alive and lean toward your pointer
      v0.28.58 | Start Codex from New message, an Agents section in the sidebar, start an agent in a folder on any drive, play audio attachments and comment at a moment, Claude Code's Plannotator tools work on Windows
      v0.28.57 | Pin artifacts, and see every artifact on one page, filter the list by project, date or agent, a thread shows its pull requests and their state, choose what the sidebar shows, and in what order, Ask AI starts from Side in the selection bar
      v0.28.56 | Questions can show trade-offs and a prototype to try, a thread with many big pictures no longer crashes the tab, Escape closes New message and keeps your draft, read threads stop being bold and keep their place, agent messages that name no thread start a new one
      v0.28.55 | Floating reply drafts, now a setting under Experimental, open questions sit next to Reply again, a comment box that keeps unsent comments as Drafts, choose how your list looks: Minimal, Balanced or Detailed, update an older linked machine from this Inbox
      v0.28.53 | Start an agent in a new folder, or from a git URL, "+" on each project row starts a session there, a reaction tray, a thread's Links, Settings → Activity, New message offers the open thread's files, Bro mode: agents write to you in plain words

      What's New in v0.28.66

      TL;DR

      • New: Pick several threads and archive or snooze them at once
      • New: Combine picked threads into one; Tidy follows your own words
      • New: Rows take their tag's colour; filter and search by tag
      • New: Files an agent's message names open beside the thread
      • New: Swipe rows on phone or iPad; list can show archived threads
      • New: Antigravity and Orca use the Inbox; T3 Codex threads get replies
      • New: Open in lists JetBrains IDEs
      • Off by default: Routines: run a saved prompt on a schedule

      v0.28.66 is mostly an Inbox release. You can pick several threads and act on them at once, ask one agent to combine them into a new thread, or have Tidy follow your own instructions. You can also swipe a row on a phone or iPad. Tags show on rows, under a thread's subject, in Filter and in Search. A file that an agent's message names opens beside the thread, and Google Antigravity joins the agents that can use the Inbox. Plan review and annotate get optional source line numbers and coloured text, and the Open in menu lists JetBrains IDEs. The release has 100 PRs. 15 of them are from 8 outside contributors, and 5 of those people made their first contribution.

      Pick several threads and act on them at once

      You can now pick thread rows and act on all of them together. ⌘-click (Ctrl- click on Windows and Linux) adds or removes a row, and Shift-click picks a range. You can also choose Select in a row's right-click menu or a phone's long-press sheet, or Select threads in the list's ⋮ menu. While rows are picked, a bar takes the place of the list header. It shows how many are picked, with Archive, Snooze, Tidy…, Combine… and Done. On a phone the actions are a sheet at the bottom of the screen. A right-click on a picked row acts on every pick. Each action gives one toast with one Undo. A thread that lives on a linked machine goes to that machine; if the machine is asleep, the change waits for it.

      Tidy now takes your own words. Its popover has "Add instructions (optional)" and remembers the instructions you used recently. Tidy on picked threads asks each thread's own agent about those threads only.

      Combine asks one agent to write a new thread from the picked ones. You choose the agent and can say what the new thread is about. The picked threads are archived only once the new thread arrives. If the agent ends or stops first, nothing is archived and the window says so. While it waits, the rows read "Combining…", with "Stop combining" in their menu. Undo brings the threads back.

      On a phone, every bottom sheet now fits the screen and scrolls inside, so the first items of a long menu are always in reach.

      #3405, #3418, #3433

      Swipe a row, and show archived threads in the list

      On a phone or an iPad, swipe a thread row as in Mail. Swipe right to mark it read (on a read row, the right side offers Mark unread). Swipe left to archive it. A long swipe or a flick runs the action when you lift your finger. A short swipe leaves the row open on its button, so you can tap it. Toasts, Undo and the "Set aside N open questions?" warning work as they do from the row menu.

      Archived threads can now show at the bottom of the list. Turn on Show archived in the list's ⋮ menu (it is off until you pick it). An Archived section then sits under Snoozed, closed until you open it. It shows the newest archived threads first, 20 at a time, up to 100, and then points you to Search. Each row says when it was archived. Unarchive is in the row's hover action, its menu, and a left swipe on a phone. The choice is the same on every linked machine and every open window.

      #3135, #3404

      Tags on rows, in the thread header, in Filter and in Search

      Rows take their tag's colour. Each tag now has a colour. A new tag gets one at once from a calm set (green, amber, the accent colour and grey), and tags you already have get one on the first load. A tagged row is tinted across its width and shows the tag's name. If you already use tags, your rows are coloured after you update. To change a tag's colour, right-click the tag in the sidebar and pick Highlight rows : five presets, your own recent colours, a hue strip, a hex field, or None. To turn every tint off, untick Show tag colors in the list's ⋮ menu. Colours and the switch are the same on every linked machine.

      A thread's tags show under its subject , each opening its tag's list, with a + to add one. A thread with no tags looks as before.

      Filter and Search. The list's Filter has a Tag section that shows how many threads each tag leaves, and you can tick several. Search has a Tag chip after "From anyone". With the Board off, resting on a #Tag in a message shows a preview of the tag's latest threads.

      Add tag no longer loses what you type when the menu moves under a still mouse.

      #3397, #3402, #3393

      Every file an agent's message names opens beside the thread

      In an agent's message, a link to a file, a code span that is a path (src/a.ts:42, README.md) and a bare path in the text now open that file beside the thread. :42, :6-13 and #L6-L13 jump to and mark the lines. Opening the file attaches nothing. Your first comment on it (a text selection, a code line, a point on a picture, a moment in a video) makes it an attachment of that message, and from then on it is counted and sent like any attachment. A relative path starts in the thread's folder. Secrets never open: dotenv files, SSH keys and credential stores are refused. Your own messages keep their links as they are.

      #2875

      Prototypes you can click through, and prototypes on the web

      An agent's prototype page now behaves in the Inbox as it does in a browser tab. A link to the same page with a query (?variant=2) loads that variant in place, GET forms and # links work, and the "Try prototypes" window follows links to another option's page or to a web page (in a new tab). Each option can open the same attached file with its own query, so stepping between options switches the variant.

      An agent can also point an option at a public https:// page. "Try prototypes" opens it straight from the web, with Comment for a whole-page comment and a button to open it in a new tab. Plain http:// on another host is still refused.

      #3162, #3319

      Reply to a new session when the one that asked has ended

      When the session that asked you has ended, the "who gets this reply" list now ends with a row such as "New Claude Code session in ledger". Pick it and your reply starts a new session of the same agent, in the same folder, on the same machine, and that session then owns the thread. The ended session stays the default, so nothing starts unless you pick the row. If the start fails, your reply is kept and the thread offers Try again.

      On a computer, that list now shows each session's title, with the agent and folder under it, as the phone already did. Two sessions with the same title get the agent's name added. In the sidebar, the Agents list keeps a fixed order (newest first seen at the top), so rows no longer jump when a turn starts or ends. An agent's name follows one rule on every device: the name you gave, then the name set in the agent, then its title.

      #3442, #3447 finishing #3343 by @sx4im, #3454, #3448

      Antigravity can use the Inbox

      Google Antigravity (the app, the IDE and the agy command) can now write to your Inbox, and your reply starts a turn in the conversation that asked. When Antigravity is on the computer, plannotator inbox adds the Inbox to its MCP config. The app and the IDE need nothing else. An agy conversation is told to run plannotator inbox antigravity once per launch when the Inbox cannot reach it yet. Each reply goes in once. The wake was tested with agy on macOS. The IDE, Windows and Linux are not tested yet.

      #3390, #3444

      T3 Code: replies reach Codex threads too

      A Codex thread running inside T3 Code could write to the Inbox, but your replies never showed up in T3. Now a reply to any T3 thread, Claude or Codex, goes in through T3's own t3 thread send on this computer, with no setup. When T3 is closed, the reply says "Waiting for T3 Code" at once, and the list row says the same as the thread. A T3 started from a Claude Code terminal, or one of T3's own short runs, no longer takes a reply meant for the thread.

      Settings → Agents has a T3 Code entry when T3 is on this computer. It says whether your replies arrive as a new turn, and when they cannot, it shows the sign-in command with Copy.

      #3375, #3381, #3412, #3438

      Orca gets the Inbox and the plannotator tool

      Claude Code chats in Orca now get what the VS Code panel gets: the plannotator_inbox tool with the reply wake, and the plannotator tool. This changes plan review in Orca: Orca shows its own "Review proposed plan" card, so Plannotator's plan review no longer opens there.

      #3460 closing #3325 reported by @ninjz, with the Orca work from #3400 by @rudycelekli

      Cloud agents use the whole Inbox

      A paired cloud agent can now do what a local agent's Inbox tool does. It can list, read and search every thread in every project, reply in any thread, start threads in any project (named by project name), resolve and snooze threads, change a thread's pull requests, and send guided reviews. It can use cards and steps while those are on. It still cannot name a path on your computer. It can also attach files up to 100 MB, videos included, by sending them in pieces.

      #3306, #3318

      Plan review and annotate: source line numbers, coloured text, and Open in

      JetBrains

      Source line numbers. Settings → Display has a Source line numbers switch, off by default. Turn it on and each block in plan review and annotate shows its source lines in a quiet gutter: 42 for one line, 42–45 for a span. The numbers stay out of copied text and out of an annotation's quote, and they are hidden on phones and in print.

      Coloured text. An author can now colour a few words with <span style="color: …"> or <font color="…">. The colour shows in plan review, annotate, Inbox messages and Markdown attachments, including table cells. Colours that are almost see-through are refused.

      Open in JetBrains IDEs. The Open in menu now lists IntelliJ IDEA, WebStorm, PyCharm, GoLand, Rider, PhpStorm, RubyMine, CLion and RustRover when they are installed. The file opens at the line.

      Annotate's default view. A new config.json key, annotateView ("wide", "focus" or "edit"), sets the view an annotate session opens in.

      A table indented under a list item no longer draws its header one column to the right.

      #3373 by @mvanhorn closing #1650 requested by @de-tre, #3378 closing #3345 requested by @zane668, #3372 by @mvanhorn (related to #3368 by @JasonLandbridge), #3463, #3314 by @BenNewman100

      A quicker Inbox window

      The Inbox window now keeps the open thread in one cache and applies live changes to it in place, instead of reading the thread again. When you press Send, your words show in the thread at once with "Sending…". If the send fails, they come back into the reply box with the reason. In a long thread, one new message now redraws only itself (before, a 266-message thread redrew 291 parts). Each agent message across four windows takes half the requests it did. On an iPad, the first load no longer stalls before the first tap works.

      #3103, #3115, #3123, #3386

      Phones and iPads

      • The comment card stays above the keyboard. On an iPhone or iPad, the comment box ended up under the keyboard and the screen jumped on every key. It now sits above the keyboard. #3380
      • Step through a thread's files on an iPad with large previous and next buttons under the open file, or a sideways swipe. A swipe that starts at the screen's edge stays Safari's Back or Forward. #3425
      • The tag (@) and recipient pickers are no longer cut off by the reply box. #3440 by @sx4im closing #3427 reported by @llwt
      • Leaving a picture's full view no longer redraws every tile button in the thread under your finger. #3371

      config.json can live in your dotfiles

      The Inbox used to write its own records into config.json: when each one-time dialog was due or shown, the tour, and similar bookkeeping. These differ on every machine and change by themselves, so config.json could not be kept in a dotfiles repo. They now go to state.json next to it. Your settings stay in config.json. Old copies in config.json are read and never removed, so an older version or another machine sharing the file keeps working. plannotator uninstall --purge removes state.json too.

      #3458 closing #2852 reported by @robsonpeixoto

      Updates, installs and proxies

      • Updates run at low priority. A background update (Update now, or auto-update) now runs at low CPU and disk priority, so the Inbox stays quick while it downloads. plannotator update in a terminal keeps normal priority. This applies from the update after this one. #3466, for #2788 reported by @zane668
      • A download mirror for the binary. install.sh now downloads the binary itself from PLANNOTATOR_RELEASE_DOWNLOAD_URL when it is set, not only the checksum. The checksum check still applies. #3310 by @rudycelekli closing #3298 reported by @navin-moorthy
      • A proxy no longer breaks the Inbox. With http_proxy (or HTTP_PROXY, ALL_PROXY) set, Plannotator sent its requests to 127.0.0.1 through the proxy. plannotator inbox status then said "not running", and an agent's send could start a second Inbox and stop yours. Local requests now skip the proxy. #3461, found while working on #3350 reported by @zane668
      • A plan review whose parent is gone exits. When the program that started a classic plan review is killed, the review's server now exits after about 10 seconds instead of running on with nobody to read its decision. #3461

      Routines: off by default

      A routine is a saved prompt with a name, a schedule and a folder. When it is due, the Inbox on this computer starts a fresh agent session in that folder, and every run lands in one thread. Turn Routines on in Settings → Capabilities (config inboxScheduledThreads). It is not offered on Windows, and it needs "Start agents from New message" on. While it is off, nothing runs and nothing is written.

      • Schedules: hourly, daily, weekdays, weekly, once, a custom cron, or none (run by hand). Runs are at least 15 minutes apart.
      • Missed runs: "Run once when I'm back" (the default) or "Skip it". A catch-up is one run, never a burst.
      • Runs use Claude Code, Codex, OpenCode or Pi, with your own permission mode. Your reply goes to the newest run's session.
      • Agents can create routines, but one an agent creates arrives off, and only you can turn it on the first time. Each change an agent makes posts a line in the routine's thread, with the old and new values.
      • Start at login: while Routines is on, the Inbox adds a login item (launchd on macOS, a systemd user unit on Linux) so it starts quietly and routines can run. Turning Routines off or plannotator uninstall removes it.

      A routine is managed on the computer that made it. Its thread works from a linked machine like any thread.

      #3409

      Reach the Inbox through your own Cloudflare: off until you set it up

      For people who do not use Tailscale, the Inbox and your review, annotate and last sessions can now be reached through your own Cloudflare Tunnel and Cloudflare Access. As over Tailscale, one owner gets in and nobody else does: only the e-mail you type at setup can sign in. Settings → Remote devices has a Cloudflare card with Set up. You can also run plannotator inbox cloudflare-access setup --email <you>. Setup needs a Cloudflare account with a domain, an API token (never saved) and cloudflared. It creates the tunnel, the sign-in gate and two addresses, checks from outside that a request without your sign-in is refused, and only then turns it on and shows the address with a QR code. teardown removes everything it made. Sessions take --cloudflare- access.

      #3388, requested in #3069

      Additional Changes

      • Last 3 days in the list's Updated filter: today and the two days before, moving with the clock. #3401 by @rudycelekli closing #3301 requested by @zane668
      • Let a trusted local app show the Inbox in a frame. A new config.json key, inboxFrameAncestors, lists the apps on this computer that may embed the Inbox window. Unset, nothing changes. #3376 closing #3299 requested by @jroquejr
      • plannotator review<word> with no such folder now stops with a clear error, instead of reviewing the folder the terminal is in. #3387
      • plannotator review<folder> reviews that folder even when the shell exported GIT_DIR. #3377
      • Mod+Shift+Enter in code review opens "Send with a note…" instead of posting the review with no note. #3210 by @rudycelekli, #3403
      • DeepSeek Harness keeps the backslashes in a typed Windows path, so /plannotator-review C:\dev\feature opens that folder. #3214 by @rudycelekli
      • A link whose URL has parentheses (such as a Wikipedia link) now works in guided reviews and PR descriptions. #3213 by @rudycelekli
      • OpenCode's annotate-last opens on the reply to your own prompt, not to a message a plugin added. #3358 by @xunguangzlj-cloud closing #3312 reported by @marwashan
      • Pi inside an Electron app gets a TLS warning that tells you to update the host app, with its Electron and Node versions. #3351 by @jiangjiang248 closing #3346 reported by @xueccci
      • After/bg on a busy Claude Code session, the Inbox tool stays connected. #3370 by @uvw closing #3369, which he also reported
      • A malformed address answers 400 in the Shapes routes, the review servers and the Inbox. In Pi it could stop the extension's host. #3414 by @sx4im closing #3411 reported by @brunnojob, #3456
      • Your words are kept. Take back is no longer offered on a reply that carried answers (the server refused it). A dialog no longer closes when a text selection ends on its backdrop. Closing the reply box while it says Transcribing keeps the take, and a file opened over the box while recording closes the mic and posts nothing. #3426, #3445
      • Questions. A question repeated in an attached file is asked once, not twice. Choices that differ only in case or a mark ("Yes" and "Yes!") are kept apart. #3422
      • Reply files keep the order you picked them in , on the phone and from another window. #3441
      • Pin / Unpin in an attachment's menu , after Download. The dialog for updating a linked machine now reads "Update {name} yourself". #3424
      • A sleeping machine's projects stay in New message's folder menu , after a reload or in a new tab. #3468
      • Short GitLab merge request references go to the project's own server. A short reference such as group/project!45 now goes to the project's own GitLab server, including self-hosted names like gitlab-master.example.com. Before, it could point at gitlab.com. If a short reference still goes to the wrong place, for example when your GitLab is reached on a port or the project's remote uses an SSH alias, name the server in gitlabHosts in config.json. A reference saved before this fix keeps its old address until you remove it and add it again. From a user report. #3525
      • The thread header shows its PR button when an agent links PRs while the thread is open. #3451
      • A thread opened from a link stays in its place in the list instead of dropping into Quiet. #3407
      • Sidebar: the Tags and Agents header buttons show when you hover the header, like its arrow. #3395
      • Linked machine updates: Try Again no longer shows "The update didn't install" while the update is working. On touch, a quick second tap on the face picker no longer picks a face by mistake. #3446
      • Guided reviews: End and Home no longer load files halfway down, and Collapse all works after switching views. #3366, #3467
      • Agent text. A session started from the Inbox is told on its first turn that you read the Inbox. Agents get eleven short lessons from the owner (for example: open a prototype and click through it before sending it). When an agent names a PR that is on no thread, the send's result suggests attaching it. #2999, #3436, #3435
      • The Board across linked machines. With the Board turned on, it shows the cards of every linked machine in the same lanes, and each action on a card goes to the machine that holds it. #3341
      • For people who already turned on code review in the Inbox: the Pull requests board spans linked machines, picked PRs can start review threads, the stack page can open a range of layers as one diff and marks what changed since you looked, the next review round asks only for what changed, and a review note no longer widens a wrapped diff on a phone. #3392, #3396, #3398, #3432, #3431, #3170 by @robfeldmann
      • Site and docs: plannotator.ai/llms.txt is now a short index that leads with the Inbox, the Inbox install prompt gives each agent its own steps, OpenClaw installs from npm (openclaw plugins install npm:@plannotator/openclaw), plannotator inbox --help has two lines corrected, the README has a new Inbox picture and a shorter top, and the end of the Inbox page now offers the install prompt first. #3379, #3382, #3374, #3384, #3465, #3474, #3479, #3478
      • Groundwork with no visible change: the thread pane as a self-contained part #3450, #3464
      • Test and CI upkeep: #3457, #3215 by @rudycelekli, #3399, #3211, #3459, #3421, #3420, #3419, #3439, #3406, #3481

      Install / Update

      macOS / Linux:

      curl -fsSL https://plannotator.ai/install.sh | 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

      • fix(review): a named directory is reviewed even when the shell exported GIT_DIR in #3377
      • OpenClaw: install from npm (site and plugin README) in #3374
      • llms.txt: route agents, Inbox first in #3379
      • Markdown: keep an author's text colour in #3378
      • Phone and iPad: the comment card stays above the keyboard in #3380
      • Inbox: leaving a phone's full view no longer swaps the thread's tile buttons in #3371
      • Guided review: End and Home stop mounting files halfway when the scroll stalls or the observer lags in #3366
      • Inbox: let a trusted local app frame the window (inboxFrameAncestors) in #3376
      • Inbox frontend foundation, step 1: one cache for the open thread in #3103
      • Inbox window: data layer step 2 (half the requests, Send shows at once, list in the cache) in #3115
      • Inbox window: an arriving message draws its own body only; first break-up of App.tsx and Thread.tsx in #3123
      • Inbox window: check the held copy against a fresh read (random sequences, and after every browser spec) in #3211
      • Inbox prompt: each agent's own steps, and a Supported agents link in #3382
      • inbox --help: two lines brought up to date in #3384
      • Inbox Board: one Board across linked machines in #3341
      • review: a sole folder name that is not there stops with a clear error in #3387
      • Inbox: one PR board across linked machines in #3392
      • fix(review): Mod+Shift+Enter opens the note composer, it no longer posts by @rudycelekli in #3210
      • Claude Code mod: a turn that starts before session.start finishes keeps the Inbox link by @uvw in #3370
      • Inbox tags: Add tag's field keeps focus while typing; same-millisecond tags keep their order in #3393
      • Fix table header shifted one column right when the table is indented under a list item by @BenNewman100 in #3314
      • Inbox: settings known before the first row on load; equal settings redraw nothing in #3386
      • Cloud agents use the whole Inbox, like a local agent in #3306
      • Tests: the snooze tests restore the time zone they started in in #3406
      • fix(pi): point Electron TLS warnings to the host app by @jiangjiang248 in #3351
      • Inbox sidebar: Tags and Agents header buttons show with the chevron in #3395
      • ci: run the Claude Code mod's engine-harness tests in #3399
      • Inbox: a thread opened from a link is looked at after the first list read lands in #3407
      • Cloud agents send files up to 100 MB in pieces in #3318
      • fix(review): a remounted decision control does not reopen the note composer in #3403
      • Inbox: a question's prototype can be a public https page in #3319
      • Inbox: tell a launched session where the person reads, on its first turn in #2999
      • Prefer human-prompt replies in OpenCode annotate-last by @xunguangzlj-cloud in #3358
      • Inbox: colour rows by tag, with a Show tag colors switch in #3402
      • Claude Code mod: a T3 thread is the process with T3's t3-code tools in #3381
      • Inbox: wake T3 threads (Claude and Codex) through t3 thread send in #3375
      • Inbox: every file a message names opens in the viewer, attached when commented on in #2875
      • Inbox: archived threads as a group in the thread list in #3404
      • Inbox T3: the waiting line shows at once, and the row says what the thread says in #3412
      • Inbox: pick threads and act on them at once, Tidy with your words, Combine in #3405
      • Inbox: a new Combine/Tidy key after a refusal; cap tag colour times at now in #3418
      • Inbox Archived: fix the two-machine test's same-millisecond tie (main's unit-2) in #3419
      • Inbox T3 test: hold the wake's send in flight while the mod polls in #3420
      • Inbox: swipe a thread row to mark it read or archive it in #3135
      • Give the thread-state model test a budget it fits in in #3421
      • Inbox: Pin in an attachment's menu; "Update {name} yourself" in #3424
      • Inbox: step a thread's files on an iPad with a bar and a swipe in #3425
      • Inbox: stop losing the person's words (Take back, dialog backdrop, dictation) in #3426
      • Inbox: every phone bottom sheet fits the screen (the thread's ⋮ too) in #3433
      • Inbox and sessions through your own Cloudflare Tunnel and Access (opt-in) in #3388
      • Inbox: ask a repeated file question once; refuse choices that read the same in #3422
      • Inbox: the next review round asks only for what changed in #3431
      • Inbox tags step 2: header tag line, Tag filter, tags in Search, Board-off preview in #3397
      • Inbox agent text: the owner's lessons for agents in #3436
      • Ended-reply test: let the disposed wake's last poll land before the clock moves in #3439
      • Inbox: name unattached PRs (bare #N too) in send_message's result in #3435
      • Inbox stack page: Layers i–j as one diff, and changed since you looked in #3432
      • Routines: run a saved prompt on a schedule, on this computer in #3409
      • Inbox: a T3 Code group in Settings → Agents in #3438
      • Inbox: let people click and navigate inside an agent's prototype page in #3162
      • Inbox PR board across machines: say what the window check stops, pin the gh routes, test merge in #3396
      • Inbox: reply files keep the order the person picked them in in #3441
      • Inbox: Antigravity, with a wake in #3390
      • Inbox PR board: Start review thread for picked PRs in #3398
      • Antigravity page: say the IDE is untested in #3444
      • Inbox: a cover while recording posts nothing again in #3445
      • fix(dsh): a typed Windows path reaches the review whole by @rudycelekli in #3214
      • Inbox reply picker: show each session's title on a computer (finishes #3343 by @sx4im, with their commits) in #3447
      • Guide viewer: a link's URL keeps its own closing paren by @rudycelekli in #3213
      • Inbox: thread header shows its PR button when the read after a change fails in #3451
      • Inbox: reply to a brand-new session when the one that asked has ended in #3442
      • fix(inbox): a closed note or a folded thread no longer widens a wrapped diff past a phone by @robfeldmann in #3170
      • Fix nine flaky tests, the machine update's false "didn't install" and the face picker's early tap in #3446
      • Inbox: Agents list keeps a fixed order, marks who waits on you, names by one ladder in #3448
      • fix(shape): return 400 for malformed percent-encoded shape paths by @sx4im in #3414
      • Inbox: the reply picker names an unnamed session by its agent, not its first thread in #3454
      • Add a rolling three-day Inbox update filter by @rudycelekli in #3401
      • Inbox: the thread pane as a self-contained slot, keyed by pane (no visible change) in #3450
      • ci: three path gates skipped PRs that break the job they gate by @rudycelekli in #3215
      • Malformed path escapes answer 400 in the review servers and the Inbox in #3456
      • Fix forward: option card on a phone and the row badge hover (main red) in #3459
      • README: a new Inbox picture (desktop and phone) in #3465
      • Open in: JetBrains IDEs, at the line by @mvanhorn in #3372
      • install.sh: download the binary from PLANNOTATOR_RELEASE_DOWNLOAD_URL by @rudycelekli in #3310
      • Inbox: tag and recipient pickers escape the reply box scroll region by @sx4im in #3440
      • Inbox: each pane opens and reads its own thread in #3464
      • Annotate: a config.json key for the default view (Wide, Focus or Edit) in #3463
      • Plan and annotate: optional source line numbers beside each block by @mvanhorn in #3373
      • CI: run an affected slice of browser specs on each PR (#3455) in #3457
      • Updates run at low priority, so the Inbox stays quick while one downloads in #3466
      • Keep machine state out of config.json (#2852) in #3458
      • Guide viewer: Collapse all works after switching views in #3467
      • Loopback requests ignore a proxy; a classic plan review exits when its parent is gone in #3461
      • Claude Code mod: Orca chat gets the tools and the wake; no Plannotator plan review in Orca (#3325; includes #3400 by @rudycelekli) in #3460
      • Inbox: keep a sleeping machine's projects in New message in #3468
      • README: Inbox section moves up; Annotate HTML below Herdr Annotate in #3474
      • Inbox page: the ending offers the install prompt first in #3479
      • Open in test: the macOS expectation for a JetBrains app at a line in #3481
      • README: shorter top, AI built in below Commands, one short Sharing section in #3478
      • fix(inbox): a short group/project!45 lands on the project's own GitLab, never gitlab.com in #3525

      New Contributors

      Contributors

      @rudycelekli sent the most work from outside the project in this release, in his first contributions. He made Mod+Shift+Enter open the note composer in code review instead of posting (#3210), kept typed Windows paths whole on DeepSeek Harness (#3214), fixed links with parentheses in the guide viewer (#3213), added the Last 3 days filter (#3401), made install.sh download the binary from a mirror (#3310), and fixed three CI path gates that let breaking changes skip the job meant to catch them (#3215). His Orca work (#3400) ships inside #3460.

      @mvanhorn added source line numbers to plan review and annotate (#3373) and JetBrains IDEs to the Open in menu (#3372).

      @sx4im made his first contribution: session titles in the reply picker (#3343, finished in #3447 with his commits kept). He also fixed the tag and recipient pickers that the reply box cut off (#3440) and malformed addresses in the Shapes routes (#3414).

      @robfeldmann found and fixed a wrapped diff that jumped while he reviewed on his phone (#3170), with recordings from a real iPhone. First contribution.

      @xunguangzlj-cloud made OpenCode's annotate-last open on the reply to your own prompt (#3358). First contribution.

      @jiangjiang248 made Pi's TLS warning point to the host app when Pi runs inside Electron (#3351). First contribution.

      @BenNewman100 fixed the header of a table indented under a list item (#3314).

      @uvw reported and fixed the Inbox tool going "not connected" after /bg on a busy Claude Code session (#3369, #3370). His fix also made the Claude Code mod's test harness run on Windows.

      Community reports and requests that shaped this release:

      • @zane668 asked for Last 3 days (#3301) and coloured text in Markdown (#3345), reported the Inbox slowing down while an update downloads (#2788), and kept digging into leftover Inbox processes (#3350), which turned up the proxy and plan review fixes
      • @robsonpeixoto asked for a config.json that works in dotfiles (#2852)
      • @de-tre asked for source line numbers (#1650)
      • @ninjz asked for the Inbox tools in Orca (#3325)
      • @jroquejr asked to embed the Inbox in a trusted app (#3299)
      • @navin-moorthy reported that install.sh ignored the download mirror for the binary (#3298)
      • @llwt reported the cut-off pickers in the reply box (#3427)
      • @brunnojob reported malformed addresses crashing the Shapes routes (#3411)
      • @marwashan reported annotate-last opening on replies to plugin messages (#3312)
      • @xueccci reported the TLS advice Electron users could not act on (#3346)
      • @JasonLandbridge asked for more editors in Open in (#3368); the JetBrains IDEs are a first step

      Full Changelog : v0.28.65...v0.28.66

    8. 🔗 HexRaysSA/plugin-repository commits sync repo: +2 plugins, -1 plugin, +8 releases, -2 releases rss
      sync repo: +2 plugins, -1 plugin, +8 releases, -2 releases
      
      ## New plugins
      - [IDAAutoTheme](https://github.com/baiguqing/idaproautotheme) (1.0.1)
      - [ida-discord-rpc](https://github.com/reversedcodes/ida-rpc) (1.3.0, 1.1.0)
      
      ## New releases
      - [SigMaker](https://github.com/mahmoudimus/ida-sigmaker): 1.17.0
      - [btf2ida](https://github.com/nightshift-labs-ai/btf2ida): 0.1.23
      - [cfiscope](https://github.com/nightshift-labs-ai/cfiscope): 0.1.20
      - [ida-mcp-bridge](https://github.com/eitapreulajhol/ida_mcp): 0.4.1
      - [memlens](https://github.com/nightshift-labs-ai/memlens): 0.3.28
      
      ## Changes
      - [memlens](https://github.com/nightshift-labs-ai/memlens):
        - removed version(s): 0.3.3
      
      ## Removed plugins
      - IDA-Discord-RPC
      
    9. 🔗 Rust Blog Enabling the parallel frontend on nightly rss

      TL;DR: We are enabling the parallel frontend of the Rust compiler on nightly by default, to find remaining issues in preparation for its stabilization.

      Context

      The Rust compiler has been using multiple threads to compile code in its "backend" part (using LLVM) for a long time. However, its "frontend" part (which includes type checking and borrow checking) has been executing sequentially, on a single thread, which of course limits the performance of the compiler. If you are interested in a more in-depth explanation of parallelism in the Rust compiler, see this previous post.

      The compiler frontend actually had support for running in parallel for a long time, but it was not enabled by default due to various issues. Three years ago, we made it possible to opt into the parallel frontend on the nightly channel, with the plan to stabilize it in 2024. Clearly, we did not achieve that goal, but work on the parallel frontend was still slowly progressing in the meantime.

      Last year, Vadim Petrochenkov, together with several other contributors, started a coordinated effort to finally get the parallel frontend over the finish line. Since then, many long-standing issues were fixed, and its performance was improved. Now we are at a point where we would like to make it widely available. But before that, we want to find out if people encounter issues with it in the wild, which is why we are enabling it by default only on the nightly channel. Once we will be confident enough that it is working well, we want to stabilize it.

      The parallel frontend has been enabled on the nightly channel by default since nightly-2026-11-14.

      Benefits

      The primary benefit of enabling the parallel frontend is, of course, faster compilation of Rust programs.

      We benchmarked the parallel frontend in our benchmark suite, which measures the duration to compile the leaf crate in a crate graph. As usual, the results were varied. In some benchmarks, the parallel frontend barely helped. In others, for example when performing a cargo check of the nalgebra, cargo or diesel crates, the compilation was almost three times faster, using 8 threads.

      In the table below, you can find the aggregated wall-time mean change for the real-world benchmarks in our suite, when building a single crate from scratch across several configurations, compared to the same build using a sequential frontend.

      Frontend threads / Profile| check| clippy| debug| opt
      ---|---|---|---|---
      2| -21.95 %| -20.74 %| -14.2 %| -12.51 %
      4| -37.99 %| -36.01 %| -29.14 %| -23.67 %
      8| -44.23 %| -41.76 %| -36.1 %| -27.88 %

      It is clear that the parallelization is not perfect, and we definitely plan to invest more effort into improving its performance. Nevertheless, with 8 threads, it can make the end-to-end compilation time of cargo check ~2x faster for several crates that we tested, which is still quite an improvement.

      The performance benefits for incremental rebuilds are much more modest, and also very hard to compare, because the performance of rebuilds depends on what was changed and how were the codegen units laid out. In our benchmark suite, we saw a mean improvement of 3-5% for incremental rebuilds. But we currently do not have great benchmarks for this use-case, so your results might vary.

      We can also zoom in on an individual crate. Here is a chart of how the wall- time scales when compiling the nalgebra 0.33 crate, for a full non- incremental build (full), full incremental build (incr-full) and an incremental rebuild (incr-patched) across several build configurations:

      Nalgebra benchmark results

      What is interesting to note is that enabling the parallel frontend can actually also make the backend faster, for reasons explained here.

      It is important to note that all benchmark results presented above measured only the compilation of a single crate. When compiling a whole crate graph, your CPU cores might already be saturated because of backend (LLVM) parallelism or by Cargo compiling multiple crates in parallel. So the final performance effect will vary heavily based on the workload that you are running, and on the number of cores that you have available.

      We also benchmarked cargo check end-to-end (checking the whole crate graph) on the cargo crate itself on a machine with 8 CPU cores. With 8 threads, it resulted in a ~15% end-to-end improvement:

      • 36.7s with 1 frontend thread
      • 35.1s with 2 frontend threads
      • 31.9s with 4 frontend threads
      • 30.8s with 8 frontend threads

      As can be seen from the results above, when the CPU cores are already saturated with parallel crate compilation and LLVM, the positive effect of the parallel frontend is reduced.

      Tuning the thread count

      At the start, the nightly toolchain will default to the parallel frontend using only 2 threads. This is a conservative choice that should still allow us to find potential issues while not increasing memory usage a lot at the same time.

      If you want to test out the performance with different thread counts, you can override the number of threads used for the frontend using the --jobs- frontend compiler flag. It can be specified either in the RUSTFLAGS environment variable, or you can put it into a .cargo/config.toml file:

      [build]
      rustflags = ["-Zunstable-options", "--jobs-frontend=8"]
      

      Currently, the performance of the parallel frontend will likely not scale very well above ~8 threads, but you can try it on your workload to test what happens. Note that using higher thread counts will likely lead to higher memory usage of the compiler, and in extreme cases it might cause you to run out of memory.

      Limitations and known issues

      Due to the used parallelism, the produced order of diagnostics might not be deterministic when using the parallel frontend.

      In some situations, the generated binary might also not be reproducible, though we currently consider these cases bugs, and we would like to identify them and fix them.

      There are currently some known issues related to the reproducibility of the Rust compiler when using the parallel frontend, which are being worked on.

      How do I opt out?

      To reiterate: this is only being enabled on nightly for now. If you are using the stable toolchain, you will still be using the sequential frontend by default.

      If you want to disable the parallel frontend on the nightly channel, pass -Zunstable-options --jobs-frontend=1 to rustc, either via the RUSTFLAGS environment variable, or with the .cargo/config.toml configuration file:

      [build]
      rustflags = ["-Zunstable-options", "--jobs-frontend=1"]
      

      If you have to do this for some reason, please do tell us why on GitHub or on Zulip. We would especially like to know about any compiler crashes that you encounter, or the produced binaries not being reproducible when the parallel frontend is enabled.

      What's next?

      Over the next few months, we will be monitoring GitHub and Zulip for any reported issues about the parallel frontend. Once we have enough confidence that it is working well, and there are no major issues, we would like to move forward and finally stabilize it.

      We would also like to improve its performance, and make more things parallel. So far, a lot of the work on the parallel frontend has been focused on making it work correctly, rather than tuning its performance down to the last percent. We thus expect that we might still be able to make further performance improvements to it.

      We would also like to make more parts of the frontend actually parallel, as some parts are currently still sequential even if parallelism is enabled. There is some ongoing work on this. Last year, we had a Google Summer of Code project focused on enabling parallel macro expansion and name resolution, and there is also an open pull request for parallelizing the lowering of the Abstract Syntax Tree (AST) to the High-Level Intermediate Representation (HIR). More work remains to be done on this front.

    10. 🔗 Andrew Healey's Blog Introducing the World's Strongest Sokoban Solver rss

      Using agents to do state-of-the-art solver research.