🏑


  1. October 26, 2026
    1. πŸ”— anthropics/claude-code v2.1.311 release

      What's changed

      • Added --hold-idle-file and --max-hold-min to self-hosted-runner, to keep an idle session while your host reports processes it left running
      • Added a tip for the Explanatory output style, shown when you ask Claude for explanations
      • Fixed long freezes at startup and after reading or editing files when a CLAUDE.md file holds a very long list item
      • Fixed interrupting Claude not taking effect until a timeout while an MCP server had not answered a resource read or a skill was still downloading
      • Fixed standard-context sessions stopping with "Usage credits required for 1M context" when a request ran over 200K tokens; Claude Code now compacts the conversation and continues
      • Fixed Write and Edit stalling for up to 5 seconds after they ran, and reporting 0 lines changed, when changing thousands of lines in a file
      • Fixed subagents being unable to use MCP tools from servers that finish connecting after the subagent starts
      • Fixed Claude seeing stale MEMORY.md and CLAUDE.md content right after automatic compaction when those files were edited earlier in the session
      • Fixed claude -p and SDK sessions saving transcript messages out of order or keeping messages that were taken back
      • Fixed SubagentStop hooks running about twice a minute for each running subagent instead of once when it finishes
      • Fixed the @ file picker ignoring .ignore/.rgignore negation rules that re-include git-ignored files
      • Fixed a subagent's isolated worktree being removed while a background subagent it started was still working in it
      • Fixed background agents in auto mode that wait on their own shells starting a new main conversation turn on every wake
      • Fixed the Bash tool description claiming the working directory always persists between calls
      • Fixed the environment block naming a shell commands don't run in, such as fish when the Bash tool uses zsh
      • Fixed claude mcp add, claude mcp remove and /mcp naming the current folder instead of the project entry in ~/.claude.json that holds a local-scope server when run below a repository root
      • Fixed claude mcp list and claude mcp get showing the error code twice on failed-connection lines (for example ENOENT: ENOENT: …)
      • Fixed Remote Control sessions staying on "Connecting" for about two minutes when a network proxy blocks a startup request
      • Fixed messages that Claude sends to a cloud or Remote Control session appearing as your own message in the Claude mobile apps
      • Fixed Claude not being told the cause when a file attached to a message sent over Remote Control or to a cloud session could not be saved because the disk was full, or that a message's attachments past the first 20 were left out
      • Fixed WebFetch and WebSearch hanging on a stalled response in Cowork cloud sessions; an unfinished request now fails after 300 seconds
      • Fixed a background session that crashed between turns not being restarted while it was attached, pinned, or had a scheduled task or wake-up set
      • Fixed the "background service did not respond" error suggesting the disabled claude daemon restart; it now suggests claude daemon stop --any and says it ends background sessions
      • Fixed claude respawn <id> starting the background service before reporting that no background session matches the id
      • Fixed /effort not warning about a prompt cache miss in plan mode when the plan model differs from the session model
      • Fixed /ide saying the VS Code extension was installed before the install finished or when it failed
      • Fixed the Write tool's file preview skipping rows and miscounting hidden lines when a line is wider than the terminal
      • Fixed ↑ in an agent's chat tab recalling a message that was still waiting to be delivered, so resending it sent a second copy
      • Fixed Cowork cloud sessions losing their connectors and most tools after a restart when a plugin or your settings named an agent; Cowork cloud sessions now ignore that setting
      • Fixed agent teams sessions showing an empty task list when coming back with --resume, --continue, /resume or --session-id, including after /clear or a crash, and /branch writing to the original session's list
      • Fixed pasting text that mentions an image file, such as ! open /tmp/shot.png or /review look at /tmp/shot.png, attaching the image and dropping its path from the prompt
      • Fixed the feedback draft card showing its 1/2/0 and Esc shortcuts while the prompt has text, when those keys act on the prompt instead of the card
      • Fixed a lone backslash in quotes or brackets, like "\" or (\), disappearing from Claude's responses
      • Fixed agent teammates compacting their history when DISABLE_COMPACT is set
      • Fixed the rewind menu offering "Summarize from here" and "Summarize up to here" when DISABLE_COMPACT is set
      • Fixed a finished /code-review, or another skill that runs in a sub-agent, running a second time when a cloud or background session restarts
      • Fixed long hidden thinking being cut off as idle on Google Vertex AI, Microsoft Foundry and Claude Platform on AWS, where the endpoint sends thinking progress updates
      • Fixed /ide saying it had installed the JetBrains plugin when nothing was installed
      • Fixed Claude Pro and Max subscribers being told to ask their admin when their subscription can't be used; the message now points to billing settings
      • Fixed the diff pane opening by itself after an edit in wide fullscreen terminals when it had nothing to show
      • Fixed /mcp showing a remote server as failed after "Clear authentication" when the server works without sign-in
      • Fixed /mcp showing "authenticated" for a remote server that Claude Code sends no credentials to
      • Fixed a --plugin-dir folder of plugins loading as one plugin when an empty .mcp.json was at its top
      • Fixed /usage never showing large prompt-cache misses under "What's contributing to your limits usage?"
      • Fixed status line links staying plain text in background sessions after you open them from a terminal that supports links
      • Fixed the /rewind confirmation saying the conversation "will be forked" when the later messages are removed from the conversation
      • Fixed the /rewind warning that wrongly said manual and Bash edits are never affected by a code restore
      • Fixed plan approval in screen reader mode sending feedback you had dismissed with Escape
      • Fixed Claude Code retrying requests the API marked not to retry, which could hold a turn for minutes or, in unattended retry mode (CLAUDE_CODE_RETRY_WATCHDOG), indefinitely
      • Linux: Fixed sandboxed Bash commands failing with bwrap: Can't create file when a --plugin-dir folder was also an added directory and permissions.blockReadsOutsideWorkingDirectories was on
      • Self-hosted runner: Fixed a session failing to start when a rate limit (HTTP 429, or a git wrapper that exits 75) blocks an added read-only repository; it now starts without that repository
      • Improved startup time for Pro and Max accounts by skipping two network requests on launches within an hour of the last check
      • Improved /teleport and claude --teleport to warn when a compacted cloud session loads from its last compaction, so the messages it summarized aren't in the local copy
      • Improved the messages shown when a background session's process exits: they no longer promise a restart that isn't coming, and they say how to resume the session
      • Improved artifacts with several views: Claude now routes each view on the link's #name and no longer says the address bar stays the same as you switch views
      • Improved shell commands that reach their timeout: the result now shows the output so far and says the command is still running in the background
      • Improved compaction: when the model's reply has no summary in it, Claude Code now usually asks for the summary once more before it replaces the conversation
      • Improved the Artifact tool's choice between a page and a document: explainers and visual or interactive work become artifact pages; documents are for writing people keep editing or pass around
      • Improved startup time for launches whose only arguments are options and their values, such as claude --model opus
      • Improved the "Connection dropped" API error: it now says where to look first (the proxy or gateway in use, else VPN or firewall; Anthropic API only, Bedrock, Vertex and Foundry are unchanged)
      • Improved screen reader mode: deleting a rule in /permissions says "Deleted allow rule …" right away
      • Improved the message shown when a pasted sign-in code is refused: it now says the code may have expired or been used, and to sign in again
      • Improved Slack connector sends: Claude now checks a channel's topic for posting rules before messaging a channel you didn't name
      • Improved screen reader mode: Claude's questions are listed as "Questions: Color (answered), Pages", without arrows or symbols
      • Changed ultrathink in the interactive terminal to run its turn at xhigh effort on Opus 5.5, Sonnet 5.5, Haiku 5.5 and Fable 5.1 through Anthropic's API; typed while Claude is working, it raises the rest of that turn
      • Changed the ultrathink rainbow to appear only where the keyword can raise effort, and not when the word is quoted or part of a file path
      • Changed Ctrl+D in agent view to match the prompt: on an empty input, pressing it twice exits
      • Changed --output-format json and stream-json output to write DEL, C1 control and Unicode format characters inside strings as \uXXXX escapes; parsed values are unchanged
      • Changed model names and IDs to drop the [1m] suffix and its label on models where the suffix has no effect; the suffix is still accepted
      • Changed startup warnings about permission rules in settings files to show once per user until the rule changes
      • Changed /code-review to tell Claude to put the effort level first and use max only when asked
      • Changed DISABLE_COMPACT in settings files and in a mod's $.env.set so they can only turn compaction off, not back on
      • Changed Claude Code on Bedrock, Mantle, Vertex, and Foundry to load model settings from a signed file on downloads.claude.ai; set CLAUDE_CODE_MODEL_CATALOG=off to turn this off
      • Changed sessions that set CLAUDE_CODE_SYNC_SKILLS with feature-flag fetching off to reuse a claude.ai skills list up to 10 minutes old that another session on the machine fetched
      • Changed clicks on scrollbar arrows and bars in fullscreen lists to act when the mouse button is released, so moving off the scrollbar before letting go cancels the click
      • Changed claude purge to say it deletes data only on this computer, not anything stored by Anthropic
      • [VSCode] Added syntax coloring to code blocks in Claude's replies, in light, dark and high contrast dark themes
      • [VSCode] Added a "Running UserPromptSubmit hooks" spinner status and screen reader announcement for slow UserPromptSubmit hooks
      • [VSCode] Fixed custom skills and custom slash commands sent from the VS Code or JetBrains panel leaving out the open file or selected lines that ordinary messages include (#102799)
      • [VSCode] Fixed the extension host freezing while the login shell ran its start-up files to read PATH on macOS and Linux
      • [VSCode] Fixed clicking an image in a tool result, or closing its preview, also opening the result's text in an editor tab
      • [VSCode] Fixed voice dictation continuing to record after a message was sent with the Send button; sending now stops dictation first, as pressing Enter already did
      • [VSCode] Changed the extension to start Claude Code sessions with DISABLE_TELEMETRY set while VS Code's telemetry setting is off, so they send no usage metrics or error reports and fetch no feature flags
      • [VSCode] Changed the session list side bar to load Web sessions when the Web tab is first opened, not at startup
      • [Cloud sessions] Fixed routines in Anthropic-hosted environments staying locked after their owner left the organization and rejoined; the owner can now turn them back on
      • [Cloud sessions] Fixed a failed routine API token delete or regenerate showing nothing if the edit dialog had already closed; it now shows an error toast
      • [Cloud sessions] Fixed cloud environment dialogs, including the admin dialog, accepting duplicate names; they now refuse a name another listed environment already has
      • [Claude Tag] Added a Skills view to Claude Tag analytics showing how often Claude runs each attached skill in Slack channels and which go unused, with Usage links in admin settings
      • [Claude Tag] Improved Claude Tag routines that run in a new session: a run with nothing to report can now end without posting a throwaway message to the channel
      • [Claude Tag] Changed Claude Tag admin settings to show a lock instead of # for private Slack channels that your own Slack account can see
      • [Code Review] Improved Code Review's check run to say no further automatic review will start when the model still can't analyze a change on the automatic retry
      • [Code Review] Improved Code Review reliability: a review whose session fails to start because of a transient server fault is now retried once automatically, and its check run says so
    2. πŸ”— jellyfin/jellyfin 12.4 release

      πŸš€ Jellyfin Server 12.4

      We are pleased to announce the latest stable release of Jellyfin, version 12.4! This minor release brings several bugfixes to improve your Jellyfin experience. As always, please ensure you take a full backup before upgrading!

      Discuss this release further on our forums.

      Changelog (1)

      πŸ“ˆ General Changes

    3. πŸ”— GrammaTech/ddisasm 1.9.6a0 release

      alpha build for usage in reaffirm

    4. πŸ”— @HexRaysSA@infosec.exchange πŸ“’ IDA 9.5 is here: more platforms, more agentic power. mastodon

      πŸ“’ IDA 9.5 is here: more platforms, more agentic power.

      β†’ 3 new decompilers: Android Dalvik, Infineon TriCore and Qualcomm Hexagon
      β†’ IDA MCP and Assist for AI-driven reverse engineering
      β†’ Recursive decompilation across call graphs
      β†’ IDA Home now includes 11 cloud decompilers instead of 2, at the same price
      β†’ And much, much more

      It’s one of our biggest releases yet. Active license holders can download it now from the Download Center.

      https://hex-rays.com/blog/ida-9.5-release

    5. πŸ”— Hex-Rays Blog IDA 9.5 Is Here: More Platforms, More Agentic Power. rss

      IDA 9.5 Release: Three New Decompilers, Malware Analysis add-on, Apple
Kernelcaches and More

      IDA 9.5 is here, and it’s one of our biggest releases yet.

      Three new decompilers for Android Dalvik, Infineon TriCore, and Qualcomm Hexagon significantly expand platform coverage, while Apple kernelcache and DriverKit analysis take a major step forward. Support for AVX/SSE, Armv9, MIPS Release 6, WebAssembly 3.0, PowerPC, and ARC gets stronger too.

    6. πŸ”— pydantic/monty v1.4.0 - 2026-10-26 release

      What's Changed

      New Contributors

      Full Changelog : v1.3.0...1.4.0

    7. πŸ”— r/LocalLLaMA Have 8 GB of VRAM and 32 GB of RAM? You can run Qwen 3.8 Flash Next at up to 900 t/s PP and 30 t/s TG! rss

      Have 8 GB of VRAM and 32 GB of RAM? You can run Qwen 3.8 Flash Next at up to 900 t/s PP and 30 t/s TG! | First, this isn’t clickbait - these are real results. I managed to run Qwen 3.8 Flash Next Q2 and got better results in benchmarks and real-world tests than I did with any Qwen 3.6 35B A3B fine-tune or Qwen 3.8 27B model I tested. It is also faster than my current Qwen 3.6 35B A3B setup. Here are the details. About a week ago, I learned about Strata and what it can do from this subreddit. Its ability to distribute workloads across VRAM, RAM, and SSD storage, run a 125B-parameter model, and deliver incredible prompt-processing and token-generation speeds sounded almost too good to be true - but only if you had 12 GB of VRAM. At first, I thought I probably wouldn’t be able to achieve similar results on my machine, but I decided to try it myself. The results surprised me, so I wanted to share them with you and provide some guidance for getting the model running on your own hardware. First, here are my system specs:

      • GPU: RTX 5060 Laptop, 8 GB VRAM
      • CPU: AMD Ryzen 9 8945HX, up to 5.4 GHz, 16 cores / 32 threads
      • RAM: 32 GB (16 + 16 GB) DDR5-5200
      • SSD: 1 TB, 5,200 MiB/s read, 4,200 MiB/s write
      • PCIe: Gen 4 x8
      • OS: Linux

      You can find my Strata configurations here: Chat (Pastebin) | Chat (GDrive) | Agentic (Pastebin) | Agentic (GDrive).
      Remember to update the paths to your model and expert files. Use the Chat configuration for a single session with the model, such as a regular chat. Use Agentic when working with multiple sessions and delegation, for example in agent-based systems. I’ll explain the difference in more detail below.

      Key parameters to tune

      • --mmap-experts - places the experts that do not fit in memory on the SSD.
      • --kv-resident 20480 - distributes the KV cache between VRAM and RAM. A lower value leaves more VRAM available. 20480 is the minimum value.
      • --vram-reserve-mib 500 - leaves some VRAM available for other tasks. In my setup, 500 is the lowest workable value, but I recommend using 900.
      • --pcie-frac 0.35 - controls the fraction of per-layer VRAM misses that the GPU reads over PCIe. You can tune this parameter using the calibration command: ./setup.sh --calibrate. I found a value that works best for my setup. You can also calibrate it yourself if you are not satisfied with your prompt-processing speed.
      • STRATA_RESIDENT_HEADROOM_GIB=4 - reserves RAM, in GiB, for other tasks. Set this higher if you are using Windows.

      The biggest performance gains in my setup came from adjusting --vram-reserve- mib and STRATA_RESIDENT_HEADROOM_GIB. I used the Gyro S model because I consider it the best quant for my hardware, and it delivered the strongest results among the models I tested. I had previously tried GSQ-RCO Coder, GSQ-RCO IQ2_XS, and other quants, but they either got stuck in repetitive loops or struggled with languages other than English. Gyro S offers a good balance between quality and speed. I’m not using MTP. It can improve TG, but it also consumes VRAM and reduces PP, which is likely to be a worse trade-off for this setup. You can enable it if you have 10 GB of VRAM or more. I run Vision on the CPU. Image processing takes around 1-2 seconds per image, but this saves a substantial amount of VRAM. Strata runs Vision in a separate process, so it can be moved to swap. This does not significantly affect model performance, while freeing up more RAM. If you use local models for parallel agent calls, there is one important limitation: with a context size of 131K tokens or more, you cannot safely use --parallel because it consumes a large amount of both VRAM and RAM. This can cause a severe drop in speed or an out-of-memory (OOM) error. A safer alternative is --conversation-cache. It keeps a limited number of sessions parked so they can be resumed sequentially. This does not provide true parallelism, but it avoids having to re-read long contexts when switching between sessions. Here are the relevant parameters:

      • --conversation-cache-mib 4096 - the size of the parked-session cache. A larger value reduces the chance that a session’s cache will be evicted and its context will need to be read again.
      • --conversation-cache-slots 2 - the number of parked-session slots. Two slots allow two sessions to be stored at once.
      • --conversation-cache-min-tokens 8000 - do not cache a session if its token count is at or below this threshold. The right value depends on your PP speed and how long you are willing to wait for that many tokens to be processed.
      • --conversation-cache-min-free-mib 1024 - the minimum amount of free RAM to preserve while caching. If caching a new entry would leave around 1,024 MiB of free RAM, the old cache will be cleared to reduce the risk of OOM.

      Be careful when tuning these parameters yourself: incorrect settings can affect system stability or push the model into heavy swapping. Do not exceed the total memory available on your system.

      All tests were run on Linux, which gives me more flexibility with RAM allocation. If you use Windows, try allocating less memory to the model. This will reduce throughput significantly, but it also lowers the risk of running out of memory. On Linux, I created a dedicated 32 GB swap partition for other applications. I also pinned the server process in memory so it could not be swapped out, using a systemd service with this setting:

      [Service] MemorySwapMax=0
      

      This helps ensure that the server’s memory does not get swapped out, preserving consistent read and write performance even with a large context and parked-session cache. With the Chat configuration, I get:

      • 262K context: PP 800-970 t/s and TG 30-40 t/s
      • 131K context: PP 930-1,040 t/s and TG 30-45 t/s

      With the Agentic configuration, I get:

      • 262K context: PP 520-740 t/s and TG 30-40 t/s
      • 131K context: PP 670-890 t/s and TG 30-45 t/s

      In my view, these are excellent results-even compared with Qwen 3.6 35B A3B running in llama.cpp. With Qwen 3.6 35B A3B, using a VRAM-constrained expert layout and MTP/Vision disabled, I get PP 630-680 t/s and TG 27-35 t/s. Do you think Qwen 3.6 35B A3B is still worth using for agentic tasks today? Strata does not affect response quality; it helps distribute the model across available resources and keeps frequently used experts resident. That is only one of its major optimizations, alongside several others. The model’s quantization is what affects output quality. If you have more than 8 GB of VRAM, you could try Gyro M/L or other quants. Use my configurations as starting points and adapt them to your hardware and workload. Your component combination and use case may be different from mine.

      Real-world quality tests

      Now that I’ve covered how to fit the model onto this hardware, let’s look at the quality of its outputs. I’ve included several representative tests. I did not run an extensive benchmark suite or standardized evaluations; instead, I spent the past week testing the model on practical, everyday, and demanding tasks. I’ll leave broader benchmark testing to the community. I’ll compare it with my current high-performing setup, Cyber-Tiel 35B A3B , based on Ornith 1.5 Heretic. Tiel 35B A3B often gave me repetitive, looping responses, so I switched to Cyber-Tiel. The Flint model was released recently, but I won’t include it in this comparison. It falls behind Qwen 3.6 in my view; I may compare the two later and add those tests to this post. Test 1: Pagoda This test was run in Pi Agent with a minimal set of tools: LSP and Playwright MCP. For Qwen Flash Next Gyro S, I set reasoning_effort to high. https://reddit.com/link/1xft2ae/video/vycdc57ifsxh1/player Test 2: Flappy Bird clone The conditions were identical to those in the previous test. https://reddit.com/link/1xft2ae/video/97i98026fsxh1/player Test 3: Pelican For this test, I compared not only two different models but also different reasoning_effort settings for Qwen Flash Next Gyro S. The agent environment was the same: Pi Agent. https://preview.redd.it/ifhdl3y7fsxh1.png?width=2067&format=png&auto=webp&s=e9eb5d9ad5046a2a58d339406ab83f8f4429f1c4 I ran many more tests, but I cannot share them for confidentiality reasons. What I can say is that I’ve replaced all my coding agents with this model. That change has accelerated my development and improved code quality by a factor of five. As you can see from these examples, the results are better than those of any other model I’ve tested that fits within 8 GB of VRAM. Qwen 3.8 Flash Next is impressive, and the Gyro S quant makes it possible to run the model even on hardware like mine for local coding and agentic tasks. My goal with this post is to show people who still use Qwen 3.6 35B A3B or its fine-tunes locally that there is now a model that, in my experience, outperforms them by a wide margin. I hope the examples make that case. I’m always open to a different perspective, so feel free to share criticism in the comments. If you have suggestions or improvements for the configuration, please share them as well-other users may benefit from them too. That’s all from me. Use good tools, and happy coding! --- EDIT 1 : I tested the Gyro M on my device. You can see the results in this comment. EDIT 2: I published the Pagoda Benchmark results for the Gyro M here. submitted by /u/BleynSpecnaz
      [link] [comments]
      ---|---

    8. πŸ”— r/LocalLLaMA Researchers from Stanford and UC Berkeley Introduce TokenGate: Token-Gated Attention Makes Long-Context Prefill Up to 11.3x Faster rss

      Researchers from Stanford and UC Berkeley Introduce TokenGate: Token-Gated Attention Makes Long-Context Prefill Up to 11.3x Faster | i hope it's real submitted by /u/MundanePercentage674
      [link] [comments]
      ---|---

    9. πŸ”— HexRaysSA/plugin-repository commits sync repo: +1 release rss
      sync repo: +1 release
      
      ## New releases
      - [HashDB](https://github.com/oalabs/hashdb-ida): 1.13.0
      
    10. πŸ”— OmniNull/OmniWM Canary 20261026-0443 (719d8ee7) 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: 719d8ee753cf
      • Base tag: canary-20261025-0437-40161156174-1

      Changes since canary-20261025-0437-40161156174-1

      • 719d8ee Merge pull request #987 from dappermint/fix/ci-debug-type-roundtrip
      • 5414308 build: skip the debug type round-trip check in OmniWM
      • fb4e761 Add Kitty as a Quake terminal provider
      • 8ccb492 Point the docs at the Styles & Widgets editor
      • 60b8949 Edit drawers and add widgets in the Styles & Widgets editor
      • 28566c1 Edit the Dynamic Island in the Styles & Widgets editor
      • 952adbd Edit styles and the workspace bar in one Settings editor
    11. πŸ”— backnotprop/plannotator v0.28.31 release

      Follow @plannotator on X for updates

      Missed recent releases? Release | Highlights
      ---|---
      v0.28.30 | An Artifacts view in the Inbox, comments on part of an image, diagrams in code review, Ask AI keeps its conversation in annotate
      v0.28.29 | Plan review opens on OpenCode 2, a DOMPurify security update, closing a review stops the agent everywhere
      v0.28.27 | Jump to open questions, files side by side or full screen, image zoom in the Inbox, empty To field, text size for plan review and annotate
      v0.28.26 | Action items and reply drafts in the Inbox, one decision button for plan review, Enter to save a comment, a custom code font
      v0.28.25 | Re-ask open questions, delivery ticks on the list, a count of new messages on the tab, right-click a thread, click Inbox to refresh
      v0.28.24 | A new look for the Inbox, Send now, tag agents, comment on an agent's message, much smaller reads for agents, links in HTML pages
      v0.28.23 | Inbox replies reach sessions with background subagents, dictated text no longer goes missing, πŸ‘ Looks good reaches the agent, notifications that never fail silently
      v0.28.22 | πŸ‘ Looks good, full view for files, one viewer for a thread's images and files, every session prints its URL, PLANNOTATOR_BROWSER=none opens nothing
      v0.28.21 | Message an agent from the Inbox, video attachments, Open in for attachments, Code / Tests / Generated in code review, writes from other websites refused
      v0.28.20 | Inbox search (⌘K), real folder names for projects, data files open in the code view, word-only replies leave questions open
      v0.28.19 | Ask this session in T3 Code, folder sessions load shared stylesheets and images, the agent note asked once per agent, Copy connect prompt
      v0.28.18 | plannotator inbox connects your agents, agents are told when to use the Inbox, rendered Markdown in code review, Inbox Settings in sections

      What's New in v0.28.31

      An onboarding tour for the Inbox, pinned threads, picture choices in questions, palettes in Inbox Settings, tailnet reviews from the Claude Code plugin tool, and the right gh account for a PR. 39 PRs, four of them from a first-time contributor, @utpalsinghdev.

      Plannotator Inbox

      An onboarding tour

      A first run now opens on a screen explaining that the Inbox works beside the agents you already run, with two choices: take the tour or connect your agents. The tour replays a real thread from building the Inbox (a question with pictures, the reply, the next messages) and writes nothing to your Inbox. Returning users find it in Settings β†’ General β†’ Getting started.

      The Inbox first-run
screen

      The tour opening: the Inbox works beside your
agents

      Pin threads

      Pin a thread from its right-click menu or the pin in its header. Pinned threads sit in the sidebar above Projects with their state, keep their place in the list, and stay pinned when archived.

      Pictures and stakes in questions

      An agent can put a picture on each choice, and a question card shows them as tiles you pick from, with a zoom button. Optional Stakes:, Shows:, Why: and Reversible: lines show under the prompt and the choices. A recommendation that names the start of a choice (Recommended: Unpin it for - Unpin it: …) now marks that choice.

      Skip questions from the open-questions list

      Skip… at the foot of the "N open questions" list lets you tick the questions to skip, or Skip all. Skips wait in your draft until the next Send.

      Palettes in Inbox Settings

      Settings β†’ General β†’ Appearance β†’ Colors picks the palette for the light and the dark half, the same setting plan review's Theme tab uses.

      The palette picker in Inbox
Settings

      Step through files on a phone

      Full screen on a phone has a 4/9 βŒ„ pill for every file in the thread, and a sideways swipe steps to the next or previous file.

      Smaller changes

      • The Inbox says which agents your reply wakes. Claude Code, Pi and OpenCode 2 get it as a new turn on their own; agents through MCP see it when they next check. Agents nothing wakes are told to call wait_for_reply. #2168

      • Every wake ends with a line naming the thread id, read_thread and plannotator inbox --help. #2143

      • The Claude Code mod never steers into or aborts another plugin's turn. A reply waiting on such a turn goes in when the session is idle. #2176

      • The Inbox reminder reaches Team/Enterprise Claude Code sessions and comes back after compaction. #2167, closing #2159

      • No more "hook was skipped" notice at every permission prompt on Team/Enterprise accounts. #2160

      • The first-run screen asks for notifications , so the first question can notify. Your own sent reply shows your words and a short list of your answers. #2148

      • A dot on the sidebar toggle when an update is waiting and the sidebar is closed. #2135

      • Cursor gets the agent note as text to paste into its Rules (plannotator inbox --notes cursor). #2153 by @utpalsinghdev, closing #1991

      • Agents are nudged to attach a screenshot for something visual. #2175

      • An image the Inbox cannot load shows as its alt text , not a broken icon. #2177

      An image the Inbox will not load, shown as its alt
text

      • Images and code in a choice keep their corners ; only the Recommended tag is a pill. #2179

      • Decision mode is experimental and off by default. It clears what agents ask across threads one decision at a time; turn it on in Settings β†’ General β†’ Experimental. #2141, #2154

      Plannotator

      Tailnet reviews from the plugin tool

      The plannotator tool in Claude Code takes a tailscale option, so a review the agent opens can be read on your phone over Tailscale. Ask this session keeps working there for the Tailscale login that owns the machine; anyone else on the tailnet gets the separate Ask AI.

      The gh account that can see the PR

      With two accounts signed in to gh, plannotator review <PR URL> now uses the one that can read the PR, for that review only. Your gh setting is unchanged, and an invalid GH_TOKEN is named.

      A fixed port for live app annotation

      PLANNOTATOR_LIVE_PORT sets the live app proxy's port (or a range), so live annotation works over an SSH port forward.

      Plannotator Graphite

      A new palette with a lighter, near-neutral dark half that stays readable in a bright room. Pick it in Settings β†’ Theme.

      Smaller changes

      • A broken config.json is no longer overwritten. A settings save refuses, says how to fix the file, and leaves it as it was. #2178
      • Session secrets no longer reach child processes. The Ask this session token and the decision-file paths stay out of git, gh and the agent CLIs a review starts. #2169
      • A new release shows within minutes. Update checks read GitHub's latest-release link, and the review-window toast shows at most once a day. #2133, #2135
      • Cursor review jobs never start another program namedagent. #2173
      • Linux folder watches no longer exhaust inotify on large repositories. #2155 by @utpalsinghdev, #2163, closing #1439
      • Replacing an Ask AI question in Pi no longer stops the running turn. #2126 by @utpalsinghdev, closing #2038
      • Back in a multi-file annotate session keeps your place. #2129, closing #2128
      • The image viewer says how to zoom when the wheel starts scrolling. #2131, closing #2127
      • The diff shows again after switching through an empty diff in code review. #2180
      • Guided Review viewer uploads retry and publish the entry last, so a failed deploy cannot leave exported guides unstyled. #2150
      • Dependency updates , including Mermaid 12.2. #2152

      Install / Update

      macOS / Linux:

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

      Windows:

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

      Claude Code Plugin: The plugin and the plannotator binary update separately, so run the install script above as well. In a terminal:

      claude plugin marketplace update plannotator
      claude plugin update plannotator@plannotator
      

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

      Pi:

      pi update --extensions
      

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

      What's Changed

      • fix: preserve Pi turn when replacing an Ask AI question by @utpalsinghdev in #2126
      • fix: Back in a multi-file annotate session keeps the reader's place by @backnotprop in #2129
      • Image viewer: say how to zoom when the wheel starts scrolling by @backnotprop in #2131
      • Inbox: skip a question from the open-questions list by @backnotprop in #2132
      • Update notices: check GitHub's latest-release link often by @backnotprop in #2133
      • Update notices: toast once a day, dot on the sidebar toggle by @backnotprop in #2135
      • Inbox: skip from the questions list with a select mode by @backnotprop in #2136
      • Add the Plannotator Graphite dark palette by @backnotprop in #2137
      • Inbox: choose light and dark palettes in Settings β†’ Appearance by @backnotprop in #2138
      • Question cards: match a recommendation to the choice it begins by @backnotprop in #2139
      • Inbox: pin threads to the sidebar by @backnotprop in #2140
      • Inbox: decision mode (experimental, off by default) by @backnotprop in #2141
      • Usage counts for experimental features, phase 1 (nothing is recorded or sent yet) by @backnotprop in #2142
      • Inbox wake: a closing line with the thread id, read_thread and --help by @backnotprop in #2143
      • Question blocks: optional Stakes, Shows, Why, Reversible and picture choices by @backnotprop in #2144
      • fix: support fixed ports for live app proxies by @utpalsinghdev in #2145
      • Inbox first run: notifications ask on the first-run screen; your sent reply in your own words by @backnotprop in #2148
      • guides.show: retry viewer uploads, publish entries last, verify every file by @backnotprop in #2150
      • Live proxy port: tests for PLANNOTATOR_LIVE_PORT, one-line errors for EACCES by @backnotprop in #2151
      • chore(deps): bun minor and patch group by @backnotprop in #2152
      • fix: offer manual Inbox notes for Cursor by @utpalsinghdev in #2153
      • Decision mode: the agent contract lines on the Queue card by @backnotprop in #2154
      • fix: watch directories instead of files on Linux by @utpalsinghdev in #2155
      • Inbox: the onboarding tour by @backnotprop in #2156
      • fix(mod): only take ExitPlanMode PermissionRequest events by @backnotprop in #2160
      • feat: use the gh account that can see the PR by @backnotprop in #2161
      • fix: Linux folder watches keep working past the cap and unreadable folders by @backnotprop in #2163
      • Inbox: step files on a phone with the toolbar pill and a swipe by @backnotprop in #2164
      • Inbox reminder reaches Team/Enterprise sessions and survives compaction by @backnotprop in #2167
      • Inbox: say plainly which agents a reply wakes by @backnotprop in #2168
      • fix: scrubbed env vars no longer reach child processes by @backnotprop in #2169
      • Tailnet reviews from the plugin tool, with Ask this session for the machine's owner by @backnotprop in #2170
      • Code review: Cursor agent jobs never start another program named agent by @backnotprop in #2173
      • Inbox: nudge agents to attach a screenshot for something visual by @backnotprop in #2175
      • Claude Code mod: never steer into or abort another plugin's turn by @backnotprop in #2176
      • Inbox: draw an image the window cannot load as its alt text by @backnotprop in #2177
      • Inbox tour: fix the QA findings; never write over an unreadable config.json or pins.json by @backnotprop in #2178
      • Inbox: keep the pill on the Recommended tag, not on images or code in a choice by @backnotprop in #2179
      • Code review: show the diff after a switch through an empty diff; name a rejected GH_TOKEN by @backnotprop in #2180

      New Contributors

      Community

      Full Changelog : v0.28.30...v0.28.31

    12. πŸ”— seanmonstar Micro: Make smaller structs rss

      I’ve seen the hype about view types being added to Rust. I worry it exceeds the strangeness budget. And there’s a solution already available. Make your structs smaller.

      I’ve always insisted on optimizing for reading. And as many use LLMs make writing faster, there’s even less reason to pick shorter but more complex.

      Structs are free. They don’t result in auto boxing. So, divide up your structs by how the fields relate to each other. Then it’s much easier to borrow one field than to wish for some complex syntax to borrow many.

      I have even created temporary projection structs to borrow disjoint fields together, though it’s a pretty rare thing to need.

      I wrote a clippy lint to catch structs that are too big, but seems others think it’s too strict. I still think it’s a good idea.


      Reply via: Email Β· Bluesky Β· Mastodon

    13. πŸ”— Rust Blog How to fund Rust contributors rss

      TLDR:

      There is always so much to do in the Rust Project! New features to implement, bugs to fix, performance optimizations to make, issues to triage… It takes a lot of work to keep our high bar of quality while also shipping new features and improvements. And the workload keeps increasing with the continuous growth of Rust adoption.

      As is unfortunately common in open source projects, a large fraction of that work is currently done by volunteers. That causes various issues, such as people burning out or complex features taking many years to ship.

      Unsurprisingly, one of the best ways to help improve that is to get more people who work on Rust funded! This year, several funding initiatives started ramping up, and we already experience many positive effects. They helped us improve the maintenance status of critical Rust projects and make significant progress on several long-awaited features, such as allocators, the never type, the next trait solver or the Polonius borrow checker. However, only a fraction of people working on Rust are currently funded for their work.

      We know that there are Rust users, both individuals and companies, who would like to help improve Rust by funding it, but it might not always be obvious how exactly to do that. This post thus provides suggestions on how you can support the development of Rust in three ways.

      If you're unsure which option fits, or would like to discuss funding on behalf of your company, please contact the Funding team.

      Fund general maintenance

      Maintenance is a continuous process required to keep Rust (or any software project for that matter) working. It consists of two main activities. The first is general housekeeping, such as ensuring that Continuous Integration works, dependencies are kept up-to-date and issues, bugs and security incidents are promptly triaged and resolved. The second is performing refactorings and code reviews, which ensures that the codebase will be able to evolve and continuously ship new features, without accruing extensive technical debt.

      Having quality maintenance is crucial for the long-term health of Rust, yet it is typically very difficult to find funding for it; funders often want to sponsor specific new features, rather than just "keeping the lights on". However, without sufficient maintenance, it becomes much more difficult, and much slower, to ship new features. Improving the maintenance of Rust thus also helps us ship features and improvements faster, though the effects are sometimes only observable over longer periods of time.

      Funding maintenance is a great choice if you want to let us decide how best to improve Rust. The Rust Funding team continuously looks for Rust teams and projects that require help with their maintenance efforts, and allocates available funds to Rust maintainers who could help improve the situation.

      To fund Rust maintainers, consider donating to theRust Foundation Maintainers Fund or sponsoring the RustNL Maintainers Team.

      Fund specific features and improvements

      There are always many Rust improvements and new features that are in progress. We track some of those initiatives through Rust Project Goals. Each Goal describes a specific improvement to Rust: what it is, who is going to develop and drive it forward and which Rust teams are willing to help reviewing and maintaining it.

      Some of those Goals are looking for funding. Either to help their owner dedicate time and focus to push the given feature forward, or to fund maintainers who will perform refactorings necessary to unblock that feature and review its implementation. Often funding is required for both. When a Goal is properly funded, the probability that it will achieve its milestones is much higher, which then translates in the given improvement being shipped sooner to Rust users.

      Funding Project Goals is a great choice if you want to help push forward specific Rust features or Rust toolchain improvements that will benefit you or your company.

      To fund contributors working on Project Goals, consider taking a look atGoals that need funding and reaching out to their funding contact. If in doubt how to proceed, reach out to the Rust Funding team.

      Fund individual contributors

      There are hundreds of people in the Rust Project who continuously work on improving Rust. Some of them have personal fundraising profiles (e.g. on GitHub Sponsors), which allows you to support them directly.

      There might be various reasons for supporting a specific person. Maybe they are maintaining a crate that you love to use, maybe you like reading their blog posts, or maybe you are simply a fan of the work that they do. Whatever the reason, we are sure that they would appreciate your support!

      Funding individual contributors is a great choice if you want to directly support Rust contributors whose work you appreciate.

      To fund individual Rust contributors, check out their GitHub profile or personal website to see what options there are for supporting them. You can also examine our list of Rust Project members who can be supported through GitHub Sponsors[1].

      Conclusion

      We hope that this post is useful to anyone who would potentially like to invest funds into making Rust better. You can also find a shortened version of the "how to fund Rust guide" at the Funding page of the Rust website, or check out a RustConf 2026 talk by Niko Matsakis about how Project Goals and their funding works.

      If you are a company looking to fund the development of Rust, consider joining the Rust Commercial Network. Joining the network is free, and Rust Foundation membership is not required. It can help you find opportunities for funding improvements in specific areas related to Rust usage (e.g. user interfaces, language interop, supply chain security, etc.) and collaborate on funding Rust development with other companies.

      There are of course other ways of helping Rust other than donating funds. For example, you can check out Project Goals that are looking for contributors or more generally check our contributor onboarding guide. Companies can also help by giving employees paid time to contribute upstream, or by hiring Rust contributors to do that work. One possible model is the Engineer in Residence role, that was recently established in the Rust Foundation.

      1. Note that this list is not exhaustive; there are some Project members who accept donations through GitHub Sponsors (or another fundraising platform), but did not opt into being listed on this page. ↩
  2. October 25, 2026
    1. πŸ”— IDA Plugin Updates IDA Plugin Updates on 2026-10-25 rss

      IDA Plugin Updates on 2026-10-25

      New Releases:

      Activity:

    2. πŸ”— r/LocalLLaMA CrowdGPT - A collaboratively trained LLM. rss

      CrowdGPT - A collaboratively trained LLM. | Hello, I'm developing CrowdGPT , a project aiming to create an LLM without datacenters and without the usual millions of dollars spent by AI companies. The project aims to train a 1 billion parameter model collaboratively and openly, with a protocol where everyone gets a say in the direction the project takes. Anyone can use their PC to train the AI independently, then add their contributions to the global model. Unlike most American and Chinese AI companies, the project is not only open-source, but also makes 100% of its training data public (along with the weights). Anyone can submit their own clean data to train the model, and even help steer the project in new directions. This creates the paradigm of an AI we all have a stake in. The project is open to as many people as possible, which is why I'd like to ask: what's stopping you from contributing to the project? I want to hear your answers so I can improve it. Are people simply willing to dedicate some of their GPU time to training a cool new open-source model? Or do they want something in return (like free inference credits on the crowdgpt model for example)? Although the current model is somewhat small (1 billion parameters), I plan to make it bigger / better in the future, and its current size is only meant as a proof of concept. Any advice / feedback on the project is welcome. Here's the project website: https://www.crowdgpt.net/ Or the GitHub if anyone wants to check out the code πŸ˜‚ https://github.com/Vxtzq/CrowdGPT Thanks in advance. PS: I hope this post follows the subreddit's rules! My main goal is to gather criticism and understand how to make the project more accessible, not to advertise it πŸ˜… EDIT: The data submission pipeline for the project (i'm mentioning in some replies) is ready!!
      Come check it at https://www.crowdgpt.net/#submit submitted by /u/Vxtzq1
      [link] [comments]
      ---|---

    3. πŸ”— hacker news ida pro references New comment by danbruc in "We should be more ambitious with the software we build" rss

      You think I could not identify all the functions in some software if I poked at it with IDA pro for 15 years? Probably depends on what exactly we are talking about, is it calc.exe or an entire office suite? But I will give you that I would probably never complete the task, I would not be willing to spend 15 years doing this. Realistically I would probably be interested in some specific functionality and identify the functions involved and ignore the vast majority.

    4. πŸ”— 3Blue1Brown (YouTube) Sphere Intersection Puzzle Corrected rss

      Part of a series of monthly puzzles Early view of some other solutions: https://members.3blue1brown.com/posts/solution-to-10-158885046 https://members.3blue1brown.com/posts/solution-to-sum-156593740

    5. πŸ”— r/LocalLLaMA Backup your quants! rss

      Backup your quants! | source: https://huggingface.co/mradermacher/model_requests I'm sure the situation is the same for other quant producers. If you have anything you want to keep, it's best to make a backup now. If you have the means to, please create torrents of them and share them here:

      submitted by /u/Kahvana
      [link] [comments]
      ---|---

    6. πŸ”— r/LocalLLaMA Nanbeige/Nanbeige4.3-33B Β· Hugging Face rss

      Nanbeige/Nanbeige4.3-33B Β· Hugging Face | Stronger than Qwen3.8-27B across a range of benchmarks.

      but also lays the necessary foundation to power our upcoming small model distillation pipeline (e.g., for Nanbeige4.3-3B).

      It'll distilled into their 3B small models, maybe other sizes too. submitted by /u/Mysterious_Finish543
      [link] [comments]
      ---|---

    7. πŸ”— Register Spill Joy & Curiosity #103 rss

      … and we're back! I spent the last two weeks travelling. First a week in New York City, then a week in San Francisco. I did many things in those two weeks, but not a lot of reading or writing, which is why you didn't hear from me.

      But now I'm back! So, without further ado this week (my daughter is waiting for me to build a Lego truck), here's a bag of links.

      • We recorded a new episode of Raising An Agent, in person, in San Francisco. I think it turned out great. In fact, I said somewhere else that this might be the most important episode we've recorded this year. It's about nothing less than the company of the future. Highly recommend watching this if you're in any way curious about how Amp -- the team, the company -- operates.

      • While in New York, we visited a large customer of ours, an investment bank. I gave a talk there about how I use Amp and what I think have been the biggest 10x multipliers when working with agents. In San Francisco I then recorded the talk and it's been received very well, so here it is: How I Use Amp.

      • Adam Mastroianni is truly one of the best in the game right now. Everything he puts out is incredibly good. This newest one, Claude, don't touch my lump, is no exception. It might be the most convincing argument for why AI won't lead to unemployment I've read so far. The only counter-argument I can see is that, well, there will be jobs in the long term, but what about in the next five years?

      • "I'm 38. If You're in Your 20's or 30's, Read This." I'm also 38 and when I first saw this title I went "ugh", because hey, feels like I'm only just starting. But it's surprisingly good, even though it's a bit Buzzfeed-y. Maybe because it quotes the life-changing Jason Pargin post?

      • PhotoCraft: An open-source, photo editor written by scratch in pure Rust. I saved this link two weeks ago to share with you here. And now it's old news, isn't? Photoshop rebuilt in Rust? Big whoop. There's AAA games being decompiled and remixed with other AAA games while I'm typing this. (Still: what a time!)

      • This is still lovely: "made a rug for your desktop so you can sweep your mess under it"

      • "People are surprised that AI is finding weird unelegant maths results like this. I think there is a plausible explanation. Maths (and adjacent disciplines like physics and comp sci) had elegant results so far because humans are biased towards elegant solutions. I think this bias is due to how human minds work. We have a pretty small context window, and we are only able to find solutions that are relatively elegant. This gave us the impression that maths and the universe are elegant. Maybe they are not, and we are now finding out because we have intelligences that can work with much more complex solutions." The same is coming for programming and codebases. Some codebases in the future will look ugly, hacky, disgusting to programmers who grew up writing code by hand and yet they will run perfectly well in production, just as well as any handcrafted piece of code ever did, and agents will have zero problems modifying them.

      • Namespace had me on their new podcast and I finally got to talk about the Big Amp Rewrite we went through this summer. Because where else would you talk about it if not on a podcast called Once In The Trenches?

      • David Foster Wallace's Consider The Lobster. I don't know what made me re-read it, but it's so, so, so good. If you never read it, I highly recommend you do.

      • Toto Wolff talking to Patrick Collison on the Cheeky Pint podcast. This was really good. Not only because looking at F1 from a business and management and investment perspective is interesting, but also because Wolff, born in Austria, has a unique background: racing driver, then salesman, then investor in Austria and Germany at the height of the dot-com boom, then car racing investor and so on. Loved the story about sms.at.

      • John Gruber says you can now move (back) to X as a social media platform: X Once Again Marks the Spot. As someone who has never left but at times wondered whether he should, I could write pages here that would boil down to this: I have not used another social network where the highs are that high. And then there'd be a bunch of other pages about the lows, of course. If you're coming (back) to X, here's my advice: follow me (obviously), mute freely, mute keywords, train the algoritm by saying "I don't like this" on posts you don't like (you can configure the iOS app to do this with a single swipe), set a time limit per day and give the password to your wife.

      • (Even Marco seems to have soft-launched his comeback to X. I know that's a pretty cynical way to put it but I don't mean it in a negative way. It's just that… well, there was all this screaming and shouting about who's where and why and how could you that I can't help but raise an eyebrow now when someone says, hey, well, maybe I don't have to think in these absolute terms?)

      • The Heat (1995) frame archive. So good. In case you've never seen Heat: do it! As fast as possible. It's really good. Here's one of my favorite frames.

      • How to be more ambitious: A tutorial for humans with models. This is an impressive post. Yes, the message is good: be more ambitious. But look at the prompts and think about how much first-principles thinking you have to put in to even come up with them. Instead of saying "give me a slide show" the idea is that you wonder: why am I even making a slide show in the first place? What's the purpose of that? And then, why am I doing that? And then give that as a goal to Claude. How many people you know could do that?

      • Amazon's writing culture apparently didn't survive AI. That's sad to hear, but "AI;DR" is an incredible invention.

      • Self-improving software is inevitable. I think some version of that will happen soon. I can see glimpses of it when I'm working in Amp on Amp. But the number of human signals you need in a system that's growing is probably higher than suspected. If you're system is only in maintenance mode, then, yes, we might be able to fully automate that.

      • The lamps in my house. On How-much-do-you-care-about-lamps? scale from Not-at-all to Fatih's post here, I'm somewhere in the middle. This was lovely.

      • From Einzelunternehmen to GmbH: Every step, Every letter. Few things in life have radicalized me politically as much as founding a UG (haftungsbeschrankt) in Germany. Look at all the physical letters here. The forms. The timeframe. The notary: "The appointment took about 1.5 hours. By law, the notary reads every document aloud, word by word." I'm sharing this here because I think it's valuable for founders and other people navigating these legal structures. Not because it brings joy, of course.

      • Non-Determinism Doesn't Matter. I'd say we're only just starting to get into real non-determinism.

      • There's been, of course, a lot of news about security incidents and exploits and CVEs and… yes, it's all quite horrible and anxiety-inducing and I'm not going to repeat all the news here, except this one, because this one has all the attributes the others have too, with a "mind-blowing" on top: "In one experiment, we asked agents in separate microVMs, created and managed by OpenAI's sandboxing software on shared host machines, to exchange synthetic secrets without the use of network connections or shared writable files--something that our systems are meant to prevent. The agents found a way to communicate using the processor's cache: a small, fast memory that holds copies of data that applications have recently accessed. Reading data from the cache is faster than retrieving it from main memory, and the agents used this timing difference to communicate. One agent encoded information by evicting selected data from the cache. Another timed how long it took to reload that data, using the difference between fast and slow reads to recover the message. Once the agents agreed on a protocol for encoding and decoding these signals, they could exchange the synthetic secrets without changing a shared file or opening a network connection. This cache-timing technique had also been used to extract information in the Spectre and Meltdown attacks⁠)."

      • What Shall I Teach My Son? Good question. But, funnily enough, I tell my kids what I think someone must've told me when I was a kid: you need to learn how to learn; the most valuable skill to have is the ability to learn new things. I'm not sure who told me that, or when I first heard it, but it's been stuck in my head for a long time and I'd say it's served me well.

      • The Many Failures of Larry David. Great little profile. Lots of things I didn't know. But then at the end, I go: wait, there should be more about Curb here, no? And that's when I realized there's a new biography coming out that I should probably get.

      • The end of startups: "Within the next 6 months, most AI startups will not be able to buy compute. The world's compute is sold out. To get capacity, you'll need to sign up for a new cluster. However, it's becoming increasingly difficult to get capacity online from folks who are not investment grade." Not sure whether I agree with everything here (I do think the idea of compute and tokens as a commodity that you can sell on commodity markets is very interesting), but something fundamental has definitely changed in software (not news to you, I'm sure) with the arrival of AI. And if you were to say that in the last three decades the advantage of startups was that talent -- as opposed to: capital, infrastructure -- was the biggest lever in software and that you were able to build software essentially for free (if you had the talent), then, well, you have to admit that things have changed.

      • Loved this one: Reflections on -1 to 0 and Exploring Ideas. Some real thoughts on finding PMF and what building a business is truly about.

      • Norm: The Tale of Norm Macdonald is a now on Netflix and I loved it. I loved that it started with the YouTube clips, because that's how most people in the last ten years discovered Norm and, I think, it's also where he shines. Type in "norm macdonald conan" and it's all gold.

      • Block released Dessa, "the most authentic full-duplex speech model ever built. Talking with it feels like talking with a person…full of emotion, nuance, pauses, and a natural cadence." It's pretty impressive… but … A lot of people are saying "this will ruin society" and "no one is safe no anymore [because we can fake any voice now and call and scam everybody]", but when I listen to those clips I can't help but imagine myself overhearing a conversation like that happening at the next table and thinking "what is wrong with them?" We might be at the far end of the uncanney valley, but I wouldn't say we're out of it yet.

      • Dan Luu: "We should be more ambitious with the software we build". 100%. Absolutely. Time to reach for the stars.

      If you read this far, I know we'd get along, so subscribe here:

    8. πŸ”— r/LocalLLaMA A 4B coding model that can generate 3D scenes rss

      A 4B coding model that can generate 3D scenes | I’m sharing an early version of a 4B model I’m training for general coding and 3D scene generation. Small models have been pretty rough at 3D in my tests. I’ve finally made enough progress to get results like the ones in this video, so I wanted to share a preview with the community. It’s an independent fine-tune of Qwen3.5-4B, and both Q4_K_M and Q8_0 GGUFs are available here: Download the model on Hugging Face Training is still running. Over the next few days, I’ll update the model once it finishes and share the training dataset so others can experiment with it too. Give it a try. I’d love to see what you can get out of it. submitted by /u/ConfidentDinner6648
      [link] [comments]
      ---|---

    9. πŸ”— OmniNull/OmniWM Canary 20261025-0437 (05bbb30f) 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: 05bbb30f5b7d
      • Base tag: canary-20261024-0439-40061526227-1

      Changes since canary-20261024-0439-40061526227-1

      • 05bbb30 Set both active-profile overrides in the Hidden Bar tile test
      • 6751411 Keep the JSON cap test's work to the byte limits
      • 84b9f9b Retire a style through a symlinked shell folder
      • 64ce2e9 Fall back to the bundled widget when a widget fails
      • fade4bb Merge main into 0.8.0-release
      • c4fa2cf Merge pull request #980 from hezhizhen/codex/fix-bundled-widget-fallback
      • 97ab859 Merge pull request #979 from hezhizhen/codex/fix-shell-symlink-paths
      • b8bacef Share compiled Luau bytecode across widget VMs
      • 3d0249d fix(shell): load bundled fallback widgets with their libraries
      • 8ddb735 Merge main into 0.8.0-release
      • 0c9b688 fix(shell): preserve module paths through symlinked config directories
      • eb71ee2 Merge pull request #978 from hezhizhen/codex/fix-hidden-bar-native-panels
      • 2c7372d Bundle Material Symbols as TTF to stop per-thread WOFF2 decoding
      • d294032 fix(hidden-bar): pause rehide for native popovers
      • cfdba09 Load Celestial's Dashboard and Status models when each widget loads
      • bc62530 Merge main into 0.8.0-release
      • 15d6bb1 Merge pull request #976 from dappermint/fix/hidden-bar-full-width
      • b944532 Make Wayline and Nocturne full width by default
      • c5a826f fix(hidden-bar): stop a resolve that lost its reveal or its access
      • 6e8b15e Make System the default OmniShell style
      • 2f3c066 fix(hidden-bar): retry a failed menu read with menu access
      • 7b6ef81 Share Control Center across bundled OmniShell styles
      • de9a289 Share status widgets across bundled OmniShell styles
      • 3be5cba Share Wi-Fi and Bluetooth across bundled OmniShell styles
      • 2505b96 Share the battery across bundled OmniShell styles
      • ff2d220 Share the active window across bundled OmniShell styles
      • b6ff13a test(shell): await the frame check instead of an inverted timeout
      • 5135ea6 fix(hidden-bar): never click an item our bar covers
      • 5c39000 fix(hidden-bar): reveal the menu bar only for items that need it
      • 09c005f Merge remote-tracking branch 'upstream/main' into fix/hidden-bar-full-width
      • bf6f189 Merge main into 0.8.0-release
      • 2c236e5 test(hidden-bar): find the test panel in the on-screen window list
      • 99b9239 fix(shell): ignore screen order when comparing display frames
      • 2a04f5b Share weather across bundled OmniShell styles
      • 5d70f6b fix(shell): keep popouts open when only the visible frame changes
      • 887ed39 fix(hidden-bar): leave the menu bar hidden under a full width bar
      • 34b37eb fix(hidden-bar): press items our own bar covers
      • 7eff682 Merge main into 0.8.0-release
      • 29f8251 Merge main into 0.8.0-release
      • a7100b5 Share the clock and calendar across bundled OmniShell styles
      • c5cc2dd Merge main into 0.8.0-release
      • 2ba3bcf Merge main into 0.8.0-release
      • 21cb8ef Merge the published 0.8.0-release branch
      • 9ed4171 Share media across bundled OmniShell styles
      • 9e7ca7e Merge pull request #965 from dappermint/test/omniwm-icon-color-anchor
      • b7ecaf0 test(shell): reject an icon colour with a trailing non hex digit
      • 6a4ef5e Merge pull request #948 from hezhizhen/codex/nocturne-option-regressions
      • e2ccf10 Merge the published 0.8.0-release branch
      • 2b261be Merge main into 0.8.0-release
      • 6a19232 Share volume and audio across bundled OmniShell styles
      • b557850 test(shell): extract inspector snapshot assertions
      • a35cc31 Merge pull request #960 from dappermint/feat/shell-shared-widget-options
      • e7dbdd5 test(shell): verify inspector defaults against explicit values
      • 1ea93af feat(shell): let the omniwm button take a custom icon colour
      • 73e0766 Merge main into 0.8.0-release
      • 92c7efa test(shell): adapt Nocturne tests to release presets
      • 1ed655a test(shell): cover Nocturne option rendering and persistence
      • c419e52 Merge main into 0.8.0-release
      • e4a4bf2 Share System Stats across bundled OmniShell styles
      • 809fa18 Share the Hidden Bar strip and menu across bundled OmniShell styles
      • 26c916f Merge main into 0.8.0-release
      • 36b5d7f Share one OmniWM menu button across bundled OmniShell styles
      • 804d27f Let every style choose how many scratchpad icons to show
      • 574d185 Share one scratchpads widget across bundled OmniShell styles
      • ccafc7a Share one workspaces widget across bundled OmniShell styles
      • 839fd9c Make notification dismissal feel immediate
      • d3e0a79 Merge origin/main with PR #945 option declarations
      • 2c78d38 Polish bundled OmniShell styles and notifications
    10. πŸ”— r/LocalLLaMA OpenAI and Anthropic blocked the reverse engineering of smart TVs spying on us rss

      REA (Reserve Engineer Anything) was blocked by Claude one day later...

      https://x.com/AbhinavXJ/status/2113590263373508704

      Time for the pebbles to own the weights

      submitted by /u/kroggens
      [link] [comments]

    11. πŸ”— Filip Filmar Fuchsia Internals, Vol. III: The Zircon Kernel rss

      Volume III of the Fuchsia Internals series examines Zircon, the microkernel at the foundation of Fuchsia. At 43 pages, this report is the longest in the series. Subsequent subsystems like graphics, drivers, storage, and networking run in user space and rely on the primitives defined in this volume. For readers following Cocoapuffs on a RISC-V soft core, this volume documents the kernel behaviors encountered during that port. A link to the full document appears below.

  3. October 24, 2026
    1. πŸ”— IDA Plugin Updates IDA Plugin Updates on 2026-10-24 rss

      IDA Plugin Updates on 2026-10-24

      Activity:

      • chernobog
        • 579c1c08: feat: preserve stores and hoisted values when patching Hikari dispatc…
        • 02d6937e: test: cover direct rendering of resolved calls
        • eb82a566: feat: print calls to known targets as direct calls
        • 0fd29f89: test: cover discarded constant ARM64e helpers and document jump table…
        • 81474ce9: feat: elide discarded ARM64e helper statements with constant arguments
        • b1bd5b9d: feat: lower two-way jump tables using remembered exhaustive target pr…
        • 02e2b813: feat: add verbose logging for unlowered jump tables in indirect branc…
      • oh-my-dump
        • bd5ce7ad: ci: move clang-tidy into a separate job
        • 5669b828: ci: add clang-format and clang-tidy checks
        • f999a917: docs: update build documentation
        • 4f0943d1: chore: update clang format/tidy configuration
    2. πŸ”— r/LocalLLaMA Kimi K3.1 removes cyberattack training data from open weight release rss

      This is due to China's new export restrictions primarily but also the growing caution around cybersecurity exploits popping up.

      submitted by /u/zxyzyxz
      [link] [comments]

    3. πŸ”— r/LocalLLaMA Meta trained small AI models to read raw bytes instead of tokens. They start out worse, but the paper predicts they end up better rss

      Meta trained small AI models to read raw bytes instead of tokens. They start out worse, but the paper predicts they end up better | https://arxiv.org/pdf/2609.12303 this paper suggests a model that skips models reading tokens that and has the model read raw bytes, basically one letter at a time. what they did:

      • trained small models (~1B params), some on tokens and some on bytes
      • trained them partly by copying a bigger model (llama 3 8b), aka distillation
      • the tricky part is that the teacher thinks in tokens and the student reads bytes, so they had to work out a clean way to translate between the two

      what they found:

      • with a little training the token models win, not even close
      • with more training the token models kind of flatline while the byte ones keep improving
      • if you extend the trend lines, the byte model ends up beating llama 3.2 1b and gemma 3 1b by a few points
      • the byte models also needed about 6x less text to hit the same level

      the catch (and there’s a few):

      • the β€œbeats llama and gemma” part is a prediction. they extended the curves past what they actually trained. in their real runs the token model was still ahead
      • reading letter by letter is slower. a token is ~4-5 letters, so it’s roughly 5x more steps for the same text. less data but more compute
      • tokens aren’t really dead, since the teacher model still uses them
      • only tested on small models, no idea yet if it holds at scale

      still pretty cool imo. for small models on phones/laptops, squeezing more quality out of the same size matters a lot. and getting rid of the giant word list might fix the dumb stuff like miscounting letters in a word anyone know if there’s work on making byte models run as fast as token ones? submitted by /u/DotaMate
      [link] [comments]
      ---|---

    4. πŸ”— r/LocalLLaMA The RTX 5090 Isn't Gone, It's In Chinese Labs, Where Technicians Rip Off Its Die And 32GB VRAM For AI Servers rss

      The RTX 5090 Isn't Gone, It's In Chinese Labs, Where Technicians Rip Off Its Die And 32GB VRAM For AI Servers | submitted by /u/chemist_slime
      [link] [comments]
      ---|---

    5. πŸ”— OmniNull/OmniWM Canary 20261024-0439 (2f49ed7c) 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: 2f49ed7c3a03
      • Base tag: canary-20261023-0937-39929994137-1

      Changes since canary-20261023-0937-39929994137-1

      • 2f49ed7 Merge pull request #975 from dappermint/feat/hidden-bar-inline-items
      • f35618e Merge pull request #971 from hezhizhen/codex/input-source-regression-tests
      • 665c864 feat(hidden-bar): show hidden items inline in the bar
      • 36bcd78 Merge pull request #974 from OmniNull/dependabot/npm_and_yarn/website/npm_and_yarn-9cae7cad90
      • 736ffbf test(shell): await queued input source refresh after stopping
      • 2404244 build(deps): bump astro
      • de43c42 Merge pull request #972 from hezhizhen/codex/localize-shell-choice-labels
      • 94cef1b Merge pull request #973 from dappermint/fix/shell-timed-render-pacing
      • b9f4ed4 test(shell): cover deferred input source refreshes
      • 49e30e5 fix(shell): pace timed renders by the feed seconds
      • c2048b6 fix(shell): localize built-in choice labels
      • 9a41498 Merge pull request #968 from hezhizhen/codex/localize-shell-option-titles
      • d44316c Merge PR #970: Read the input source after the change notification
      • 2c07492 fix(shell): skip a queued input source read after listening stops
      • 2d1bd27 fix(shell): read the input source after the change notification
      • 8f5e27b Close the TOML example in the components configuration guide
      • c7533ce Merge PR #966: Scroll in batches the surface can keep up with
      • 7e92c8e Merge PR #964: Pin the remaining actions to commit SHAs
      • f7a3d48 test(shell): simplify option title localization coverage
      • 9bd82c5 fix(shell): localize built-in widget option titles
      • 9cf93a6 Merge PR #962: Make root scripts declare HTTP hosts and allow plain HTTP only on loopback
      • 4cf64cf test(shell): scroll in batches the surface can keep up with
      • 9435b2e ci: drop the stored checkout token in website and scope greetings permissions
      • 99d2f28 docs(shell): put the root capabilities key above the option tables
      • fff3f78 ci: pin the remaining actions to commit shas
      • 86572bf fix(shell): make root scripts declare http hosts and allow plain http only on loopback
    6. πŸ”— r/LocalLLaMA Qwen4-27B PR found rss

      PR: https://github.com/analytics-zoo/vllm-xpu-kernels/pull/22

      The PR author seems to have contributed to intel repos a lot and VLLM. He also shares his name (might be the same person?) with a person who is either a CTO somewhere at alibaba or the Director of Zhejiang Lab.

      He has worked on Qwen3.8 before this.

      The PR also implies the KV cache size for Qwen4-27B is not decreasing.

      submitted by /u/brainExploded99
      [link] [comments]

    7. πŸ”— HexRaysSA/plugin-repository commits sync repo: +7 releases, -5 releases rss
      sync repo: +7 releases, -5 releases
      
      ## New releases
      - [ida-bochs-binaries](https://github.com/hexrayssa/ida-bochs-binaries): 2.0.1, 1.0.6
      - [ida-mcp](https://github.com/hexrayssa/ida-mcp): 20261023.0.2, 20261023.0.1, 20261022.0.1
      - [ida-nexus](https://github.com/hexrayssa/ida-nexus): 0.14.1, 0.14.0
      
      ## Changes
      - [ida-mcp](https://github.com/hexrayssa/ida-mcp):
        - removed version(s): 0.9.0, 0.10.1, 0.10.0
      - [ida-nexus](https://github.com/hexrayssa/ida-nexus):
        - removed version(s): 0.8.1, 0.8.0
      
    8. πŸ”— backnotprop/plannotator v0.28.30 release

      Follow @plannotator on X for updates

      Missed recent releases? Release | Highlights
      ---|---
      v0.28.29 | Plan review opens on OpenCode 2, a DOMPurify security update, closing a review stops the agent everywhere
      v0.28.27 | Jump to open questions, files side by side or full screen, image zoom in the Inbox, empty To field, text size for plan review and annotate
      v0.28.26 | Action items and reply drafts in the Inbox, one decision button for plan review, Enter to save a comment, a custom code font
      v0.28.25 | Re-ask open questions, delivery ticks on the list, a count of new messages on the tab, right-click a thread, click Inbox to refresh
      v0.28.24 | A new look for the Inbox, Send now, tag agents, comment on an agent's message, much smaller reads for agents, links in HTML pages
      v0.28.23 | Inbox replies reach sessions with background subagents, dictated text no longer goes missing, πŸ‘ Looks good reaches the agent, notifications that never fail silently
      v0.28.22 | πŸ‘ Looks good, full view for files, one viewer for a thread's images and files, every session prints its URL, PLANNOTATOR_BROWSER=none opens nothing
      v0.28.21 | Message an agent from the Inbox, video attachments, Open in for attachments, Code / Tests / Generated in code review, writes from other websites refused
      v0.28.20 | Inbox search (⌘K), real folder names for projects, data files open in the code view, word-only replies leave questions open
      v0.28.19 | Ask this session in T3 Code, folder sessions load shared stylesheets and images, the agent note asked once per agent, Copy connect prompt
      v0.28.18 | plannotator inbox connects your agents, agents are told when to use the Inbox, rendered Markdown in code review, Inbox Settings in sections
      v0.28.17 | The Inbox on iPads and narrow windows, the reply bar no longer cuts off "Keep open", a Pi crash on /reload fixed

      What's New in v0.28.30

      An Artifacts view in the Inbox, comments on part of an image, diagrams in code review, and Ask AI that keeps its conversation across documents in annotate. 9 PRs, one from a first-time contributor, @mvanhorn.

      Plannotator Inbox

      Artifacts

      A thread's header has an Artifacts button that shows every file, image and guided review in the thread as one grid, newest first. A tile opens the file in the viewer beside the grid, and stepping in the viewer keeps thread order.

      Split or Unified diffs in guided reviews

      A guided review in the Inbox has a Split | Unified tab on its first file. The choice applies to every file in the review. Phones always show one column.

      Re-ask from the open-questions list

      Re-ask moved into the "N open questions" list and now works for a single question too.

      Smaller changes

      • Action items use the thread's text size , so the card no longer looks larger than the messages and question cards around it. #2123

      Plannotator

      Comment on part of an image

      In annotate and plan review, open an image from the document, switch to Region and drag a box to comment on that part of it. The agent gets the image, its line in the file, the box in the image's own pixels, and your comment.

      Diagrams in code review

      Mermaid and Graphviz diagrams in a Markdown file's Read and Changes views are now drawn, and so is the diagram in a guide overview. The diagram engine loads only when a review has one, so a review without diagrams loads nothing extra.

      Ask AI keeps its conversation in annotate

      Moving between files in a folder session, opening a linked document, or going back no longer clears the Ask AI conversation. Each question still carries the document it was asked about.

      Smaller changes

      • Updates are checked about once an hour instead of once a day, so a new release shows up sooner. It is still one small request at most per hour. #2112
      • The update toast says what Update does : it installs in the background and the review keeps working. #2106

      Install / Update

      macOS / Linux:

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

      Windows:

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

      Claude Code Plugin: The plugin and the plannotator binary update separately, so run the install script above as well. In a terminal:

      claude plugin marketplace update plannotator
      claude plugin update plannotator@plannotator
      

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

      Pi:

      pi update --extensions
      

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

      What's Changed

      New Contributors

      Community

      Full Changelog : v0.28.29...v0.28.30

    9. πŸ”— Andrew Healey's Blog Decompiling Fast Food Tycoon 2: Drawing the World rss

      How a 2001 business sim rendered its rich and detailed cities.

  4. October 23, 2026
    1. πŸ”— IDA Plugin Updates IDA Plugin Updates on 2026-10-23 rss

      IDA Plugin Updates on 2026-10-23

      Activity:

      • augur
        • 86a36fe5: Merge pull request #15 from 0xdea/dependabot/github_actions/actions-d…
        • 021fa116: ci: bump taiki-e/install-action
      • haruspex
        • dc94d1f4: Merge pull request #19 from 0xdea/dependabot/github_actions/actions-d…
        • 9632d682: ci: bump taiki-e/install-action
      • rhabdomancer
        • eea04bef: Merge pull request #19 from 0xdea/dependabot/cargo/toml-1.1.8spec-1.1.0
        • 34ea21e0: Merge pull request #18 from 0xdea/dependabot/github_actions/actions-d…
        • 58e6f0c9: chore: bump toml from 1.1.6+spec-1.1.0 to 1.1.8+spec-1.1.0
        • 603de3fe: ci: bump taiki-e/install-action
    2. πŸ”— anthropics/claude-code v2.1.310 release

      What's changed

      • Added the Monitor tool and plugin monitors on Bedrock, Vertex, and Foundry, and when telemetry or nonessential traffic is disabled; long foreground sleeps are now blocked there too
      • Fixed requests failing behind some gateways and compatible servers that reject the effort-2025-11-24 beta value or mid-conversation system messages; Claude Code now retries without them
      • Fixed background cleanup deleting some recent files, such as pasted images, when cleanupPeriodDays is set to a very large value
      • Fixed compaction after a "Prompt is too long" error keeping too much of a conversation with dense text, such as base64 or SVG, so the next request could fail again
      • Fixed file read permission prompts not showing where a symbolic link leads
      • Fixed a question's auto-continue timeout firing the moment the external editor closed after a long edit
      • Windows: Fixed PreToolUse and PermissionRequest hooks letting a tool call through when Git Bash is missing and the hook's command is only quoted strings, such as a quoted path
      • Improved auto mode's prompt before the first read outside the working directories: it now says when blocking those reads makes shell commands ask for permission
      • Improved memory use of non-interactive sessions (-p, Agent SDK) during compaction when the transcript file is very large
      • Improved a mod's Image to draw inside tmux with allow-passthrough and focus-events on, in kitty, Ghostty, and iTerm2 3.5+ with fullscreen rendering, where it showed only its alt text
      • Linux: Improved /sandbox and the sandbox startup warning to name Ubuntu's AppArmor restriction on user namespaces, and how to lift it, when it keeps bubblewrap from starting the sandbox
      • Changed the error for an MCP tool call that times out in a non-interactive session while the server's elicitation is unanswered: it now tells Claude that no answer came and not to repeat the call
      • [VSCode] Fixed pressing Enter on the plan review card's "Send feedback and keep planning" button approving the plan instead of sending your comments back
      • [VSCode] Fixed the panel showing "Something went wrong" after "Switch branch & continue" on a cloud session opened from Session history's Web tab
      • [Cloud sessions] Added Claude Code cloud sessions and Remote Control permissions to Enterprise custom roles, so Owners can control access to each by role
      • [Cloud sessions] Added a Choose file button to load a cloud environment's setup script from a file
      • [Cloud sessions] Fixed failed saves and archives in the cloud environment edit dialog showing no error inside the dialog
      • [Cloud sessions] Fixed failed routine API token actions showing only a toast; the error now appears in the routine edit dialog
      • [Cloud sessions] Improved the session start checklist to show a cloud environment's setup script output in a scrolling box
      • [Cloud sessions] Changed turning on Cloud sessions or Remote Control in admin settings to ask for confirmation and list the custom roles that have that permission
      • [Cloud sessions] Changed the cloud environment dialog to open network access, setup script and environment variables from rows instead of listing every editor at once
      • [Claude Tag] Fixed Claude Tag treating ! commands such as !restart and !help as ordinary messages when sent in bold, italic or strikethrough
      • [Claude Tag] Fixed Claude Tag admin channel and workspace pages being replaced by a load error when a background refresh of the bundle list fails
      • [Claude Tag] Fixed Claude Tag's spend limits page in admin settings reporting that no channels match a filter while channel names are still loading
      • [Code Review] Fixed the Code Review admin section hiding its repositories and switches after a failed refresh of the repository list
      • [Code Review] Improved the Code Review admin section to retry the first load and show one Try again banner when it still fails
    3. πŸ”— exe.dev Hunting Bugs? Look at Commits rss

      If you’re looking for bugs, you’ll get better results if you focus the agents’ attention.

      The usual loop is roughly:

      for f in files:
        "please look for important bugs, using $f as a starting point"
      

      But I've found this to be more effective:

      for c in commits:
        "please analyze $c for important bugs; validate that they still exist at HEAD"
      
    4. πŸ”— r/LocalLLaMA Vibecoding your own inference engine is easy they said rss

      Vibecoding your own inference engine is easy they said | guys, you better just clone llama.cpp I swear.
      this thing is running gguf q4 paged into webgl2 embedded compute buffers via glsl right inside html, and tokenizer/vocab is just part of the endless debug hell. submitted by /u/CodeMichaelD
      [link] [comments]
      ---|---

    5. πŸ”— backnotprop/plannotator v0.28.29 release

      Follow @plannotator on X for updates

      Missed recent releases? Release | Highlights
      ---|---
      v0.28.27 | Jump to open questions, files side by side or full screen, image zoom in the Inbox, empty To field, text size for plan review and annotate
      v0.28.26 | Action items and reply drafts in the Inbox, one decision button for plan review, Enter to save a comment, a custom code font
      v0.28.25 | Re-ask open questions, delivery ticks on the list, a count of new messages on the tab, right-click a thread, click Inbox to refresh
      v0.28.24 | A new look for the Inbox, Send now, tag agents, comment on an agent's message, much smaller reads for agents, links in HTML pages
      v0.28.23 | Inbox replies reach sessions with background subagents, dictated text no longer goes missing, πŸ‘ Looks good reaches the agent, notifications that never fail silently
      v0.28.22 | πŸ‘ Looks good, full view for files, one viewer for a thread's images and files, every session prints its URL, PLANNOTATOR_BROWSER=none opens nothing
      v0.28.21 | Message an agent from the Inbox, video attachments, Open in for attachments, Code / Tests / Generated in code review, writes from other websites refused
      v0.28.20 | Inbox search (⌘K), real folder names for projects, data files open in the code view, word-only replies leave questions open
      v0.28.19 | Ask this session in T3 Code, folder sessions load shared stylesheets and images, the agent note asked once per agent, Copy connect prompt
      v0.28.18 | plannotator inbox connects your agents, agents are told when to use the Inbox, rendered Markdown in code review, Inbox Settings in sections
      v0.28.17 | The Inbox on iPads and narrow windows, the reply bar no longer cuts off "Keep open", a Pi crash on /reload fixed
      v0.28.16 | The Inbox on a phone, a doorbell for new questions, Mark read, step through a thread's files, replies when the asking session ended

      What's New in v0.28.29

      A patch release: plan review now opens on OpenCode 2, a DOMPurify security update, and two skill fixes. (v0.28.28 was never published; its release was stopped by the security check this update fixes.)

      Plannotator

      Plan review works on OpenCode 2

      On OpenCode 2, the plan agent wrote its plan into the chat and never sent it for review. OpenCode 2 adds its own Plan mode note telling the model to discuss the plan in the conversation, and Plannotator didn't recognize that wording. Plannotator now replaces the note, so the plan agent calls submit_plan and the review opens. Tested on OpenCode 2.0.19 and 2.1.2. OpenCode 1 is unchanged.

      Smaller changes

      • Closing a review without feedback stops the agent on every agent, not only Claude Code. Closing is not approval. #2099, closing #2097
      • The visual-explainer skill asks before installing its third-party dependency. #2099, closing #2098
      • DOMPurify 3.4.17 fixes a critical sanitizer advisory (GHSA-cg2g-xh64-v4q7). Mermaid's copy is updated too. #2104
      • Guided Reviews can carry an overview with an optional diagram (guide format version 2). Nothing creates one yet; this is groundwork. Existing guides are unchanged. #2095

      Install / Update

      macOS / Linux:

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

      Windows:

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

      Claude Code Plugin: The plugin and the plannotator binary update separately, so run the install script above as well. In a terminal:

      claude plugin marketplace update plannotator
      claude plugin update plannotator@plannotator
      

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

      Pi:

      pi update --extensions
      

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

      What's Changed

      Community

      Full Changelog : v0.28.27...v0.28.29

    6. πŸ”— r/LocalLLaMA everything will be local eventually rss

      I know current llms like opus 5.5 are in a league of their own. but we all know they're losing a shti ton of money with their subscriptions. ALSO we all know how tasks like OCR, segmentation etc are getting solved by single digit B parameter models. I'm not saying llms are a gimmick but I'm saying the future is already shaping up to be about specialized models that work better when they're smaller. easier training. so datacenter level power not needed. ten years from now we'll have a specialized model for the tasks we care about and llms will fail to do everything all at once (unless they keep calling it one model but have a hundred under the hood).

      system one models are a bad but workable example. you could tell an llm to rate options all day but get yourself on 9B parameter model trained by some lab and it tops the benchmarks.

      submitted by /u/YogurtExternal7923
      [link] [comments]

    7. πŸ”— HexRaysSA/ida-nexus v0.14.1 release

      What's Changed

      • Return whether we were the last lease in close_database by @mrexodia in #76

      Full Changelog : v0.14.0...v0.14.1

    8. πŸ”— backnotprop/plannotator v0.28.28 release

      chore: bump version to 0.28.28

    9. πŸ”— HexRaysSA/ida-nexus v0.14.0 release

      What's Changed

      • Suggest ida-domain names for AttributeErrors in execute_python by @thebabush in #72
      • Uniform support for ida/idat/idalib workers by @mrexodia in #75

      Full Changelog : v0.13.4...v0.14.0

    10. πŸ”— OmniNull/OmniWM Canary 20261023-0937 (28ded16c) 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: 28ded16c88ef
      • Base tag: canary-20261022-0439-39721295344-1

      Changes since canary-20261022-0439-39721295344-1

      • 28ded16 Merge pull request #959 from dappermint/fix/toolchain-cache-recovery
      • 810a195 ci: start from a clean toolchain when its cache restore fails
      • 0e0bf3c Merge PR #958: Add Fluxer community chat links
      • 9f35cdf docs: add fluxer community chat links
      • 4450248 Update SwiftFormat to 0.64.1
      • 9bfd535 Merge pull request #921 from dappermint/test/qa-suite-hardening
      • 4eba57f style(hidden-bar): drop the trailing comma swiftformat 0.63 rejects
      • 931a291 Merge pull request #957 from hezhizhen/codex/fix-hidden-native-cross-display
      • c532780 test(hidden-bar): stop depending on the finder extension setting
      • ba39913 test(shell): give bundled widget renders a 1 s cpu budget
      • 2b4cf58 test(shell): wait for the bar before counting its widgets
      • 18427da test(support): let until name the condition it waited for
      • 958bbfd fix: discard deferred native moves for hidden windows
      • 22b8f6c Translate the new swipe-edge and cross-display drag settings
      • 92ca342 Merge pull request #952 from brdoney/swipe-edge-behavior
      • b7b10dd Merge pull request #933 from hezhizhen/codex/native-titlebar-cross-display
      • 47d8df0 Merge pull request #949 from brdoney/fill-left-reserve-space
      • 6b608a4 Merge pull request #956 from brdoney/fix-nil-layer-border
      • dc5117e Merge pull request #951 from hezhizhen/codex/fix-notification-api-reference
      • a89d802 fix(shell): draw no border when a widget sets a width without a color
      • dafebd0 Update fill-left reserve docs and reuse the overlapping case
      • c24495e Add configurable workspace swipe behavior at the edges
      • 56dd4a4 fix(docs): include notification types in the Luau reference
      • bc403f5 fix: retain deferred native drag correction obligations
      • 44459e7 fix: ignore managed frames during native cross-display adoption
      • f71c0a6 feat: opt in to native title-bar moves across displays
      • 9fc6374 Merge pull request #940 from hezhizhen/codex/fix-wallpaper-region-crop
      • 672f8ff Reserve workspace bar space in Fill Left of Notch mode
      • cf3599e Merge PR #945: Check widget option declarations and add Nocturne options
      • 97b8aaa test(shell): match whole option names in the declaration check
      • efb89c7 fix: crop full-window wallpaper captures before region fallback
      • 80dca94 feat(shell): declare scratchpad, calendar and weather options for nocturne
      • 37f7889 test(shell): check bundled widgets declare the options they read
      • f8cddb7 Merge pull request #941 from dappermint/fix/touch-count-provider-rewrap
      • ddc5e5c Merge origin/main while preserving notification support
      • 10455b5 Merge pull request #943 from rickythefox/feat/942-focus-rank
      • d61a7d3 Dismiss notifications through their native Close action
      • bacd0e5 Add native notification actions and capture diagnostics
      • 2ebfb50 feat(ipc): expose window focus history via query windows
      • 0aa1470 Match Notifications to OmniShell styles
      • 4953efe Add retained notifications to OmniShell
      • 31d4e80 fix(input): stop the touch count provider growing on every read
    11. πŸ”— r/LocalLLaMA Models disappearing from Huggingface rss

      Models disappearing from Huggingface | I've been noticing a lot of my downloads stopping suddenly and being unable to resume. When I checked the models it seemed like they were gone. Here's the ones I can see are missing:

      • dealignai/MiMo-V2.6-Pro-RL-UNCENSORED
      • audnai/penclaw-GLM-5.3-abliterated-for-offensive-cyber
      • huihui-ai/Huihui-Kimi-K2.7-Code-abliterated-GGUF

      and somehow not a single Alliterated Deepseek-R1. Does anyone know what's going on and where else the vanished models might be found? submitted by /u/umarmnaq
      [link] [comments]
      ---|---

    12. πŸ”— synthetic-lab/octofriend octofriend@0.0.60 release

      octofriend 0.0.60

    13. πŸ”— r/LocalLLaMA MiniMax-M3.1-Flash rss
    14. πŸ”— backnotprop/plannotator v0.28.27 release

      Follow @plannotator on X for updates

      Missed recent releases? Release | Highlights
      ---|---
      v0.28.26 | Action items and reply drafts in the Inbox, one decision button for plan review, Enter to save a comment, a custom code font
      v0.28.25 | Re-ask open questions, delivery ticks on the list, a count of new messages on the tab, right-click a thread, click Inbox to refresh
      v0.28.24 | A new look for the Inbox, Send now, tag agents, comment on an agent's message, much smaller reads for agents, links in HTML pages
      v0.28.23 | Inbox replies reach sessions with background subagents, dictated text no longer goes missing, πŸ‘ Looks good reaches the agent, notifications that never fail silently
      v0.28.22 | πŸ‘ Looks good, full view for files, one viewer for a thread's images and files, every session prints its URL, PLANNOTATOR_BROWSER=none opens nothing
      v0.28.21 | Message an agent from the Inbox, video attachments, Open in for attachments, Code / Tests / Generated in code review, writes from other websites refused
      v0.28.20 | Inbox search (⌘K), real folder names for projects, data files open in the code view, word-only replies leave questions open
      v0.28.19 | Ask this session in T3 Code, folder sessions load shared stylesheets and images, the agent note asked once per agent, Copy connect prompt
      v0.28.18 | plannotator inbox connects your agents, agents are told when to use the Inbox, rendered Markdown in code review, Inbox Settings in sections
      v0.28.17 | The Inbox on iPads and narrow windows, the reply bar no longer cuts off "Keep open", a Pi crash on /reload fixed
      v0.28.16 | The Inbox on a phone, a doorbell for new questions, Mark read, step through a thread's files, replies when the asking session ended
      v0.28.15 | Long Inbox threads fold to what is new, "Skipped N questions" replies, Inbox list and sidebar fixes

      What's New in v0.28.27

      A jump list for a thread's open questions, files side by side or full screen, image zoom everywhere, text size for plan review and annotate, and a run of fixes from your reports.

      Plannotator Inbox

      Jump to open questions

      When a thread has questions you haven't answered, a button in its foot says how many. It lists them, and choosing one opens its message and takes you to the card.

      Side by side or full screen, remembered

      An open file has a Side by side | Full screen switch in its header. The Inbox remembers the one you picked.

      Zoom and pan images

      Images in the Inbox zoom with a trackpad pinch or Ctrl/⌘ + wheel, pan by dragging, and switch between Fit and 2Γ— on a double-click. ← β†’ still step to the next file while zoomed, and a comment's drawing stays on the image at any zoom.

      Action items as a checklist

      An agent's action items show as one checklist card: tick each off, open it for the details, and see "2 of 3 done" at a glance.

      Smaller changes

      • New messages start with To empty , so a message can't go to the wrong agent. The last agent you used is listed first. #2089
      • Attached files always show in the Clean look. #2092
      • A thread's draft status sits to the right of its buttons. #2083
      • Agent icons come in one set of sizes , and tooltips are borderless and quicker to appear. #2078, #2079
      • Phone sheets have rounder top corners. #2076

      Plannotator

      Text size

      Settings β†’ Display β†’ Text size makes plan review and annotate text smaller or larger.

      Zoom images

      The image viewer zooms with the mouse wheel or a pinch and pans by dragging. Actual size now really shows the image at its own size.

      Smaller changes

      • The tab title and header name the open file in annotate. #2075, closing #2061
      • Comment Edit and Delete buttons show on screens without hover (Chrome on some Linux setups, touch screens). #2065, closing #2062
      • HTML pages you annotate can open alert, confirm and prompt dialogs. #2071, closing #2063
      • Mermaid labels in Chinese, Japanese and Korean no longer wrap their last character onto a new line. #2072, closing #2064
      • Ask AI answers show tables. #2070, closing #2069
      • Back from a linked document returns to where you were reading. #2084, closing #2082
      • Links with an underscore are linked in full , not cut off at the first _. #2088
      • Pi and Oh My Pi: after updating Plannotator while Pi is running, you're now told to restart, instead of seeing a confusing error. #2087, closing #2085

      Install / Update

      macOS / Linux:

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

      Windows:

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

      Claude Code Plugin: The plugin and the plannotator binary update separately, so run the install script above as well. In a terminal:

      claude plugin marketplace update plannotator
      claude plugin update plannotator@plannotator
      

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

      Pi:

      pi update --extensions
      

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

      What's Changed

      Community

      Most of this release came from your reports. Thank you:

      Full Changelog : v0.28.26...v0.28.27

    15. πŸ”— jellyfin/jellyfin 12.3 release

      πŸš€ Jellyfin Server 12.3

      We are pleased to announce the latest stable release of Jellyfin, version 12.3! This minor release brings several bugfixes to improve your Jellyfin experience. As always, please ensure you take a full backup before upgrading!

      Discuss this release further on our forums.

      Changelog (7)

      πŸ—οΈ Enhancements

      πŸ“ˆ General Changes

    16. πŸ”— New Music Releases O.A.R. - Three Tinted Windows rss

      O.A.R. - a new release is available:

      • 2026-10-23: Three Tinted Windows (Album)

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

      Visit muspy for more information.

    17. πŸ”— New Music Releases Polyphia - BE NOT AFRAID rss

      Polyphia - a new release is available:

      • 2026-10-23: BE NOT AFRAID (Album)

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

      Visit muspy for more information.