🏡
  • ↔
  • →
  1. August 16, 2026
    1. 🔗 gildas-lormeau/single-file-cli v2.1.2 release

      SingleFile CLI 2.1.2

      Command-line fixes

      • Fixed case variants of options being silently ignored, e.g. --compress-html false or --include-bom (option names are now canonicalized when parsing)
      • Fixed --settings-file-profile being ignored
      • Fixed settings files overriding options passed explicitly on the command line
      • Fixed --http-header values containing "=" being truncated, e.g. base64 credentials
      • Fixed the error thrown when passing --http-header values without "="
      • A missing URL, unknown options and invalid option values are now reported as explicit errors with a non-zero exit code (#183)
      • --help now also works when using --urls-file

      URLs file fixes

      • Fixed single character option values being dropped, e.g. --crawl-max-depth 2
      • Fixed blank lines being captured as pages
      • Fixed duplicate URLs being captured multiple times
      • Unknown or invalid options in URLs files are now reported as warnings

      Capture fixes

      • Fixed --browser-load-max-time and --browser-capture-max-time not interrupting captures of hanging pages or downloads, which could run forever (#134)
      • Fixed parallel captures overwriting each other when resolving identical filenames (files are now created exclusively)
      • Error messages are now included in the file set with --errors-file (#136)
      • The error displayed when the browser executable cannot be found now includes the path and suggests --browser-executable-path

      Co-authored by Claude (Claude Code)

    2. 🔗 HexRaysSA/plugin-repository commits sync repo: +1 plugin, +1 release rss 
      sync repo: +1 plugin, +1 release

## New plugins
- [climacros](https://github.com/allthingsida/climacros) (1.0.5)
    3. 🔗 gildas-lormeau/single-file-cli v2.1.1 release
      • Fixed --output-json and fetching resources when running with Node.js 24 or 25
      • The browser is now relaunched without --browser-single-process when it crashes on startup
      • Fixed the compilation of executables embedding unrelated files
      • Added a CI workflow running the linter and the test suite
    4. 🔗 gildas-lormeau/single-file-cli v2.1.0 release

      SingleFile CLI 2.1.0

      Breaking changes

      • Node.js 24+, Deno 2.2+ or Bun 1.2+ is now required
      • --browser-single-process is now enabled by default (#194 by @madcow). Pass --browser-single-process=false to run the browser with multiple processes
      • --embed-pdf, --embedded-pdf, --embed-screenshot and --embedded-image now fail with an error when --compress-content is not set. These options were silently ignored before

      Crawler fixes

      • Fixed pages being skipped when they are linked both with and without a URL fragment
      • Fixed --crawl-replace-URLs ignoring links containing a URL fragment
      • Fixed --crawl-replace-URLs replacing links with the wrong filename when filenames conflict, e.g. pages with the same title
      • Fixed --crawl-replace-URLs when used with --output-directory (#190 by @brasswood)
      • Fixed the detection of inner links when URLs contain a port number
      • mailto:, javascript: and tel: links are now ignored when crawling

      Capture fixes

      • Fixed pages being captured too early when they contain iframes
      • Fixed the delay set with --browser-wait-until-delay. It is now restarted when the page reaches a new lifecycle state
      • Fixed --output-json when saving compressed pages with Node.js or Bun
      • Fixed --embed-pdf (broken since 2.0.78)
      • Fixed a stack overflow when fetching large resources (#192 by @brasswood)
      • Fixed the parsing of emulated media features (#200 by @FaFre)
      • Fixed --output-directory when used with --filename-conflict-action overwrite
      • Fixed fetching file:// URLs on Windows and file:// URLs containing a query or a fragment

      Reliability fixes

      • Fixed unhandled promise rejections when the browser crashes or cannot be found
      • Fixed a deadlock when the browser writes too much data on stdout or stderr
      • Fixed the CLI hanging when invalid page data is received from the browser
      • Fixed temporary profile folders not being removed when launching the browser fails
      • Fixed exit codes when the process is interrupted with Deno, e.g. Ctrl-C now exits with code 130
      • Fixed error codes not being forwarded when fetching resources from the browser

      Misc

      • Added a test suite based on the Node.js test runner (npm test)
      • Removed the ws dependency
      • Updated SingleFile core

      Co-authored by Claude (Claude Code)

    5. 🔗 PrimeIntellect-ai/prime-agent Beta (v0.7.2-beta.496.1.06e4a19) release

      Automated beta build from main (06e4a19dc902382dbb90b67fbe4ed53c3f7b99b2).

    6. 🔗 Register Spill Joy & Curiosity #95 rss

      In the last two weeks I've shipped: a new experimental provider backend for our orbs, an in-product bug reporting feature (not released yet) including an admin area where we can triage bugs, disk and memory warnings for orbs, visible setup logs when orbs are starting, a full Comet Busters-like game that's hidden as an easter egg on our website, a microphone selector for our dictation features, a new work-in-progress page that explains what orbs are that has a bunch of handwritten text and videos and other stuff I put in there by hand, user preferences for themes, and a few smaller things.

      I also fixed around twenty bugs and removed 5k lines of code that we no longer need.

      "We get it, man, you shippe--"

      Nah, nah, nah! Not the point. The point is this:

      I have not used my local development environment for any of this. I've done all of this remotely, using Amp, in orbs. Everything! Backend for remote machines; messages sent across three services to warn about system resources; landingpage. The freaking game is probably the least surprising thing here, isn't it? And it's a game with custom assets!

      Isn't this wild? No, I know, it is, that's what I'm saying.

      "Surely some things you want to check or test locally, no?" Nah, not really. I mean, yes, that's probably what I would've said half a year ago if you'd told me I won't need my local dev setup anymore.

      Turns out that, no, you don't. You can just ask the agent to give you "irrefutable proof" that something works and if you have an orb and it can do whatever it wants and install whatever it needs it will find a way to give you that proof. Orbs are malleable, the agent can shape them to fit the task by installing and running whatever it needs and and then you get a bespoke made-for-exactly- this-task machine in which an agent can go crazy and if you ask it it will give you a presentation or a narrated video in which it shows by -- frame-by- frame, man! -- that the race condition has been fixed.

      And then, what else do you need your local dev env for? Editing code by hand? Come on, man. Reviewing code deeply? Amp has a diff viewer, so you don't need to do that locally either. And for all of the things I shipped here, I didn't review each line anyway. I do spot checks and make sure the architecture is right, yes, but do I need local tools for that? No. You can ask the agent to help you with reviewing by quizzing you, by giving you diagrams, by showing you a presentation.

      What about the fiddly things? The things you do want to feel your way towards, with your hands? Little bit of padding here, some margin there; now let me flip these two paragraphs and-- ah yes, better. That kind of stuff? That's actually where I'm now experimenting the most because I do have this need to flip words and paragraphs and move stuff around. I want to look at it, change something, look again; undo, redo, change, undo, and back around again.

      But here too the game has changed in a way I find marvelous. Because you can just dictation-dump all your ideas to the agent and hand it screenshots and assets and raw notes and snippets and then ask it to provide you with example pages and 15 different variations of the widget you're interested in, and then you can tweak those and say "this one's good, let's use this one" and you feel like you're the head chef strolling through the kitchen, spoon in hand, tasting the soup over here, tasting the dessert over there, saying "nah" or "mmmmh, good" or "into the trash", and your headless and faceless and bodyless sous-chefs don't mind at all and just do what you say and try again.

      Then weeks go by and you notice you haven't git pulled in a long time and every time you do end up doing that again (due to nostalgia?) maybe use more than one checkout, you notice that it starts to feel… yucky? dirty? unclean?

      Wild times. Exciting times. The models are there now. And if you doubt that, just wait a couple months.

      • New episode of Raising An Agent is out! We recorded this one in-person, in Munich, and talked about everything that was on our mind last week (and this week): orbs, jellyware, why AI by itself doesn't lead to slop, how you need to rethink software now, and, maybe most importantly, the mind-blowing realization of that week in Munich, that no one cares about their local dev env anymore. We all had to wipe our laptops four weeks ago and people said they still haven't ported their dotfiles over and at this point don't care anymore.

      • Speaking of which: I recorded a short video on why orbs aren't "just VMs" and why saying "orbs are just VMs" is missing the mark, just like saying "the cloud is just another person's computer". Also: woo boy, some people are really bothered by product names? Well, too late. It's orbin' time. I get emails from customers telling me they want to get their team "into orbit", others signing off with "happy orbin'!", and customers greeting us in Slack channels with "I love me some orbin' in the mornin'."

      • My teammate Will wrote about how we can push straight to main and still have SOC2. One of the most asked questions we got in the last few months: "Wait, you don't use pull requests? How do you have SOC2 then?" Turns out that SOC2 doesn't require PRs.

      • Very short video in which I show off how I iterate with agents in orbs, working on landingpages and making visual changes, something.

      • Stolen Thoughts - Stealing Reasoning Traces from Proprietary LLM APIs. First of all: wow, what a name, what a website. And then, of course, this is fascinating, isn't it? But I'm not sure whether it's much more than that.

      • Wired also has a write-up on it: A New Trick Reveals AI Models' Inner Thoughts.

      • Read Austin Kleon's Don't Call It Art. Lovely, as expected. If you're in any way interesting in making things or building or writing or just … doing stuff on the Internet: get all of his books. They're very short but very good and very inspiring.

      • It's been a while since I've wanted to access to something this badly: "Cerebras powers GPT-5.6 Sol on Ultrafast mode, delivering up to 750 output tokens per second." Hey, tell the kids to cup their ears real quick. Motherfucking seven hundred and fifty tokens per second. Fucking hell! If there's a sweet angel at OpenAI reading this and can give me access: I will fly to San Francisco and hold your hands and kiss your forehand before I kneel down to thank you and to bless your family and the house they live in and the ground they walk on.

      • Zuckerberg weighs in: "I do not understand why anyone who believes that AI will eliminate most jobs and much of humanity's relevance would rush to build that future." (No, I have not read the whole thing.)

      • The hardest working font in Manhattan. This was long, but soooo good. So good. On a spectrum from "doesn't care about to fonts" on the left to "writes a long and deeply researched article about the history of an unknown font" I'm slightly to the right of center, but I read the whole thing and think you should too if you ever thought "that's a neat font." (Except if that font was Papyrus, of course.)

      • Nail it to the walls: There are no lossless transformations of natural-language text. Very, very, very good. (Sidenote: can you imagine working at a 1000 people org and people use AI to generate Slack messages, emails, PRDs, and slide shows? Yup. Horror stories between two parens.)

      • Craig Mod: A Swarm of Blood Robots. Insert the usual adjectives that I use when talking about Craig Mod's writing: excellent, fantastic, lovely, beautiful. They all apply here too. There are so many things I want to quote here: the section about writing with LLMs, the part about the Weirdness, some of his example projects, the end about the usefulness of these tools. But instead let me just share this one observation: maybe my views on the future of software are so aligned with Craig's (if you go back and read the last twenty issues of this newsletter you'll find that my thoughts on liquid software, jellyware, the future of software, etc. match what he's describing here) because Craig is not part of the software industry and he's not huffing and puffing about how things aren't done properly and he's not stomping his feet about these models being bad at X and Y and he's not stuck in a ten-year old world view of how software's supposed to be built and instead he just has a ton of ideas for things to build and leans into seeing what these models can do and then goes and does it.

      • Sudo Aquarelle, a watercolor simulator. So nice.

      • Finally an end to this stupid argument: "Code was never the hard part" is an insult to all programmers.

      • There is No "Done": Reflections on a Completed AT Thru-Hike. This was great, saying that as someone who's dreamt of walking the AT since he read A Walk in the Woods many, many years ago.

      • I didn't know that the Apple TV has color calibration via iPhone.

      • One of the most beautiful things I've come across this week: Ordinary Abundance. "All the items in this room were once out of reach; some not yet invented, others too rare or costly for the vast majority of people. Today, most of us lucky enough to live with them walk past without a second thought." We'd all probably do well by scrolling through it once a week.

      • Are you a hardcore Rust engineer and want to work remotely with a small and equally hardcore team and do systems- and infrastructure programming? Look no further. I highly recommend working with Nathan and Nick.

      • The Antithesis Principle. This was fascinating. I failed to apply it to every example and got different answers, which makes me think that either (a) the principle is not that clearly defined (possible) or (more likely) that (b) my brain's not wired in this way and I could probably benefit from rewiring it a bit.

      • OpenAI has a friction@ email address employees can use if they feel like they're being blocked.

      • My wife and I were talking about Dolly Parton this week and I said, "Have you ever seen her when she was younger? Or heard her talk?" She said, "No, I haven't." I immediately pulled out my phone and showed her this video.

      • Reminds me: I fell off the wagon again and have watched this video five times in the last 24hrs and I'm about to watch it again, so here, you watch it too. It's only one of the greatest things ever recorded. Danny Carey performing Pneuma.

      • "My dad used to tell me that you could yell at a bear and it would go away. Camping when I was 10, a bear came into the site. Dad got out of the tent and yelled at it, and it just snorted back at him. Dad got back into the tent. 'That's all I got.' A lot of life is like this."

      You should subscribe and tell your friends about this newsletter too, because I know you love it and you keep telling me, but I need the numbers to go up, for the shareholders (and the board):

    7. 🔗 r/LocalLLaMA Qwen3.8-27B vs Qwen3.6-27B writing ray-tracers in BASIC rss

      Qwen3.8-27B vs Qwen3.6-27B writing ray-tracers in BASIC | one of my llm hobbies is re-creating graphics demos i used to write in BASIC in the late 1980s. i slopped together an agentic harness and a basic-to-js transpiler in a web page i've been playing with for a few months. the agent can write basic programs, run them, examine the resulting images, and iterate. qwen3.6 could do a ray-tracer with some user input -- often it got something wrong that it couldn't see/didn't notice, and hence wouldn't fix without further prompting. qwen3.8 typically knocks it out of the park on its own, iterating to a good result. both models are running the unsloth UD-Q8_K_XL quants. i'm pretty happy with 3.8 so far. the user prompt was "write a recursive ray-tracing demo to render three metallic spheres (copper, silver, gold) over a glossy checkerboard plane and under a deep blue sky. use the cook-torrance model to render the spheres." submitted by /u/Ok-Breakfast1878
      [link] [comments]
      ---|---

  2. August 15, 2026
    1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-08-15 rss

      IDA Plugin Updates on 2026-08-15

      New Releases:

      Activity:

    2. 🔗 HexRaysSA/plugin-repository commits sync repo: +1 release rss 
      sync repo: +1 release

## New releases
- [IDA-MCP](https://github.com/captain-ai-hub/ida-mcp): 0.8.1
    3. 🔗 r/LocalLLaMA If you would have told me half a year ago that a local model running in my office would be able to one-shot a Super Mario clone, I would have called you nuts. Qwen3.8-27B is a different beast. rss

      If you would have told me half a year ago that a local model running in my office would be able to one-shot a Super Mario clone, I would have called you nuts. Qwen3.8-27B is a different beast. | Running the Q8 GGUF on my Framework Desktop is not fast, but it's extremely smart for overnight batches and background jobs. Can't wait to play around with MTP and other quants. Have any of you found ways to improve speed while keeping accuracy? https://mikeveerman.github.io/qwen38-27b-mario Edit: to avoid copyright issues and to see how creative it would get, I asked Qwen3.8 to make it circus-themed instead of Mario-themed. It's technically no longer a one-shot. submitted by /u/MikeNonect
      [link] [comments]
      ---|---

    4. 🔗 r/LocalLLaMA Aged like fine wine rss

      Aged like fine wine | submitted by /u/TigleLive
      [link] [comments]
      ---|---

    5. 🔗 r/LocalLLaMA Qwen 3.8 35BA3B spotted rss

      Qwen 3.8 35BA3B spotted | https://preview.redd.it/xwbkbbj55ijh1.png?width=1554&format=png&auto=webp&s=abd354c8a6bef033d5fb8383c49e4a682ab22105 Just wait and see https://github.com/modelscope/ms-swift/commit/ab726e9d445a6520a70df2c831177d46adb1f589 submitted by /u/BazzyIm
      [link] [comments]
      ---|---

    6. 🔗 r/LocalLLaMA Qwen 3.8 - 27B is a game changer rss

      So a bit of context, I am a cybersecurity senior analyst
      I am interested in LLMs for that field especially with MCPs to connect them to the tools or for writing scripts

      I started this field by doing assembly language reading for hacking games when I was a teenager then that became malware analysis then I started to analyze traffic and logs at work for a living
      Before work I competed in cybersecurity competitions known as capture the flag to solve only one category of the challenges and that is malware analysis

      Now here is the scene in LLM x Cybersecurity

      Entry-level CTF challenges (I used to solve around 2017-2018, got first job in 2019) were solved and saturated by LLMs a long time ago (See intercode CTF benchmark)

      Then High level CTFs (NYU CTF Bench, CSAW challenges, and CyBench) these were solved a while ago

      Today we have
      CyberGym (vulnerability description (CVE report not real details) plus code base find vulnerability
      That was solved

      Then ExploitGym (the one recent OpenAI model escaped and hacked hugging face to find solution, the 2 vulnerabilities themselves are trivial (JWT spoofing with no server side checks for Jfrog sandbox and JS + Python template in open source data viewer of Hugging face)
      Still impressive for a fully autonomous model

      ExploitGym gives vulnerability details + exploit technique/details and codebase (I wonder how/why OpenAI model escaped it in the first place those details should manage it this is why I feel it is staged but whatever right)

      ExploitBench
      More realistic threat vector
      1-day not 0-day (0-day is a novel vulnerability no one else knows about it hence the name, 1-day is a known vulnerability patched, if in an open source project you can compare patches before and after and know it but not as valuable as 0-day since people will/should update their software, 0-days can and are used against high profile targets like in some 3rd world countries used for surveillance (and possibly non-3rd world countries ?!) but you usually can’t use a 1-day for that but still)

      So ExploitBench is 1-days in V8 engine (used in chrome, electron vs code almost everything!!)

      Gives the model a patch diff and codebase base that is it

      Models are going wild on ExploitBench and ExploitGym but haven’t gotten there yet at the moment and only recent frontier models improved massively instead of near zero across the board

      This is a massive risk indicator
      Imagine models capable of exploiting any and every piece of software written by less capable people or other weaker LLMs (complex vulnerabilities!)

      Not only that but global elite CTFs like DEF CON

      You have an OpenSage harness (and ADK like Google adk or Anthropic adk, however this OpenSage ADK asks the model to design its own agent/s!, with whatever tools or sandbox environments it finds fitting for the Subagent to do the assigned subtask effectively, it can even design its own MCPs!, models don’t fully utilize that yet but some do and improved form like 39% to ~60% just by using that harness (same model!) )

      1. Now my own benchmarks are simple

      Some malware samples that I learned during my career and consider personal milestones

      And one SIEM analysis challenge (logs that contains an attack plus normal behavior)

      I tests on lots of models (Qwen3.6, heavily trimmed down Minimax 2.5 …etc, on my Strix halo and compared with opus at the time (the best opus at the time was 4.5!, it was better solved major stuff but didn’t implement the code required to decompose the malware and analyze its second stage)

      Now enter Qwen 3.8 27b
      3.
      What was SOTA like 6 months ago or around beginning of this year
      Now we have better local models at the same task

      Qwen 3.8 devoured the malware that Opus couldn’t

      I had some time analyzing and remembering its custom implementation (it has custom RC4 decryption routine, that is tricky with string manipulation!
      And Strix halo isn’t the fastest LLM machine

      By the time I remembered that malware and how it works

      Qwen had already extracted and disassembled the decrypted payload!

      I am stunned

      This is super dangerous

      I imagine how a single person / threat actor can now do what a state-sponsored intelligence service shacking team was required to do 1 year ago

      These teams usually have

      1. Usual network scanning or mapping especially of their targets
        This can be easily done by even weaker models or no models at all

      2. Initial access operations (phishing campaigns until some clicks or attempting to profile people like receptionist or sales people or HR, essentially any first line of communication at an organization or a company, to later make a targeted phishing against them)

      This could be also better done with the aid of deep fakes and other stuff

      1. Advanced and resourced teams would have zero-day or 1-day research teams
        Especially against software used on the targets site from team 1

      This third step can be fully automated with models now
      This is the hardest step

      Defenders can use LLMs but it is much harder to integrate new tools than offensive teams

      At this level the world will change
      Tbh I always thought cybersecurity was harder to automate with LLMs than software engineering or IT
      But with this, this is super unbelievable

      And not only a cloud model or an expensive to run locally model
      A local model! Can you believe it
      No traces no API calls no nothing

      Empowered with the right environment setup and tools and it can do what teams of attackers or malware analysts were needed to do

      Btw for malware analysis I give it Ghidra and a sandbox with python (it can use pefile or capstone or whatever it needs and it does use them!)

      And also recently I added a Vbox with Vbox MCP and a debugger inside that box with another MCP for the LLM to control both (snapshot restore functionality and debugger functionality)

      These tasks were hard and not every security analyst was a malware analyst
      Even malware analysis positions are very rare and technical and don’t pay well because not much needed (I used to starts at assembly in assembly debuggers for nights at times!)

      This is going above and beyond

      Anyone had similar moments in cybersecurity or anything else ?

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

  3. August 14, 2026
    1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-08-14 rss

      IDA Plugin Updates on 2026-08-14

      New Releases:

      Activity:

      • augur
        • 5a538755: ci: bump the actions-dependencies group with 3 updates
      • capa
      • efiXplorer
        • fe106ca6: feat: use uncached ctree for analysis, combine efixplorer windows and…
        • 65f3af5e: fix: use decompile uncached (#146)
        • 6b2707c2: feat(ui): combine efixplorer windows and preserve deterministic order
        • 9c24e3c0: build: update idasdk and disable warnings for third-party headers (#144)
        • e66f693d: feat: add support for linux aarch64 builds (#143)
      • eject_idb
        • 4fb7b2fb: Maintenance release (v0.0.3)
      • haruspex
        • 072bd725: ci: bump the actions-dependencies group with 3 updates
      • ida-sdk
        • 2a9143f2: idapython: Make the standalone build self-sufficient
        • e7239805: sdk: Rebuild the Windows int128/network libs CRT-neutral
        • dca60670: build: Default to Release for every standalone entry point
        • 225c3064: build: Ship the Windows Qt import libs
      • qscripts
        • 6d361f34: hcli: package qscripts as flat per-IDA-version plugin zips (hcli-inst…
      • rhabdomancer
        • 10c1433e: Merge pull request #7 from 0xdea/dependabot/github_actions/actions-de…
        • 5ea066d0: ci: bump the actions-dependencies group with 3 updates
      • Security-Tools
        • 5fbe3378: Add Proxychains for Windows with documentation and configuration
      • twdll
        • 389b8551: feat!: properly return POLITICAL PARTY LIST
    2. 🔗 tintinweb/pi-subagents v0.16.1 release

      No content.

    3. 🔗 exe.dev No Plan Survives Contact With the Enemy (Reality) rss

      If you’ve ever presented the design of a product after the fact, you know the most interesting bit is the surprises. What broke at scale? Where did you change course? What did the customers do that you didn’t expect? What were the interesting metrics? These are impossible to predict in advance. They’re also the most important parts—the punch lines.

      When we talk to folks about how they use coding agents they usually fall near one end of a spectrum: planners , who work on a spec or design with an agent, and iterators , who write a short prompt, and iterate on (or throw out) the results. Of course, this is all new, and none of us knows what we’re doing yet. (This is the time to let a thousand flowers bloom. Build your own software factory.)

      But the debate on planning vs iteration is not new. (And neither side is right, though you should consider about what works for your team, and why). We’ve read clear PRDs or slides that have set the direction for a product or project. We’ve been in meetings where the prototype carried the day after weeks of failed paper designs. And everything in between.

      If your most precious commodity is your attention, ask your agents for the design after they’ve built the thing. Ask it for the surprising things. The sticky bits. The workarounds. The contentious topics in review. The traditional funny quote here is from Frank Westheimer, who said “Why spend a day in the library when you can learn the same thing by working in the laboratory for a month?” If it’s the coding agent—and not you—in the lab, however, this is turned upside down: let the agent spend some extra cycles in the lab, and get one layer deeper on the design.

      The planners and iterators are closer than they think: a plan that’s been prototyped is a better plan.

    4. 🔗 modem-dev/hunk v0.18.2 release

      What's Changed

      • Speed up hunk diff in repositories with many untracked files by @benvinegar in #742

      Full Changelog : v0.18.1...v0.18.2

    5. 🔗 r/LocalLLaMA Local uncensored Opus 4.6 at home - Qwen3.8 27B heretic rss

      Local uncensored Opus 4.6 at home - Qwen3.8 27B heretic | Someone made a heretic version of Qwen 3.8 27B, giving us a local Opus 4.6 tier model but without any refusals or safeguards! Fuck Dario submitted by /u/Temporary_Idea8880
      [link] [comments]
      ---|---

    6. 🔗 BarutSRB/OmniWM OmniWM v0.6.2 release

      What's New Since 0.6.1

      0.6.2 makes macOS app hiding a first-class visibility state, rebuilds native- fullscreen placeholder handling, adds launch safety checks, repairs Menu Anywhere submenus, and hardens the CLI against hostile or unusual window text.

      Before You Upgrade — Breaking Changes

      • Accessibility and Input Monitoring are now required at launch. Input Monitoring was previously only prompted for when you set up a System Hyper Trigger, although secure-input detection already depended on it; OmniWM now blocks window-management startup until both permissions are granted. Screen Recording remains optional and only enables Overview thumbnails, drag previews, and captured Hidden Bar glyphs. If you continue without Screen Recording, the permissions window returns on each launch.
      • Other window managers now block startup. A second OmniWM instance, a recognized resident window manager, or an incomplete current-user process scan stops bootstrap with no bypass. The recognized managers are AeroSpace, Amethyst, bobrwm, Glide, komorebi, Nehir, Paneru, parket, Rift, Tangrid, TrimWM, yabai, and Yashiki; Hammerspoon and skhd are not treated as conflicts on their own. Quit the conflicting manager or background service, then choose Check Again , or quit OmniWM.
      • Upgrade OmniWM andomniwmctl together. The IPC protocol moves from 10 to 11, and protocol-10 operational requests are refused with error: protocol_mismatch; version discovery remains available. Third-party IPC clients must adopt protocol 11.
      • Hidden-app state has a new IPC contract. isAppHidden and the is-app-hidden field now expose macOS Hide directly; isVisible and --visible exclude windows whose app is hidden. The old layoutReason: "macos-hidden-app" value is gone, so automation using it must migrate to isAppHidden.
      • Commands targeting macOS-hidden windows changed. window focus now unhides the app and focuses the exact window. window navigate and window summon-right reject a hidden target or anchor with not_found until it is unhidden.
      • The fixed-column consume/expel actions are no longer shortcut-assignable. Existing consumeOrExpelWindowLeft and consumeOrExpelWindowRight TOML assignments are ignored and removed on the next settings rewrite. Their behavior remains available through omniwmctl command consume-or-expel-window-left and consume-or-expel-window-right; normal directional Move shortcuts remain assignable.
      • Human-readable CLI output is sanitized. Table, text, and TSV cells replace control characters and Unicode line separators with spaces, and table padding now follows terminal-cell width. JSON preserves the original string values and remains the lossless choice for automation.

      Configuration compatibility is otherwise unchanged: no other persisted settings keys or defaults changed, there is no new saved-layout or restore format, and OmniWM still requires macOS 26+ on Apple Silicon.

      macOS Hide

      • Cmd-H now behaves like a real visibility suspension. Hidden-app windows leave Niri and Dwindle layout, navigation, focus recovery, resizing, and balancing immediately, so visible windows reclaim the space. Their durable placement and sizing remain intact, and unhiding restores the exact Niri column or Dwindle tree position. #566
      • Hidden windows remain searchable in the Command Palette, where a red App hidden badge marks them; selecting one unhides its app and focuses that exact window. The Workspace Bar uses eye-slash indicators, with distinct styles and VoiceOver descriptions when some or all windows in a grouped app are hidden.
      • Overview is the deliberate exception: windows from hidden apps are dropped from it entirely, and they cannot be dragged or driven by structural hotkeys there until the app is unhidden.
      • Niri sizing, preset cycling, reset, and balance now operate only on visible column members, so a hidden sibling can no longer clamp a visible window or have its saved size rewritten.

      Native Fullscreen

      • Native-fullscreen placeholders now reserve the real accepted tile slot. The redesigned card follows layout animation and survives window identity changes; its reserved slot can be moved or resized with normal layout commands while the live window is on its macOS fullscreen Space, and activating the card switches back to that window.
      • Placeholders hide correctly on inactive and fullscreen Spaces, stay out of focus and border ownership, and are excluded from OmniWM capture. They request exclusion from the macOS screenshot window picker, with retries and diagnostics if macOS refuses it.
      • Fullscreen transition expiry, app termination during service downtime, window recreation, and ambiguous multi-display identities now recover safely. A failed position write can no longer become a bogus permanent minimum-size constraint.

      Menu Anywhere and Shortcuts

      • Menu Anywhere submenus now load complete snapshots and preserve the source app's enabled and disabled states. Nested menus no longer truncate to one row or expose partial actions; an incomplete Accessibility read shows (Unavailable) instead. #571
      • The advanced-command switch is now Include Advanced Commands and sits directly beneath the shortcut list, replacing the old Show Advanced toggle in the Controls section. When a search match is hidden by it, OmniWM reports how many are hidden and offers a Show Advanced Commands button.
      • The Command Palette hotkey advisory now checks whether the matching macOS symbolic shortcut is actually enabled, and re-evaluates whenever OmniWM becomes active again — including on return from System Settings.

      CLI and Automation

      • Opaque window IDs now round-trip custom session tokens containing colons or complex Unicode. #567
      • Window titles and app names can no longer inject rows or columns into table and TSV output. #568
      • Emoji sequences, combining marks, and wide characters now align correctly in terminal tables without truncating Unicode text.

      Diagnostics, Launch, and Documentation

      • Bug-report captures now include ordered app-visibility traces plus native-fullscreen lifecycle, projection, geometry, panel, and capture-exclusion evidence.
      • The launch permissions screen explains each permission and refreshes after returning from System Settings. OmniWM shows a temporary Dock icon while that screen is open, then returns to its menu-bar-only role.
      • Input Monitoring status is now read through IOKit HID rather than CoreGraphics, so Settings → Hotkeys and the launch gate use the same HID-level permission check.
      • The launch overlay has been rebuilt around a synchronized wordmark and tagline sequence, replacing the previous Dwindle tile-build animation. The full sequence now runs 3.6 seconds, up from 2.6.
      • The README Requirements and Quick Start sections were rewritten for the new permission model — start there if you are upgrading.
      • The Nix documentation now links ryoppippi's real-world Home Manager configuration alongside the existing community packages.

      Thanks

      • Brian Smyth (@bps) — the macOS-hidden app focus and layout foundation in #566.
      • Aisling (@aislingheart) — the Menu Anywhere submenu and item-state fixes in #571.
      • Yuri Chukhlib (@YuriNachos) — delimiter-safe opaque window IDs and control-safe CLI rendering in #567 and #568.

      Aisling and Brian Smyth join the contributors section, and Earl Gresh and Carson Full join Omni Sponsors.

      Release Integrity

      The OmniWM app is Developer ID signed, Apple-notarized, stapled, and Gatekeeper verified.

      • OmniWM-v0.6.2.zip SHA-256: 232bf91debeea589465bf1230b9afc78f76edb383a9fad36f1d07d6f9ed4deb4
      • GhosttyKit.xcframework-v0.6.2.zip SHA-256: 38301d5540ec5d1e482b12fffbd0fe3c4d8ee56eee7bb0b737d13e9a86873972
    7. 🔗 tintinweb/pi-subagents v0.16.0 release

      image

    8. 🔗 r/LocalLLaMA Qwen3.8-27B is identical to Qwen3.6-27B! rss

      Qwen3.8-27B is identical to Qwen3.6-27B! | Interestingly, the 3.8 version has exactly the same architecture - meaning all the capability gains come from training improvements! See the diff (0 changes) here! https://hfviewer.com/compare/qwen3.6-27b-vs-qwen3.8-27b submitted by /u/Course_Latter
      [link] [comments]
      ---|---

    9. 🔗 r/LocalLLaMA Qwen 3.8 27B Released! Please Share Your Experience rss

      With your experiments, Qwen 3.8 27B most close which frontier model? And please specify which quantization you run. I will post to comments my tests and experience too.

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

    10. 🔗 r/LocalLLaMA Qwen/Qwen3.8-27B · released rss

      Qwen/Qwen3.8-27B · released | submitted by /u/de4dee
      [link] [comments]
      ---|---

    11. 🔗 r/LocalLLaMA IT'S OUT rss

      IT'S OUT | submitted by /u/Certain-Cod-1404
      [link] [comments]
      ---|---

    12. 🔗 HexRaysSA/plugin-repository commits sync repo: +1 plugin, +9 releases rss 
      sync repo: +1 plugin, +9 releases

## New plugins
- [eject_idb](https://github.com/allthingsida/eject_idb) (0.0.3)

## New releases
- [IDA-MCP](https://github.com/captain-ai-hub/ida-mcp): 0.8.0, 0.7.1, 0.7.0
- [QScripts](https://github.com/allthingsida/qscripts): 1.2.8
- [SigMaker](https://github.com/mahmoudimus/ida-sigmaker): 1.14.3
- [ida-codemode](https://github.com/hexrayssa/ida-codemode): 0.6.1, 0.6.0, 0.5.3
    13. 🔗 tintinweb/pi-subagents v0.15.2 release

      No content.

    14. 🔗 earendil-works/pi v0.84.2 release

      New Features

      • Fullscreen transcript search — Search and navigate matches in fullscreen mode. See TUI Fullscreen Viewport.
      • Configurable default tools — Choose startup built-in tools globally or per project. See Tools.
      • Configurable fullscreen exit output — Print the transcript or only a resume hint on exit. See Interactive Mode.

      Added

      • Added fullscreen transcript search with Ctrl+Shift+F, incremental match highlighting, configurable search match theme colors, and next/previous navigation with Enter/Ctrl+G and Shift+Enter/Ctrl+Shift+G.
      • Added experimental strict JSON-schema constrained sampling for the default read, bash, edit, and write tools under PI_EXPERIMENTAL=1.
      • Added a fullscreen exit output setting to choose between printing the final transcript and only a session resume hint.
      • Added the defaultTools setting for configuring the initial built-in tool selection globally or per project.
      • Added --use-theme <name[/name]> to choose an initial per-run interactive theme without changing saved settings (#7722 by @rwachtler).
      • Added expandPromptTemplates to extension pi.sendUserMessage() options for explicitly dispatching commands and expanding skills and prompt templates. See pi.sendUserMessage() (#7857 by @mrexodia).
      • Added inherited createGatewayBindingFetch() for routing Cloudflare AI Gateway requests through a Workers AI binding without an API token (#7901 by @Maximo-Guk).
      • Added inherited AssistantMessage.endTurn to preserve OpenAI Codex's terminal end_turn signal for diagnostics (#7766).
      • Added inherited unbound single-line transcript scrolling actions for fullscreen mode. See TUI Fullscreen Viewport (#7903 by @midastruth).

      Changed

      • Changed inherited Kimi Coding requests to use pi's runtime User-Agent header.
      • Replaced the inherited Mistral SDK transport with a native Chat Completions HTTP stream, eliminating its generated client and schema runtime overhead.
      • Documented the generic AI_AGENT=pi process marker and how it differs from PI_CODING_AGENT=true (#7747).
      • Changed inherited OpenAI Responses deferred tool loading to prefer message-anchored additional_tools where supported while retaining tool-search and top-level fallbacks (#7709).
      • Reduced inherited fullscreen rendering allocation churn by painting full-width layout rows directly instead of recompositing them on every frame.

      Fixed

      • Fixed managed-tool downloads delaying TUI startup and hiding diagnostics in fullscreen mode by mounting the TUI first and showing download progress and warnings inside it.
      • Fixed opening a model selector immediately after startup cancelling and restarting the in-progress model catalog refresh.
      • Fixed inherited GitHub Copilot login triggering API rate limits while enabling model policies by limiting concurrent policy updates (#6187).
      • Fixed fullscreen transcript search snapping back to the current match during manual scrolling and fragmented mouse input leaking into the search query.
      • Fixed inherited required LaTeX arguments starting on a new line being parsed as empty (#7760).
      • Updated the transitive nanoid development dependency to address a denial-of-service vulnerability.
      • Fixed fallback rendering for extension tool results to collapse long output and honor tool expansion (#7979).
      • Fixed JSON and RPC message_update events dropping cumulative usage during streaming. See JSON Event Mode and RPC message_update (#7982 by @christianklotz).
      • Fixed pi.sendMessage(..., { triggerTurn: false }) steering an active run instead of only recording the custom message (#8022 by @cristinaponcela).
      • Fixed the defaultTools setting dropping extension and SDK custom tools when selecting built-in defaults.
      • Fixed the subagent example rejecting YAML array syntax for the tools frontmatter field (#7598 by @alexsavio).
      • Fixed the subagent example dropping parent session model, thinking, and tool configuration (#7897 by @virtuald).
      • Fixed custom system prompts concatenating the current working directory with later appended prompt content (#7887 by @distributedlock).
      • Fixed inherited OpenAI Responses function and custom tool calls losing namespaces during streaming, proxying, and replay (#7709).
      • Fixed inherited upstream request buffer failures not triggering automatic assistant retries.
      • Fixed inherited built-in and custom DeepSeek API models sending output limits through an unsupported field.
      • Fixed inherited Amazon Bedrock replay rejecting tool arguments that contain empty object keys while preserving all valid nested values (#7882 by @muyiyr).
      • Fixed inherited DeepSeek compatibility detection for base URLs whose hostname contains uppercase letters (#7933 by @yearth).
      • Fixed inherited Google Generative AI and Vertex AI responses with tool calls incorrectly treating output-limit or provider-error stops as normal tool use (#8059).
      • Fixed inherited fullscreen mouse drag selection and OSC 8 link activation in terminals that report generic SGR mouse release button codes (#7963).
      • Fixed inherited focused fullscreen overlays not receiving mouse wheel or viewport scroll keys such as PageUp and PageDown (#7894).
      • Fixed inherited LaTeX control spaces split across line endings causing complete expressions to fall back to raw source.
      • Fixed split Alt+Enter input over SSH being misread as Escape, added PI_TUI_ESC_TIMEOUT for high-latency terminals, and limited that timeout to lone Escape input (#7899 by @powerfooI).
      • Fixed inherited idle fullscreen sessions repainting and clearing text selection when the terminal loses focus (#7892 by @terrorobe).
      • Fixed fullscreen selection copy to use the host clipboard and report failure instead of claiming success when OSC 52 is unsupported (#8110 by @Panoplos).
    15. 🔗 r/LocalLLaMA A preliminary Qwen3.8-27B model card is live! rss

      A preliminary Qwen3.8-27B model card is live! | If you scroll down from the countdown at https://huggingface.co/Qwen/Qwen3.8-27B, you see a big model card with a bunch of sections: Highlights, Model Overview, Quickstart, Best Practices, Citation, etc! No benchmarks on this yet as far as I can tell. We'll still need to wait another 5.5 hours for those I reckon. Edit: Ladies and gentlemen, the model is live. Let the testing begin! submitted by /u/-Cubie-
      [link] [comments]
      ---|---

    16. 🔗 r/LocalLLaMA GLM 5.3 Released rss

      GLM 5.3 Released | Official Announcement https://z.ai/blog/glm-5.3 submitted by /u/jmorant555
      [link] [comments]
      ---|---

    17. 🔗 matklad Printing Lists rss

      Printing Lists

      Aug 14, 2026

      To print a comma-separated list, a concise idiom is to optionally print the comma first, before the element:

      for (items, 0..) |item, item_index| {
    if (item_index > 0) std.debug.print(", ");
    std.debug.print("{}", .{item});
}
    18. 🔗 New Music Releases Above & Beyond - When You Believe rss

      Above & Beyond - a new release is available:

      • 2026-08-14: When You Believe (Single)

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

      Visit muspy for more information.

    19. 🔗 New Music Releases Armin van Buuren - Burn It Up rss

      Armin van Buuren - a new release is available:

      • 2026-08-14: Burn It Up (Single)

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

      Visit muspy for more information.

    20. 🔗 New Music Releases Saliva - Breaking Through rss

      Saliva - a new release is available:

      • 2026-08-14: Breaking Through (Album)

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

      Visit muspy for more information.

    21. 🔗 New Music Releases Ferry Corsten - Bring Me Back to Life rss

      Ferry Corsten - a new release is available:

      • 2026-08-14: Bring Me Back to Life (Single)

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

      Visit muspy for more information.

    22. 🔗 New Music Releases Unprocessed - Lost Tapes rss

      Unprocessed - a new release is available:

      • 2026-08-14: Lost Tapes (EP)

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

      Visit muspy for more information.

  4. August 13, 2026
    1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-08-13 rss

      IDA Plugin Updates on 2026-08-13

      New Releases:

      Activity:

      • binsync
        • 6befb4f1: Remove unused imports from util_panel.py (#532)
      • capa
        • 894d2d0d: Sync capa-testfiles submodule
        • eceae7da: test(freeze): cover dynamic null descriptions
        • 09871f4b: freeze: omit null description fields from freeze JSON
        • 1e676729: Sync capa-testfiles submodule
      • grokathon
      • haruspex
      • heretek-claude-harness
        • 27ef0952: fix: line endings
        • 2250c790: feat: consolidate RE-AI and heretek-skills into unified Claude Code P…
        • ae57d581: refactor: remove heretek-swarm from heretek-claude-harness to keep it…
        • 73e2b3fd: feat: consolidate agent harness components (#244)
        • 056b7d46: fix(script): sync terminal_bench_ab.sh
        • a7d1db07: ci: replace custom script steps with published Heretek-AI/harness-aud…
        • dce3debf: feat: add 4-pillar readiness scorecard calculation & badge generator
        • 94decd04: feat: integrate Harbor TerminalBench 2.0 A/B evaluation suite, herete…
        • 822608d2: ci: add publish-npm.yml workflow for automatic npm releases
        • e112bca1: feat: publish @heretek-ai/heretek@1.0.0 to npm registry
        • d6951fdb: docs: total documentation pass across CLAUDE.md, AGENTS.md, README.md…
        • 73ca057a: feat: add ruby, elixir, csharp language packs and heretek init auto-d…
        • 00b62d61: feat: add heretek status scorecard TUI and heretek metrics latency be…
        • 85426867: feat: add npm package launcher and GitHub Pages marketplace publishin…
        • 111de22e: feat: add heretek init auto-detector and python, rust, typescript lan…
        • 117d9df8: feat: add frontend-design, web-design-guidelines, grilling skills and…
        • e853047f: feat: add fallow plugin and agentic-readiness audit skill
      • ida-codemode
        • 10317b7c: Properly wait for database to be closed on the last lease
        • 439289f5: 0.6.1
        • 9c91f80f: Add ida-codemode reference CLI command and improve docs
        • 1bf94167: 0.6.0
        • 47c3bc1b: Create single ida-codemode CLI entry point with subcommands
        • 0ef1aca0: 0.5.3
        • 6ec7fb28: Add ida-codemode-exec python repl
        • 258eba42: Refactor public API surface
        • 0825f8e4: Deduplicate MCP setup instructions
        • 6298194d: Merge pull request #24 from HexRaysSA/api-changes
      • ida-pro-mcp
        • c97ca717: fix(ci): clear ruff failures from explicit _common imports
        • 5cfe1051: fix(agent): keep public ida_* names on the wire and pass the live IDA…
      • ida-sigmaker
        • bf31d68c: chore: release v1.14.3
        • 61b6cae7: ci: build Windows ARM64 wheels in the deploy matrix
      • plugin-ida
        • ef2a86b4: chore(deps-dev): Update types-setuptools requirement (#24)
        • 6bf3c094: chore(deps): Bump actions/setup-python from 6.2.0 to 7.0.0 (#23)
        • c8f7009c: chore(deps): Bump actions/checkout from 7.0.0 to 7.0.1 (#22)
        • 5f559f3c: chore(deps): Bump actions/attest-build-provenance from 4.1.0 to 4.2.2…
        • 5cf8af53: chore(deps): Bump step-security/harden-runner from 2.19.4 to 2.20.1 (…
      • rhabdomancer
    2. 🔗 backnotprop/plannotator v0.27.3 release

      Follow @plannotator on X for updates

      Missed recent releases? Release | Highlights
      ---|---
      v0.27.2 | Mobile plan and code review, Codex CLI 0.147 fix, folder annotate cold-start, configurable markdown extensions
      v0.27.1 | Open-in-editor launch fix, file headers respect Viewed/Git-add visibility toggles
      v0.27.0 | Call Flow analysis, --tailscale remote reviews, review panel remembers your view, Pi rebuild (breaking command rename), focus-mode shortcut
      v0.26.8 | Placed comment markers on HTML pages, shift-click multi-select, live app annotation
      v0.26.7 | Pinpoint targets any element on HTML pages, smarter hover labels, zero-scan hit testing
      v0.26.6 | Fixed empty environment variables in sandboxed sessions (Bun 1.3.14 builds)
      v0.26.5 | HTML pinpoint element annotations, durable annotate submissions, installer fallback for old git, vim HUD cursor fix
      v0.26.4 | Skill-menu hover jitter fix (same-day patch on v0.26.3)
      v0.26.3 | Skill references in comments with / or $, reachable remote session URLs, worktree switcher tooltips
      v0.26.2 | Single-file diff tabs render fully, no more silently dropped review files, light/dark theme pairs, palette-matched code blocks
      v0.26.1 | GitButler 0.22.0 compatibility via capability-probed JSON flags
      v0.26.0 | Edit Mode (suggest by editing the diff), Guided Review virtualization, colorblind theme, safe uninstall, installer opt-outs, OpenCode 2 support

      What's New in v0.27.3

      One fix on top of v0.27.2. If you are coming from an earlier version, the full v0.27.2 notes follow below; v0.27.3 is that release plus:

      Folder annotate no longer freezes the session on large repos

      Community-reported within hours of v0.27.2: opening a folder annotate session on a repo with hundreds of directories could freeze the entire local server while the file-tree watcher ran its initial scan, and a browser reconnect rebuilt the watcher from scratch, so on big repos the freeze fed itself and file switching appeared permanently dead. The bug predates v0.27.2 by six releases; the reporter's repo was simply large enough to make it unbearable.

      Three changes close the whole class: the watcher now warms up off the request path, so the session answers immediately while the scan runs behind it; disconnects reuse the warm watcher for 30 seconds instead of rescanning, which breaks the freeze loop; and macOS and Windows now use the operating system's native recursive watcher, measured at about 3ms to start versus 9 seconds for the previous scan on a 228-directory repo. The regression test pins it: a nested 780-directory tree that blocked the server for 79 seconds before now answers in under one second, and that test runs in CI so this cannot quietly return.

      Reported by @abanoub-ashraf in #1313.

      This is also the first release whose pipeline publishes a CycloneDX SBOM and attests it alongside the existing build provenance.

      What's New in v0.27.2

      Plannotator now works on your phone. This release ships a full mobile experience for plan review, code review, and annotation, alongside a security hardening pass, a fix for Codex review jobs on current Codex CLI versions, a large folder-mode performance win, and configurable markdown extensions. Fourteen PRs, including a community fix from @leoreisdias and a community-requested feature from @sgiath.

      Plan and code review on phones and tablets

      Review a plan from your couch. Approve a diff from the train. Plannotator's plan review, code review, and annotate surfaces now adapt to phones and tablets with a compact touch experience: full-width reading layouts, a full- screen navigator for files and contents, touch-safe comment composition that stays clear of the software keyboard, 44px touch targets, and safe-area-aware layouts that respect notches and home indicators. On iPhone Safari, plans use the browser's natural document scroll so the address bar collapses as you read.

      Desktop behavior is unchanged. The compact experience activates only on coarse-pointer devices at tablet widths and below, so a narrow desktop window keeps the workspace you know. Pair it with v0.27.0's --tailscale flag or remote mode and your phone becomes a first-class review device: start a review on your workstation, scan the QR code, and annotate from anywhere on your tailnet.

      This shipped as a five-part stack: viewport and safe-area foundation, keyboard-safe comment composition, touch and dialog primitives, the code review shell, and the plan shell.

      Codex review jobs work again on current Codex CLIs

      Codex CLI 0.147.0 removed the --full-auto flag, which broke every Plannotator Codex review, Guided Review, and Code Tour job at launch with an argument error. Plannotator now passes --approve-for-me, the flag Codex introduced as its replacement, across all three job builders.

      Note the floor this implies: Codex review jobs now require codex-cli 0.147.0 or newer. Older Codex CLIs do not recognize the new flag. Thanks to @tgenov for independently reporting the breakage and pushing on a read-only sandbox for review jobs, an idea now tracked in #1310.

      Folder annotate opens in milliseconds on large repos

      Opening a folder annotate session initialized a file watcher across the entire .git/refs tree to keep git status live in the file browser. On repos with hundreds of branches and tags that took 9 to 23 seconds before the first file selection was responsive. The watcher now targets the five specific git files that drive status display (HEAD, index, the reflog, packed-refs, and the current branch ref), bringing cold start to about 30ms on the same repos with the same live status behavior.

      Annotate any markdown-like file with configurable extensions

      Livebook notebooks, Quarto documents, and other markdown-dialect files were rejected by annotate because the accepted extensions were hardcoded. A new config-only setting registers extra extensions to treat as markdown:

      { "markdownExtensions": [".livemd"] }

      in ~/.plannotator/config.json. Listed extensions are accepted everywhere annotate accepts .md: the CLI, the folder file browser, linked-doc and wiki- link navigation, frontmatter stripping, and version history. Entries are validated hard, and dotenv-family extensions can never be registered since annotate history copies file contents. Requested by @sgiath in #1307.

      Security hardening across the supply chain

      Four security-focused changes landed in this cycle:

      • Pi 0.79+ required. The Pi extension now requires Pi 0.79.1 or newer and refuses older hosts with a clear message instead of running with weaker project-trust behavior. If you are on an older Pi, update Pi first. #1291
      • Continuous scanning. Semgrep CE and Trivy now run on every PR and weekly in monitor mode, with fail-closed scanner health checks and pinned, checksum-verified tooling. #1294
      • Weekly DAST. An isolated OWASP ZAP passive scan runs weekly against a disposable annotate session on an internal-only network with no credentials and blocked egress. #1299
      • Marketing site on Astro 7. plannotator.ai moved from Astro 5 to 7.1.6, clearing eight dependency advisories. #1293

      Additional Changes

      • New reviewers start in Tree view. First-time code review users now land on the file tree instead of the Git status panel. Returning users keep whatever view they had. #1292
      • Quieter first run. The plan-AI, vim-mode, and analysis-layers announcement dialogs are gone, and automatic AI provider selection no longer persists anything until you explicitly choose a provider. Fewer interruptions before your first review. #1295

      Install / Update

      macOS / Linux:

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

      Windows:

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

      Claude Code Plugin: Run /plugin in Claude Code, find plannotator , and click "Update now".

      OpenCode: Clear cache and restart:

      rm -rf ~/.bun/install/cache/@plannotator

      What's Changed

      Community

      This release carries a lot of community fingerprints:

      • @leoreisdias fixed the Codex CLI breakage in #1231, restoring Codex review jobs for everyone on current Codex versions.
      • @tgenov independently diagnosed the same Codex breakage in #1302 and proposed running review jobs read-only, now tracked in #1310.
      • @sgiath requested configurable markdown extensions for Livebook notebooks in #1307, with a workaround-quality write-up that traced both allowlists involved.
      • @edision reported that Pi's thinking: "max" level is silently ignored in #1304, queued for an upcoming patch.
      • @MartinNeudecker proposed direct edits alongside suggestions in code review in #1308, and followed up with workflow details that are shaping the design.
      • @ashish921998 picked up the skill-menu screen reader accessibility issue in #1233.

      Full Changelog : v0.27.2...v0.27.3

    3. 🔗 tintinweb/pi-subagents v0.15.1 release

      No content.

    4. 🔗 r/LocalLLaMA Trained a 1.5B to write shell commands so I'd stop googling tar flags. Runs on a laptop CPU in ~1 sec. rss

      Trained a 1.5B to write shell commands so I'd stop googling tar flags. Runs on a laptop CPU in ~1 sec. | I've been googling "tar extract gz" for about ten years. and I finally did something about it. It started out as a research project and I ended up with a Fine-tuned Qwen2.5-Coder-1.5B on 125k natural-language/command pairs, merged and quantized to Q4_K_M. 941MB which runs through llama.cpp. On my laptop (i5-11320H, 4 threads): 31.9 tok/s, 0.59s median per query, 1.6GB RAM. I benchmarked it and it scores 0.620 on InterCode-ALFA. Untuned Qwen2.5-Coder-7B gets 0.613, GPT-4o gets 0.73. Not frontier, but it's roughly a 7B's answer at a quarter the parameters on a CPU. Theres a 3B variant too that scores higher. There's also few static safety checker, because it will absolutely write a command that wipes your root if you ask it to: I have published the weights: huggingface.co/ThorOdinson246/nl2sh-1.5b-Q4_K_M and Code: github.com/ThorOdinson246/whatisit-nl2sh . I posted few days ago in LocalLLM and it did well 300+ stars and so many good suggestions so I figured people here will be interested too. Both Apache-2.0. If you want to poke holes in the method or you've got ideas, please comment or open a PR. A ⭐ helps if you find it useful. submitted by /u/PicassoOnPause
      [link] [comments]
      ---|---

    5. 🔗 backnotprop/plannotator v0.27.2 release

      Follow @plannotator on X for updates

      Missed recent releases? Release | Highlights
      ---|---
      v0.27.1 | Open-in-editor launch fix, file headers respect Viewed/Git-add visibility toggles
      v0.27.0 | Call Flow analysis, --tailscale remote reviews, review panel remembers your view, Pi rebuild (breaking command rename), focus-mode shortcut
      v0.26.8 | Placed comment markers on HTML pages, shift-click multi-select, live app annotation
      v0.26.7 | Pinpoint targets any element on HTML pages, smarter hover labels, zero-scan hit testing
      v0.26.6 | Fixed empty environment variables in sandboxed sessions (Bun 1.3.14 builds)
      v0.26.5 | HTML pinpoint element annotations, durable annotate submissions, installer fallback for old git, vim HUD cursor fix
      v0.26.4 | Skill-menu hover jitter fix (same-day patch on v0.26.3)
      v0.26.3 | Skill references in comments with / or $, reachable remote session URLs, worktree switcher tooltips
      v0.26.2 | Single-file diff tabs render fully, no more silently dropped review files, light/dark theme pairs, palette-matched code blocks
      v0.26.1 | GitButler 0.22.0 compatibility via capability-probed JSON flags
      v0.26.0 | Edit Mode (suggest by editing the diff), Guided Review virtualization, colorblind theme, safe uninstall, installer opt-outs, OpenCode 2 support
      v0.25.1 | Codex no longer launches on review open, annotate-last follows the live conversation, pi-todos mirror, Claude Opus 5, abandoned-gate dismissal

      What's New in v0.27.2

      Plannotator now works on your phone. This release ships a full mobile experience for plan review, code review, and annotation, alongside a security hardening pass, a fix for Codex review jobs on current Codex CLI versions, a large folder-mode performance win, and configurable markdown extensions. Fourteen PRs, including a community fix from @leoreisdias and a community-requested feature from @sgiath.

      Plan and code review on phones and tablets

      Review a plan from your couch. Approve a diff from the train. Plannotator's plan review, code review, and annotate surfaces now adapt to phones and tablets with a compact touch experience: full-width reading layouts, a full- screen navigator for files and contents, touch-safe comment composition that stays clear of the software keyboard, 44px touch targets, and safe-area-aware layouts that respect notches and home indicators. On iPhone Safari, plans use the browser's natural document scroll so the address bar collapses as you read.

      Desktop behavior is unchanged. The compact experience activates only on coarse-pointer devices at tablet widths and below, so a narrow desktop window keeps the workspace you know. Pair it with v0.27.0's --tailscale flag or remote mode and your phone becomes a first-class review device: start a review on your workstation, scan the QR code, and annotate from anywhere on your tailnet.

      This shipped as a five-part stack: viewport and safe-area foundation, keyboard-safe comment composition, touch and dialog primitives, the code review shell, and the plan shell.

      Codex review jobs work again on current Codex CLIs

      Codex CLI 0.147.0 removed the --full-auto flag, which broke every Plannotator Codex review, Guided Review, and Code Tour job at launch with an argument error. Plannotator now passes --approve-for-me, the flag Codex introduced as its replacement, across all three job builders.

      Note the floor this implies: Codex review jobs now require codex-cli 0.147.0 or newer. Older Codex CLIs do not recognize the new flag. Thanks to @tgenov for independently reporting the breakage and pushing on a read-only sandbox for review jobs, an idea now tracked in #1310.

      Folder annotate opens in milliseconds on large repos

      Opening a folder annotate session initialized a file watcher across the entire .git/refs tree to keep git status live in the file browser. On repos with hundreds of branches and tags that took 9 to 23 seconds before the first file selection was responsive. The watcher now targets the five specific git files that drive status display (HEAD, index, the reflog, packed-refs, and the current branch ref), bringing cold start to about 30ms on the same repos with the same live status behavior.

      Annotate any markdown-like file with configurable extensions

      Livebook notebooks, Quarto documents, and other markdown-dialect files were rejected by annotate because the accepted extensions were hardcoded. A new config-only setting registers extra extensions to treat as markdown:

      { "markdownExtensions": [".livemd"] }

      in ~/.plannotator/config.json. Listed extensions are accepted everywhere annotate accepts .md: the CLI, the folder file browser, linked-doc and wiki- link navigation, frontmatter stripping, and version history. Entries are validated hard, and dotenv-family extensions can never be registered since annotate history copies file contents. Requested by @sgiath in #1307.

      Security hardening across the supply chain

      Four security-focused changes landed in this cycle:

      • Pi 0.79+ required. The Pi extension now requires Pi 0.79.1 or newer and refuses older hosts with a clear message instead of running with weaker project-trust behavior. If you are on an older Pi, update Pi first. #1291
      • Continuous scanning. Semgrep CE and Trivy now run on every PR and weekly in monitor mode, with fail-closed scanner health checks and pinned, checksum-verified tooling. #1294
      • Weekly DAST. An isolated OWASP ZAP passive scan runs weekly against a disposable annotate session on an internal-only network with no credentials and blocked egress. #1299
      • Marketing site on Astro 7. plannotator.ai moved from Astro 5 to 7.1.6, clearing eight dependency advisories. #1293

      Additional Changes

      • New reviewers start in Tree view. First-time code review users now land on the file tree instead of the Git status panel. Returning users keep whatever view they had. #1292
      • Quieter first run. The plan-AI, vim-mode, and analysis-layers announcement dialogs are gone, and automatic AI provider selection no longer persists anything until you explicitly choose a provider. Fewer interruptions before your first review. #1295

      Install / Update

      macOS / Linux:

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

      Windows:

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

      Claude Code Plugin: Run /plugin in Claude Code, find plannotator , and click "Update now".

      OpenCode: Clear cache and restart:

      rm -rf ~/.bun/install/cache/@plannotator

      What's Changed

      Community

      This release carries a lot of community fingerprints:

      • @leoreisdias fixed the Codex CLI breakage in #1231, restoring Codex review jobs for everyone on current Codex versions.
      • @tgenov independently diagnosed the same Codex breakage in #1302 and proposed running review jobs read-only, now tracked in #1310.
      • @sgiath requested configurable markdown extensions for Livebook notebooks in #1307, with a workaround-quality write-up that traced both allowlists involved.
      • @edision reported that Pi's thinking: "max" level is silently ignored in #1304, queued for an upcoming patch.
      • @MartinNeudecker proposed direct edits alongside suggestions in code review in #1308, and followed up with workflow details that are shaping the design.
      • @ashish921998 picked up the skill-menu screen reader accessibility issue in #1233.

      Full Changelog : v0.27.1...v0.27.2

    6. 🔗 Jeremy Fielding (YouTube) Flexible Engineering at Open Sauce rss

      GMpartner Taking a quick look at making customized parts at scale with @GeneralMotors. #ad #GMxOpenSauce

      If you want to join my community of makers and Tinkers consider getting a YouTube membership 👉 https://www.youtube.com/@JeremyFieldingSr/join

      If you want to chip in a few bucks to support these projects and teaching videos, please visit my Patreon page or Buy Me a Coffee. 👉 https://www.patreon.com/jeremyfieldingsr 👉 https://www.buymeacoffee.com/jeremyfielding

      Social media, websites, and other channel

      Instagram https://www.instagram.com/jeremy_fielding/?hl=en Twitter 👉https://twitter.com/jeremy_fielding TikTok 👉https://www.tiktok.com/@jeremy_fielding0 LinkedIn 👉https://www.linkedin.com/in/jeremy-fielding-749b55250/ My websites 👉 https://www.jeremyfielding.com 👉https://www.fatherhoodengineered.com My other channel Fatherhood engineered channel 👉 https://www.youtube.com/channel/UC_jX1r7deAcCJ_fTtM9x8ZA

      Notes:

      Technical corrections

      Nothing yet

    7. 🔗 r/LocalLLaMA MiniMax-Music3 released! rss

      MiniMax-Music3 released! | submitted by /u/Acceptable-Cycle4645
      [link] [comments]
      ---|---

    8. 🔗 r/LocalLLaMA deepseek-ai/DeepSeek-V4-Pro-0813 · Hugging Face rss

      deepseek-ai/DeepSeek-V4-Pro-0813 · Hugging Face | submitted by /u/mossy_troll_84
      [link] [comments]
      ---|---

    9. 🔗 backnotprop/plannotator v0.27.1 release

      Follow @plannotator on X for updates

      Missed recent releases? Release | Highlights
      ---|---
      v0.27.0 | Call Flow analysis, --tailscale remote reviews, review panel remembers your view, Pi rebuild (breaking command rename), focus-mode shortcut
      v0.26.8 | Placed comment markers on HTML pages, shift-click multi-select, live app annotation
      v0.26.7 | Pinpoint targets any element on HTML pages, smarter hover labels, zero-scan hit testing
      v0.26.6 | Fixed empty environment variables in sandboxed sessions (Bun 1.3.14 builds)
      v0.26.5 | HTML pinpoint element annotations, durable annotate submissions, installer fallback for old git, vim HUD cursor fix
      v0.26.4 | Skill-menu hover jitter fix (same-day patch on v0.26.3)
      v0.26.3 | Skill references in comments with / or $, reachable remote session URLs, worktree switcher tooltips
      v0.26.2 | Single-file diff tabs render fully, no more silently dropped review files, light/dark theme pairs, palette-matched code blocks
      v0.26.1 | GitButler 0.22.0 compatibility via capability-probed JSON flags
      v0.26.0 | Edit Mode (suggest by editing the diff), Guided Review virtualization, colorblind theme, safe uninstall, installer opt-outs, OpenCode 2 support
      v0.25.1 | Codex no longer launches on review open, annotate-last follows the live conversation, pi-todos mirror, Claude Opus 5, abandoned-gate dismissal
      v0.25.0 | Vim keyboard controls, Approve with Notes, scriptable annotate gates, persistent Guided Reviews, memory and file-watching hardening

      What's New in v0.27.1

      Two fixes on top of v0.27.0. If you are coming from an earlier version, the full v0.27.0 notes follow below; v0.27.1 is that release plus:

      Open in editor no longer breaks after repeated sessions

      Community-reported: the open-in-editor button in code review could stop working after a few review cycles. Two defects were behind it. The launch call waited on the editor command with no time limit, so a lingering editor CLI left the button as a dead spinner. And the launched editor shared the review session's process group, so an editor cold-started from the button could be killed along with the session, which can strand the editor's own single- instance state and make every later open a silent no-op. Editor launches are now fully detached into their own process group and the wait is bounded: instant failures still show the friendly error, and a healthy launch can never hang the button or die with the session.

      File headers respect the Viewed and Git-add visibility toggles

      v0.27.0 added toggles to hide the Viewed and stage controls in the file tree, but the same controls still appeared in every file header in the diff. Toggling a control off now hides it everywhere: tree, sections, file headers, and guide file cards. Viewed state and the V/A keyboard shortcuts are unaffected.

      What's New in v0.27.0

      This is the largest release since v0.25.0: Call Flow analysis for code review, a first-class Tailscale story for reviewing from another device, a rework of the review panel around how people actually switch views, and a rebuilt Pi integration. Fourteen PRs landed. Every feature went through independent review, and the release as a whole passed two full QA sweeps (a 28-item verification workflow plus live journey, seam, and free-roam testing) before tagging.

      Important

      Breaking change for Pi users: the Pi plan-mode command is renamed /plannotator → /plannotator-plan-mode. The old command no longer does anything. Update any saved workflows or muscle memory. See the Pi section below for why.

      Call Flow: see the call paths your diff changes

      Code review gets a third analysis layer alongside semantic diff: Call Flow , powered by CallDiff (AST-based, built with Tree-sitter, 22 languages supported). Enable it and the review computes, for the changeset on screen, every call path that gained or lost a call: trees rooted at your entry points, walking down to the exact functions the diff touched. A tax calculation moving from before a discount to after it shows up as a removed call and an added call in the same tree, rendered across every route that reaches it. A text diff cannot show you that.

      Enabling Call flow is consent for a small managed runtime install (about 5 MB: a pruned CallDiff core plus only the language packs your changed files need). The install runs in the background while you review; missing languages install themselves later under the same consent, and a Languages list supports installing ahead. Nothing is downloaded unless you opt in, the app works fully without it, and a failed install degrades to a clear retry, never a broken review.

      The path view organizes into collapsible entry sections with changed-path defaults and file boundaries. Every Call Flow row is commentable: click a row to start a comment, shift-click to collect multiple steps into one annotation. Comments on rows inside the visible diff anchor inline; rows outside it become file- or review-scoped feedback with the full call context preserved for your agent. A searchable raw view with a color-classified rendering is there when you want the unprocessed output, and Cmd+F inside the panel searches the analysis rather than the file tree.

      Review from your iPad: --tailscale mode, tailnet auto-detection, and a QR

      code

      Two community threads asked the same question from different directions: can I run the agent on my Mac and do the review from an iPad, and can I get a diff out of a VPS without SSH port-mapping gymnastics. @nikuscs went as far as building a proof-of- concept wrapper script. As of this release the answer is built in:

      plannotator review --tailscale

      The server stays bound to localhost. Plannotator runs tailscale serve in front of it, prints an HTTPS URL that works on every device in your tailnet, and renders a QR code in the terminal so a phone or tablet joins by pointing a camera at it. The serve mapping is cleaned up when the session ends, an existing mapping on the port is never stolen, and if Tailscale is not installed the command fails fast with an actionable message. annotate and annotate-last support the same flag.

      For classic remote mode, PLANNOTATOR_URL_HOST=auto now resolves your machine's MagicDNS name (or tailnet IP) automatically, so multi-VPS setups no longer configure a hostname per machine. Remote-ready output includes the same QR code.

      Security posture, spelled out: nothing binds beyond localhost under --tailscale, the URL is reachable only inside your own tailnet, public exposure (funnel, ngrok-style tunnels) is deliberately not supported, and the annotate agent terminal stays off for tailnet-published sessions unless you set the existing PLANNOTATOR_AGENT_TERMINAL_REMOTE=1 opt-in. The feature went through an independent security review plus an external reviewer's pass, and the follow-up hardening from both is included: startup failures exit immediately instead of hanging, serve mappings are retried on teardown and never leak silently, foreground serve configs are detected as conflicts, and nohup sessions survive terminal close exactly as they did before.

      The review panel remembers how you work

      If you review in the Tree view, every new session used to open on Git status anyway, and getting back meant one more click every single time. The panel now records the view you last used (Tree or Git status) and opens there. The toggle itself gets the full top row with Tree first, the search and collapse controls moved down next to the file tree, and the footer's copy button gave way to a copy-all control in the sidebar. An explicit choice in Settings still wins over the memo.

      The Commits rail also stops trapping you: clicking a commit used to permanently replace your working diff, with no way back short of restarting the session. Commits is now a self-contained detour. Entering it remembers what you were reviewing; returning to Tree restores that exact diff, and reloading mid-detour lands you back on your session default instead of stuck on a historical commit.

      Two smaller traps closed with the same work: the first-run setup dialog no longer re-runs its one-time reset if you closed the tab without dismissing it, and the fallback view toggle now reflects what is actually on screen.

      Pi integration rebuilt: no more prompt-cache busting

      The Pi extension no longer touches Pi's system prompt at all. Previously it injected planning instructions there, which busted Pi's prompt cache on every phase change and dropped AGENTS.md content, as @paullegranddc reported in #922. Phase framing now travels as ordinary conversation messages, so caching works the way Pi expects and your project instructions survive.

      This rebuild is why the plan-mode command is renamed: /plannotator → /plannotator-plan-mode describes what the command actually does now, and there is no alias for the old name. If you type /plannotator today, nothing happens; use /plannotator-plan-mode.

      Focus mode from the keyboard

      @omardoescode asked for a keybind that clears both sidebars at once for keyboard-first annotation work, and it shipped the same day: Mod+. toggles focus mode in plan review and annotate. First press closes the Contents sidebar and the annotation panel, second press restores exactly what was open before. The binding was chosen after a full conflict audit across every surface and layout (it is also the same key code review already uses to collapse its sidebar), it never fires while you type, and the shortcuts help modal documents it in a new View section.

      Standing instructions for Guided Review

      Guided Review now accepts reviewer-supplied instructions, two ways: per-launch text appended to that guide's brief, and standing instructions stored once and applied to every guide whose launch carries none. Tell it "always lead with data-model changes" once and every future guide complies. Stored globally under your Plannotator data directory, editable from the guide launch surface.

      When a guide fails validation because it referenced files outside the changeset under review (for example, when instructions steer it toward a commit that is not on screen), the error now says exactly that, names the files, and tells you the fix: open that commit in the Commits panel first, then relaunch.

      Hardened release pipeline and security scanning

      The release and deployment pipeline was rebuilt around supply-chain hygiene: every CI action is pinned to a commit SHA, releases validate that the tag sits on main and matches all seven release-coupled version manifests before anything publishes, npm publishing moved to trusted publishing (OIDC) with no long-lived token in the workflow, package construction is separated from the privileged publish step, and deploys wait for the exact commit to pass the full test suite. Gitleaks and zizmor scanning now run on every push and PR with SARIF output into GitHub code scanning, and Dependabot keeps dependencies under watch.

      None of this changes the product, but if you consume Plannotator's binaries or npm packages, the artifacts you install are now attested end to end under a stricter pipeline.

      Additional Changes

      • Last-used view, Commits restore, and panel fixes are covered above; the same PRs also added a tooltip to the per-row stage button and equal-width panel toggle segments. #1273
      • Pi crash containment: a hard VCS failure during Call Flow analysis now returns a structured error instead of killing the Pi server process. #1272
      • Worktree diff-type guard: degenerate worktree: diff types with an empty path no longer fall back to the server's own directory. #1273
      • @plannotator/ui 0.30.0 for host applications: unanchored-annotation reporting via onUnanchoredChange, and readOnly mode keeps the host footer slot. #1263

      Install / Update

      macOS / Linux:

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

      Windows:

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

      Claude Code Plugin: Run /plugin in Claude Code, find plannotator , and click "Update now".

      OpenCode: Clear cache and restart:

      rm -rf ~/.bun/install/cache/@plannotator

      What's Changed

      • feat: reviewer-supplied extra instructions for Guided Review by @backnotprop in #1267
      • feat: add optional CallDiff call-flow analysis by @backnotprop in #1268
      • fix: never touch Pi's system prompt; phase framing as conversation messages by @backnotprop in #1269
      • feat: make the CallDiff runtime a strictly opt-in, in-UI install by @backnotprop in #1270
      • feat: install Call Flow automatically in the background on opt-in by @backnotprop in #1271
      • fix: contain /api/call-flow analysis throws as JSON error responses by @backnotprop in #1272
      • fix: remember the last-used panel view; full-width toggle and cleaner panel chrome by @backnotprop in #1273
      • ci: harden releases and add security scanning by @backnotprop in #1274
      • feat: refine Call Flow navigation and annotations by @backnotprop in #1277
      • fix: restore the prior diff when leaving the Commits view by @backnotprop in #1278
      • feat: focus-mode shortcut to toggle both sidebars by @backnotprop in #1279
      • feat: tailnet auto-advertise, ready QR code, and a first-class --tailscale mode by @backnotprop in #1280
      • fix: tailscale gate exit codes and lease gating, conditional SIGHUP, informative guide validation error by @backnotprop in #1286
      • feat(ui): onUnanchoredChange report + readOnly keeps the host footer slot by @backnotprop in #1263
      • fix: hide viewed and stage controls in file headers when toggled off by @backnotprop in #1288
      • fix: detach open-in-editor launches and bound the wait by @backnotprop in #1289

      Community

      This release was shaped by the community more than any recent one:

      • @nikuscs proposed Tailscale support and built a working proof-of-concept wrapper, then described the multi-VPS workflow that guided the design. --tailscale mode is that idea, productized.
      • @freak4pc and the iPad-review thread on X articulated the "review without touching the machine" use case that the QR code and auto-advertised URLs serve.
      • @omardoescode requested the focus-mode keybind (#1276), shipped in this release, and filed the font customization request (#1275) now on the roadmap.
      • @paullegranddc reported the Pi prompt-cache busting and AGENTS.md loss (#922) that drove the Pi rebuild.
      • An external reviewer's pass on the Tailscale PR caught three correctness issues before release; the fixes shipped in #1286.

      Full Changelog : v0.26.8...v0.27.1

    10. 🔗 Console.dev newsletter SolidStart 2 rss

      Description: JS framework for web apps.

      What we like: Framework built on Solid v1 for high performance, lightweight web applications. Built on Vite 8 with Rolldown, which brings modern tooling and deployment targets like Netlify, Cloudflare, and general Nitro web servers. Build-in support for auth & sessions, middleware, websockets, data mutation.

      What we dislike: Confusing documentation across Solid, Router, SolidStart, with varying versions v1 and v2.

    11. 🔗 Console.dev newsletter Amp rss

      Description: Agentic coding environment.

      What we like: Every chat thread can be a cloud VM with multiple repos checked out (or work locally using the CLI). Custom coding harness involves multiple adversarial models to check work as it works. Built-in authenticated preview URLs. Terminal access. Use your existing coding LLM subscription e.g. ChatGPT.

      What we dislike: Uses tokens quite quickly. No native desktop (or mobile) apps - all PWAs.

generated: August 16, 2026 at 18:11:17