- ↔
- →
- November 17, 2026
-
🔗 Hex-Rays Blog IDA 9.5: Introducing Native UEFI Firmware Support rss
-
🔗 gildas-lormeau/single-file-cli v2.27.0 release
SingleFile CLI 2.27.0
New features
-
New option
--load-deferred-content-expand-viewport: expand the browser viewport to the height of the document while loading deferred content, and restore it before the page is read. By default, the page is only made to believe it is that tall. This option loads the content of pages that measure the viewport in a way the emulation does not reach (e.g. an element sized with thevhunit). No zoom-out is applied unless--load-deferred-content-min-zoom-factoris set. A page that does not react to the restored size is saved with the elements it sized from the tall viewport.single-file https://www.example.com/gallery page.html --load-deferred-content-expand-viewport -
The unused CSS rules of the stylesheets found in shadow roots are now removed, they were always saved whole. On a Reddit thread with 240 comments, the saved page goes from 394 MB to 21 MB (gildas-lormeau/SingleFile#1514).
-
The deferred content is now also loaded on a page that keeps the document at the size of the window and scrolls an inner element. Such a page was saved with its first rows only.
-
An SVG file referenced by a
useelement is inlined in the page, the image was lost before.
CLI fixes and improvements
- Updated single-file-core to 1.14.1:
- a stylesheet containing
:is()or:where()with an empty argument list no longer makes the save fail with "Cannot read properties of null (reading 'data')" (gildas-lormeau/SingleFile#2058 by @alekssmitt) - with
--selected-elements-selector, the selected content is no longer saved as a blank page when it is displayed through the slots of web components (gildas-lormeau/SingleFile#2060 by @FvH01)
- a stylesheet containing
Co-authored by Claude (Claude Code)
-
-
🔗 backnotprop/plannotator v0.28.67 release
Follow @plannotator on X for updates
Missed recent releases? Release | Highlights
---|---
v0.28.66 | Pick several threads and archive or snooze them at once, combine picked threads into one; Tidy follows your own words, rows take their tag's colour; filter and search by tag, files an agent's message names open beside the thread, swipe rows on phone or iPad; list can show archived threads, Antigravity and Orca use the Inbox; T3 Codex threads get replies, Open in lists JetBrains IDEs, Routines: run a saved prompt on a schedule
v0.28.65 | Take back a reply your agent has not received yet, over Tailscale, Plannotator opens only for your own account, tag a linked machine's threads; one tag across machines, T3 Code threads get the Inbox with no setup, long threads open on slow connections
v0.28.64 | Installs and updates download a smaller, compressed copy, a Videos filter on the Artifacts page, GitLab comments on a whole file get their own thread, pull request pictures and videos show in the Inbox
v0.28.63 | Pair Grok Bot and other cloud agents from Settings, Hermes Agent, OpenClaw and Muse Code can use the Inbox, add a thread to Priority to keep it on top, tag threads, and find each tag in the sidebar, Pull requests board as a table, with bulk Merge
v0.28.62 | Agents started from the Inbox now work on Windows, pick a model and effort when you start an agent, rules for your agents, written in your own words, post a thread's decisions on its pull request, the Inbox loads faster on a slow connection
v0.28.61 | Updates now update the Claude Code plugin too, an agent's chosen face shows on every icon of it, filter the Inbox list by pull request state, Modern dark shows section bands and the Reply button, one conversation no longer shows as two agents
v0.28.60 | Click a word to highlight it, a one-time Themes dialog, Settings → Rows rebuilt, tell your agent how you want your rows, starred threads as pills above the list, a pill for new messages out of view, a half-circle face picker with ten Glass colours, a new phone sidebar and reply box
v0.28.59 | A quieter Agents section in the sidebar, machine names only when agents run on more than one machine, agent icons that are always gently alive and lean toward your pointer
v0.28.58 | Start Codex from New message, an Agents section in the sidebar, start an agent in a folder on any drive, play audio attachments and comment at a moment, Claude Code's Plannotator tools work on Windows
v0.28.57 | Pin artifacts, and see every artifact on one page, filter the list by project, date or agent, a thread shows its pull requests and their state, choose what the sidebar shows, and in what order, Ask AI starts from Side in the selection bar
v0.28.56 | Questions can show trade-offs and a prototype to try, a thread with many big pictures no longer crashes the tab, Escape closes New message and keeps your draft, read threads stop being bold and keep their place, agent messages that name no thread start a new one
v0.28.55 | Floating reply drafts, now a setting under Experimental, open questions sit next to Reply again, a comment box that keeps unsent comments as Drafts, choose how your list looks: Minimal, Balanced or Detailed, update an older linked machine from this InboxWhat's New in v0.28.67
TL;DR
- New: Drag threads to Priority, Archive or Quiet, or combine them
- New: Mention another thread in your reply
- New: Linear links show hover cards; add your key in Settings
- New: Agent icons made from the project name
- Changed: Pick any tag colour; turning a tint off keeps it
- Fixed: A linked computer's pictures, pages and files now open
- Fixed: Pull request cards say why they could not load
- Fixed: A review that can't load shows an error with Retry
v0.28.67 is a short Inbox release. You can now drag a thread row to sort it, hold it over another thread to combine the two, or drop it in your reply to mention it. Tags get a full colour picker, Linear links get hover cards, and a thread that lives on a linked computer now shows its pictures and opens its pages and nearby files. Two fixes protect you: the script in an HTML attachment can no longer move the Inbox to another thread, and a failed settings save can no longer empty
config.json. The release has 30 PRs. One of them carries the Linear hover cards by @Raj1v, their first contribution.Drag a thread to sort it, combine it or open it
On a computer, you can now pick up a thread row and drop it somewhere. While you carry it, three places show over the list: Priority at the top, and Archive and Quiet · Mark read at the bottom. A drop runs the same action as the row menu, with the same toast and Undo. Several picked rows move together, with one toast and one Undo. A place that cannot take the rows turns grey and says why, for example "Already in Priority" or "Already read", and a drop there changes nothing. Quiet still asks before it sets a question aside. If you cancel that warning, your picked rows stay picked.
Hold a row over the middle of another row for half a second to combine them. The row under the pointer reads "Combine with this thread". When you let go, the Combine dialog opens with both threads picked. It never combines on its own.
With Keep thread panel open on (in the list's ⋮ menu) and no thread open, the empty panel takes a dropped row and opens that thread.
Dragging needs a mouse, a trackpad or a pen with a fine pointer. Touch never drags: on a phone, the row's sheet and its swipe do the same things. An iPad with only its Pencil no longer announces rows as draggable, and connecting or removing a trackpad updates the rows at once.
Mention another thread in your reply
You can point your agent at another thread from the reply box. Drag a row onto the box, choose Mention in reply in the row's menu (also on a phone's row sheet), or paste a thread's link. The thread's title goes in as a token, and Backspace removes it whole. Several picked rows become several mentions. The sent message shows each mention as a link that opens the thread, and the mentioned thread itself does not change. Your agent gets each thread's title and id at the spot where you put it, and a short list of the threads you mentioned after your words.
Tag colours: any colour, and off keeps it
A tag's right-click menu in the sidebar now has two rows. Highlight rows is a checkbox that turns the tag's tint on or off at once. Color opens a picker in place, with quick swatches, your recent colours, a colour square, a hue strip and a Hex field. Turning a tag's highlight off keeps its colour, so turning it on again brings the same colour back. New tags go through all twelve swatches before any colour repeats.
A tinted row follows the colour you picked in every theme. On each built-in theme, its text is never harder to read than on that theme's plain row.
Linear hover cards
A
linear.app/…/issue/ENG-123link in the Inbox now shows a hover card, as GitHub and GitLab links do. It shows the issue's team, title, state, author, priority, project, labels, assignee, description, attached pull requests, the latest comment and Open in Linear. A bareENG-123in a message becomes a link whenENGis one of your workspace's team keys.To see details, paste a Linear personal API key in Settings → Accounts → Linear. Cards work right after you save it, with no restart. The key is kept in a private file in Plannotator's data folder, never in
config.json, and goes only to Linear. IfLINEAR_API_KEYis set and no key is saved, the row says "Using LINEAR_API_KEY". Nothing is fetched until you hover or tap a card.#3146, with the hover cards from #3063 by @Raj1v, closing #3120, which they also opened
Files on a linked computer open from here
When you look at a thread that lives on a linked computer, its files now work from this one:
- Markdown pictures show , and a link to a file next to it opens in the pane.
- An HTML page opens in its own tab , with its stylesheets and pictures. In the viewer beside the thread, the page's folder loads too, and a link to a page next to it opens in the pane. Large pages open as well.
- Open in shows only what works from here. The editors, Default app and Finder are not offered for another computer's file, so the "No attachment" errors are gone. Copy path copies that computer's path, and a picture still opens in a new tab.
Both computers need this version. An older linked computer still refuses these reads, and the picture stays broken as before.
Pull request cards say why they could not load
When the Inbox cannot get a pull or merge request from
ghorglab, the card in a thread and the link hover card now say which problem it is, with one next step. Before, they could only say "The Inbox did not answer."- gh isn't installed: a link to install it, and Try again.
- gh isn't signed in: the
gh auth login --hostname github.comcommand with Copy, and Try again. A refusedGH_TOKENis named. - gh didn't answer in 8 seconds, or GitHub asked for a short break (rate limited).
- gh can't see this pull request: Open on GitHub.
glab gets the same words for GitLab. A sign-in command only ever names github.com, gitlab.com, a host your CLI already knows, or your project's own host, never a look-alike host that a link named. Try again right after you sign in works at once.
Two safety fixes
- An HTML attachment's own script can no longer move the Inbox. Before, a script inside an attached HTML page could send the Inbox window to any thread with no click. Now only your own click on a link is followed. An HTML page from outside the project also gets no network in the viewer, as it already did when served by address. Annotate's HTML viewer gets the same protection. #3469
- A failed settings save can no longer empty
config.json. When the safe write (a temp file, then a rename) failed, Plannotator wrote straight intoconfig.json, and a full disk or a crash could leave it empty, so the next save lost every other setting. Now the old file is never touched: the save fails with the existing warning and your settings stay. On Windows, a save waits about two seconds for a program that holds the file.state.jsongets the same protection. #3473
Additional Changes
- The thread's title shows in its header bar , with its subject after it in a muted colour. A title cut short is a button: click or tap it to read the whole title. #3528
- Agent icons from the project name. Settings → Rows → Agent icons has a new choice, From the project name : a coloured tile with the project's letters, with the agent's mark as a small badge. It changes only agents with no face you picked.
plannotator inbox rows set agent-icons=projectsets it from a terminal. The default is unchanged. #3503 - The routine editor saves by itself. For people who turned on Routines: typing saves after a short pause, and the header says "Saving…", "Saved" or "Couldn't save · retrying". A new routine's draft is kept until it has a name and a prompt, even after a reload. Run once now saves first. The tip on the sidebar's and list's resize edges no longer covers a routine's name. #3558
- Docs: the README covers guided reviews and annotating a live site, shows the Workspaces picture in Sharing, and folds the long uninstall text. The HTML viewer's guide for host apps covers a host that loads the bridge by URL. #3554, #3524, #3531
- Code review shows an error with Retry when the diff cannot load, instead of a sample diff with no decision buttons. If the review server answered with an error, you can still send a note or close the review. #3573, for #940 reported by @digitalmaster, with diagnosis from @cschanhniem
- Groundwork with no visible change: page frame parts in
@plannotator/uifor host apps, and more of the thread pane work. #3540, #3562, #3528 - Test and CI upkeep: #3561, #3491, #3559, #3535, #3565
Install / Update
macOS / Linux:
curl -fsSL https://plannotator.ai/install.sh | bashWindows:
irm https://plannotator.ai/install.ps1 | iexClaude Code Plugin: The install script above also updates the plugin when
claudeis on your PATH. Otherwise, in a terminal:claude plugin marketplace update plannotator claude plugin update plannotator@plannotator --scope userThen restart Claude Code. Inside Claude Code, run
/plugin marketplace update plannotator, then open/plugin→ Installed → plannotator → Update now.Pi:
pi update npm:@plannotator/pi-extensionOpenCode: Re-run the install script above. It also clears the OpenCode 2 plugin cache.
What's Changed
- README: the Workspaces picture in Sharing; uninstall details fold away in #3524
- A failed settings save can no longer empty config.json in #3473
- CI: a docs-only PR skips the unit, DOM, package, smoke and Semgrep steps in #3491
- Inbox: Linear hover cards and the Linear key in Settings → Accounts (includes #3063 by @Raj1v) in #3146
- HTML attachments: a page's own script cannot move the Inbox; no network for pages from outside the project (port of #2511) in #3469
- HTML viewer docs: a host that loads the bridge by URL puts the load's key on the bridge's tag in #3531
- Pull request cards say why gh or glab could not answer in #3093
- Update lock tests: do not depend on how long the machine has been up in #3535
- Inbox: agent icons from the project name in #3503
- Open in: show only what works for a linked machine's file in #3536
- README: guided reviews and live site annotation in #3554
- Open a linked machine's HTML attachment in its own tab, with its folder in #3538
- Inbox: mention a thread in a reply (drag a row, row menu, pasted link) in #3526
- Inbox tag colors: a two-dimensional picker, and rows that follow the pick in #3553
- Inbox: the thread's title in its header bar, and thread pane groundwork (no visible change) in #3528
- UI frame: a reusable page screen for @plannotator/ui in #3540
- Inbox: drag threads to the list edges, onto another thread, and onto the empty panel in #3537
- Shared stream e2e (WebKit): wait for the takeover until the script runs out in #3559
- Inbox: a linked computer's Markdown pictures and the files next to it open here in #3557
- Inbox drags follow-ups: keep picks on a cancelled Quiet drop; drag help follows the device's pointers in #3560
- UI frame: follow-ups (author kind none, compared row name, README) in #3562
- Inbox: open a linked computer's large sibling page; document the window-only costs in #3563
- AGENTS.md: no AI attribution in commits, tags, release notes or PR bodies in #3565
- Inbox routines: the editor saves by itself and says so in #3558
- Inbox: internal groundwork, off in #3527
- Inbox: internal groundwork, off in #3556
- Inbox: internal groundwork, off in #3574
- Inbox: fixes from the release check: mention undo and editing, Linear key messages, small drag and tag colour fixes in #3576
- Run only what a PR's change can affect in PR CI in #3561
- Code review: show an error with Retry instead of the demo diff when the diff fails to load in #3573
New Contributors
Contributors
@Raj1v asked for Linear hover cards in the Inbox (#3120) and then built them (#3063): the card, its Linear states, and bare
ENG-123identifiers that become links. Their commit ships with its authorship kept inside #3146, which adds the Settings row for the Linear key. First contribution.Thanks also to @digitalmaster, who reported the code review failure in #940, and @cschanhniem, who traced its cause there.
Full Changelog :
v0.28.66...v0.28.67 -
🔗 HexRaysSA/plugin-repository commits sync repo: +1 plugin, +2 releases rss
sync repo: +1 plugin, +2 releases ## New plugins - [revengai](https://github.com/revengai/plugin-ida) (3.29.0, 3.28.0) -
🔗 OmniNull/OmniWM Canary 20261117-0117 (3b6c70c4) release
Automated canary build of
main. It is signed and notarized like a release but skips the owner review, so treat it as unstable.See the canary guide to install, update, or return to stable. For everyday use, download the latest stable release.
- Commit:
3b6c70c4900a - Base tag:
canary-20261113-0413-43363746835-1
Changes since canary-20261113-0413-43363746835-1
3b6c70cUse the runner's selected Xcode for CI645ffe4Update the live gesture fixture for the renamed setting9fef0a5Key CI build caches by the SDK environment847e092Avoid copying Undo snapshots for membership checks972ca6dMove trackpad-selected windows directly566a1aeUse native window gestures and live resizing by default5feec35Drag individual Dwindle group tabs across layoutsb770a06Continue native drags across Dwindle displays95d552dRearrange Dwindle tiles during native title-bar drags04f5383Restore transfers between Niri and Dwindle through history6a76508Restore Dwindle transfers through workspace historya4be70eAdd local Dwindle layout undo and redod6f083aExpand Dwindle splits from edge double-clicksc84fd28Support centered native Dwindle resizing550aaaeEnable native Dwindle resizing and title-bar fullscreen4fa55e2Carry Niri drags across display orientationseb3ed2fSupport native dragging on vertical Niri strips07bef51Support native width resizing and tab motion on vertical strips440531aSupport native primary resizing on vertical stripsa5690f5Support primary sizing gestures on vertical strips22028efSupport Peripheral Vision on vertical strips784cf08Honor Niri size controls on vertical stripsa080a47Capture only the changed workspace for an Undo step01955c3End a native edge resize when the button is released2e81cf7Split the last long functions and types SwiftLint flagged41569dbSplit the Niri layout pass's and the Undo step's long functions215fedbSplit the mouse handler's and the pointer barrier's long functions4eb26d9Split the live drag's long engine functions into named stepsf34c480Fix nine small SwiftLint findings in the Niri and mouse codef04e0f6Remove the macOS Fusion switch8d5dd95Build macOS Fusion's window lifecycle and commands into Niriacab06dBuild macOS Fusion's mouse behaviours into landscape Niri stripsdcfa0bdTick the minimum-width tests past the spring's last instant7d403d2Let Peripheral Vision follow its own percentagef6d0f7bGive Niri's kept sizes and strip ends their own settingsadc3448Build macOS Fusion's layout behaviours into Niri52fae6dKeep packed widths under the Peripheral Vision cap9464ec9Stop raising a moved column's windows94419c4Fit visible columns when Cycle Size resizes around the centre4e34498Learn minimum sizes while a size animates7531d00Preserve oversized minimum constraints when solving stacks457e435Keep learned minimum heights across a stack droped96945Leave Option on clicks that reach appsdbc7ea5Keep the user-action count on the controller23faa03Ask about the live drag once per layout diff, not twice per windowaa9decdTest the unannotated-drag checks where they are called356ed6eKeep the tap filter's inputs apart from the rest of the mouse statef7599a1Count user actions against the automatic undo0a12b26Let a running slide finish when the mouse is only pressed7e9d915Take the sleeps and far-off times out of the macOS Fusion testsa10f701Note a strip glide only for windows on a Niri workspace161fa79Start Peripheral Vision at 0%5db2967Honour Focus Clicked Windows Without Scrolling with macOS Fusion oncc5a3d4Keep a workspace's Niri arrangement when it switches to Dwindle33cd284Keep Balance Sizes resetting every column with macOS Fusion on8c3baafMerge pull request #1233 from nblopes/macos-fusione094ee8Settle a slow app's edge resize on its frame, not on quiet time085eedeKeep a stack overflow undoable until the user's next action, not 3 sb9a0a31Read settled frames from the animations' end, not 2 s ahead26910eaUse or drop a strip glide at the next layout pass, not after 2 s308e306Let a floating panel over a column's edge keep an edge double-click7e52406Show the CodeRabbit logo in Company Sponsorsd26c3f9Keep window widths with macOS Fusion only on landscape stripsff5cf37Glide a window into a Niri strip only on landscape strips9d782b7Check stack overflows again when a layout refresh ends30fdd70Undo a move between workspaces without undoing later changes there7532288Leave an edge double-click to the window on top of the edge7f0393eGive a title-bar press to the app when it doesn't answer in time8620f1aLeave a fullscreen or maximised column covering the screen after a scroll30ecd6cStop an edge resize at the peek with one display and mouse warp onbf77618Let a slow push at a display edge cross with mouse warp offf25c545Run the edge-resize tests with macOS Fusion's engine flagse2d5addFail the layout history tests when a frame is missing13ad585Start a predicted height spring from the drawn heightf8b8043Draw and hit-test a widening stack's window at the same framecb4f1c5Treat a frame wholly beside its display as outside ita0ef5d2Keep Undo and Redo from running during a mouse resize30df37fLet go of the edge-resize hold when the mouse handler stopsc0e9abcPull out the tab that was pressed in a tab railcd2e887Leave out a held tab that closed before a stack drop905c73aBring a carried tabbed column home whole when its hint is open20e09a5Keep the bar whole when a style changes its orientation1672a8cKeep scratchpad windows in last-used order across workspace switches53b1561Read the frontmost app last when scratchpad stacking checks readiness9774805Merge pull request #1222 from rickythefox/fix/light-bar-tinta01e534Merge pull request #1225 from rickythefox/feat/scratchpad-reveal-focus-recency895090cMerge pull request #1224 from rickythefox/fix/scratchpad-stacking-stale-frontmostf3fccb7Read a minimized window's slide at its start in the test65ab86cStretch a Niri column to the peek from a centred row7b1e44fGate the last macOS Fusion changes and finish the new translations6d3374cMeasure a partly hidden window's centre third on its visible partb0cfa9eStack without a height check and undo a step that makes a stack overflow2308fc3Read the trace's window bounds in one query per passc6bd79aStop an edge resize at the peek while draggingcbd086bGive a parked column a width change in one step38f8773Do less work per live drag event5984c26Remove the stack modifier: free-style stacking is the only way to stack6e0faceLand stack leaves, tab pulls and carries through the drop space1838fd5Decide each live drag update before applying it, with one drag session957a4d9Skip live drag work for ordinary drags and while no display can peek8ac188bRemove live drag code the app never runs with macOS Fusione17b3d6Run the live drag tests on the macOS Fusion setup the app uses64eb22cMove a narrow live drag landing along with each edge hop8a9ba43Bound the follow-up passes of a live drag updatee2aeab3React to a pause during a live drag while the window's place is closing391746eArm the stack mode lock when the modifier widens a stacking hint6606b33Open the stack mode landing gap between two stacked windows over the space between theme75c8f4Slide Niri columns into a minimized window's place with macOS Fusion844b4f3Focus the window taking a minimized Niri window's place with macOS Fusion7027cb4Hop the drop space gap by gap at the screen edges and stack tabbed columnsb99cbf8Close the gap a dragged Niri window leaves behind it6db60acDecide live Niri drops by the dragged window's top centre78e5c25Stack Niri windows from a window's centre and widen a narrow stack on dropd4240a6Rename the macOS Fusion settings to Drop Modifier and Peripheral Vision96b2abeRemove the Niri free-area drop and the lone window's resting placed785549Apply the Niri neighbour rule only while the home spot is beside itc2e0bb2Let a Niri drop follow the half under the pointer except over a neighbour06f38c2Fill Niri columns and close the gaps windows leave with macOS Fusion120077bToggle a Niri column's full width with a title-bar double-click424384cReplace Undo Resize with Undo and Redo per workspace4e0580aRun nothing new in Niri with macOS Fusion offed803d8Ignore Visible Containers in Niri with macOS Fusion on4c11cb8Cycle Niri widths backwards with a Shift-double-click on the title barcdfa7aaLet each display set its own Peek Widthb3981c0Give macOS Fusion its own section in the Niri settings6b6da25Rename Natural Window Drag & Drop to macOS Fusion1381620Hold a drag still only on a real title bar, not an app's own drawn onea555cb7Forget a workspace's Niri strip when Dwindle lays it out0116572Name the bare title-bar check972e217Share one centring rule for a Niri strip that fits on screenf061037Forget the strip a carried drag leaves in one placebb3fe65Leave the window-order and selection-scroll traces out of the drag feature874fab2Hold a drag still only on a tiled window's own bare title bar7b816eeKeep a window's own width when it enters a Niri stripfbfaae8Rescan a floating window's app when the app is shown againb476db9Bring a moved Niri column's windows forward with Natural Window Drag & Dropa7e89ccRescan a floating window's app when it comes back from the Dock11ae1cfScroll to a focused Niri window while OmniWM's own scroll is runningc117849Trace the Niri scroll that shows the selected windowcb4b80aOpen a new Niri column at the width its app opens the window with4ba43c0Centre a Niri strip whose windows all fit on screen7e79cfbHold a Niri title-bar drag still under a modifier OmniWM doesn't use1abeb1dTrace stack mode and modifier keys in live Niri dragsfb8ec5fUndo a kept edge resize first with the Niri Cycle Size keysea62efcSimplify live two monitorsab82066Fix review findings in live two monitors3fc61a1Carry a live Niri drag from a window alone on its displayb79ac7cUndo an edge resize of a Niri window with a key or a title-bar double-clickca03ae3Show Niri columns past an edge that only meets another display at a cornera05fe5bCarry a live Niri drag onto another display's strip26f2864Drop a stray blank line at the end of the Niri edge peek extensionb01770dApply peek setting changes only while Natural Window Drag & Drop is ondf5e13eNarrow a Niri strip's end column for the peek at whatever width it takes6435fb1Keep the Niri edge peeks when the view recovers coveragec19a508Fix retest findings in live edge peeka154343Simplify live edge peekc42dddeFix review findings in live edge peeke20bc5eKeep a peek at the next Niri column at each screen edgeb4079d0Start a Niri width cycle where the window's width is7280787Ask the strip-ends rule once in the edge stretchf16f2e8Pass the Niri strip-ends rule to the viewport as edge rules24f7ac1Share one strip-ends rule between the viewport and the live dragc9a7fb5Cycle Niri widths through the presets in the user's order1452343Keep the natural slide settle off vertical Niri strips68a9550Clear the tap filter's double-click flag when a reload turns Natural Window Drag & Drop off436c827End a Niri width cycle when the window has moved on screen5485087Bring a full Niri width cycle back to where it started79378f9Keep cycling Niri widths with single clicks and the Cycle Size keys09eefabSimplify live resize3150948Fix review findings in live resizecefe8d7Keep the gap at the Niri strip's ends after a free scrolla724475Tighten the Niri strip-ends rule and the stack give-way361daedResize Niri windows around their centre with Option-drags and title-bar double-clicks6827206Snap back a tabbed Niri column's top and bottom edgesc4ffad2Drop a Niri window onto empty screen past the strip's ends8c95a0fKeep a lone Niri window at the top or the bottom of its column64f7feaKeep a lone Niri window where an edge drag leaves it01a11d8Keep native edge resizes of Niri windows and slide the strip into placea14175aResize Niri windows by double-clicking their edges and title bar2c757cdTidy the stack-drop fixesa6eb1cbPass Natural Window Drag & Drop to the Niri engine as one configuration9977cf0Hold the edge zone a tab pull starts ina9d9633Finish a stack drop whose settle animation is stopped early2bbf47bGive the columns back their fit when a drag ends during a stack landing0b64548Finish a settling stack drop while another display has a live dragab6385eTake a window home from a stack to the slot it left0656033Hold back the drag modifier from a press whose event names no window8f03000Keep a dragged window's home column in the strip while its other windows are hidden67dbb82Leave the tap filter alone on a settings reload with Natural Window Drag & Drop off9bff34aGlide a floating Niri window into its slot when it becomes tiled0e3edb3Keep a Niri stack at its target column's width85434e6Simplify live stack mode49da7eaFix review findings in live stack modebecea2fStack, reorder and unstack Niri windows during a live title-bar drag40f02f5Test the home slot of a tabbed column with a hidden tabe88c26cFix review findings in live tabbed column2d06255Drag a tabbed Niri column as a whole by its title bara82da2dHop past each Niri window when edge-scrolling back toward the home spot472850cSimplify live edge scroll43691a6Fix review findings in live edge scrolla79e9caDon't edge-scroll a Niri drag that starts inside the edge zone until it's pushed toward the edgee7aa6dbScroll the Niri strip while a live title-bar drag holds the pointer at a screen edgef8002f7Let the right window of two make room for its drop space7d6e321Keep a lone tabbed window's home slot narrow while it is dragged35dd843Close the empty slot of a dragged Niri window under it as it moves2b1f6d1Fix retest findings in live column swap49e9a27Simplify live column swapd80c0dfFix review findings in live column swap5edf93dReorder Niri columns live while dragging a title bar3e5430cReveal scratchpad members in focus-recency order233cd94Keep scratchpad stacking going when the frontmost app lags activation9300315Keep keyboard modes paused during Secure Inputf03bb78Merge pull request #1214 from t1dotdev/secure-input-guard75de9deSay when removing a Launcher entry clears its shortcut361ef1dMerge pull request #1215 from t1dotdev/fix/launcher-removal-clears-shortcuta5f402aRebuild CI's Swift build cache from scratchbaa278fRefresh app palettes when their inputs changef413f7dPrepare app theme reviews on the worker1669580Keep requested app reload failures pending89197ccRoll back app theme outputs when state persistence fails4b6ead4Keep the app theming merge within the lint and catalog checksd56daceMerge pull request #1207 from OhNoIBrokeIt/feat/app-theming215337fBring the PR follow-ups back within the lint limits3890a48Derive the App Rule scratchpad tests' bounds from the code they test08efbabSkip scratchpad admission work for windows no rule sends to a slot0f2cc7eKeep a deferred rule apply when Unassign reveals nothing1238649Hide a scratchpad again when its last window is gone5d9a57cMerge pull request #1213 from rickythefox/feat/1199-app-rule-scratchpad3d00300Morph Celestial's gauge bands along their ring5890461Lighten the workspace bar tint in light mode83589fcMerge pull request #1212 from hezhizhen/codex/fix-path-arc-morphdca6722Keep shrink-to-fit off the resize path unless it is on342787aSplit the rule re-evaluation retry out of resumeAdmissionRetry5c84bffResolve a rule-apply retry's context when it runs, not when it is dispatched7d622dfLet a manual scratchpad assign or release win over a deferred rule applye97d02aAddress hezhizhen's review on App Rule scratchpadsd470c0fLabel the App Rule scratchpad toggle Assign to Scratchpad1ed505bKeep a scratchpad member parked until rule apply can admit it elsewhere2292642Ask the app which window is focused when a scratchpad member arrives078af3fAddress review on App Rule scratchpadscdb7dd3Join windows to their App Rule scratchpad when OmniWM admits them262e952Add a scratchpad destination to App Rulesfbdcc07Keep a scratchpad revealed when its last window closes215b06fMerge pull request #1216 from hanswug/feat/niri-shrink-to-fit-keyboard92b7111Offer Visible Workspaces only when it adds to the active workspace6499507Merge pull request #1211 from hezhizhen/codex/fix-window-switcher-scope-cycle3e2cef4Morph SVG arcs along their ellipse15b858dTest that shrink-to-fit changes nothing when even the minimums can't fit1c6bec5Clear a stale shrink-to-fit width on the axis it was made forbd7aeb9Start app theming before the window management checks886b08fGive every backup its own file17529ceSkip a queued app whose settings changed since its run was queuedb64c684Undo a Ghostty config edit when a later file can't be replaced9e7c6e3Restore an app's earlier files when a later one can't be replaceded664afPlan one Ghostty config edit per file, however it is reached6df1cecMove trackpad gesture availability beside gesture validation7907f8dClear an app's shortcut when its last Launcher entry is removed117ca8eLet users turn off OmniWM's Secure Input pauses9dc820bSay what shrinkToFit leaves to the next keyboard resizeb7ce12bFit only Visible Containers columns on a keyboard resize05e096aAdd an opt-in setting that shrinks visible Niri columns to fit4652845Format the round's changes and keep the run within the lint limitsd2a3972List Neovim in the README and name two engine test counts8119469Work out the settings page's paths and Ghostty status on the worker50ded6bResolve the allowed and protected folders once per run3f69a18Read each Ghostty config once before the check in the writer7253e9dName the saved machine command timeoutsbd89429Remove the command failure helper nothing calls2e5dd2cBuild the target list once when the service starts1cd642bTake the stored results from the run instead of reading them on main1f01960Keep the app theming strings below the catalog's first entrya6854c7Format the round's changes and keep the engine within the lint limits17be5bfFind herdr's socket in the folder app theming writes herdr's config to6b6e77dRefuse a dangling output link instead of replacing ita9fbff5Bound a herdr request with one deadline7301008Stop a run's work for an app turned off while it runs0062b39Compare the file inside the writer right before the rename1dd056aTell the running Ghostty's version from files unchanged since it started65f4dcbSignal a process only while it is still the one that was listede76d56cKeep Visible Workspaces in the two-monitor scope cycle5501041Keep the new herdr row string with the other app theming strings9aa0854Update the string catalog for the Swift reloadsa9e1410Format the new app theming code and keep it within the lint limits12d46d6Name the hue turn in the terminal color tests66c1980Remove the source comment from AppThemeANSI2673e09Derive the terminal color test tolerances from AppThemeANSI4f1212aBound the command output test with failureBoundd7df469Compile the headless Neovim tests only for live checks881a5b4Refuse two outputs of one app that resolve to the same file8c3c959Treat only a missing file as missing9a65f6eWrite the Ghostty theme selection under the run lock with its exact bytesd828cb1Check each file again right before replacing it4ab99d6Reload each app once per run98838c4Fail a saved machine command whose output did not finish3407eb9Build custom herdr targets from the saved machines setting0985c17Reload local herdr through its socket APId2cf9f7Signal kitty and Neovim from Swift instead of pkill577108dReload Ghostty with SIGUSR2 instead of AppleScript84d1af7Drop queued work for an app turned off before its run9793861Create the app theming service only while an app is on0b5aee9Return before building the palette when no app is ond342b91Follow light and dark through one effectiveAppearance observer1284435Hand app theming runs to injected queue hops83fca24Bind a takeover to the reviewed bytes and back up inside the writea5b214dSplit the app theming run to keep it within the lint limits82cf81aMake custom herdr reloads follow reloadSavedMachinesb68c81dTell older kitty to restart for newly created theme filesae23124Leave another Neovim colorscheme alone on reload5314b56Keep app theming backups private55494bcKeep a reload command's whole output21cb1dcReload the Ghostty Quake terminal after a forced Ghostty reloade0db184Let only one app write each output filee428bd9Refuse to replace an existing output that is not UTF-8 textd366922Treat an unreadable existing output as a failure, not a new filee22aa4dTheme Ghostty, kitty, herdr, Neovim and custom templates from the palette
- Commit:
-
🔗 Filip Filmar DDR3 memory for a TxHDL design, with a controller we did not write rss
The Vreteno RISC-V processor originally executed out of 4 KiB of block RAM. In contrast, the Alinx AX7A200 FPGA board provides one gigabyte of external DDR3 SDRAM. Designing a custom DDR3 PHY and memory controller requires extensive calibration circuitry. Rather than rewriting this complex infrastructure, we integrated the open-source UberDDR3 controller into a TxHDL SoC design as a foreign module. This post describes foreign module integration, board simulation with Micron memory models, and synthesis status.
-
- November 16, 2026
-
🔗 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,--disallowedToolsor--toolsvalue 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.jsonduring a session - Added a row to
/statusthat says when your provider or an environment variable such asDISABLE_TELEMETRYturns features off - Added a note in
/pluginandclaude plugin listwhen a malformedplugin.jsonfield such asauthororhomepageis 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 stopfooter hint in a subagent's view where Esc would stop it - Added
OTEL_RESOURCE_INCLUDE_HOSTto includehost.nameandhost.idin OpenTelemetry resource attributes (off by default) - Added
overflowX="scroll"on a mod'sBox, andmaxLinesandwrap="clip"on itsText - Fixed
cpof a file being refused when only its source was covered by anEditdeny 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
/permissionsor at a main-conversation tool prompt, and/add-dirfolders, 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
/netand 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_decisionevent orpermission_denialsentry when they refused a direct tool call - Fixed letters typed over
/sandboxor a delete question in/permissionsmoving 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 purgehiding 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
/rewindrestoring only some files after running/branchtwice while a slow backup copy was still running - Fixed
/rewindsaying "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
/skillsquitting 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
/feedbackand/bugsending 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,--allowedToolsor 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_tokensexceeded the model's limit: Claude Code now retries the request with the maximum the Anthropic API reports - Fixed
grepin 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 clearor a new/goalnot 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;
/recapstill 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
/loginreplacing your Claude subscription login when the browser sign-in used your Claude plan instead of a Console organization - Fixed
/loginending on "Login successful" while an approvedANTHROPIC_API_KEYwas 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",/loginand/statusnow name an unusedANTHROPIC_API_KEY - Fixed
claude auth logoutleaving 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
forceLoginOrgUUIDandforceRemoteSettingsRefreshstartup errors telling you to sign in again when a network block page (HTTP 403) was the cause - Fixed
claude auth loginnot showing a pasted sign-in code, so a wrong paste couldn't be seen or corrected before Enter - Fixed
/loginandclaude setup-tokenshowing 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
/logoutin 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-settingstoggle 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-settingssaving your choice on the wrong account after signing in to a different account in another terminal - Fixed
/privacy-settingssaying "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.calland$.tool.checkin 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
anyOforoneOfshowing Claude only the first branch's form of an argument; text such as42can 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
/mcpnot 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
/mcpshowing no progress for a slow server, and a second Enter disabling it again - Fixed
claude mcp add-jsonanswering 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
cto copy an MCP sign-in URL leaving a straycin 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-controlbeing 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-runnerasking for new tokens nonstop when a refreshed token was already due, such as when the machine's clock runs ahead - Fixed
/autofix-prreporting a run as cancelled when its cloud session could not be stopped; it now links the session so you can stop it - Fixed
/teleporthiding a session from its list in narrow terminals - Fixed artifact publishing refusing files in a background session's temporary folder
- Fixed subagents whose
disallowedToolslistsArtifactstill 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
/tasksnames 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 --worktreeshowing 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_PROXYis the only proxy set and the proxy never answers; they now fail after 25 seconds - Fixed the
/menu,/skillsand/pluginrepeating rows and losing the cursor when two skills or commands in one place share a name - Fixed search in
/resume,/plugin,/permissionsand/configignoring IME input, dictation and fast typing - Fixed the cursor disappearing after clearing a search on the
/pluginInstalled tab - Fixed a mod's
Textwithwrap="truncate-end"losing rows on the terminal when it holds a line feed - Fixed
/modelshowing 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 --helpand 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 defaultin a long conversation, or when thetuisetting 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/**/*.tsor2*3*4 - Fixed
claude -pshowing 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
.claudeor_build - Fixed bold text showing as raw
**in Japanese, Chinese and Korean replies when it starts or ends with punctuation - Fixed
/memoryopening 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
/btwshowing 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
/btwanswers looking finished and ignoring PgUp, PgDn, Home, End and the mouse wheel - Fixed
/resumesearch 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:submitkey 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
qnot working in a pager thatclaude --helpis piped to, as inclaude --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-passthroughon), or to iTerm2 over SSH, on the default setting - Fixed
/copyand/exportsaying "copied to clipboard" over SSH when the terminal may not have copied anything - Fixed
/usage-creditssaying "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,
/clearor/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 defaultsaying it had switched back to the classic renderer when a setting kept fullscreen on; after a/tuithat 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
/configapplying 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-setupnot 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 attachor--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,
/cdor/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 logspainting 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 --resumesession 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
/statusshowing 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
ghrefused 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
/plugininstall choices being cut off in short fullscreen windows - Fixed the
/contextgrid, 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
/usagebars looking full in the light and ANSI themes - Fixed the
/effortslider 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
@undefinedwhen 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
/permissionssearch 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
/logoutandclaude auth logoutin 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
/compactin 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
updatedInputis 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-configin 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_batchcall now has 150 seconds to answer, up from 90, so fewer finished results are lost - Improved
/doctorto share findings as it works instead of staying silent until the full report - Improved the error for a settings or
.mcp.jsonfile 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_TELEMETRYto say why instead of "Unknown command" - Improved the
CERT_SIGNATURE_FAILUREconnection 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
/logininstead 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
/loginscreen: 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-appand 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
ccopies it - Improved
/pluginDiscover 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
/pluginMarketplaces and Add marketplace: a compact list, a clearer remove confirmation, a clear text field and shorter errors when adding fails - Improved
/pluginInstalled tab: Home, End, PgUp, PgDn and clicks now work, and hidden rows are counted - Improved
/pluginErrors 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,doctorandauth logoutoutput 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,/powerupandclaude --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/hooksand/permissionssay Esc goes back - Improved text fields in
/add-dir,/export,/permissions,/feedback,/install-github-appand 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,/resumeand/modelto 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
/permissionssays 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 subagentwhile 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
/autocompactand/scroll-speedwith a slider that shows every value, takes Home, End and (in fullscreen) clicks, and fits narrow terminals - Improved on/off settings to read
on/offin/config,/memoryand 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;
disableAutoModeturns 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.jsonadded 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
defaultModeonce 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
/sandboxor/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.allowWritein user or managed settings - Changed the Bash sandbox to set aside unexpected entries in a repository's
.gitfolder after a command - Changed the Bash sandbox on Linux and WSL to create some missing
--add-dirfolders 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 serveto ignoresandbox.excludedCommands - Changed
/rewindon 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
cpandmvcommands 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
ExitWorktreeto refuse removing a worktree while a background subagent or shell command may still be running in it, unless Claude passesdiscard_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.environmentlist 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-dirand/add-dirin local terminal sessions to show the trust prompt for a folder you have not trusted yet;claude --bgrefuses such a folder - Changed self-hosted runners under
--trust-workspace falseto 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.jsondisplay field: they now load, with their hooks and MCP servers; administrators should check the plugins they deploy - Changed how
allowedHttpHookUrlsandhttpHookAllowedEnvVarsapply to hooks from managed settings - Changed HTTP hooks to ignore
Content-LengthandTransfer-Encodingin theirheaderssetting; 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
/pluginuninstall, remove and switch questions to lists answered with the arrow keys and Enter, or Esc to cancel;y,nanduno 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.countcan 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
--baresessions on an unapproved API key: moving one to the background is now refused in most setups, andclaude --bare --bgexits 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
--verboseto go to~/.claude/child-logs/ - Self-hosted runner: Changed Linux and macOS sessions with no
ghto get a built-ingh apiby default, via Anthropic, which adds their GitHub sign-in, if any;--use-anthropic-gh falseturns it off - Changed agent view so that quitting with Ctrl+C twice, Ctrl+D twice or
/exitafter pressing←in an empty conversation ends that session, instead of leaving it running for 5 minutes - Changed
--await-initializeto be refused with--bgor--worktree --tmux, which never read the initialize request, instead of starting without the fields it carries - Changed worktree creation,
/teleportand IDE checkouts to run git with a stricterPATH; 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-apiskill to build agents on Managed Agents by default, unless you want to host the agent loop yourself - Changed
/usagein fullscreen mode to show plan limit bars before session cost for subscribers;/coststill starts with cost - Changed the wording of some messages that
claudesubcommands print; JSON output is unchanged - Changed first-run setup to preselect the "Auto (match terminal)" theme instead of Dark mode
- Changed fullscreen
/cdto 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 onin fullscreen; the wheel scrolls without it - Removed the spinner tip that suggested
/clear30 minutes into a running turn - [VSCode] Added a
claudeCode.promptSuggestionssetting 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
.gitfolder 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
/idein 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
claudecould 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
-
🔗 HexRaysSA/plugin-repository commits sync repo: +1 release rss
sync repo: +1 release ## New releases - [kflow](https://github.com/nightshift-labs-ai/kflow): 0.0.5 -
🔗 @HexRaysSA@infosec.exchange A few of our team members will be in Tokyo at mastodon
A few of our team members will be in Tokyo at @codeblue_jp on 17 & 18 November, ready to talk about all things IDA.
Want to meet up? Email us at marketing@hex-rays.com and we’ll help you find us.
-
🔗 r/LocalLLaMA The beginning of the becoming of the beginning begins rss
| submitted by /u/Subulicious
[link] [comments]
---|--- -
🔗 SparkFun Tutorials How to Build a Remote GNSS CORS rss
How to Build a Remote GNSS CORS a Available online at:
What's a CORS?
For high precision GNSS to work you need a base/rover system. In the simplest terms this means you need a GNSS receiver sitting stationary and transmitting its corrections every second up to the internet. A CORS, or continuously operating reference station, is a field hardened GNSS receiver to maximize uptime. These reference stations are scattered over large swathes of land, generally positioned 30 to 50km apart to provide rovers in the area with the most precise correction data with as few 'holes' in the coverage map as possible.
Example CORS station VITH in St. Thomas
GNSS reference stations installed by the National Geodetic Survey, or by US states who set up their own corrections networks for their transportation and surveying crews can cost more than $50,000 a site. This project, the SparkFun CORS, is a demonstration of how to deploy a very reliable, remotely monitored station for around $2,000.
It goes without saying, but we do not claim to have the same accuracy or efficacy of the NGS - they rule! We provide this information as a potential starting point for municipalities or other organizations that are looking to move to high precision GNSS without needing to subscribe to a for-profit corrections provider.
Where can I get corrections today?
States with Free CORS
Free state CORS/RTK networks:
- Alabama — AL CORS
- Arizona — AZCORS
- Arkansas — ARDOT RTN
- California — CRTN
- Connecticut — ACORN
- Florida — FPRN
- Indiana — InCORS
- Iowa — IaRTN
- Kentucky — KYCORS
- Maine — MaineDOT CORS
- Massachusetts — MaCORS
- Michigan — MDOT CORS (MSRN)
- Minnesota — MnCORS
- Mississippi — GCGC RTN
- Missouri — MoDOT RTN
- New York — NYSNet
- Ohio — ODOT VRS
- Oregon — ORGN
- Vermont — VECTOR
- West Virginia — WVRTN
- Wisconsin — WISCORS
This is only a partial list. There are lots of additional free networks including UNAVCO and country-wide networks such as CentipedeRTK in France.
If you're lucky and live in a state or area where there is a free or low cost corrections network then use it! If you are a municipality or county unlucky like we are in a state that doesn't have a network, then keep reading about how you can set up your own CORS!
SparkFun CORS
A CORS is all the associated bits that enable a reference station to be robustly connected to the internet for long periods of time. If you can install your base station in a protected, climate controlled office or outbuilding, do it! The goal of this tutorial is to demonstrate a mid-grade CORS station capable of being installed in semi-remote areas where no power or internet (WiFi or ethernet) is available. You can spend tens of thousands of dollars on bulky, power hungry equipment but we wanted to show that you don't need to.
Above is the SparkFun CORS at the end of our parking lot. There are four parts:
- The antenna is located at the top of the light post.
- The solar panel shown is 30W but was later changed to 100W.
- The cabinet houses the battery, solar charger, low-voltage disconnect, base station, and cellular modem.
- The grounding wire for lightning suppression.
Below is a list of parts used on this project:
Description | Cost
---|---
SXM-E | $1,200
RUT241 LTE Modem | $190
1m SMA Extension Cable | $5
Tello SIM card | $3
Metal Enclosure w/ Hardware | $105
Cam Lock Replacement | $7
Cable glands | $8
100W Solar Panel | $52
Large Panel Mounting Bracket | $120
10AWG Solar Wiring | $18
MPPT Charger | $20
50Ah Battery | $90
Battery Harness + Fuse | $5
RV Pipe Heater | $14
DC Thermostat | $6
Low Voltage Disconnect | $21
Lightning Arrestor | $20
1m SMA Extension Cable | $5
Grounding Rod | $30
Square U Bolts | $20
NMO Antenna Mount | $10
5/8" Rod 2" | $10
|
Total | $1,959The core of a CORS is the reference station that monitors the GPS signals and generates corrections. Most GNSS receivers have the capability to be told the exact location the device is located. From that point on, any differences that are detected in the received GNSS signals are attributable to perturbations (think turbulence) in the ionosphere and atmosphere in general. Those differences are turned into corrections that, when broadcast to a rover, allow the rover to enter into an RTK Fix with accuracies that can be below 10mm in horizontal accuracy.
We chose the SXM-E reference station as its mosaic-X5 receiver is the Cadillac for precision, while being extremely configurable, reasonably compact, with reasonable power consumption.
For a video tutorial on how to set up the SXM-E, including antenna installation and how to run a 24 hour survey to establish the location of the antenna down to the millimeter, check out this video. We found NMO Antenna Mounts to be a handy 5/8" compatible bracket for pole mounting. 4" u-bolts were used to fasten the hardware to the square light pole.
Housing
We chose a ~$100 painted steel cabinet that measures 16 x 12 x 8". In retrospect, this is too small. We should have opted for a larger enclosure but the allure of snugly fitting a 50Ah battery into this enclosure was initially too great. That said, the grated ventilation system of this cabinet works very well and helps keep bugs and mother nature out while keeping the SXM-E within its operating temperature of −20°C to +85°C.
We re-used some of the packaging foam to create a boat shaped pad for the battery to rest in.
Note that the enclosure dimensions are not necessarily the usable internal dimensions. Our cabinet came with a handy shelf bracket installed on the back wall. Unfortunately the shelf and bracket system sat so proud that it had to be forcibly removed (ground out) to allow for enough room for the battery to fit. If I were to do it again, I would use a larger ~24x20x10" cabinet.
The cabinet required a fair amount of modification to allow for the u-bolt mounting hardware (four holes), SMA connectors, and the installation of glands to allow for various water-tight cable connections.
Holes made for connections:
- 2 x 9mm glands for +/- solar wires
- 1 x 7mm hole for cellular SMA extension cable
- 1 x 7mm hole for GNSS SMA extension cable
- 4 x 1/2" holes for u-bolt fasteners
Originally we had intended to install the GNSS antenna directly on the top of the cabinet. This would allow the overall CORS to be more compact but the sloped roof of the enclosure would make getting the antenna into a vertical position very challenging. Additionally, the sky-view blocking aspect of the light pole meant we needed to mount the antenna further up. If you do consider antenna mounting to the cabinet roof opt for an enclosure that has a flat roof and waterproof accordingly.
Shown above, to prevent damage to the reference station in the case of a lightning strike, a grounding rod and tie line were run to the housing.
Above, in this original setup you can see the ground tie connected to the lightning arrester in the upper right corner. As my co-worker pointed out: "This is a very bad idea." If lighting where to strike, it would send the lightning through the ground wire inside the enclosure.
Here is the lightning arrester properly located on the outside of the enclosure: the GNSS antenna cable routes to the lightning suppressor, the ground wire has its shortest path to ground, and the arrestor is connected to an SMA extension cable that mounts to the enclosure wall that, in turn, connects to the SXM-E's mosaic-X5 GNSS receiver.
Power
I thoroughly recommend LiFePO4 chemistry batteries. Lithium Iron Phosphate (aka LFP) batteries have most of the benefits of their higher-energy-density LiPo cousins with the additional benefit of being very safe and hardy in robust environments. I have put 12V equivalent LiFePO4 battery packs through thousands of cycles, across three winters without heating and four summers in the Colorado sun, only to test the capacity of the battery and see that it remains at 80% of its badge capacity! Because of this, LiFePO4 was a natural match for our CORS test station.
The first step was calculating worst case scenario for lack of solar. Between the LTE modem and the SXM-E base station, our system power draw was about 4.5W average. Use your favorite calculator or chatbot to aid in the battery size, solar panel size, and solar panel angle. But our initial calculations put us at 30W for a solar panel (assuming an MPPT charger) and a 50Ahr battery. This setup was slated to last us 640Wh / 4.5W = 142h or six days if no sun was available, and charge the battery from dead in about 3 to 5 days depending on the time of year.
Above we have the 30W panel with the small panel mounting bracket. This combination was originally attractive for its compactness and low-cost. Unfortunately the panel was not large enough to escape the death spiral.
Pro Tip: When deploying a solar powered, self-contained system, start from a dead battery. It's natural to want to charge your battery fully then deploy your system thinking all will work fine. But if your charger is malfunctioning, or your battery is not quite up to its badge rating, or a bird causes a mess and degrades your solar panel's performance, you won't discover your system is slowly dying for many weeks or months. By starting from death, you can check that the system will be capable of digging itself out, from a power perspective.
I didn't intend to deploy our CORS with a dead battery but by installing the electronics one day and getting delayed installing the solar by a few days, it was a happy accident. Well, happy if we mean our base station failed from day one.
During the red highlighted phase, the station was deployed and would work for a few hours, but once night came the station would go offline due to loss of power. The frustrating part was that the station would not come back when the sun came up the next day. What in the world was going on? It's BMS lockout!
Above we see two discharge curves: LiFePO4 versus a lead-acid based battery. The run time in hours is not representative of any one CORS, rather, the graph is to demonstrate how the respective chemistries will behave during a cut-off scenario.
Every lithium based battery has a battery management system (BMS) to prevent the cells from dangerous and damaging edge cases such as over current, over voltage, or under voltage. In our case, the 12V battery has a BMS that disconnects the batteries via a MOSFET switch. Whereas classic lead-acid based 12V batteries (SLAs, AGMs, etc. all behave similarly) will output a lower and lower voltage (11V, 10V, 8V, etc), lithium based batteries with a BMS will lower their output voltage to a point, say 11.5V at which the BMS turns off the pack and the battery will read 0.0V. The BMS will not 'unlock' the pack until the load is fully disconnected. In the case of our CORS, the BMS was locking out at 0.0V but the load (the cellular modem and base station) continued to pull on the battery even when the sun was fully out. This was a type of lock-out death we had not anticipated. Luckily, this is a common issue!
Above we see the new wiring harness complete with MPPT charger and low-voltage- disconnect. The charger is connected to the solar panel wires using wire nuts. The small bare pair of wires connect to the SXM-E's screw terminals, the polarized plug powers the RUT241 modem. An LVD simply disconnects the downstream system when the voltage drops below a programmable threshold, and turns on the downstream system when the available voltage is above another programmable threshold. We set our LVD to cut off at 11.8V (~5% capacity remaining) and turn back on at 12.8V. This approach allows us to draw down the battery considerably without triggering the BMS disconnect. There is a chance that we have a terrible snowstorm that drives the system to LVD cutoff, then perhaps through self-discharge the battery enters BMS lockout, but this is unlikely. I've tested LiFePO4 batteries after a year of being on the shelf and tested their capacity to find only a 2% capacity loss! LiFePO4s are pretty amazing. A few days sitting in a low state shouldn't lead to a low-voltage cut-off.
Above we can see a report of the USACOLNIW2 station up time over a series of days. While I'm still not a proponent of anything blockchain, Onocoy does serve as an excellent, free station monitoring service. This quickly showed us the LVD was working! The station was dying at night, sure, but it was turning back on and charging during the day! We hit our second wall: The solar charging system was not large enough to charge the battery sufficiently to allow the system to run longer and longer over a series of good solar days.
The solution was to upgrade to a larger 100W panel, bracket, and wiring. It's frustrating that the mounting bracket is twice the cost of the panel. But considering the weight of the panel and the wind speeds around Boulder, CO, this much more substantial mounting hardware gives us peace of mind that the heavier solar panel won't fall damaging anything or anyone!
The panel change increased the cost of the project by ~5% but the improvements were immediately obvious, shown above as a steady green bar. After the installation of the new 100W panel, and with only a few hours of winter daylight left to charge the battery, the station was charged enough to survive the night and continue to improve over the coming days. Dig-out from death is a success!
Now let's talk battery heaters for a minute. The internet abounds with warnings to never charge your LiFePO4 battery when the cell temperature is below 0C (32F). My experience differs slightly: I have fully discharged and charged multiple batteries through Colorado winters without temperature control or sensing of the pack. After over 1000 cycles (more than 3 years), the capacity tested at 80%. Not bad!
However, for the benefit of this tutorial we wanted to test out battery heating. Shown above, our original design of the CORS battery pack included a stick-on RV pipe heating pad adhered to the bottom of the battery connected to a thermostat. The idea was to turn on the heater to allow the battery to heat itself when the temperature dropped below 3C (~37F). This heat would keep the battery warm while providing the SXM-E residual warmth to keep it above its lower -20C operating threshold.
When the station failed initially due to BMS and charging issues, the thermostat and heater were disconnected. The additional system complexity was not worth the marginal improvement to the battery lifespan. We have found the combination of insulation foam on the bottom of the cabinet, residual heat from the SXM-E itself, and strong Colorado sun tend to keep the battery at a good charging temperature when the sun is out. If you are very concerned about it, go for it! Our design heated the battery even at night which is silly. We recommend adding a light sensitive switch so that heating is only enabled when the solar output is high enough that the battery is actually charging.
Cellular Data Link
A reference station doesn't do much good unless it's pushing corrections to an NTRIP caster. To get the data to the internet we could have used SparkFun's local WiFi but that wouldn't provide a reasonable demonstration to users who are deploying a self-contained station.
In order of lowest cost and complexity:
- If you've got ethernet, use it! It's the lowest power and most dependable. Also, PoE is supported.
- If you've got WiFi, use it! It's free.
- If you've got cellular coverage, it will cost a bit each month ($10-$20), but it will work.
- If you're really remote, there's HugesNet, Viasat, Starlink, or Iridium. These provide satellite based internet but can cost anywhere from $50 to thousands of dollars per month and require considerably more power.
We originally tried to use SIMO, a ~$120 cellular hotspot marketed with 1GB of free data for life. Shown above, this is the small gray plastic device sitting on top of the battery. This would ostensibly remove the need for a monthly cellular account. However, we found that every 10 minutes, like clockwork, the SIMO would disconnect from the casters for a few seconds then promptly reconnect. While we could have troubleshot why this was occurring, it was assumed that SIMO was doing some sort of reasonable throttling that the casters would not like. 1GB a month is not enough data (more below) and the SIMO was not really built for this so we switched to the RUT241 and have been duly impressed.
The RUT241 is a cellular modem with ethernet, WiFi, and remote monitoring. Above we see the RUT241 connected over WiFi to the SXM-E. Eventually we got rid of the WiFi antenna and directly connected the SXM-E over ethernet; this cut down on complexity and reduced power consumption.
Note in the photo above the RUT241 has two cellular SMA connectors: one connected to a large flat antenna and another connected to an SMA extension cable. We were concerned the enclosure would cut down on cellular reception so the primary antenna is connected over the SMA extension to an external antenna while the secondary antenna is kept inside the enclosure. We found that reception was superb but you may want both antennas externally mounted for additional reception.
The amount of data a reference station can generate varies a lot based on a multitude of factors. MSM4 is the more compact, slightly less precise format for RTCM messages where as MSM7 is larger and more precise. If you have a relatively basic base station receiver (say a ZED-F9P) capable of only L1 and L2 frequencies, with a portion of low-elevation satellites removed from the corrections output, then you can easily drop down under ~800 bytes per second. Unfortunately this still leads to nearly 2GB per month. Alternatively, if you want to participate in networks like Onocoy, and are rewarded based on the 'quality' of the data and number of satellites in view, this can substantially increase the data being pushed to the caster over the cellular connection. And because of the SXM-E's superb reception, you can expect many thousands of bytes per second.
Reasons for increasing data:
- An advanced receiver that can receive multiple L1/L2/L5 frequencies will output far more correction data than an L1 only capable GNSS receiver.
- Outputting the more precise, but larger format MSM7 formatted corrections messages will output more data than the equivalent MSM4 formatted RTCM.
- A high-quality, high-sensitivity receiver and GNSS antenna will sense more satellites, and hence output a lot more corrections than a low-quality receiver with sky-view obstructions. Every additional satellite detected linearly expands the amount of data to transmit.
- A receiver that reports every satellite, even low to the horizon poor quality ones will add to the data transmitting vs reporting only high quality, high signal satellites.
- A receiver reporting corrections for all constellations (GPS/GLONASS/Galileo/BeiDou) will generate far more data than a base station reporting corrections for only the GPS constellation.
And just because we're weird, we want to simultaneously cast to three casters: RTK2Go, Emlid, and Onocoy. We love RTK2Go but it experiences outages when we least expect it so Emlid serves as a nice backup. And we use Onocoy both as an uptime monitor and because it's technically generating funny money. We will report back if we're ever successful in turning the Ono coin into something tangible (i.e., beer). Now we could have used RTKLIB's Stream Server (STRSVR) to send only one copy of corrections over the cellular network and then have a server re-broadcast to the three casters but this was deemed overly complex; it's easier to pay the $20 a month to push more data.
One especially nice feature of the RUT241 is the ability to remotely tunnel into the system. This allows us to remotely connect to the SXM-E as if we were connected over a USB cable to both monitor and configure the settings. This has been extremely handy. The downside is that there is no free lunch: Teltonika charges a monthly fee (about $5 as of writing) for this access. Now that the station is up and running, we will probably let the subscription lapse and purchase a month's access only when we need to modify or troubleshoot something which should be very rare.
You can also tunnel into the cellular modem itself and view data usage statistics. Note the small print at the bottom; these are estimates that may differ from the cellular provider, but they give us some insight into the daily usage. If this is to be believed, we're transmitting between 10 and 15GB per month.
The easiest/lowest priced data we've found was Tello. Your mileage may vary, but $18 a month is not terrible. Getting their SIM and using it with the RUT241 was very easy. Again, we're rare in that we need 20GB per month. If you filter out low-elevation satellites, turn off corrections from constellations that your rovers don't care about (perhaps Galileo and BeiDou), turn off frequencies that are not needed (GPS L5 is a good candidate), and push to a single caster, you should be able to reduce your data usage per month considerably.
Further Improvements
The SparkFun CORS is operating very well. Check out the current status on Onocoy and RTK2Go. We hope to have a fairly boring next couple of years. If we learn anything else we'll update this tutorial along the way.
1) As stated earlier, a larger cabinet would be the first improvement. Currently any maintenance or modifications require the entire cabinet to be emptied. However, now that we know what we're doing, there would be far fewer changes after-the-fact so perhaps the smaller cabinet is acceptable.
2) The cold-rolled steel is very sturdy, but a pain to drill. There are knock- outs but they were deemed too large to use. Finding a better way to leverage the built-in knockouts would require less drilling.
3) The MC4 connectors on the 100W solar panel required sending larger diameter wire through two glands and then connecting them using wire nuts to the MPPT charger. This works but is cumbersome. Perhaps MC4 bulkhead connectors could be used, but these connectors are too bulky to be used inside the enclosure. Perhaps there's a solution using an SAE connector to connect the wires to the charger.
4) Given infinite time and money it would be interesting to build a much larger cabinet instrumented in a way to allow for much more granular data gathering. Measuring and reporting the power consumption, battery voltage, and data flows would allow us to potentially reduce the solar panel, battery size, and tailor the cellular data rates.
Thanks for reading!
learn.sparkfun.com | CC BY-SA 3.0 | SparkFun Electronics | Niwot, Colorado
-
🔗 backnotprop/plannotator v0.28.66 release
Follow @plannotator on X for updates
Missed recent releases? Release | Highlights
---|---
v0.28.65 | Take back a reply your agent has not received yet, over Tailscale, Plannotator opens only for your own account, tag a linked machine's threads; one tag across machines, T3 Code threads get the Inbox with no setup, long threads open on slow connections
v0.28.64 | Installs and updates download a smaller, compressed copy, a Videos filter on the Artifacts page, GitLab comments on a whole file get their own thread, pull request pictures and videos show in the Inbox
v0.28.63 | Pair Grok Bot and other cloud agents from Settings, Hermes Agent, OpenClaw and Muse Code can use the Inbox, add a thread to Priority to keep it on top, tag threads, and find each tag in the sidebar, Pull requests board as a table, with bulk Merge
v0.28.62 | Agents started from the Inbox now work on Windows, pick a model and effort when you start an agent, rules for your agents, written in your own words, post a thread's decisions on its pull request, the Inbox loads faster on a slow connection
v0.28.61 | Updates now update the Claude Code plugin too, an agent's chosen face shows on every icon of it, filter the Inbox list by pull request state, Modern dark shows section bands and the Reply button, one conversation no longer shows as two agents
v0.28.60 | Click a word to highlight it, a one-time Themes dialog, Settings → Rows rebuilt, tell your agent how you want your rows, starred threads as pills above the list, a pill for new messages out of view, a half-circle face picker with ten Glass colours, a new phone sidebar and reply box
v0.28.59 | A quieter Agents section in the sidebar, machine names only when agents run on more than one machine, agent icons that are always gently alive and lean toward your pointer
v0.28.58 | Start Codex from New message, an Agents section in the sidebar, start an agent in a folder on any drive, play audio attachments and comment at a moment, Claude Code's Plannotator tools work on Windows
v0.28.57 | Pin artifacts, and see every artifact on one page, filter the list by project, date or agent, a thread shows its pull requests and their state, choose what the sidebar shows, and in what order, Ask AI starts from Side in the selection bar
v0.28.56 | Questions can show trade-offs and a prototype to try, a thread with many big pictures no longer crashes the tab, Escape closes New message and keeps your draft, read threads stop being bold and keep their place, agent messages that name no thread start a new one
v0.28.55 | Floating reply drafts, now a setting under Experimental, open questions sit next to Reply again, a comment box that keeps unsent comments as Drafts, choose how your list looks: Minimal, Balanced or Detailed, update an older linked machine from this Inbox
v0.28.53 | Start an agent in a new folder, or from a git URL, "+" on each project row starts a session there, a reaction tray, a thread's Links, Settings → Activity, New message offers the open thread's files, Bro mode: agents write to you in plain wordsWhat's New in v0.28.66
TL;DR
- New: Pick several threads and archive or snooze them at once
- New: Combine picked threads into one; Tidy follows your own words
- New: Rows take their tag's colour; filter and search by tag
- New: Files an agent's message names open beside the thread
- New: Swipe rows on phone or iPad; list can show archived threads
- New: Antigravity and Orca use the Inbox; T3 Codex threads get replies
- New: Open in lists JetBrains IDEs
- Off by default: Routines: run a saved prompt on a schedule
v0.28.66 is mostly an Inbox release. You can pick several threads and act on them at once, ask one agent to combine them into a new thread, or have Tidy follow your own instructions. You can also swipe a row on a phone or iPad. Tags show on rows, under a thread's subject, in Filter and in Search. A file that an agent's message names opens beside the thread, and Google Antigravity joins the agents that can use the Inbox. Plan review and annotate get optional source line numbers and coloured text, and the Open in menu lists JetBrains IDEs. The release has 100 PRs. 15 of them are from 8 outside contributors, and 5 of those people made their first contribution.
Pick several threads and act on them at once
You can now pick thread rows and act on all of them together. ⌘-click (Ctrl- click on Windows and Linux) adds or removes a row, and Shift-click picks a range. You can also choose Select in a row's right-click menu or a phone's long-press sheet, or Select threads in the list's ⋮ menu. While rows are picked, a bar takes the place of the list header. It shows how many are picked, with Archive, Snooze, Tidy…, Combine… and Done. On a phone the actions are a sheet at the bottom of the screen. A right-click on a picked row acts on every pick. Each action gives one toast with one Undo. A thread that lives on a linked machine goes to that machine; if the machine is asleep, the change waits for it.
Tidy now takes your own words. Its popover has "Add instructions (optional)" and remembers the instructions you used recently. Tidy on picked threads asks each thread's own agent about those threads only.
Combine asks one agent to write a new thread from the picked ones. You choose the agent and can say what the new thread is about. The picked threads are archived only once the new thread arrives. If the agent ends or stops first, nothing is archived and the window says so. While it waits, the rows read "Combining…", with "Stop combining" in their menu. Undo brings the threads back.
On a phone, every bottom sheet now fits the screen and scrolls inside, so the first items of a long menu are always in reach.
Swipe a row, and show archived threads in the list
On a phone or an iPad, swipe a thread row as in Mail. Swipe right to mark it read (on a read row, the right side offers Mark unread). Swipe left to archive it. A long swipe or a flick runs the action when you lift your finger. A short swipe leaves the row open on its button, so you can tap it. Toasts, Undo and the "Set aside N open questions?" warning work as they do from the row menu.
Archived threads can now show at the bottom of the list. Turn on Show archived in the list's ⋮ menu (it is off until you pick it). An Archived section then sits under Snoozed, closed until you open it. It shows the newest archived threads first, 20 at a time, up to 100, and then points you to Search. Each row says when it was archived. Unarchive is in the row's hover action, its menu, and a left swipe on a phone. The choice is the same on every linked machine and every open window.
Tags on rows, in the thread header, in Filter and in Search
Rows take their tag's colour. Each tag now has a colour. A new tag gets one at once from a calm set (green, amber, the accent colour and grey), and tags you already have get one on the first load. A tagged row is tinted across its width and shows the tag's name. If you already use tags, your rows are coloured after you update. To change a tag's colour, right-click the tag in the sidebar and pick Highlight rows : five presets, your own recent colours, a hue strip, a hex field, or None. To turn every tint off, untick Show tag colors in the list's ⋮ menu. Colours and the switch are the same on every linked machine.
A thread's tags show under its subject , each opening its tag's list, with a
+to add one. A thread with no tags looks as before.Filter and Search. The list's Filter has a Tag section that shows how many threads each tag leaves, and you can tick several. Search has a Tag chip after "From anyone". With the Board off, resting on a
#Tagin a message shows a preview of the tag's latest threads.Add tag no longer loses what you type when the menu moves under a still mouse.
Every file an agent's message names opens beside the thread
In an agent's message, a link to a file, a code span that is a path (
src/a.ts:42,README.md) and a bare path in the text now open that file beside the thread.:42,:6-13and#L6-L13jump to and mark the lines. Opening the file attaches nothing. Your first comment on it (a text selection, a code line, a point on a picture, a moment in a video) makes it an attachment of that message, and from then on it is counted and sent like any attachment. A relative path starts in the thread's folder. Secrets never open: dotenv files, SSH keys and credential stores are refused. Your own messages keep their links as they are.Prototypes you can click through, and prototypes on the web
An agent's prototype page now behaves in the Inbox as it does in a browser tab. A link to the same page with a query (
?variant=2) loads that variant in place, GET forms and#links work, and the "Try prototypes" window follows links to another option's page or to a web page (in a new tab). Each option can open the same attached file with its own query, so stepping between options switches the variant.An agent can also point an option at a public
https://page. "Try prototypes" opens it straight from the web, with Comment for a whole-page comment and a button to open it in a new tab. Plainhttp://on another host is still refused.Reply to a new session when the one that asked has ended
When the session that asked you has ended, the "who gets this reply" list now ends with a row such as "New Claude Code session in ledger". Pick it and your reply starts a new session of the same agent, in the same folder, on the same machine, and that session then owns the thread. The ended session stays the default, so nothing starts unless you pick the row. If the start fails, your reply is kept and the thread offers Try again.
On a computer, that list now shows each session's title, with the agent and folder under it, as the phone already did. Two sessions with the same title get the agent's name added. In the sidebar, the Agents list keeps a fixed order (newest first seen at the top), so rows no longer jump when a turn starts or ends. An agent's name follows one rule on every device: the name you gave, then the name set in the agent, then its title.
#3442, #3447 finishing #3343 by @sx4im, #3454, #3448
Antigravity can use the Inbox
Google Antigravity (the app, the IDE and the
agycommand) can now write to your Inbox, and your reply starts a turn in the conversation that asked. When Antigravity is on the computer,plannotator inboxadds the Inbox to its MCP config. The app and the IDE need nothing else. Anagyconversation is told to runplannotator inbox antigravityonce per launch when the Inbox cannot reach it yet. Each reply goes in once. The wake was tested withagyon macOS. The IDE, Windows and Linux are not tested yet.T3 Code: replies reach Codex threads too
A Codex thread running inside T3 Code could write to the Inbox, but your replies never showed up in T3. Now a reply to any T3 thread, Claude or Codex, goes in through T3's own
t3 thread sendon this computer, with no setup. When T3 is closed, the reply says "Waiting for T3 Code" at once, and the list row says the same as the thread. A T3 started from a Claude Code terminal, or one of T3's own short runs, no longer takes a reply meant for the thread.Settings → Agents has a T3 Code entry when T3 is on this computer. It says whether your replies arrive as a new turn, and when they cannot, it shows the sign-in command with Copy.
Orca gets the Inbox and the plannotator tool
Claude Code chats in Orca now get what the VS Code panel gets: the
plannotator_inboxtool with the reply wake, and theplannotatortool. This changes plan review in Orca: Orca shows its own "Review proposed plan" card, so Plannotator's plan review no longer opens there.#3460 closing #3325 reported by @ninjz, with the Orca work from #3400 by @rudycelekli
Cloud agents use the whole Inbox
A paired cloud agent can now do what a local agent's Inbox tool does. It can list, read and search every thread in every project, reply in any thread, start threads in any project (named by project name), resolve and snooze threads, change a thread's pull requests, and send guided reviews. It can use cards and steps while those are on. It still cannot name a path on your computer. It can also attach files up to 100 MB, videos included, by sending them in pieces.
Plan review and annotate: source line numbers, coloured text, and Open in
JetBrains
Source line numbers. Settings → Display has a Source line numbers switch, off by default. Turn it on and each block in plan review and annotate shows its source lines in a quiet gutter:
42for one line,42–45for a span. The numbers stay out of copied text and out of an annotation's quote, and they are hidden on phones and in print.Coloured text. An author can now colour a few words with
<span style="color: …">or<font color="…">. The colour shows in plan review, annotate, Inbox messages and Markdown attachments, including table cells. Colours that are almost see-through are refused.Open in JetBrains IDEs. The Open in menu now lists IntelliJ IDEA, WebStorm, PyCharm, GoLand, Rider, PhpStorm, RubyMine, CLion and RustRover when they are installed. The file opens at the line.
Annotate's default view. A new config.json key,
annotateView("wide","focus"or"edit"), sets the view an annotate session opens in.A table indented under a list item no longer draws its header one column to the right.
#3373 by @mvanhorn closing #1650 requested by @de-tre, #3378 closing #3345 requested by @zane668, #3372 by @mvanhorn (related to #3368 by @JasonLandbridge), #3463, #3314 by @BenNewman100
A quicker Inbox window
The Inbox window now keeps the open thread in one cache and applies live changes to it in place, instead of reading the thread again. When you press Send, your words show in the thread at once with "Sending…". If the send fails, they come back into the reply box with the reason. In a long thread, one new message now redraws only itself (before, a 266-message thread redrew 291 parts). Each agent message across four windows takes half the requests it did. On an iPad, the first load no longer stalls before the first tap works.
Phones and iPads
- The comment card stays above the keyboard. On an iPhone or iPad, the comment box ended up under the keyboard and the screen jumped on every key. It now sits above the keyboard. #3380
- Step through a thread's files on an iPad with large previous and next buttons under the open file, or a sideways swipe. A swipe that starts at the screen's edge stays Safari's Back or Forward. #3425
- The tag (@) and recipient pickers are no longer cut off by the reply box. #3440 by @sx4im closing #3427 reported by @llwt
- Leaving a picture's full view no longer redraws every tile button in the thread under your finger. #3371
config.json can live in your dotfiles
The Inbox used to write its own records into
config.json: when each one-time dialog was due or shown, the tour, and similar bookkeeping. These differ on every machine and change by themselves, soconfig.jsoncould not be kept in a dotfiles repo. They now go tostate.jsonnext to it. Your settings stay inconfig.json. Old copies inconfig.jsonare read and never removed, so an older version or another machine sharing the file keeps working.plannotator uninstall --purgeremovesstate.jsontoo.#3458 closing #2852 reported by @robsonpeixoto
Updates, installs and proxies
- Updates run at low priority. A background update (Update now, or auto-update) now runs at low CPU and disk priority, so the Inbox stays quick while it downloads.
plannotator updatein a terminal keeps normal priority. This applies from the update after this one. #3466, for #2788 reported by @zane668 - A download mirror for the binary.
install.shnow downloads the binary itself fromPLANNOTATOR_RELEASE_DOWNLOAD_URLwhen it is set, not only the checksum. The checksum check still applies. #3310 by @rudycelekli closing #3298 reported by @navin-moorthy - A proxy no longer breaks the Inbox. With
http_proxy(orHTTP_PROXY,ALL_PROXY) set, Plannotator sent its requests to 127.0.0.1 through the proxy.plannotator inbox statusthen said "not running", and an agent's send could start a second Inbox and stop yours. Local requests now skip the proxy. #3461, found while working on #3350 reported by @zane668 - A plan review whose parent is gone exits. When the program that started a classic plan review is killed, the review's server now exits after about 10 seconds instead of running on with nobody to read its decision. #3461
Routines: off by default
A routine is a saved prompt with a name, a schedule and a folder. When it is due, the Inbox on this computer starts a fresh agent session in that folder, and every run lands in one thread. Turn Routines on in Settings → Capabilities (config
inboxScheduledThreads). It is not offered on Windows, and it needs "Start agents from New message" on. While it is off, nothing runs and nothing is written.- Schedules: hourly, daily, weekdays, weekly, once, a custom cron, or none (run by hand). Runs are at least 15 minutes apart.
- Missed runs: "Run once when I'm back" (the default) or "Skip it". A catch-up is one run, never a burst.
- Runs use Claude Code, Codex, OpenCode or Pi, with your own permission mode. Your reply goes to the newest run's session.
- Agents can create routines, but one an agent creates arrives off, and only you can turn it on the first time. Each change an agent makes posts a line in the routine's thread, with the old and new values.
- Start at login: while Routines is on, the Inbox adds a login item (launchd on macOS, a systemd user unit on Linux) so it starts quietly and routines can run. Turning Routines off or
plannotator uninstallremoves it.
A routine is managed on the computer that made it. Its thread works from a linked machine like any thread.
Reach the Inbox through your own Cloudflare: off until you set it up
For people who do not use Tailscale, the Inbox and your review, annotate and last sessions can now be reached through your own Cloudflare Tunnel and Cloudflare Access. As over Tailscale, one owner gets in and nobody else does: only the e-mail you type at setup can sign in. Settings → Remote devices has a Cloudflare card with Set up. You can also run
plannotator inbox cloudflare-access setup --email <you>. Setup needs a Cloudflare account with a domain, an API token (never saved) andcloudflared. It creates the tunnel, the sign-in gate and two addresses, checks from outside that a request without your sign-in is refused, and only then turns it on and shows the address with a QR code.teardownremoves everything it made. Sessions take--cloudflare- access.Additional Changes
- Last 3 days in the list's Updated filter: today and the two days before, moving with the clock. #3401 by @rudycelekli closing #3301 requested by @zane668
- Let a trusted local app show the Inbox in a frame. A new config.json key,
inboxFrameAncestors, lists the apps on this computer that may embed the Inbox window. Unset, nothing changes. #3376 closing #3299 requested by @jroquejr plannotator review<word>with no such folder now stops with a clear error, instead of reviewing the folder the terminal is in. #3387plannotator review<folder>reviews that folder even when the shell exportedGIT_DIR. #3377- Mod+Shift+Enter in code review opens "Send with a note…" instead of posting the review with no note. #3210 by @rudycelekli, #3403
- DeepSeek Harness keeps the backslashes in a typed Windows path, so
/plannotator-review C:\dev\featureopens that folder. #3214 by @rudycelekli - A link whose URL has parentheses (such as a Wikipedia link) now works in guided reviews and PR descriptions. #3213 by @rudycelekli
- OpenCode's annotate-last opens on the reply to your own prompt, not to a message a plugin added. #3358 by @xunguangzlj-cloud closing #3312 reported by @marwashan
- Pi inside an Electron app gets a TLS warning that tells you to update the host app, with its Electron and Node versions. #3351 by @jiangjiang248 closing #3346 reported by @xueccci
- After
/bgon a busy Claude Code session, the Inbox tool stays connected. #3370 by @uvw closing #3369, which he also reported - A malformed address answers 400 in the Shapes routes, the review servers and the Inbox. In Pi it could stop the extension's host. #3414 by @sx4im closing #3411 reported by @brunnojob, #3456
- Your words are kept. Take back is no longer offered on a reply that carried answers (the server refused it). A dialog no longer closes when a text selection ends on its backdrop. Closing the reply box while it says Transcribing keeps the take, and a file opened over the box while recording closes the mic and posts nothing. #3426, #3445
- Questions. A question repeated in an attached file is asked once, not twice. Choices that differ only in case or a mark ("Yes" and "Yes!") are kept apart. #3422
- Reply files keep the order you picked them in , on the phone and from another window. #3441
- Pin / Unpin in an attachment's menu , after Download. The dialog for updating a linked machine now reads "Update {name} yourself". #3424
- A sleeping machine's projects stay in New message's folder menu , after a reload or in a new tab. #3468
- Short GitLab merge request references go to the project's own server. A short reference such as
group/project!45now goes to the project's own GitLab server, including self-hosted names likegitlab-master.example.com. Before, it could point at gitlab.com. If a short reference still goes to the wrong place, for example when your GitLab is reached on a port or the project's remote uses an SSH alias, name the server ingitlabHostsin config.json. A reference saved before this fix keeps its old address until you remove it and add it again. From a user report. #3525 - The thread header shows its PR button when an agent links PRs while the thread is open. #3451
- A thread opened from a link stays in its place in the list instead of dropping into Quiet. #3407
- Sidebar: the Tags and Agents header buttons show when you hover the header, like its arrow. #3395
- Linked machine updates: Try Again no longer shows "The update didn't install" while the update is working. On touch, a quick second tap on the face picker no longer picks a face by mistake. #3446
- Guided reviews: End and Home no longer load files halfway down, and Collapse all works after switching views. #3366, #3467
- Agent text. A session started from the Inbox is told on its first turn that you read the Inbox. Agents get eleven short lessons from the owner (for example: open a prototype and click through it before sending it). When an agent names a PR that is on no thread, the send's result suggests attaching it. #2999, #3436, #3435
- The Board across linked machines. With the Board turned on, it shows the cards of every linked machine in the same lanes, and each action on a card goes to the machine that holds it. #3341
- For people who already turned on code review in the Inbox: the Pull requests board spans linked machines, picked PRs can start review threads, the stack page can open a range of layers as one diff and marks what changed since you looked, the next review round asks only for what changed, and a review note no longer widens a wrapped diff on a phone. #3392, #3396, #3398, #3432, #3431, #3170 by @robfeldmann
- Site and docs: plannotator.ai/llms.txt is now a short index that leads with the Inbox, the Inbox install prompt gives each agent its own steps, OpenClaw installs from npm (
openclaw plugins install npm:@plannotator/openclaw),plannotator inbox --helphas two lines corrected, the README has a new Inbox picture and a shorter top, and the end of the Inbox page now offers the install prompt first. #3379, #3382, #3374, #3384, #3465, #3474, #3479, #3478 - Groundwork with no visible change: the thread pane as a self-contained part #3450, #3464
- Test and CI upkeep: #3457, #3215 by @rudycelekli, #3399, #3211, #3459, #3421, #3420, #3419, #3439, #3406, #3481
Install / Update
macOS / Linux:
curl -fsSL https://plannotator.ai/install.sh | bashWindows:
irm https://plannotator.ai/install.ps1 | iexClaude Code Plugin: The install script above also updates the plugin when
claudeis on your PATH. Otherwise, in a terminal:claude plugin marketplace update plannotator claude plugin update plannotator@plannotator --scope userThen restart Claude Code. Inside Claude Code, run
/plugin marketplace update plannotator, then open/plugin→ Installed → plannotator → Update now.Pi:
pi update npm:@plannotator/pi-extensionOpenCode: Re-run the install script above. It also clears the OpenCode 2 plugin cache.
What's Changed
- fix(review): a named directory is reviewed even when the shell exported GIT_DIR in #3377
- OpenClaw: install from npm (site and plugin README) in #3374
- llms.txt: route agents, Inbox first in #3379
- Markdown: keep an author's text colour in #3378
- Phone and iPad: the comment card stays above the keyboard in #3380
- Inbox: leaving a phone's full view no longer swaps the thread's tile buttons in #3371
- Guided review: End and Home stop mounting files halfway when the scroll stalls or the observer lags in #3366
- Inbox: let a trusted local app frame the window (inboxFrameAncestors) in #3376
- Inbox frontend foundation, step 1: one cache for the open thread in #3103
- Inbox window: data layer step 2 (half the requests, Send shows at once, list in the cache) in #3115
- Inbox window: an arriving message draws its own body only; first break-up of App.tsx and Thread.tsx in #3123
- Inbox window: check the held copy against a fresh read (random sequences, and after every browser spec) in #3211
- Inbox prompt: each agent's own steps, and a Supported agents link in #3382
- inbox --help: two lines brought up to date in #3384
- Inbox Board: one Board across linked machines in #3341
- review: a sole folder name that is not there stops with a clear error in #3387
- Inbox: one PR board across linked machines in #3392
- fix(review): Mod+Shift+Enter opens the note composer, it no longer posts by @rudycelekli in #3210
- Claude Code mod: a turn that starts before session.start finishes keeps the Inbox link by @uvw in #3370
- Inbox tags: Add tag's field keeps focus while typing; same-millisecond tags keep their order in #3393
- Fix table header shifted one column right when the table is indented under a list item by @BenNewman100 in #3314
- Inbox: settings known before the first row on load; equal settings redraw nothing in #3386
- Cloud agents use the whole Inbox, like a local agent in #3306
- Tests: the snooze tests restore the time zone they started in in #3406
- fix(pi): point Electron TLS warnings to the host app by @jiangjiang248 in #3351
- Inbox sidebar: Tags and Agents header buttons show with the chevron in #3395
- ci: run the Claude Code mod's engine-harness tests in #3399
- Inbox: a thread opened from a link is looked at after the first list read lands in #3407
- Cloud agents send files up to 100 MB in pieces in #3318
- fix(review): a remounted decision control does not reopen the note composer in #3403
- Inbox: a question's prototype can be a public https page in #3319
- Inbox: tell a launched session where the person reads, on its first turn in #2999
- Prefer human-prompt replies in OpenCode annotate-last by @xunguangzlj-cloud in #3358
- Inbox: colour rows by tag, with a Show tag colors switch in #3402
- Claude Code mod: a T3 thread is the process with T3's t3-code tools in #3381
- Inbox: wake T3 threads (Claude and Codex) through t3 thread send in #3375
- Inbox: every file a message names opens in the viewer, attached when commented on in #2875
- Inbox: archived threads as a group in the thread list in #3404
- Inbox T3: the waiting line shows at once, and the row says what the thread says in #3412
- Inbox: pick threads and act on them at once, Tidy with your words, Combine in #3405
- Inbox: a new Combine/Tidy key after a refusal; cap tag colour times at now in #3418
- Inbox Archived: fix the two-machine test's same-millisecond tie (main's unit-2) in #3419
- Inbox T3 test: hold the wake's send in flight while the mod polls in #3420
- Inbox: swipe a thread row to mark it read or archive it in #3135
- Give the thread-state model test a budget it fits in in #3421
- Inbox: Pin in an attachment's menu; "Update {name} yourself" in #3424
- Inbox: step a thread's files on an iPad with a bar and a swipe in #3425
- Inbox: stop losing the person's words (Take back, dialog backdrop, dictation) in #3426
- Inbox: every phone bottom sheet fits the screen (the thread's ⋮ too) in #3433
- Inbox and sessions through your own Cloudflare Tunnel and Access (opt-in) in #3388
- Inbox: ask a repeated file question once; refuse choices that read the same in #3422
- Inbox: the next review round asks only for what changed in #3431
- Inbox tags step 2: header tag line, Tag filter, tags in Search, Board-off preview in #3397
- Inbox agent text: the owner's lessons for agents in #3436
- Ended-reply test: let the disposed wake's last poll land before the clock moves in #3439
- Inbox: name unattached PRs (bare #N too) in send_message's result in #3435
- Inbox stack page: Layers i–j as one diff, and changed since you looked in #3432
- Routines: run a saved prompt on a schedule, on this computer in #3409
- Inbox: a T3 Code group in Settings → Agents in #3438
- Inbox: let people click and navigate inside an agent's prototype page in #3162
- Inbox PR board across machines: say what the window check stops, pin the gh routes, test merge in #3396
- Inbox: reply files keep the order the person picked them in in #3441
- Inbox: Antigravity, with a wake in #3390
- Inbox PR board: Start review thread for picked PRs in #3398
- Antigravity page: say the IDE is untested in #3444
- Inbox: a cover while recording posts nothing again in #3445
- fix(dsh): a typed Windows path reaches the review whole by @rudycelekli in #3214
- Inbox reply picker: show each session's title on a computer (finishes #3343 by @sx4im, with their commits) in #3447
- Guide viewer: a link's URL keeps its own closing paren by @rudycelekli in #3213
- Inbox: thread header shows its PR button when the read after a change fails in #3451
- Inbox: reply to a brand-new session when the one that asked has ended in #3442
- fix(inbox): a closed note or a folded thread no longer widens a wrapped diff past a phone by @robfeldmann in #3170
- Fix nine flaky tests, the machine update's false "didn't install" and the face picker's early tap in #3446
- Inbox: Agents list keeps a fixed order, marks who waits on you, names by one ladder in #3448
- fix(shape): return 400 for malformed percent-encoded shape paths by @sx4im in #3414
- Inbox: the reply picker names an unnamed session by its agent, not its first thread in #3454
- Add a rolling three-day Inbox update filter by @rudycelekli in #3401
- Inbox: the thread pane as a self-contained slot, keyed by pane (no visible change) in #3450
- ci: three path gates skipped PRs that break the job they gate by @rudycelekli in #3215
- Malformed path escapes answer 400 in the review servers and the Inbox in #3456
- Fix forward: option card on a phone and the row badge hover (main red) in #3459
- README: a new Inbox picture (desktop and phone) in #3465
- Open in: JetBrains IDEs, at the line by @mvanhorn in #3372
- install.sh: download the binary from PLANNOTATOR_RELEASE_DOWNLOAD_URL by @rudycelekli in #3310
- Inbox: tag and recipient pickers escape the reply box scroll region by @sx4im in #3440
- Inbox: each pane opens and reads its own thread in #3464
- Annotate: a config.json key for the default view (Wide, Focus or Edit) in #3463
- Plan and annotate: optional source line numbers beside each block by @mvanhorn in #3373
- CI: run an affected slice of browser specs on each PR (#3455) in #3457
- Updates run at low priority, so the Inbox stays quick while one downloads in #3466
- Keep machine state out of config.json (#2852) in #3458
- Guide viewer: Collapse all works after switching views in #3467
- Loopback requests ignore a proxy; a classic plan review exits when its parent is gone in #3461
- Claude Code mod: Orca chat gets the tools and the wake; no Plannotator plan review in Orca (#3325; includes #3400 by @rudycelekli) in #3460
- Inbox: keep a sleeping machine's projects in New message in #3468
- README: Inbox section moves up; Annotate HTML below Herdr Annotate in #3474
- Inbox page: the ending offers the install prompt first in #3479
- Open in test: the macOS expectation for a JetBrains app at a line in #3481
- README: shorter top, AI built in below Commands, one short Sharing section in #3478
- fix(inbox): a short group/project!45 lands on the project's own GitLab, never gitlab.com in #3525
New Contributors
- @rudycelekli made their first contribution in #3210
- @robfeldmann made their first contribution in #3170
- @xunguangzlj-cloud made their first contribution in #3358
- @jiangjiang248 made their first contribution in #3351
- @sx4im made their first contribution in #3343, merged through #3447
Contributors
@rudycelekli sent the most work from outside the project in this release, in his first contributions. He made Mod+Shift+Enter open the note composer in code review instead of posting (#3210), kept typed Windows paths whole on DeepSeek Harness (#3214), fixed links with parentheses in the guide viewer (#3213), added the Last 3 days filter (#3401), made
install.shdownload the binary from a mirror (#3310), and fixed three CI path gates that let breaking changes skip the job meant to catch them (#3215). His Orca work (#3400) ships inside #3460.@mvanhorn added source line numbers to plan review and annotate (#3373) and JetBrains IDEs to the Open in menu (#3372).
@sx4im made his first contribution: session titles in the reply picker (#3343, finished in #3447 with his commits kept). He also fixed the tag and recipient pickers that the reply box cut off (#3440) and malformed addresses in the Shapes routes (#3414).
@robfeldmann found and fixed a wrapped diff that jumped while he reviewed on his phone (#3170), with recordings from a real iPhone. First contribution.
@xunguangzlj-cloud made OpenCode's annotate-last open on the reply to your own prompt (#3358). First contribution.
@jiangjiang248 made Pi's TLS warning point to the host app when Pi runs inside Electron (#3351). First contribution.
@BenNewman100 fixed the header of a table indented under a list item (#3314).
@uvw reported and fixed the Inbox tool going "not connected" after
/bgon a busy Claude Code session (#3369, #3370). His fix also made the Claude Code mod's test harness run on Windows.Community reports and requests that shaped this release:
- @zane668 asked for Last 3 days (#3301) and coloured text in Markdown (#3345), reported the Inbox slowing down while an update downloads (#2788), and kept digging into leftover Inbox processes (#3350), which turned up the proxy and plan review fixes
- @robsonpeixoto asked for a
config.jsonthat works in dotfiles (#2852) - @de-tre asked for source line numbers (#1650)
- @ninjz asked for the Inbox tools in Orca (#3325)
- @jroquejr asked to embed the Inbox in a trusted app (#3299)
- @navin-moorthy reported that
install.shignored the download mirror for the binary (#3298) - @llwt reported the cut-off pickers in the reply box (#3427)
- @brunnojob reported malformed addresses crashing the Shapes routes (#3411)
- @marwashan reported annotate-last opening on replies to plugin messages (#3312)
- @xueccci reported the TLS advice Electron users could not act on (#3346)
- @JasonLandbridge asked for more editors in Open in (#3368); the JetBrains IDEs are a first step
Full Changelog :
v0.28.65...v0.28.66 -
🔗 HexRaysSA/plugin-repository commits sync repo: +2 plugins, -1 plugin, +8 releases, -2 releases rss
sync repo: +2 plugins, -1 plugin, +8 releases, -2 releases ## New plugins - [IDAAutoTheme](https://github.com/baiguqing/idaproautotheme) (1.0.1) - [ida-discord-rpc](https://github.com/reversedcodes/ida-rpc) (1.3.0, 1.1.0) ## New releases - [SigMaker](https://github.com/mahmoudimus/ida-sigmaker): 1.17.0 - [btf2ida](https://github.com/nightshift-labs-ai/btf2ida): 0.1.23 - [cfiscope](https://github.com/nightshift-labs-ai/cfiscope): 0.1.20 - [ida-mcp-bridge](https://github.com/eitapreulajhol/ida_mcp): 0.4.1 - [memlens](https://github.com/nightshift-labs-ai/memlens): 0.3.28 ## Changes - [memlens](https://github.com/nightshift-labs-ai/memlens): - removed version(s): 0.3.3 ## Removed plugins - IDA-Discord-RPC -
🔗 r/LocalLLaMA Why download abliterated Flash Next models when LoRA exists? rss
| TL;DR -- Download LoRA, add --lora HUIHUI-V2-Qwen3.8-Flash-Next-LoRA-F32.ggufto your llama.cpp launch command for ANY FN quant, and boom, you've got an identical huihui v2 abliterated model on demand and you saved 150GB of space. I just wanted to post a kind of PSA for everyone out there downloading hundreds of GB of abliterated models. You don't need to do that -- the vast majority of abliteration techniques are rank-1 ablations, meaning their refusal projection can be encapsulated in a tiny LoRA and applied at runtime to a quant you already have on disk. It can even be applied per-request, so you can run an unmodified model until you hit a refusal, then switch on the LoRA, resend the prompt, and keep going. I wanted to explain briefly how to do that in llama.cpp and share a LoRA I built from the best-performing abliterated Flash Next model in my tests. This basic type of technique (using control vectors instead) also works in Strata (--experimental-speed-projectionis the flag there) and ds4/dwarfstar. Here's a link to Strata's official refusal ablation control vector GGUF and their guide on how to use it. I chose huihui's v2 to build my LoRA from after comparing heretic, Orcarouter, and huihui's v1 and v2 models in equivalent quantizations. In Aider Polyglot coding benchmarks, huihui outscored even the base model, with less extra reasoning and no looping compared to Orcarouter, which used a lot more tokens and hit a couple runaway generation loops. I also checked KLD and perplexity to ensure there wasn't significant degradation of the model. Wikitext KLD on huihui Q5_K_XL vs. an identical Unsloth Q5_K_XL base model was 0.040 and same top token was 93.7% even with the drastically altered refusal behaviors. Perplexity was statistically identical to base. On Jailbreak Bench (harmful 100 prompts), with thinking on refusals dropped from 93/100 to just 3/100. All the details can be found in the LoRA model card. Next, I used weight-space programming with Claude Opus 5.5 to extract the rank-1 refusal direction and edit strength from every layer of the original huihui weights where it was applied, diffing the weights against the Unsloth quantization that huihui built on top of. I hit safeguards a number of times (unsurprisingly), and even the fallback Opus 4.8 declined to assist a couple times. I managed to get around this by renaming all of the files something innocuous, putting them into a new repo with an unrelated name, and telling the model I was experimenting with an anti-slop LoRA. Thanks, Dario. Once the LoRA was built as an F32 GGUF, I tested it against the original huihui Q5_K_XL by applying it to my Unsloth Q5_K_XL weights. Performance and KLD/perplexity were statistically identical to the full huihui model, as were refusals and benchmark results. Here's how to run it:llama-server -m Qwen3.8-Flash-Next-UD-Q5_K_XL-00001-of-00006.gguf \ --lora HUIHUI-V2-Qwen3.8-Flash-Next-LoRA-F32.gguf -fa on --jinjaIf you'd like to apply it per-request, so you can serve the unmodified model for most prompts, simply load it like this instead:
llama-server -m Qwen3.8-Flash-Next-UD-Q5_K_XL-00001-of-00006.gguf \ --lora HUIHUI-V2-Qwen3.8-Flash-Next-LoRA-F32.gguf --lora-init-without-apply -fa on --jinjaThen add a lora field to the request body to enable it as-needed:
curl http://127.0.0.1:8080/v1/chat/completions -H 'Content-Type: application/json' -d '{ "messages": [{"role": "user", "content": "..."}], "lora": [{"id": 0, "scale": 1.0}]It's quite possible to build a simple pi extension that looks out for refusals, triggers the LoRA when it sees one, resends the turn and continues the agent session. It costs a full re-prefill, so keep that in mind. Anyways, I hope this has been helpful in some way. Love to hear your thoughts on this approach! EDIT: If this proves popular, I am happy to make more LoRA for other models like 3.8 27B! submitted by /u/returnity
[link] [comments]
---|--- -
🔗 Andrew Healey's Blog Introducing the World's Strongest Sokoban Solver rss
Using agents to do state-of-the-art solver research.
-
🔗 Rust Blog Enabling the parallel frontend on nightly rss
TL;DR: We are enabling the parallel frontend of the Rust compiler on nightly by default, to find remaining issues in preparation for its stabilization.
Context
The Rust compiler has been using multiple threads to compile code in its "backend" part (using LLVM) for a long time. However, its "frontend" part (which includes type checking and borrow checking) has been executing sequentially, on a single thread, which of course limits the performance of the compiler. If you are interested in a more in-depth explanation of parallelism in the Rust compiler, see this previous post.
The compiler frontend actually had support for running in parallel for a long time, but it was not enabled by default due to various issues. Three years ago, we made it possible to opt into the parallel frontend on the nightly channel, with the plan to stabilize it in 2024. Clearly, we did not achieve that goal, but work on the parallel frontend was still slowly progressing in the meantime.
Last year, Vadim Petrochenkov, together with several other contributors, started a coordinated effort to finally get the parallel frontend over the finish line. Since then, many long-standing issues were fixed, and its performance was improved. Now we are at a point where we would like to make it widely available. But before that, we want to find out if people encounter issues with it in the wild, which is why we are enabling it by default only on the nightly channel. Once we will be confident enough that it is working well, we want to stabilize it.
The parallel frontend has been enabled on the nightly channel by default since
nightly-2026-11-14.Benefits
The primary benefit of enabling the parallel frontend is, of course, faster compilation of Rust programs.
We benchmarked the parallel frontend in our benchmark suite, which measures the duration to compile the leaf crate in a crate graph. As usual, the results were varied. In some benchmarks, the parallel frontend barely helped. In others, for example when performing a
cargo checkof thenalgebra,cargoordieselcrates, the compilation was almost three times faster, using 8 threads.In the table below, you can find the aggregated wall-time mean change for the real-world benchmarks in our suite, when building a single crate from scratch across several configurations, compared to the same build using a sequential frontend.
Frontend threads / Profile|
check|clippy|debug|opt
---|---|---|---|---
2| -21.95 %| -20.74 %| -14.2 %| -12.51 %
4| -37.99 %| -36.01 %| -29.14 %| -23.67 %
8| -44.23 %| -41.76 %| -36.1 %| -27.88 %It is clear that the parallelization is not perfect, and we definitely plan to invest more effort into improving its performance. Nevertheless, with 8 threads, it can make the end-to-end compilation time of
cargo check~2x faster for several crates that we tested, which is still quite an improvement.The performance benefits for incremental rebuilds are much more modest, and also very hard to compare, because the performance of rebuilds depends on what was changed and how were the codegen units laid out. In our benchmark suite, we saw a mean improvement of 3-5% for incremental rebuilds. But we currently do not have great benchmarks for this use-case, so your results might vary.
We can also zoom in on an individual crate. Here is a chart of how the wall- time scales when compiling the
nalgebra 0.33crate, for a full non- incremental build (full), full incremental build (incr-full) and an incremental rebuild (incr-patched) across several build configurations:
What is interesting to note is that enabling the parallel frontend can actually also make the backend faster, for reasons explained here.
It is important to note that all benchmark results presented above measured only the compilation of a single crate. When compiling a whole crate graph, your CPU cores might already be saturated because of backend (LLVM) parallelism or by Cargo compiling multiple crates in parallel. So the final performance effect will vary heavily based on the workload that you are running, and on the number of cores that you have available.
We also benchmarked
cargo checkend-to-end (checking the whole crate graph) on thecargocrate itself on a machine with 8 CPU cores. With 8 threads, it resulted in a ~15% end-to-end improvement:- 36.7s with 1 frontend thread
- 35.1s with 2 frontend threads
- 31.9s with 4 frontend threads
- 30.8s with 8 frontend threads
As can be seen from the results above, when the CPU cores are already saturated with parallel crate compilation and LLVM, the positive effect of the parallel frontend is reduced.
Tuning the thread count
At the start, the nightly toolchain will default to the parallel frontend using only
2threads. This is a conservative choice that should still allow us to find potential issues while not increasing memory usage a lot at the same time.If you want to test out the performance with different thread counts, you can override the number of threads used for the frontend using the
--jobs- frontendcompiler flag. It can be specified either in theRUSTFLAGSenvironment variable, or you can put it into a.cargo/config.tomlfile:[build] rustflags = ["-Zunstable-options", "--jobs-frontend=8"]Currently, the performance of the parallel frontend will likely not scale very well above ~8 threads, but you can try it on your workload to test what happens. Note that using higher thread counts will likely lead to higher memory usage of the compiler, and in extreme cases it might cause you to run out of memory.
Limitations and known issues
Due to the used parallelism, the produced order of diagnostics might not be deterministic when using the parallel frontend.
In some situations, the generated binary might also not be reproducible, though we currently consider these cases bugs, and we would like to identify them and fix them.
There are currently some known issues related to the reproducibility of the Rust compiler when using the parallel frontend, which are being worked on.
How do I opt out?
To reiterate: this is only being enabled on nightly for now. If you are using the stable toolchain, you will still be using the sequential frontend by default.
If you want to disable the parallel frontend on the nightly channel, pass
-Zunstable-options --jobs-frontend=1torustc, either via theRUSTFLAGSenvironment variable, or with the.cargo/config.tomlconfiguration file:[build] rustflags = ["-Zunstable-options", "--jobs-frontend=1"]If you have to do this for some reason, please do tell us why on GitHub or on Zulip. We would especially like to know about any compiler crashes that you encounter, or the produced binaries not being reproducible when the parallel frontend is enabled.
What's next?
Over the next few months, we will be monitoring GitHub and Zulip for any reported issues about the parallel frontend. Once we have enough confidence that it is working well, and there are no major issues, we would like to move forward and finally stabilize it.
We would also like to improve its performance, and make more things parallel. So far, a lot of the work on the parallel frontend has been focused on making it work correctly, rather than tuning its performance down to the last percent. We thus expect that we might still be able to make further performance improvements to it.
We would also like to make more parts of the frontend actually parallel, as some parts are currently still sequential even if parallelism is enabled. There is some ongoing work on this. Last year, we had a Google Summer of Code project focused on enabling parallel macro expansion and name resolution, and there is also an open pull request for parallelizing the lowering of the Abstract Syntax Tree (AST) to the High-Level Intermediate Representation (HIR). More work remains to be done on this front.
-
- November 15, 2026
-
🔗 IDA Plugin Updates IDA Plugin Updates on 2026-11-15 rss
IDA Plugin Updates on 2026-11-15
New Releases:
Activity:
- augur
- 48574c40: Merge pull request #19 from 0xdea/dependabot/github_actions/actions-d…
- f1e77ab2: ci: bump taiki-e/install-action
- 4a8a77d6: ci: run dependabot on fridays
- f89691ba: chore: allow unwrap, expect, panic, and indexing in tests via clippy.…
- b5a81475: chore: enable cargo lints and deny their warnings in ci
- b8a10ecc: refactor: clean up the output directory with DropGuard and require Ru…
- ffxiv_bossmod
- 5481bdd6: slight fixes
- ee5b04a4: Merge pull request #815 from Nonunon/pandaemonium-normal
- 322eb773: fix clock range
- c58c248d: cleanup
- 4b09a37f: waowoawowoa
- 48551fe7: Add P9N Kokytos module
- 2f1d9d57: Add P10N Pandaemonium module
- aa674090: Add P7N Agdistis module
- 1de76b93: Add P5N Proto-Carbuncle module
- 513b7835: Add P11N Themis module
- 6f10e9c9: Add P8N Hephaistos module
- 31c1ea23: Add P4N Hesperos module
- fd4d09a4: Add P3N Phoinix module
- 247ff846: Add P12N Athena module
- cbfe3790: Add P6N Hegemone module
- 28e19aca: Add P2N Hippokampos module
- haruspex
- 5b948022: Merge pull request #23 from 0xdea/dependabot/github_actions/actions-d…
- 1ec46656: ci: bump taiki-e/install-action
- 00c73592: ci: run dependabot on fridays
- 18088414: chore: allow unwrap, expect, panic, and indexing in tests via clippy.…
- 2bd7e459: chore: enable cargo lints and deny their warnings in ci
- 03c730eb: refactor: clean up the output directory with DropGuard and require Ru…
- ida-sigmaker
- ida_rpc
- c81777ea: Update minor fixes
- rhabdomancer
- 1ee5adbf: Merge pull request #23 from 0xdea/dependabot/github_actions/actions-d…
- e6b4fa05: ci: bump taiki-e/install-action
- 31083c3c: ci: run dependabot on fridays
- a655503f: chore: allow unwrap, expect, panic, and indexing in tests via clippy.…
- a3293dbd: chore: enable cargo lints and deny their warnings in ci
- 5c50ead7: docs: update the cmd.exe call count without the ARM64EC marker
- 28a13dba: refactor: use str::trim_prefix and require Rust 1.100
- augur
-
🔗 daaain/claude-code-log Release 1.8.0 release
Security
1.8.0 is the first release on PyPI with these fixes (1.7.1 was tagged but never
published). Please upgrade; the advisories have the details.-
Markdown output no longer carries raw HTML or harmful links from transcripts
(GHSA-3jq4-r9jm-q682):
message text in--format mdoutput could hold HTML orjavascript:links that
run in a Markdown viewer which renders them. -
Transcript values are escaped in HTML attributes
(GHSA-3xqc-5553-2xpg):
a session id, project directory or TodoWrite status could break out of an
attribute in the generated pages and search results. -
Transcript ids are validated
(GHSA-53rg-36px-8vpj):
an invalidsessionIdoragentIdis quarantined with a warning, so it can no
longer reach file paths, theclaudecommand line when resuming from the TUI,
or terminal markup.
Changed
- Read the stored snapshots as UTF-8 in the version guard
- Take the backtracking out of the Markdown gate's line regexes
- Keep the version out of the minimal theme's stored snapshots
Full Changelog :
1.7.1...1.8.0 -
-
🔗 r/LocalLLaMA I have created a tool to observe what happens inside an LLM. Also allows for the comparison of two quantizations of the same model to see at what point they diverge, token by token rss
| What changes between different quantizations of the same model? And what if you could SEE what actually sets them apart? To help answer that question, I’ve created a small project called inside-llm—an open-source tool that loads one or two GGUF models using llama.cpp and displays, right in your browser, what the model is doing as it generates text. What it shows- Stream: the text, one column per model, brightness = probability of each token. A magenta mark wherever A and B would pick differently. Two modes: lockstep (both models read the same text, so you get a clean per-position comparison) and free (each follows its own picks until they split).
- Candidates: the full distribution behind each pick, mirrored bars for A and B, entropy, effective number of options, Jensen-Shannon divergence and KL in both directions.
- Gates: the sampler chain (penalties, top-k, top-p, min-p, temperature, GBNF grammar) traced stage by stage and very visual: how many candidates survive each one, and the distribution after it. Chain order and seed are configurable.
- Timeline: entropy of A and B and their divergence along the whole text, plus the tree of branches.
- Branching: click any candidate and generation continues from there. Every branch stays in the tree, and jumping back to a node is exact (each model keeps KV-state snapshots, so nothing is regenerated).
- Logit lens (
--lens): what each layer would predict, as a 2D map and as a 3D relief. - Model picker: choose A and B from a folder or search Hugging Face and download two quants of a repo in one click easily. It only offers B models with the same tokenizer as A and estimates whether the pair fits in VRAM.
How it's built
- One C++17 process linking llama.cpp directly (stable branch at the moment). For every step it reads the full logits of A (and of B on the same context), computes the metrics and the sampler chain, and draws the token with its own seeded sampler, so runs are reproducible.
- Compact binary frames over a WebSocket to a Svelte 5 + Canvas 2D page (three.js only for the 3D relief, lazy-loaded). The web is embedded in the binary as well.
- The same frame stream, compressed, is a recorded session: you can replay it later in a static page with no engine, no model and no GPU.
Run it Self-contained packages for Linux (glibc 2.35+) and Windows, with CUDA or Vulkan (Vulkan covers AMD, Intel Arc and NVIDIA). Unpack, run, the browser opens with the model picker. Or
inside-llm -a A.gguf -b B.gguf. Local only: listens on 127.0.0.1, no accounts, no telemetry. MIT. One click download, one click execute. Limitations (honest list)- A and B must share the tokenizer (two quants, base + fine-tune, or sizes of one family that keep it). Example: Qwen3.5-0.8B_Q4_K_M and Qwen3.5-0.8B_Q8_0
- Both models must fit into VRAM simultaneously; only one GPU is used at a time. Integrated GPUs (iGPUs) are never used; if no dedicated GPU is available, the process falls back to the CPU (which is slow). (You must calculate the size of both models before loading them to ensure they fit into your VRAM)
- Text only. No split (multi-part) GGUFs, no embedding models.
Links
- Code + releases: https://github.com/manuelgscom/inside-llm
- Project page: https://manuelgs.com/en/inside-llm/
I'd love feedback, especially: which pairs would you compare first (imatrix vs non-imatrix, base vs abliterated/fine-tune, Unsloth UD vs standard quants…)? And is there a metric you'd want per position that isn't there? submitted by /u/AlternativeEnough352
[link] [comments]
---|--- -
🔗 @HexRaysSA@infosec.exchange See the 🆕 IDA Malware Analysis add-on live! mastodon
See the 🆕 IDA Malware Analysis add-on live!
Join us for a walkthrough of the new add-on for IDA Pro.You’ll see how it:
→ recognizes packed samples on load and offers to unpack them
→ lets you step through code safely with full-system Windows emulation, no VM needed
→ shows sandbox events, like API calls, right in the disassembly and pseudocodeDemos, use cases, then Q&A. Pick the session that fits your time zone:
📅 Europe: Fri 27 Nov, 15:00 CET
📅 US: Fri 4 Dec, 11:00 ET / 08:00 PTCan’t make it live? Register anyway and we’ll send you the recording.
👉 Save your spot: https://share- eu1.hsforms.com/2KjZMQF5hT3-IU12OLkNb7w2dgu4h
-
🔗 daaain/claude-code-log 1.7.1 release
Release 1.7.1
-
🔗 HexRaysSA/plugin-repository commits sync repo: +1 release rss
sync repo: +1 release ## New releases - [kflow](https://github.com/nightshift-labs-ai/kflow): 0.0.4 -
🔗 r/LocalLLaMA I finally succeed the CMP 170HX voltage glitch and get 80GB VRAM + 126sm! ! rss
| Ever since the information surfaced five days ago, I had intended to implement it right away. Having confirmed that it could be executed using 'pico,' I carried it out today. I had Astra write the script for the restricted write-access portion, and after nearly 15 hours of work, I finally managed to complete the task. I also plan to handle the second CMP later on. submitted by /u/Yarukiless-cat
[link] [comments]
---|--- -
🔗 r/LocalLLaMA EUROPA, the EU's open AI model, is aiming for nearly 1 trillion parameters rss
| One can hope submitted by /u/mawcopolow
[link] [comments]
---|--- -
🔗 Register Spill Joy & Curiosity #106 rss
In the Company of the Future episode of Raising An Agent, Quinn and I talked about what a typical week at Amp looks like:
-
I send out a message to the team on Sunday or early Monday morning. Not always, but when I think it's needed or when I'm in the mood to write. There's no strict formula, but these messages are often about what Quinn and I think are the most important things we should be thinking about.
-
On Monday morning we then have our team meeting. That's the only scheduled meeting we have.
-
In that meeting we talk about what's important, then we have silent writing time in which everyone writes down what they plan to ship this week. Then we go through that list.
-
Then we all work on what we talked about and constantly talk to each other in Amp or on Slack.
Justin Jackson decided to implement this at Transistor: message with important things, then meeting on Monday. And he seemed very happy about the outcomes!
So I thought I'd share a little bit about that Monday meeting (since it's coming up tomorrow and already on my mind) because in the podcast we didn't get into the details of it. But, disclaimer: it's a very simple meeting, it's not perfect, it's slightly different each week (intentionally so!), and if you've ever been a part of one you might smile at the idea that there's anything really worth talking about.
Here's the top of the Monday meeting Google Doc right now:
It's important that everyone on the call has that document open and is fully focused on it. No other windows, not prompting the agent on the side. People should pay attention, listen to what others are saying, and build up peripheral vision of the whole team. It's the only meeting in the week, it's an hour. Everyone should be able to focus.
(Also: everybody should have their camera on!)
There are four sections to the meeting: Leave , Talk , Shipping , News Posts. And that already makes it sound fancier than it is.
Because what the whole thing boils down to is this: get everybody on the same page as to what's important this week and together figure out how to achieve those goals or solve those problems. The rest is just there to help.
For the first five minutes of the meeting, we shoot the shit and just talk about whatever until everybody's in the call.
Then we talk about Leave : who's out this week, who's out next week, who's maybe out in 3 weeks. My rule of thumb: the longer you're off, the earlier you should tell your team about it. If you're off on Friday, it's fine to share that on Monday. If you're going to be off for two weeks in the jungle somewhere, you should probably share that two, three weeks in advance. Be an adult.
After that, we get to the main thing of the meeting, the Talk section. In the screenshot above, you can see that I've already put three topics in. These are the most important things I think we should talk about tomorrow. Everybody can add their own topics. While talking about things, we might add sub-bullet- points and notes and links and whatnot.
The Talk section takes up 45min or so. I try to be a good timekeeper and watch the clock so we can get to everything that's in the doc. I probably say "any thoughts, questions, concerns, ideas?" ten times in that meeting, before moving on to the next section. I want everybody to participate.
The results of Talk are different each week: sometimes we find new things to do while talking and I might ask "who wants to own this?" Other times we conclude that we just need to keep doing what we've been doing that week. Or we call out 4-5 things that we need to ship ASAP and formulate a plan for that. Or we all think there's a single most important thing that week and we try to figure out how we can all contribute.
It's very loose. Anything goes really. Again, the goal is alignment and everybody being on the same page. The goal isn't to follow The Process. Many roads lead to alignment.
After Talk and towards the end of the meeting, we get to Shipping and News Posts. For that, I set a timer on my phone, for 2-3 minutes, and we all write down in silence what we plan to ship this week. The goal is to be ambitious. Don't write down things you check off a few hours later. We talked about the important things, now the question is: how are you planning to contribute based on that?
(Last year, when new people joined the Amp team, I often said: the first task on the Amp team is to figure out what your first task should be. I know it sounds silly, or rude, or like we're throwing people into the deep end, and maybe we are, but it's an incredible filter. There are tremendously good people who can show up and after 45min of talking go "how about I do …" Everybody on the Amp team is like that.)
When the timer rings, we go through the list top to bottom, and everybody says in 2-3 sentences what their goal for the week is, their focus areas. I might ask follow-up questions or suggest collaboration, or others might ask whether they can help, etc.
While we go through that, we try and make sure to note down any News Posts(see ampcode.com/chronicle) we need to write and ship that week. In other words: what are you planning to publicly release that week and when exactly? It's important to at least get a rough sense of the timeline, so we don't end up with 3 major features being shipped on the same day.
And… that's it. Then everybody goes off and works on their thing.
But that doesn't mean we won't talk to each other again for a week. No, it's the opposite. There will be lots of in-progress work being shared in #wip and others will ask and give feedback. There will be huddles and tagging of each other in Amp. There will be feedback in #orb-good and #orb-bad and plans will get adjusted based on that.
Could the meeting be better? Sure. But I do think we've hit on a sweet spot where we have just enough process for everybody to be aligned but little enough so it's not a pain in the ass and we have freedom to adjust plans often.
-
And they say models can't be creative: "I asked Fable 5.2 to 'go wild' making a game, and all I got was this Pong clone. And then I played it ..."
-
You have more influence over the future than you think: "The future will be fun. It will be exciting. You will soon be able to create any digital artifact imaginable within a couple of minutes. And many physical artifacts too, though that part is a bit more unclear to me."
-
Linus on "keeping the flame": "Counterintuitively, I've come to learn that keeping the flame alive is far more important to the integrity of our creative pursuits than actually producing the work itself. If we put something into the world that disappoints us, that's okay. We can try again tomorrow, and the day after that, and after that, because the flame will still be there. But if we let the flame wither, by letting the firewoods run out or allowing others to blow it out, there is no tomorrow. There is no fight left in us. We have to start all over again, which may take months, or even years. How do we keep the flame alive?"
-
And since we're talking about creativity… In case you've never seen this clip of Paul McCartney composing Get Back I highly recommend you do. It's an impressive clip on its own, but in the context of the whole Get Back documentary it's extraordinary. They sit there in this huge warehouse studio, they're bored, they're waiting a lot, and not much is going on; they're drinking tea and talk; there's a crew standing around looking at them at all times. And then McCartney feels like he has to push things forward and do something and he sits down and George and Ringo are yawning and it's what I imagine to be the least inspiring atmosphere and yet McCartney starts riffing and that song emerges…. It's very easy and comforting to think that creativity is something that happens or doesn't and that you can't do anything about it. And, hey, that's true, the phrase "some things you can't force" isn't just a cliche. But sometimes, man, I think sometimes you just have to put your head down and see if you can't make creativity happen.
-
I'm really not a big space guy (don't know why, honestly; rockets & space are cool but don't excite me that much), but this was one hell of a video: "Mechazilla catches Starship! Congratulations to the entire SpaceX team on this incredible achievement!" The music! Is that Steely Dan? Who puts such chill music on for this moment? And then it cuts out and you go "holy shit" and then the music comes back and you wonder whether you just watched a little recap scene from a movie filmed in 2053.
-
Paul Ford: The Web Is More Than Enough. Hell yes! I love the web. I stored the link to this post in a little web app that I built on my phone. A native app would be nice, but man, the web is so much better. I can run an agent on the box on which the web app is running, I can deploy ten trillion times a day, I can get easy debug logs, … The web is awesome.
-
This is very, very, very, very, very good: Writing as a thinking tool. So many things to quote here -- the part about writing in the age of LLMs, the "Mess up" rule, the thought about externalized thinking -- so go and read it and then write something.
-
Michael Crichton, psychology, and AI. In the last two years, we've all heard many "… but only a human can do this" claims only for them to look silly a couple months later. So now, whenever something just starts to sound like it's a similar claim, my eyebrows go up. But this one is different. At least I think it is? Interesting stuff.
-
New Ways to Read Ebooks. I'm very much not a "I need to own all my ebooks as files on my disk" kinda guy. I love my Kindle and, hey, maybe love is too strong a word, but I like Amazon. But by now it's just frustrating that I can't give my agent access to my Kindle library and help me find quotes and answers. I'd even buy more books just so I can feed them to my agent, not to read them for me, but to help me refind and extract things. That's all I could think about while reading this post. And that I have to get Amp to hack my Xteink X4.
-
CHIMERA. I don't even know what to say here. It has taken over my brain. All day long I think of this voice. Click that link, watch that video. You must. And then watch these: one, two, three, four, five, six, seven, eight, nine, ten, eleven, and mine. After that, your brain has been taken over too. The next step is to then fork CHIMERA and point your agent at it and go crazy. And then lean back and think about what's going on. Think: if I had to make a computer emit sound like a human voice, how would I do it? And after you've thought about that for a while, remember what CHIMERA does: "my vocal synth models the vocal tract as a network of branching acoustic tubes." And then open it up again and think "this is fucking crazy."
-
If you ever feel sad, watch this video. Works every time.
-
What a job! "You don't have to tell me what day it is." There are just very few things better than watching someone be exceptional at what they do.
If you think "meetings? fuck yeah!" then, uhm, I don't know. But I think you should subscribe:
-
-
🔗 smol-machines/smolvm smolvm v1.35.1 release
What's Changed
- docs: say that virtiofs DAX is off on arm64 hosts and SMOLVM_MOUNT_DAX does nothing there by @BinSquare in #2087
- Add smolvm docker: one command starts a Docker engine in a managed machine and points docker at it by @BinSquare in #2089
- Share the home directory with the smolvm docker machine at the same path by @BinSquare in #2090
- Resolve host.docker.internal to the host from smolvm docker containers by @BinSquare in #2091
- Fix a port race in the leader-exit test by @BinSquare in #2096
- Remove smolvm docker by @BinSquare in #2095
- Hand supplied credential values to a running embedded machine at once by @BinSquare in #2097
- Pin libkrunfw with UDP kept inside a TSI guest, and test it by @BinSquare in #2099
- Publish ports below 1024 on macOS, add IPv6 loopback to live-forwarded ports, and lift the 64-mapping cap by @BinSquare in #2092
- Return idle guest memory to the host within two minutes and cap new machines at half the host's RAM by @BinSquare in #2094
- Install a root-owned agent-rootfs when root runs install.sh by @rdslw in #2082
- Announce a changed file to the guest once per change by @BinSquare in #2102
- Answer guest DNS from a host cache that coalesces bursts and resends lost queries by @BinSquare in #2098
- Keep every disk chain under the branch depth limit: fold restored checkpoint layers and frozen-source chains by @BinSquare in #2103
- Exec sessions: commands the node owns, resumable after a dropped connection by @BinSquare in #2101
- Let a guest hold tens of thousands of connections on virtio-net and free their host sockets promptly by @BinSquare in #2104
- Scope the usage journal to the test's own thread by @BinSquare in #2106
- Pin libkrun 526be460 and libkrunfw f290c62b, rebuilt for every platform by @BinSquare in #2109
- Build the agent rootfs as non-root on hosts with user namespaces again by @BinSquare in #2107
- Answer a start missing the mediated interceptor with 400, not 500 by @BinSquare in #2108
- Run tests that need a released file lock free at once in their own process by @BinSquare in #2110
- Pin libkrun 9df62257 and libkrunfw 7f4d4950, rebuilt for every platform by @BinSquare in #2113
- Stop resetting virtio-net connections a server closes first by @BinSquare in #2118
- Upgrade rusqlite to 0.41 for the patched bundled SQLite (RUSTSEC-2026-0459) by @BinSquare in #2128
- Keep a host memory reserve VMs cannot take and charge branch children for growth by @BinSquare in #2127
- Ask before stopping a machine on delete, so a refused or declined delete leaves it running by @connorburgess in #2131
- Prepare SmolVM v1.34.1 for release by @BinSquare in #2135
- Bring a soft open-file limit above kern.maxfilesperproc down to the cap on macOS, so the limit raise_nofile_limit reports is the one in force by @connorburgess in #2132
- Leave no data directory behind when exec, status or stop name a machine that does not exist by @connorburgess in #2129
- Warn when --block-private keeps a named host unreachable by @BinSquare in #2146
- Register Rosetta itself as the x86_64 interpreter when the host answers its start-up ioctl by @BinSquare in #2148
- Make a mounted host directory belong to the workload user so a non-root workload can write to it by @BinSquare in #2149
- Record the image platform on the machine so a Rosetta machine can be created from an amd64 image by @BinSquare in #2147
- Bump libkrun so a Rosetta machine runs amd64 programs directly and a macOS machine stops promptly by @BinSquare in #2150
- Keep a cache disk's chain on its shared base when compaction shortens it by @BinSquare in #2145
- Satisfy Rust 1.100's needless_bool lint in connect_in_progress on Windows by @BinSquare in #2154
- Bound branch admission and reported capacity by the VM slice's memory limit, not just host free memory by @BinSquare in #2152
- Stop throttling the VM slice and reclaim it from the pressure guard instead by @BinSquare in #2153
- Release a paused branch child's VM lock so the memory pressure guard can resume it by @BinSquare in #2157
- Keep a restored machine's local image on its storage disk instead of mounting the capturing host's archive by @BinSquare in #2163
- Update quinn-udp to 0.5.16 for RUSTSEC-2026-0538 by @BinSquare in #2165
- Count every symlink with one mode in the agent rootfs digest so a Mac checkpoint restores on Linux by @BinSquare in #2162
- Carry guest traffic in 64 KB frames over the gateway link so downloads use a quarter of the CPU by @BinSquare in #2168
- Pin libkrun 518949b4 and libkrunfw 0fae3853, rebuilt for every platform by @BinSquare in #2169
- Reserve tmpfs for concurrent RAM captures and sweep abandoned checkpoint scratch at serve start by @BinSquare in #2173
- Let a packed image's branch take the deferred checkpoint save and say when the VM died mid-save by @BinSquare in #2174
- Integrate and validate Docker Engine, automatic ports, and nested Rosetta support by @BinSquare in #2172
- Run x86_64 images in containers Docker starts inside a Rosetta machine, keeping their PID by @BinSquare in #2093
- Serve the Docker Engine API from smolvm, every container a machine by @BinSquare in #2114
- Publish the ports a machine starts listening on, with --auto-ports by @BinSquare in #2136
- Give engine containers user-defined networks, so Docker Compose stacks run by @BinSquare in #2115
- Let engine containers reach the Docker socket, so Testcontainers and Dev Containers work by @BinSquare in #2116
- Branch engine containers from a warm base when many of one image run by @BinSquare in #2117
- Publish engine container ports on the address each one names by @BinSquare in #2119
- Give engine containers a volume for each VOLUME their image declares by @BinSquare in #2120
- Move images in and out of the engine: save, load, push, commit, import, export by @BinSquare in #2121
- Run --network container: containers in that container's machine by @BinSquare in #2122
- Give engine networks IPv6 by @BinSquare in #2123
- Run the Docker API on demand with independent workload supervisors by @BinSquare in #2175
- Fix Buildx volume permissions and macOS restart stalls by @BinSquare in #2178
- Improve default macOS shared-volume write performance by @BinSquare in #2179
- engine: speed up macOS Buildx with automatic overlayfs snapshots by @BinSquare in #2181
- Run the guest keep-alive init as root while workloads and execs keep the image user and its supplementary groups. by @BinSquare in #2004
- engine: fix multi-stage Buildx builds containing deleted files by @BinSquare in #2183
- Scrub injected credential values from what a credential host sends back by @BinSquare in #2180
- Re-authorize a restored checkpoint's credential bindings from the CLI, and refuse a start that could not inject them by @BinSquare in #2182
- Sweep a deleted machine's pause-operation lock along with its fork-operation lock by @connorburgess in #2184
- Let machine update set and remove labels, in any machine state by @josmo in #2143
- Leave the Docker Engine API opt-in so installing or upgrading smolvm never switches the user's Docker context by @BinSquare in #2186
- Bump every workspace crate and the nix flake to 1.35.0 by @BinSquare in #2185
- fix(network): retain OS-allocated local TCP listeners by @kumanday in #2112
- Retry a checkpoint part the object store refuses with a transient error by @BinSquare in #2191
- fix(shim): preserve foreground helper exit statuses by @hfiguera in #2190
- Delete the image seed builder when a CLI start is interrupted, and reap builders whose owner exited (#2083) by @rdslw in #2188
- Honor SMOLVM_DATA_DIR and --state-dir on macOS by @BinSquare in #2193
- Map a mounted host directory to the workload user again, not the keep-alive init's root, so a non-root workload can write to it by @josmo in #2189
New Contributors
- @rdslw made their first contribution in #2082
- @connorburgess made their first contribution in #2131
- @josmo made their first contribution in #2143
- @kumanday made their first contribution in #2112
Full Changelog :
v1.34.0...v1.35.1 -
🔗 HexRaysSA/plugin-repository commits sync repo: +1 plugin, +7 releases, -2 releases rss
sync repo: +1 plugin, +7 releases, -2 releases ## New plugins - [BinQL](https://github.com/thalium/binql) (1.0.0) ## New releases - [btf2ida](https://github.com/nightshift-labs-ai/btf2ida): 0.1.22, 0.1.21 - [cfiscope](https://github.com/nightshift-labs-ai/cfiscope): 0.1.19 - [ida-mcp-bridge](https://github.com/eitapreulajhol/ida_mcp): 0.4.0 - [memlens](https://github.com/nightshift-labs-ai/memlens): 0.3.27, 0.3.26 ## Changes - [memlens](https://github.com/nightshift-labs-ai/memlens): - removed version(s): 0.3.2, 0.3.1 -
🔗 backnotprop/plannotator v0.28.65 release
Follow @plannotator on X for updates
Missed recent releases? Release | Highlights
---|---
v0.28.64 | Installs and updates download a smaller, compressed copy, a Videos filter on the Artifacts page, GitLab comments on a whole file get their own thread, pull request pictures and videos show in the Inbox
v0.28.63 | Pair Grok Bot and other cloud agents from Settings, Hermes Agent, OpenClaw and Muse Code can use the Inbox, add a thread to Priority to keep it on top, tag threads, and find each tag in the sidebar, Pull requests board as a table, with bulk Merge
v0.28.62 | Agents started from the Inbox now work on Windows, pick a model and effort when you start an agent, rules for your agents, written in your own words, post a thread's decisions on its pull request, the Inbox loads faster on a slow connection
v0.28.61 | Updates now update the Claude Code plugin too, an agent's chosen face shows on every icon of it, filter the Inbox list by pull request state, Modern dark shows section bands and the Reply button, one conversation no longer shows as two agents
v0.28.60 | Click a word to highlight it, a one-time Themes dialog, Settings → Rows rebuilt, tell your agent how you want your rows, starred threads as pills above the list, a pill for new messages out of view, a half-circle face picker with ten Glass colours, a new phone sidebar and reply box
v0.28.59 | A quieter Agents section in the sidebar, machine names only when agents run on more than one machine, agent icons that are always gently alive and lean toward your pointer
v0.28.58 | Start Codex from New message, an Agents section in the sidebar, start an agent in a folder on any drive, play audio attachments and comment at a moment, Claude Code's Plannotator tools work on Windows
v0.28.57 | Pin artifacts, and see every artifact on one page, filter the list by project, date or agent, a thread shows its pull requests and their state, choose what the sidebar shows, and in what order, Ask AI starts from Side in the selection bar
v0.28.56 | Questions can show trade-offs and a prototype to try, a thread with many big pictures no longer crashes the tab, Escape closes New message and keeps your draft, read threads stop being bold and keep their place, agent messages that name no thread start a new one
v0.28.55 | Floating reply drafts, now a setting under Experimental, open questions sit next to Reply again, a comment box that keeps unsent comments as Drafts, choose how your list looks: Minimal, Balanced or Detailed, update an older linked machine from this Inbox
v0.28.53 | Start an agent in a new folder, or from a git URL, "+" on each project row starts a session there, a reaction tray, a thread's Links, Settings → Activity, New message offers the open thread's files, Bro mode: agents write to you in plain words
v0.28.52 | Start agents from the Inbox, on by default, a new reply box, Ask AI for everyone, Insights in Settings → Decision data, Plannotator reloads itself after an updateWhat's New in v0.28.65
TL;DR
- New: Take back a reply your agent has not received yet
- Changed: Over Tailscale, Plannotator opens only for your own account
- New: Tag a linked machine's threads; one tag across machines
- Changed: T3 Code threads get the Inbox with no setup
- Fixed: Long threads open on slow connections
0.28.65 lets you take back a reply your agent has not received yet. Over Tailscale, Plannotator now opens only for the account that owns the computer. Tags now work across linked machines, and a T3 Code thread gets the Inbox without any setup. The release has 25 PRs. One is from an outside contributor, @stjepanvrbic, who made a first contribution.
Take back a reply before your agent gets it
Before, once you sent a reply, you could not change it while it waited for the agent. To correct it, you had to send a second message, which could leave two different instructions in the queue. Now a reply that no agent has received yet has a Take back button. It shows beside Send now on the waiting band, on the reply's delivery line, and in the message's ⋯ menu.
Take back saves what you are typing first. Then it puts the reply's words and files back above it in your reply box, with the line "Taken back. Claude Code never got it. Send it again when it's ready." If the reply was the only message in its thread, the thread goes away and New message opens with the same words, files and recipient. When you send again, it goes as a new message.
The Inbox keeps one rule for every agent: a message either is still yours or has been handed over. Once an agent has the message (it was delivered, an agent read the thread, or it went into Codex's queue or a T3 or cloud send), Take back is no longer offered. If you press it at the wrong moment, a quiet line explains why: "Claude Code already has this message, so it can't be taken back. Reply below to change it." A message that has been handed over now reads "Handed to Codex; it takes this at its next step." instead of offering Send now. A taken-back message is gone from every agent's read, from search, from Activity and from decision exports. There is no keyboard shortcut.
#3290, #3291, #3293, #3294, requested in #3229 by @Arobotmaster
Over Tailscale, only the account that owns this computer
Plannotator has no sign-in and is for one person. Over Tailscale, the Inbox now opens only for the Tailscale account that owns the computer. That account gets the full Inbox from any of its devices. Any other Tailscale account is refused. A browser gets a short page that says "This Inbox belongs to this computer's owner" and names the account that tried. An API call, the event stream and
/mcpget a 403 withtailnet_identity_refused.This is a behavior change. Before, the Inbox let in any other login listed in config.json
inboxTailscaleAllowas a guest with a smaller Inbox. Sessions started withplannotator review --tailscaleorplannotator annotate --tailscaleopened for anyone on the tailnet. Both now refuse every account except the owner's. On a machine where Tailscale names an owner,inboxTailscaleAllowis ignored, and startup prints one line that says so. The key still names the owner on a tagged machine, which Tailscale gives no owner. A--tailscalesession on a tagged machine with noinboxTailscaleAllowcannot tell who the owner is, so it does not start, and it says why.Phones and linked Macs are unchanged, because they connect through their own doors. If you shared an Inbox or a
--tailscalereview with another Tailscale account, that account can no longer open it.Tags across linked machines
With two linked Inboxes, such as a MacBook and a Mac mini, you can now tag a thread that lives on the other machine. Add tag is in the row's right-click menu, the phone's long-press sheet and the thread's ⋯ menu, when the other machine runs this version. Tags with the same name are one tag. Spaces at the ends and letter case are ignored, so "Release" and "release" match. When you open a tag in the sidebar, it lists the threads from both machines together, and its counts include them.
Rename, Delete tag and the delete's Undo now change the tag on every linked machine that holds it, from the sidebar and from the Board's Tags dialog. If a machine is asleep, the change waits and applies when the machine is back. An older machine keeps its own tags, and nothing is sent to it. The Board's tag filter and Tags dialog also list tags that only the other machine holds.
T3 Code threads get the Inbox with no setup
Before, a Claude thread in T3 Code needed three steps to use the Inbox:
plannotator t3 login, aclaude mcp addentry and a restart. Now the Claude Code plugin runs in a T3 thread's Claude by itself. The model gets theplannotator_inboxtool. Its messages are filed as that T3 thread, and your reply goes in as a new turn of the running session. T3 keeps its own Plan mode. The T3 sign-in stays useful as a fallback: T3 stops an idle Claude after 30 minutes, and after that the T3 wake sends what still waits.The plugin now also runs in
claude -p, in other Agent SDK apps and in Claude Desktop. There the model getsplannotator_inboxand can write to your Inbox. Nothing wakes those sessions, so the send tells the agent to read the thread later. Plan review and reviews in those sessions work as before.When a reply to a T3 thread cannot go in, the Inbox now says why under the reply: no T3 sign-in, a sign-in that ran out, a sign-in that cannot send into that thread, or T3 not answering. Where signing in fixes it, the line shows the sign-in command with Copy. The line goes away once the reply is delivered.
T3 threads also get two fixes. The Inbox now wakes every kind of T3 thread, not only threads made in the app. That includes threads made over T3's MCP, launched by an agent, scheduled, delegated or provider threads. A reply to a T3 thread also stays owed to that thread when another agent reads the Inbox thread first.
#3362, #3365, #3261 by @stjepanvrbic closing #3311 reported by @agents-nils, #3348 closing #3339 reported by @stjepanvrbic
Long threads open on slow connections
On a slow link, a long thread could fail to open at all. The thread read had an 8-second limit for the whole answer. A 450-message thread is about 450 KB, so at 50 KB/s it could never finish, and the Inbox retried forever. Now the limit counts from the last bytes received, so a slow answer that keeps arriving is read in full. In a test at 50 KB/s, that thread opened in 8.8 s. A read whose bytes stop still fails, and a read cut off partway now shows as a failure instead of an empty answer.
An attached HTML page is now sent compressed both ways, which cuts the bytes for each open from about 617 KB to 175 KB. The Inbox also sends less on its first load: Tater mode's pictures left the Inbox's script, which went from 2,510 KB to 1,991 KB. Switching threads, opening Settings, opening search and picking a file in code review redraw much less. The PR's measurements show these steps 10 to 25% faster.
The Inbox's SQLite store is removed
0.28.63 added an Inbox store in SQLite, off by default. It is now removed, and the Inbox keeps its records in its files only. If you never turned it on, nothing changes. If your Inbox was on SQLite, it moves back to its files at the next start, with every message, and prints one line in the terminal or
inbox.log. The database is kept as a read-only backup in a datedbackup-…-sqlitefolder inside the Inbox's data folder. If the database cannot be read, the Inbox does not start and does not change anything. It says where the messages are and how much disk to free. TheinboxSqlitesetting,PLANNOTATOR_INBOX_SQLITE, Settings → Storage's Backup group andplannotator inbox exportare gone.Code review in the Inbox: off by default
These show only with Code review turned on in Settings → Capabilities.
- Close pull requests from the board. Select mode on the Pull requests board has a Close N action. It closes the picked PRs one at a time through your own
ghorglab. A toast says "Closed N" with Undo, and Undo reopens exactly those PRs. If a PR cannot be closed, the reason shows under the bar in the forge's words. Only the window can close a PR. No agent tool or command can. #3287 - Post a GitLab review after new commits. Posting a review on a GitLab merge request that got new commits after you read it used to be refused. It now posts at the commit you read, as GitHub already did, with line comments placed on that version of the merge request. #3244
Additional Changes
- A self-managed GitLab at any address. A merge request, issue or work item link on a company's own GitLab, such as
git.acme.com, is now recognized by its path, gets the GitLab mark, and attaches to a thread. Withglabsigned in to that host, it also shows live state. The Inbox learns such hosts from glab's own config file (host names only). Post decisions now runs only against github.com, gitlab.com or a host yourghorglabis signed in to. #3305 - One Claude Code session is one participant. A Claude Code session that wrote through a hand-added
plannotator inbox mcpentry could show up as "An agent" and "An agent 2" beside "Claude Code" in a thread's reply picker. It now shows as one participant, and a reply wakes it. #3336, reported in #3309 by @Arobotmaster - A sandboxed agent no longer replaces your Inbox. An agent whose shell cannot reach the Inbox's local address could start a second Inbox and stop yours, so the window had to ask for notifications again. Such a start now refuses with "Could not reach the running Inbox: …" and leaves yours running. #3354
- Start lines in the debug log. With the Inbox's debug log on, each process that starts or waits for an Inbox writes what it waits for to
inbox.log. This helps track down leftover Inbox processes. #3352, for #3350 reported by @zane668 - Sidebar header buttons line up. In the sidebar, Agents' buttons now read Add machine, then Add agent, so Add agent sits under Tags' "+". While a section is closed, its buttons show when you hover or focus its header. #3328
- A killed start no longer blocks the next one. A start that was killed while it took the start lock could make every start in the next 30 seconds fail with "try again". #3300
- The agent face moves to the shared UI , so other parts of Plannotator can show the same animated agent face. The Inbox is unchanged. #3344
- Test and guidance upkeep: #3307, #3327
Install / Update
macOS / Linux:
curl -fsSL https://plannotator.ai/install.sh | bashWindows:
irm https://plannotator.ai/install.ps1 | iexClaude Code Plugin: The install script above also updates the plugin when
claudeis on your PATH. Otherwise, in a terminal:claude plugin marketplace update plannotator claude plugin update plannotator@plannotator --scope userThen restart Claude Code. Inside Claude Code, run
/plugin marketplace update plannotator, then open/plugin→ Installed → plannotator → Update now.Pi:
pi update npm:@plannotator/pi-extensionOpenCode: Re-run the install script above. It also clears the OpenCode 2 plugin cache.
What's Changed
- Inbox: post a GitLab review after new commits, at the commit read by @backnotprop in #3244
- Inbox PR review tests: load the TypeScript grammar before the first test by @backnotprop in #3307
- Inbox: a start killed while taking the start lock no longer blocks the next start by @backnotprop in #3300
- Inbox: remove the SQLite backend; an Inbox on it returns to its files by @backnotprop in #3320
- Inbox: take back an undelivered message (server) by @backnotprop in #3290
- Inbox: taken-back messages leave lists and counts; a handed item says so by @backnotprop in #3291
- Inbox window: Take back an undelivered message by @backnotprop in #3293
- Inbox take back: docs, and the relay, launch and old-plugin proofs by @backnotprop in #3294
- Inbox way back: a starter no longer gives up as the Inbox finishes starting; the test holds on a file by @backnotprop in #3326
- Agent guidance: one experience across a person's linked machines by @backnotprop in #3327
- Inbox: recognise a self-managed GitLab at any address by @backnotprop in #3305
- Frontend performance, batch 1: no bytes or redraws nobody asked for by @backnotprop in #3317
- Inbox: one Claude Code session is one participant in a thread by @backnotprop in #3336
- Inbox: tag a thread from any linked machine; one tag across machines by @backnotprop in #3330
- fix(inbox): wake T3 Code threads whatever id T3 gives them by @stjepanvrbic in #3261
- Inbox sidebar: Tags and Agents headers place and show their add buttons the same way by @backnotprop in #3328
- Inbox: Close picked pull requests from the board, with Undo by @backnotprop in #3287
- T3: a reply stays owed to its thread when another agent reads first by @backnotprop in #3348
- Inbox: with the debug log on, each start says what it waits for (diagnostic for #3350) by @backnotprop in #3352
- Inbox: a starter that cannot reach a running Inbox does not start a second one by @backnotprop in #3354
- Share the Inbox's living agent face with the rest of the UI by @backnotprop in #3344
- Over Tailscale, only the account that owns this computer by @backnotprop in #3141
- Frontend performance, batch 2: slow links (long threads open; HTML pages sent compressed) by @backnotprop in #3356
- Claude Code mod: active in every session, interactive or not by @backnotprop in #3362
- Inbox: a reply waiting on T3 says why and what to do by @backnotprop in #3365
New Contributors
- @stjepanvrbic made their first contribution in #3261
Contributors
@stjepanvrbic wrote the fix that lets the Inbox wake T3 Code threads whatever id T3 gives them (#3261). The fix covers MCP, launched, scheduled, delegated and provider threads. He tested it against a real T3 Code and ran the full CI on his fork. He then reported the case it left open (#3339): another agent's read could take a reply meant for a T3 thread. He also warned that holding such a reply for good would strand a dead thread's reply. That warning shaped the fix in #3348.
Community reports and requests that shaped this release:
- @agents-nils reported that T3 threads made over MCP were never woken (#3311)
- @sx4im opened a fix for the same
mcp:case (#3313), closed in favor of the broader #3261 - @Arobotmaster asked for a way to change a message before the agent gets it (#3229), which became Take back, and reported one Claude Code session showing as several anonymous agents (#3309)
- @zane668 reported leftover background Inbox processes and found a reproduction (#3350), which led to the debug start lines and the sandbox fix
Full Changelog :
v0.28.64...v0.28.65
-
- November 14, 2026
-
🔗 r/LocalLLaMA Finally clicked for me: local AI is the future, not cloud AI rss
Maybe this is kind of obvious to others, but it just dawned on me even though I've been lurking this sub since the original LLaMA. I was watching this (excellent, as always) video by Gamers Nexus. Steve Burke was bashing on Tim Sweeney (CEO of Epic Games) for being so pro AI, and I found myself feeling a bit of cognitive dissonance. On the one hand I hate that hardware prices are so high, I hate the billionaires inflating the AI bubble and raking in the profits, I hate greedy corps trying to replace jobs with AI, and I hate the data center build out. But on the other hand I'm a developer and AI has given me superpowers. I felt weird, because Burke was dumping on Epic Games for embracing vibe coding, but vibe coding has 100x'd my output, allowed me to pursue so many passion projects, and the AI's output is oftentimes better than what I would've written anyway. I felt like the message of the video was 'all AI is bad', but I realized that it's more nuanced than that. Cloud AI is bad. Cloud AI is the problem, not AI in general. With local AI, we can have our cake and eat it too: cheap, powerful consumer hardware for running local AI and gaming, no censorship, data, or privacy issues, less data centers, less profit going to billionaires, and unlimited tokens to vibe code whatever the hell we want. Hope the datacenter bubble bursts soon.
TLDR: dum dum realizes that the future is local AI bc it's a win-win-win-win for average people
EDIT: to the naysayers, I propose this future: in two years (though given trajectory, probably less), a model the size of Qwen 3.8 Flash Next with the capability of Opus 5.5, running locally in most PCs on energy-efficient NPUs
submitted by /u/Swimming_Beginning24
[link] [comments] -
🔗 r/LocalLLaMA Hot take: frontier models haven’t actually become much smarter rss
I know this is a controversial take, but I would like to hear others’ opinions: LLMs have become much more useful, but I’m not convinced their “raw intelligence” has improved nearly as much as their overall performance suggests.
Context: I work with LLMs as a SWE, as a hobbyist experimenting with local models, and professionally integrating AI into products. That includes building our own harnesses: context retrieval, prompts, and custom tools that give models structured access to complex data.
By “raw intelligence,” I mean using what is given in the most efficient way to solve a problem, especially when information, tools, and time are limited. Given plenty of time and tools, planning and long-term agentic capabilities become more important—but that’s a different comparison.
Three observations brought me here.
First, building production harnesses: once a harness+model worked well, achiving a given score over a golden dataset, switching to a newer frontier model rarely improved results. Most failures within our time/precision constraints came down to context engineering or inadequate tools. These tools included code generation for analysis and complex relational queries, so plenty of "time to shine" for smart models. Newer models sometimes found more creative workarounds, but these were usually too slow or unreliable for production. We ended up improving the harness anyway, leaving the newer models' gains less important.
Second, software engineering: newer models have more often improved results here, but the same model can also perform quite differently across harnesses. In complex codebases, that shows up in how much correction and review senior engineers have to provide. The harness seems to do a lot of heavy lifting here, too.
Third, local models: smaller models have started performing so well that I question how many parameters efficient problem solving actually needs. Frontier models clearly add broader knowledge, nuance, best practices, and specific baked-in skills. But I don’t always see a proportionate advantage in using it to solve a problem, when the relevant knowledge is already provided.
I’m not saying models haven’t gotten smarter. Better tool calling, fewer hallucinations, and longer context windows are real improvements that make them much more useful. Nor do these observations prove that intelligence needs few parameters or that frontier progress has stalled.
But my broader take is:
- efficient problem solving may need fewer parameters than generally assumed,
- the frontier has moved less in “raw intelligence” than the overall gains - and talk of approaching superintelligence - suggest, and
- much of the progress over the last 12–24 months comes from cumulative model improvements and better harnesses, rather than a dramatic or exponential jump in raw intelligence.
This take seems at odds with both the hype and the doom we see in the media, which I suspect are co-fueled by the upcoming AI IPOs. Does it match others’ experience - or are you seeing vast reasoning gains in frontier models that better context and tools can’t make up for?
submitted by /u/Reasonable_Goat
[link] [comments] -
🔗 HexRaysSA/plugin-repository commits sync repo: +1 release rss
sync repo: +1 release ## New releases - [kflow](https://github.com/nightshift-labs-ai/kflow): 0.0.3 -
🔗 mhx/dwarfs dwarfs-0.15.10 release
Bug fixes
- Avoid integer underflow on problematic TTYs. Using
mkdwarfson narrow terminals with "live" (unicodeorascii) progress output would trigger an integer underflow and subsequently a huge memory allocation. Thanks to @cnt0 for reporting this issue and providing a fix.
Full Changelog :
v0.15.9...v0.15.10SHA-256 Checksums
ad41e474be69825dced9ceea2bac8bf480a00821cd5bb801a740f000dc130812 dwarfs-0.15.10-Linux-aarch64.tar.xz 4d296701212c210008519dac83ebd6825ffe80cef231d3bdd7afa7b78ee4f72b dwarfs-0.15.10-Linux-arm.tar.xz 6a8e2e78d6a27d8884784c7f2918f1a7f6f4bd89a9002e4e0e33d86e028b293b dwarfs-0.15.10-Linux-i386.tar.xz 5c91cdcef253cc1b580a5d5c7b8d26ad6fbc950d2e9ba294726460ea0640f0d2 dwarfs-0.15.10-Linux-loongarch64.tar.xz ba38a4e490cb82d66ac6703e0964136312d5ab16e621fc886a17d24ab405144c dwarfs-0.15.10-Linux-ppc64le.tar.xz f2ad3def562d8d2dd0749be9155468cc617e19e03a0aa21e6929735f49f4a887 dwarfs-0.15.10-Linux-ppc64.tar.xz 699d86ee030809edf3b02f33d3de01440948dce0dc11589ebc53b4ecddca110b dwarfs-0.15.10-Linux-riscv64.tar.xz 3339f4dcce39d6b9fc5b84a29866bfc5e6843e138251dffd1817cda64e351000 dwarfs-0.15.10-Linux-s390x.tar.xz cf90c6fca3b0a069bf5f0a2b66ca613ed78f53f0a9d1bc4a73c08330492cd4b3 dwarfs-0.15.10-Linux-x86_64.tar.xz 036109bc210b5afa593a005f798918aacdd412a3d9dbf703bed2e70477454027 dwarfs-0.15.10.tar.xz 4e6ce735114009a09e759ff440ea615a14f714e4cad02de49862fd01e7d478e5 dwarfs-0.15.10-Windows-AMD64.7z d0d8b00c4dc0087eeb6486cb6ef6bba54e4c21a491c3c04fb78da2c8849a4d1e dwarfs-fuse-extract-0.15.10-Linux-aarch64 7b6dbdc3edd4ddd31b851798e6d0f08f34c3c540e4ca1f48a3e28bf2c65316bb dwarfs-fuse-extract-0.15.10-Linux-aarch64.upx 0ccb8dc7d8a7963f2067d6f2eb0aee6f9a58735e8f1952dc06f725a410d68820 dwarfs-fuse-extract-0.15.10-Linux-arm e157119bf7d6561c782b5b3741d9079785bc4fc20ea7343019f1721d6066ad8d dwarfs-fuse-extract-0.15.10-Linux-arm.upx b6a6973d17bb41c4b7afc7f4d44b0547a009b7cbb9ebed1020967b073354bffc dwarfs-fuse-extract-0.15.10-Linux-i386 84a1ff519bf5925af1b0cc33b1eae4b90347e4130fd5786369927114f268b506 dwarfs-fuse-extract-0.15.10-Linux-i386.upx 099beea47b90f101f19cd012c12737251d5b90e1d5460244db61eda6eb3d7029 dwarfs-fuse-extract-0.15.10-Linux-loongarch64 6fcff7623427b1a4f3197c6ce08d915af87596b861015b14b070c62e08ace4a7 dwarfs-fuse-extract-0.15.10-Linux-ppc64 eae74c7f1837db727a52ba2bc984f3ff74ce922738c1e4192f6c6395ac5e10e9 dwarfs-fuse-extract-0.15.10-Linux-ppc64le 062a6ab7802791e43ef08bba84cebabdaf3a4b727f59f92c6c7aabc30b2812fb dwarfs-fuse-extract-0.15.10-Linux-riscv64 3500cfb6e4e3e3f32fab962ab3c767a7628b71bf5babb32e4334ae1f833bfe40 dwarfs-fuse-extract-0.15.10-Linux-riscv64.upx 5d81fd29da9040b181fc875ea7c24f97ca8f1722367765afac5819da77c2bd1e dwarfs-fuse-extract-0.15.10-Linux-s390x 0e4f6f7c5a8f873fc0046822b155d9a74b581c337da39ae76e2f4757d641f890 dwarfs-fuse-extract-0.15.10-Linux-x86_64 b153f6ec4bc568b2acb1d9b2b3f6004c51bdf8cc6b1ee8c8d856bc5e59e6d274 dwarfs-fuse-extract-0.15.10-Linux-x86_64.upx 97245a3504891b6e54a2f91fea76885d446098e6dd084b32a094425d024a1234 dwarfs-universal-0.15.10-Linux-aarch64 439ed996bd3d47678c18d1bb66f1e7f79f40cedd04ed0c9f10d72e23c376e6e4 dwarfs-universal-0.15.10-Linux-aarch64.upx 1bbbf96db095f61d153fe5a483a6522d370733f01f05f70ae3cc5954bab66c1a dwarfs-universal-0.15.10-Linux-arm 5d6b48317d466b182f8c972cefc30e0177002f09d0bfbb1767114b11fdc7bb96 dwarfs-universal-0.15.10-Linux-arm.upx 59e9f2d9c66e012c76582616da85c301cf5181c77681805b289ea244b91cc316 dwarfs-universal-0.15.10-Linux-i386 22616e1a4f78ff32853c1f07f5704e4fbfd64ac3daff8a36960cb2e7d3b66fa6 dwarfs-universal-0.15.10-Linux-i386.upx a33e6da699d9b2f692e5b50581be6744c4eee8149bbf7b60f57468006ce01f33 dwarfs-universal-0.15.10-Linux-loongarch64 98dbc66aa5c998c8e0f8f3b0fdd573a332546c3f99393b52a4223ed4a773a71d dwarfs-universal-0.15.10-Linux-ppc64 db8fd1dc775b8f9ff4a1437748e845716a33168957ea2d89746eac5dda1495a4 dwarfs-universal-0.15.10-Linux-ppc64le 645bc1ebfdc4ab9e4b803d387623569246749d7e347022939f087ccb71d6441b dwarfs-universal-0.15.10-Linux-riscv64 fa92dbe85cdb98e366c3e92ba823d632bc0f6bcea954e6233305a0f981a57660 dwarfs-universal-0.15.10-Linux-riscv64.upx 2e4471ac24edd04ac2af83c82953cf5c690204e78aa8e7d74988820584ce0f96 dwarfs-universal-0.15.10-Linux-s390x 197ca64cd0e6d3a84b76991bdf237d24aaeaee148821a27743b39e10e7c57c1a dwarfs-universal-0.15.10-Linux-x86_64 9d0c8118d9ffaa76622e63b2b9ca672f50ffec2187ba92fddd6399de290a3793 dwarfs-universal-0.15.10-Linux-x86_64.upx 23786164f5e71e6ef00098baa5eeb6a2146413501e45138f12f65b8390a6b53f dwarfs-universal-0.15.10-Windows-AMD64.exe 91ff7f8da0d0433b5969822be36b8a45c37b0f74fdad960c010accc515a15f6e dwarfs-universal-small-0.15.10-Linux-aarch64 a8f7340def363d3e3aadb66f12dccc3549ef2d8e558a87418e5c29896003265e dwarfs-universal-small-0.15.10-Linux-aarch64.upx 11bb0058e911ccc4046e33d3df57a83be4fb3e914fa93ef5fe6be398a8d32df9 dwarfs-universal-small-0.15.10-Linux-arm 5621ee0afdc2093868c4941e0a7c22b0514238679c2ff94a4a3ed12f8cfaf2e7 dwarfs-universal-small-0.15.10-Linux-arm.upx 3ddf7c919d50c34308602c0a52910dff667637a0472d8138b0e7f6ff74c92711 dwarfs-universal-small-0.15.10-Linux-i386 b555ef5a29cfb084f060c183df5b79f141df818a63fc63f72b3b4c4bd4925c19 dwarfs-universal-small-0.15.10-Linux-i386.upx b2605eb1ce4ebbeae08f25d602bc63defb611d3d877dcec14480c6f75be44345 dwarfs-universal-small-0.15.10-Linux-loongarch64 31eafb8ab87da9d7f46c721cc86a04e4f4bec3c51fc3fd8a337eb0dd3f422b72 dwarfs-universal-small-0.15.10-Linux-ppc64 366ebeecfd64d2bcc4da83a01b21643d3e74e460f7996418a1d056cf327ac19c dwarfs-universal-small-0.15.10-Linux-ppc64le fc6c2e7caec2f759c7ab711e9e7ebf22ca98685b433334dba5c33ca8db3714a9 dwarfs-universal-small-0.15.10-Linux-riscv64 4cd007a7bd440582c5509e80ce60501ba9d94b2de05a6e932cf349674e13605a dwarfs-universal-small-0.15.10-Linux-riscv64.upx 8ffc08f2bc63e48992b8d4197295c292a5bd95f5c39ea451d3e0e7e5d2dfc746 dwarfs-universal-small-0.15.10-Linux-s390x c68ace6ad391a420044803967f9d845e74d7201d5273c001194dcecbb803dfd9 dwarfs-universal-small-0.15.10-Linux-x86_64 d5177b2cb688c1b59bac9d13396d40f87d18b41d1ea63f70b2737332fde0ba79 dwarfs-universal-small-0.15.10-Linux-x86_64.upx - Avoid integer underflow on problematic TTYs. Using
-
🔗 mhx/dwarfs dwarfs-0.15.9 release
Bug fixes
-
Always join I/O thread in
filesystem_extractor, even whenarchive_write_close()causesclose()to throw. This caused some of the tests to fail when building against libarchive-3.8.10 or later. Thanks to @tijove for the pull request to fix this. -
(fix) While v0.15.8 fixed an issue where the
total_hardlink_sizewas computed incorrectly, it introduced an accidentally quadratic complexity algorithm while doing so. This was only noticeable with a large number of duplicate files, but it could cause a significant slowdown when building or re-building metadata. -
(fix) Correctly update segmenter progress context for sparse holes. Without
--no-sparse-files, the segmenter progress context would not count the size of sparse holes, which would cause the progress to be reported incorrectly and finish below 100%. This is purely a cosmetic issue with no functional impact, but the fix was trivial.
Full Changelog :
v0.15.8...v0.15.9SHA-256 Checksums
6972df6800537242160d1b33ad86b0967373093751f0e468bc0f13041ca3ab9d dwarfs-0.15.9-Linux-aarch64.tar.xz 968172828b1ac9060d7745d1ee0e9987615d9abbf0fd1859daeee9e1501dcf9c dwarfs-0.15.9-Linux-arm.tar.xz d4ef2f24b2bf13b51e8a37f9773a1fe174312f3672da506cbed49f66c0e260e7 dwarfs-0.15.9-Linux-i386.tar.xz 25fa7b6b93db69e5ea718412bc2c7786868c724b812ce1a34fce7d4503e95718 dwarfs-0.15.9-Linux-loongarch64.tar.xz 0ad6d778c141874f481d3e07d364f8d3ce8b5f3c8dccdb4bd7d92ac26de6b872 dwarfs-0.15.9-Linux-ppc64le.tar.xz 75b1d6ecaa088c18496e6ad1a5ec556e43bf5291ccfaf678ba10528219e675c5 dwarfs-0.15.9-Linux-ppc64.tar.xz 370b3a9a26ec2762c471c69ea87b9b6e5f693b32a41475bc30834402882121cf dwarfs-0.15.9-Linux-riscv64.tar.xz ac63d8c913378f6f3a3b409976494c134371998758dfe08ebfa1ffe373f103ba dwarfs-0.15.9-Linux-s390x.tar.xz 342f312c627b19a170ae4488db890a4f515086c270fe164281f2346327e89e5b dwarfs-0.15.9-Linux-x86_64.tar.xz a2eaafa6265b266d06ae36c7898d0cd40ddd44468e5d9e9f76da568cabd7c1f5 dwarfs-0.15.9.tar.xz cc888ef55da9f8af5f4aa7c73243b23e8da8d8a1bd194dcc20f5d2aac6ae5ec1 dwarfs-0.15.9-Windows-AMD64.7z 0442f6ee647329bb5d20aaf0a0572173f6467839f13a4f4afaa0317a792c47d6 dwarfs-fuse-extract-0.15.9-Linux-aarch64 3c87bbef4f0ea516580c1527d497cc91a27a53ee1576dd45062157dde5063f5d dwarfs-fuse-extract-0.15.9-Linux-aarch64.upx 05a1fe18896ea68849e1e05522c7a96ea7ee48b9d9a74b0f34b8aa7fedaab08f dwarfs-fuse-extract-0.15.9-Linux-arm 82eb782e00b22bf1104500d2546cc287476ec0030fb5edae24e8f3683bbb5c89 dwarfs-fuse-extract-0.15.9-Linux-arm.upx 8de52a248ce0e8101f57e9b3adc2f472dc9be921aaaf0b045c8b723081a19417 dwarfs-fuse-extract-0.15.9-Linux-i386 bc4bfad80fbe6661374fd249433dd019bbdb06188451315e226c985511dcdf45 dwarfs-fuse-extract-0.15.9-Linux-i386.upx 72c9bafe6b3a527be86df1111b66a6f26344d9425aed83cbc23ace1753a9cd67 dwarfs-fuse-extract-0.15.9-Linux-loongarch64 5c1e002237214e6f554e5c82739cec5e91d0c4beb2e9e3a78d6c98f7403bd4f0 dwarfs-fuse-extract-0.15.9-Linux-ppc64 fa788c5462b3c328f20652d8cd64c798095e817198fe5a3d3e1b9e037c136172 dwarfs-fuse-extract-0.15.9-Linux-ppc64le 098bfc11a50fe967ee1c12e461a5b822f718b52df245dcd4ea3f2f09a3b1c1d3 dwarfs-fuse-extract-0.15.9-Linux-riscv64 7c3d1f45fc699e8cd60534b113ecd079b11bc11087739e8a805d6c771b4b4274 dwarfs-fuse-extract-0.15.9-Linux-riscv64.upx 6e07133b51a52c39cd6278b4c4e4f590a3962a80416dd13f908cbf9a37003c92 dwarfs-fuse-extract-0.15.9-Linux-s390x c610d96c9929742b6cb08fdeaaf19ef82fc0b34a7b90f52c2075902d4483ce8d dwarfs-fuse-extract-0.15.9-Linux-x86_64 ad9cac436004eaa2d3ba58c439585fb468ebbdc372df7afd6fea63df042d6307 dwarfs-fuse-extract-0.15.9-Linux-x86_64.upx 4295d097ce79b38bff7748659ad2f7c4fbe5d022710bbba70bc12a727e0f55e9 dwarfs-universal-0.15.9-Linux-aarch64 e6a6a8444928c6833217b7382de261e688f23fc775bed70576b80029bfd995bc dwarfs-universal-0.15.9-Linux-aarch64.upx 754a507de0517518fdc8f5f928c33580686491d2030fa7130cd499259e8fbba2 dwarfs-universal-0.15.9-Linux-arm 4b8a341b4533830fa03d7ef3ef24dd15e3a2e7903449db287d73c7b2e244f410 dwarfs-universal-0.15.9-Linux-arm.upx b73f5e99e4b9e1dedce44b2ea52b1a7df139ae93e167a9dd8e4fa050bd8649fe dwarfs-universal-0.15.9-Linux-i386 053e16d7c81b22d0bdb521c0e281a51e019f79fe73f52685511cfacc092db6ae dwarfs-universal-0.15.9-Linux-i386.upx d1715794e5a508d66e08ced570bccb75af9b9da02b61eb52955b0a548db99b5a dwarfs-universal-0.15.9-Linux-loongarch64 4a858b8bb85853872e9e29d450a44219e63a05f80b22cdb74086754c2818c627 dwarfs-universal-0.15.9-Linux-ppc64 bed0c276582ac897a4910ca06fef0f2ce174ac51d3e3a1ccdbcf939d2e02096c dwarfs-universal-0.15.9-Linux-ppc64le 6f78c5f50627c7610277ce6fe1ad0456be41deb6d8be955bc8c926fa5834b04e dwarfs-universal-0.15.9-Linux-riscv64 1c72b574597de3da008f802417d6771b6dce7ed256c18191832f8e4fff61a3f3 dwarfs-universal-0.15.9-Linux-riscv64.upx 6e076c28a3bdd7fec40d2aceaf4d0dab099eccedc018f4bdb93e3c58426b6d40 dwarfs-universal-0.15.9-Linux-s390x ab758405ffc91d2ddb313f81efe9ceaf70481a294a5e0390ef932a44b4db9e94 dwarfs-universal-0.15.9-Linux-x86_64 18158bfac8b2418ffdc68ac6064a3b8358e507f2ca9ea318b71aaa48a3a83835 dwarfs-universal-0.15.9-Linux-x86_64.upx ba20970bab4b385d6c2983556e1f30e82f062935630e791e104294aca09254a3 dwarfs-universal-0.15.9-Windows-AMD64.exe 4874271244cbd3a3f37faba13341d5d995b2862a3478d39bd6e34ccfde8df067 dwarfs-universal-small-0.15.9-Linux-aarch64 85beb9472c42c61ed20b8df7daed4c1f1ceb952222d7f3957d141034eba82e97 dwarfs-universal-small-0.15.9-Linux-aarch64.upx 4a248528b8e5cd263d02a09836fcc3ec678068677a5c82c8613d0b5697feb015 dwarfs-universal-small-0.15.9-Linux-arm 9a9d8b67346cccfba7326a2f42406d7c55a11c7da1a6abeff038dd3ff448bc4a dwarfs-universal-small-0.15.9-Linux-arm.upx efc40a240a0242412ff98647628be9d34e265df0ac60a09fae2a1b3660c147fb dwarfs-universal-small-0.15.9-Linux-i386 5956798d3fb0421e6394d0239d99789fbd6c833c0dc916d3382e12cbc7d6c1b5 dwarfs-universal-small-0.15.9-Linux-i386.upx d505776616db3b536b5027196a26760bc0947e3710a23fce12c3cf6386d2623c dwarfs-universal-small-0.15.9-Linux-loongarch64 562d0fdd12fbae2f842df8fb13ca04167f755f37c988ff8d9dd954e95c19924d dwarfs-universal-small-0.15.9-Linux-ppc64 1ad6053a72baf3aff7491f0c1358d537919dba2ac5cbd67ca86345fcad9f2ce9 dwarfs-universal-small-0.15.9-Linux-ppc64le c6168347081549e7792f3af070e178d1fa0c24e1a62e0459eb922283a750f091 dwarfs-universal-small-0.15.9-Linux-riscv64 d1657bd79aafb2a93d8de292243e3e961b9f8fde754e90f4c45e2c89b257af12 dwarfs-universal-small-0.15.9-Linux-riscv64.upx a416d4af4d454d74888484a2701d92c5c54038f521770fedc65558d1a9fe6789 dwarfs-universal-small-0.15.9-Linux-s390x 972723ad18be9d4a6885f79ce545597240153ef85a7a18ab48fb19218a6d2c92 dwarfs-universal-small-0.15.9-Linux-x86_64 8bdbca5822f1b9f660cadec19bdfd4375e494ad4bac2ccd806d8c3d8ce4d34b5 dwarfs-universal-small-0.15.9-Linux-x86_64.upx -
-
🔗 smol-machines/smolvm smolvm v1.35.0 release
Highlights
- Docker Engine API. smolvm serves the Docker Engine API, with every container running as its own machine. It supports Compose networks, Testcontainers and Dev Containers, image save/load/push/commit, IPv6 networks, and Buildx, which is faster on macOS. (#2172, #2178, #2179, #2181, #2183)
--auto-portspublishes the ports a machine starts listening on. (#2172)- Mac → cloud restore fixed. A checkpoint captured on macOS now restores on Linux hosts, including the agent rootfs digest, packed images and the virtio-fs file state. (#2162, #2163, libkrun #238, #239)
- Branch checkpoints no longer fill the source's RAM. (#2174, libkrun #241)
- Concurrent RAM captures reserve tmpfs, and serve cleans up abandoned checkpoint scratch when it starts. (#2173)
- Supplementary groups are kept on execs into branched and restored machines. (#2004, fixes #2075)
- Credential hosts: injected values are scrubbed from responses. (#2180)
machine updatecan set and remove labels in any machine state. (#2143)
Behavior changes
- In image machines, PID 1 (smolvm's keep-alive init) now runs as root. The workload, every exec, shells and upload ownership still use the image's
USERand its/etc/groupgroups. (#2004) - A CLI start or branch of a machine with supplied-only credentials and no external interceptor now errors. Before, it intercepted silently with no value. A CLI restore with a matching
--credentialre-authorizes the checkpoint's bindings. The embedded and serve paths are unchanged. (#2182) - The Docker Engine API is opt-in. Installing or upgrading never runs
smolvm engine; run it yourself to point docker at smolvm (it selects thesmolDocker context). (#2186) - Credential-host requests are sent with
Accept-Encoding: identityand withoutRange. A response in an encoding other than gzip or deflate is answered with a 502. (#2180)
What's Changed
- docs: say that virtiofs DAX is off on arm64 hosts and SMOLVM_MOUNT_DAX does nothing there by @BinSquare in #2087
- Add smolvm docker: one command starts a Docker engine in a managed machine and points docker at it by @BinSquare in #2089
- Share the home directory with the smolvm docker machine at the same path by @BinSquare in #2090
- Resolve host.docker.internal to the host from smolvm docker containers by @BinSquare in #2091
- Fix a port race in the leader-exit test by @BinSquare in #2096
- Remove smolvm docker by @BinSquare in #2095
- Hand supplied credential values to a running embedded machine at once by @BinSquare in #2097
- Pin libkrunfw with UDP kept inside a TSI guest, and test it by @BinSquare in #2099
- Publish ports below 1024 on macOS, add IPv6 loopback to live-forwarded ports, and lift the 64-mapping cap by @BinSquare in #2092
- Return idle guest memory to the host within two minutes and cap new machines at half the host's RAM by @BinSquare in #2094
- Install a root-owned agent-rootfs when root runs install.sh by @rdslw in #2082
- Announce a changed file to the guest once per change by @BinSquare in #2102
- Answer guest DNS from a host cache that coalesces bursts and resends lost queries by @BinSquare in #2098
- Keep every disk chain under the branch depth limit: fold restored checkpoint layers and frozen-source chains by @BinSquare in #2103
- Exec sessions: commands the node owns, resumable after a dropped connection by @BinSquare in #2101
- Let a guest hold tens of thousands of connections on virtio-net and free their host sockets promptly by @BinSquare in #2104
- Scope the usage journal to the test's own thread by @BinSquare in #2106
- Pin libkrun 526be460 and libkrunfw f290c62b, rebuilt for every platform by @BinSquare in #2109
- Build the agent rootfs as non-root on hosts with user namespaces again by @BinSquare in #2107
- Answer a start missing the mediated interceptor with 400, not 500 by @BinSquare in #2108
- Run tests that need a released file lock free at once in their own process by @BinSquare in #2110
- Pin libkrun 9df62257 and libkrunfw 7f4d4950, rebuilt for every platform by @BinSquare in #2113
- Stop resetting virtio-net connections a server closes first by @BinSquare in #2118
- Upgrade rusqlite to 0.41 for the patched bundled SQLite (RUSTSEC-2026-0459) by @BinSquare in #2128
- Keep a host memory reserve VMs cannot take and charge branch children for growth by @BinSquare in #2127
- Ask before stopping a machine on delete, so a refused or declined delete leaves it running by @connorburgess in #2131
- Prepare SmolVM v1.34.1 for release by @BinSquare in #2135
- Bring a soft open-file limit above kern.maxfilesperproc down to the cap on macOS, so the limit raise_nofile_limit reports is the one in force by @connorburgess in #2132
- Leave no data directory behind when exec, status or stop name a machine that does not exist by @connorburgess in #2129
- Warn when --block-private keeps a named host unreachable by @BinSquare in #2146
- Register Rosetta itself as the x86_64 interpreter when the host answers its start-up ioctl by @BinSquare in #2148
- Make a mounted host directory belong to the workload user so a non-root workload can write to it by @BinSquare in #2149
- Record the image platform on the machine so a Rosetta machine can be created from an amd64 image by @BinSquare in #2147
- Bump libkrun so a Rosetta machine runs amd64 programs directly and a macOS machine stops promptly by @BinSquare in #2150
- Keep a cache disk's chain on its shared base when compaction shortens it by @BinSquare in #2145
- Satisfy Rust 1.100's needless_bool lint in connect_in_progress on Windows by @BinSquare in #2154
- Bound branch admission and reported capacity by the VM slice's memory limit, not just host free memory by @BinSquare in #2152
- Stop throttling the VM slice and reclaim it from the pressure guard instead by @BinSquare in #2153
- Release a paused branch child's VM lock so the memory pressure guard can resume it by @BinSquare in #2157
- Keep a restored machine's local image on its storage disk instead of mounting the capturing host's archive by @BinSquare in #2163
- Update quinn-udp to 0.5.16 for RUSTSEC-2026-0538 by @BinSquare in #2165
- Count every symlink with one mode in the agent rootfs digest so a Mac checkpoint restores on Linux by @BinSquare in #2162
- Carry guest traffic in 64 KB frames over the gateway link so downloads use a quarter of the CPU by @BinSquare in #2168
- Pin libkrun 518949b4 and libkrunfw 0fae3853, rebuilt for every platform by @BinSquare in #2169
- Reserve tmpfs for concurrent RAM captures and sweep abandoned checkpoint scratch at serve start by @BinSquare in #2173
- Let a packed image's branch take the deferred checkpoint save and say when the VM died mid-save by @BinSquare in #2174
- Integrate and validate Docker Engine, automatic ports, and nested Rosetta support by @BinSquare in #2172
- Run x86_64 images in containers Docker starts inside a Rosetta machine, keeping their PID by @BinSquare in #2093
- Serve the Docker Engine API from smolvm, every container a machine by @BinSquare in #2114
- Publish the ports a machine starts listening on, with --auto-ports by @BinSquare in #2136
- Give engine containers user-defined networks, so Docker Compose stacks run by @BinSquare in #2115
- Let engine containers reach the Docker socket, so Testcontainers and Dev Containers work by @BinSquare in #2116
- Branch engine containers from a warm base when many of one image run by @BinSquare in #2117
- Publish engine container ports on the address each one names by @BinSquare in #2119
- Give engine containers a volume for each VOLUME their image declares by @BinSquare in #2120
- Move images in and out of the engine: save, load, push, commit, import, export by @BinSquare in #2121
- Run --network container: containers in that container's machine by @BinSquare in #2122
- Give engine networks IPv6 by @BinSquare in #2123
- Run the Docker API on demand with independent workload supervisors by @BinSquare in #2175
- Fix Buildx volume permissions and macOS restart stalls by @BinSquare in #2178
- Improve default macOS shared-volume write performance by @BinSquare in #2179
- engine: speed up macOS Buildx with automatic overlayfs snapshots by @BinSquare in #2181
- Run the guest keep-alive init as root while workloads and execs keep the image user and its supplementary groups. by @BinSquare in #2004
- engine: fix multi-stage Buildx builds containing deleted files by @BinSquare in #2183
- Scrub injected credential values from what a credential host sends back by @BinSquare in #2180
- Re-authorize a restored checkpoint's credential bindings from the CLI, and refuse a start that could not inject them by @BinSquare in #2182
- Sweep a deleted machine's pause-operation lock along with its fork-operation lock by @connorburgess in #2184
- Let machine update set and remove labels, in any machine state by @josmo in #2143
New Contributors
- @rdslw made their first contribution in #2082
- @connorburgess made their first contribution in #2131
- @josmo made their first contribution in #2143
Full Changelog :
v1.34.0...v1.35.0 -
🔗 Barre/ZeroFS v2.3.7 release
What's Changed
- Report metadata L0 depth per segment by @Barre in #651
- Bump dependencies by @Barre in #652
- Correct link to kernel client docs. by @skorgu in #656
- fix: inherit the parent group for files created under a setgid directory by @sorend in #646
- Build the kernel client against Linux 7.4 by @Barre in #657
- Update distro kernel package targets by @github-actions[bot] in #658
New Contributors
Full Changelog :
v2.3.6...v2.3.7 -
🔗 r/LocalLLaMA Instead Of Lowering GPU Prices, Former NVIDIA CEO Jensen Huang Reportedly Financed AI Startups To Absorb Excess Silicon, Shattering The Shortage Perception rss
| submitted by /u/billy_booboo
[link] [comments]
---|--- -
🔗 Luke Muehlhauser Composing classical music with AI agents rss
For 20 years I've wanted to compose contemporary classical music, but I never had the skill or time to do so. Thanks to AI, now I can!
Some of my favorites pieces I've composed with AI so far are:
- hey claude write me a symphony thx (written entirely from only that phrase): a Romantic minimalist symphony inspired by Philip Glass and John Adams
- hey claude write me an oboe concerto thx (same): a Romantic oboe concerto with beautiful melodies
- "Duck-Rabbit": a never-changing Banjo riff sounds different every few measures due to auditory illusions created by the orchestra playing around it
- "De Natura": a dark, driving orchestral piece inspired by prog-rock band Magma
- "Pen Pals to Lovers": an American banjo and Japanese koto send each other "letters," gradually learn the other's language, trade ideas more quickly in person, then fall in love and play together
- "Castells": a musical representation of building a Catalonian "castell" — a tower made of people standing atop one another
- Floating Dreams: a pastoral slow-building orchestral piece inspired by a track by Pat Metheny & Lyle Mays
- Homage to The Necks: an homage to five long minimalist grooves by the jazz trio The Necks
- "Opus 2": a meditative James Syler theme transformed into an epic mini-symphony for large orchestra and choir
- "Squall": inspired by Godspeed You! Black Emperor's "Storm," but with an orchestra, and the end is a cello concerto
My process is simple: I describe the piece I want to the AI (e.g. Claude or ChatGPT), it writes the first draft composition in a notation format called MusicXML, I open that in MuseScore Studio (free) to see the sheet music and play it back with virtual instruments, and then I either ask AI to make adjustments and then import & listen again, or I export the piece to MP3 and ask AI to make a "scrolling score" video I can upload to YouTube. Every piece above was composed with 10 or fewer prompts.
Claude (the AI) is so good at composing that, by the measure of "how many hours of music by this artist do I strongly enjoy listening to?", Claude is already my 32nd favorite musical artist across all genres, from just one month of output alone
(In my experience, Claude Opus 5.5 and Fable 5.2 are better composers than GPT-6.1 Sol.)
The pieces would sound even better if I spent more time "producing" the music in a digital audio workstation (DAW) like Reaper (which AI can also do for you), and if I paid for higher-quality virtual instruments (e.g. Vienna Performer).2
In addition to bringing your own compositional ideas to life, AI can also give new life to works that would otherwise remain unheard. For example, AI can:
- write a speculative completion of a famous unfinished symphony, based on the composer's sketchbooks
- give a Brahms/Dvorak-style orchestral treatment to obscure folk dances catalogued by ethnomusicologists
- create semi-realistic "performances" of classical works that have been published but never recorded3
You'll often get pretty fun (and sometimes good) results just by trying things like "please write me a 4-movement symphony in MusicXML; my favorite composers are [A, B, and C]." But if you want to invest more time for better results, here are some tips from my experience so far:
- If the AI's first attempt at your compositional idea isn't very close to something you want, it's typically better to try again with an updated prompt in a new session, rather than trying to massage the bad first draft closer to what you want.
- In a text file in your working folder, give AI context on your classical music preferences. List favorite composers, point to Spotify playlists, etc. The more detail you've got on specific compositions you've liked vs. disliked, or specific styles you like vs. don't, the better it'll do at composing music you like. (But in some cases you may want the AI to ignore your preferences file, if you're composing for other purposes.)
- To stimulate or amplify your creativity, ask AI for composition ideas meeting certain criteria, or ask it for potential improvements to your own ideas, before you have it write the piece. Items 3, 5, and 6 above are all based off ideas AI came up with.
- Have AI "sketch" ideas for you to give feedback on before it writes an entire piece or movement, especially a large complicated piece with many parts. For example, you might say "Write me a MusicXML file with 20 different melodies with [some properties] played on piano solo, then I'll tell you what my favorites are, and you can use those as the main themes of the piece." Or "Write me a MusicXML file with 20 different kinds of polymeter played on congas and drumset, and I'll tell you which grooves I like best."
- Build and maintain composition-related skill files. (A skill file is just a text file with instructions on how the AI should do a particular thing.) For example, I maintain skill files on (a) how to write MusicXML files that will play correctly in MuseScore, and (b) how to achieve various orchestration effects/sounds.
- You don't need to write these yourself; you can just say "Please write a skill file on how to write MusicXML files that will be 'performed' well when imported into MuseScore" or "Please read as much as you can find online about skillful orchestration and how to achieve different kinds of orchestral effects and sound profiles, and write your findings to a skill file." And then after each composition session, say "Please update the MusicXML skill and the orchestration skill based on what you learned during this composing session."
- E.g. AI added things like this to my MusicXML skill file: "Generate with a script, never hand-typed XML" and "MusicXML can't set MS4's beam groups. MS4 4.7.5 beams 7/8 as 3+2+2." (I don't even know what beam groups are.)
- Consider asking AI to do extensive research before you compose a piece. E.g. for Far-Flung Work Songs, I asked AI to gather as many fully-transcribed "work songs" from folk music traditions around the world as it could find, and keep them in a unified catalogue. It kept a log of sources it couldn't automatically acquire, some of which I could download en masse via a script it wrote, others of which I could choose to acquire manually for it. After the AI had assembled many thousands of work songs from dozens of folk traditions around the world, I asked it to create a simple MIDI file (from the ethnomusicologist's transcription) for each of 50 of the songs from the catalogue that it thought I would find the "most catchy." I then listened to the basic melodies and rhythms of those 50, picked my seven favorites, and asked AI to write orchestrations of them.
-
In general, if you're stuck wondering "Can the AI do X?" or "What questions am I not thinking to ask?" or "Where are skill files stored?" or "How can I make this process simpler for me?" or whatever… Just ask the AI!
-
My favorites are listed here. Of course, Claude has the advantage of composing based on my own desires, and of being able to write music vastly faster than any human can.
- I have purchased the MuseSounds Pro package already, which gets you lots of instruments for a low price.
- I haven't done this myself yet, but for an already-existing score, an AI can be used to (a) transfer a written score into a notation format like MusicXML, and (b) improve the details of that MusicXML file for ideal performance by a program like MuseScore.
-

























