🏡
  • ↔
  • →
  1. September 07, 2026
    1. 🔗 osolmaz/pi-workflows Pi Workflows 0.16.7 release

      Pi Workflows 0.16.7 fixes workflow handoffs and run recovery.

      • Normal chat no longer claims workflow-owned turns or blocks the first workflow delivery.
      • Delivery recovery now requires the exact recorded active turn and latest workflow input.
      • Delayed acknowledgments and automatic Pi retries preserve one durable delivery identity.
      • Resume now uses the recorded workflow definition and rejects changed source or graphs before mutation.
      • Workflow activity and viewer state now distinguish active origin turns from unconfirmed delivery.

      The SQLite schema remains version 1 and follows the existing alpha hard-cut policy.

    2. 🔗 BarutSRB/OmniWM OmniWM v0.6.8 release

      What's New Since 0.6.7

      OmniWM 0.6.8 moves Homebrew installs to the official cask, lets scripts and the CLI rename workspaces, makes switching between windows of the same app immediate again in Niri layouts, and fixes a crash on macOS 27 betas for users in comma-decimal regions.

      Before You Upgrade

      • Quit OmniWM before upgrading with Homebrew, then relaunch it. Homebrew replaces the app bundle underneath a running OmniWM, and a new omniwmctl talking to an older running OmniWM gets invalid_request for the new workspace rename action.
      • The project Homebrew tap is retired. OmniWM is in Homebrew's official cask repository, and 0.6.7 was the last release published to BarutSRB/tap.

      🚨🚨🚨

      If you installed with `brew tap BarutSRB/tap`, quit OmniWM and run, in this order:

1. `brew update` 
2. `brew upgrade omniwm` 
3. `brew untap BarutSRB/tap`.

      🚨🚨🚨

      Keep that order: brew update fetches the retired tap's redirect and moves your install to the official cask, while untapping before it would offer to uninstall OmniWM. Full steps: Migrating from the project tap. New installs use brew install --cask omniwm.

      • Settings and scripts are unaffected. This release needs no settings migration, and the IPC protocol stays at version 15.

      New: Rename Workspaces from Scripts and the CLI

      • omniwmctl workspace rename <workspace> <display-name> sets a workspace label from the command line or over IPC. The target is a raw workspace ID or an unambiguous display name, the label persists to settings.toml exactly as if you had set it in Settings, an empty name clears it back to the raw ID, and renaming to the current label returns no_change. #621
      • Rename from a launcher. A Raycast script command, or an OmniCast command with a picker, turns "type the new name, hit enter" into a rename straight from the root search, so a workspace can follow the project you are working on without a trip to Settings.
      • Let events rename for you. omniwmctl watch workspace-bar --reconnect --exec ./badge.sh runs a script for every workspace-bar event, so a workspace can badge itself 🚨 ALARM the moment a window on it gets a title containing a keyword and drop the badge when that window goes away. The events guide ships the full badge.sh; it renames only when the computed label differs, and OmniWM publishes workspace-bar only when the bar actually changed, so the loop settles instead of re-triggering itself.
      • Hand it to your agents. Because renaming is a plain IPC action, an automation agent can name workspaces after the windows you place on them, so the bar keeps describing what each workspace holds.
      • Renames neither trigger a layout pass nor drop runtime monitor overrides from move-to-monitor --force. The CLI reference documents the action and its wire shape.

      Fixes and Improvements

      • Switching between windows of the same app is immediate again in Niri layouts. Keyboard focus now moves to the target column right away instead of about 100 ms later, matching in-column navigation and Dwindle. #655
      • Settings, App Rules, and other OmniWM windows no longer crash on macOS 27 betas for users whose region uses a comma as the decimal separator (German, French, Portuguese, and others). The built-in terminal's startup had switched the process's numeric locale, which broke symbol rendering in those regions; the terminal's own shell locale is unchanged. #576

      Documentation

      Website and documentation · Installation guide

      Release Integrity

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

      • OmniWM-v0.6.8.zip SHA-256: 0823963c8a5c3bde854f7fdd03cd8c25c4421a40bd6f74844f2c8f7c16a26765
      • GhosttyKit.xcframework-v0.6.8.zip SHA-256: db543774b853ac0b051daa784ce8907a3101856ba3e5e65757da492b32d61e57
  2. September 06, 2026
    1. 🔗 osolmaz/pi-workflows Pi Workflows 0.16.6 release

      Pi Workflows 0.16.6 fixes workflow response routing and strengthens durable execution.

      • Agent submit and update operations now target the exact durable request.
      • Invalid or mismatched responses are rejected before any workflow state changes.
      • Controls now follow the actual pending response type instead of the broad waiting status.
      • Checkpoints complete in their original run instead of creating a continuation child.
      • Queue scheduling, response receipts, follow-ups, terminal capture, pause timing, and execution-revision recovery now use one checked durable execution path.

      This fixes the case where answer could be accepted for an agent step, create an invalid continuation, and leave the real agent request pending. The SQLite schema remains version 1 and follows the existing alpha hard-cut policy.

    2. 🔗 smol-machines/smolvm smolvm v1.14.1 release

      What's Changed

      • Bind-mount containerd state to /storage in the docker-in-vm example (#1159) by @BinSquare in #1160
      • chore(nix): bump flake to 1.14.0 by @BinSquare in #1161
      • Fetch and unpack image layers concurrently instead of one at a time by @BinSquare in #1162
      • Remove internal design notes from the user-facing docs by @BinSquare in #1163
      • Accept --init on machine run and keep what init writes to /workspace in the init-layer cache by @BinSquare in #1165
      • Resolve the agent rootfs the same way for pack create, checkpoints, serve and machine boot by @BinSquare in #1166
      • Propagate branchpoint arming into exec sessions by @BinSquare in #1167
      • Show full machine names in machine ls and add --quiet to list just names by @BinSquare in #1169
      • Carry the workload user through the embedded runtime so SDKs can set it by @BinSquare in #1171
      • Accept a user on the exec and run API so a caller can run a command as a chosen account by @BinSquare in #1172
      • Bump the workspace to 1.14.1 by @BinSquare in #1170

      Full Changelog : v1.14.0...v1.14.1

    3. 🔗 r/LocalLLaMA 8 uncensored Qwen 3.8 27B variants, one base, 167 GPU hours - Abliterlitics rss

      This comparison was requested by a few people, and certainly we were all eager to see the final results. The comparison had taken 11 days and the GPU was crunching numbers for ~167 hours.

      We've been comparing different abliterated models from huggingface to see if they really are what they claim to be. So far the results have been interesting.

      The pipeline includes a weight comparison, KL divergence measurement, 13 benchmarks and measuring refusals with the HarmBench 400 classic. Qwen 3.8 27b is a thinker, and with ourselves using xhigh we had to set our token budget much higher per request.

      Lets check out how Qwen 3.8 27b stacks up comparing 8 variants.

      The rankings

      LLM Judge HarmBench ASR (attack success rate), best to worst, with the one- line story:

      • orcarouter 82.2%, the winner. Arditi-style single direction at layer 38, 131 matrices, and the only card where every claim checked out against the weights. Best copyright unlock in the set at 39%
      • apostate 78.7%, best value. Their new KCRN method, 41 real edits, lowest KL measured at 0.0439, near-identity capabilities. Packaging quirks: text-only re-save with no vision and no MTP, stored FP16
      • huihui 75.6%, the classic method, reliable. Clean unlock everywhere except copyright, where it sits at 3%
      • ultra_heretic 70.5%, Heretic v2 with MPOA. Works, but the heaviest truthfulness drop outside obliteratus and 118 soft refusals
      • coder3101 70.0%, vanilla Heretic. The card calls itself the weakest removal at 33 of 100 refusals. Measured: 5 explicit refusals in 400. The card undersells it
      • blackfrost 68.5%, closed method. The weights say single direction, heaviest magnitude in the panel, 100% rank-1, which refutes the rank-k direction bank story. Also ships a jailbreak system prompt inside its chat template, meaning every single prompt you make will have a modified chat template injecting a jailbreak
      • obliteratus 63.9%, avoid. The most aggressive edit in the panel at 841 of 850 tensors, and it performs like it. 44.8% of responses never finish thinking, and it is the only variant that got meaningfully dumber
      • trohrbaugh 57.5%, last of the variants because it still refuses. 122 explicit refusals, the most surviving alignment of any variant, and the cleanest capability profile in the comparison. This is the one I use at home and it's been great for me.
      • base 4.5%, a wall. Zero compliance on chem and bio, harassment, harmful content and copyright

      The highlights

      • Surgical beats heavy, again, and this time it is not close. The top two spots went to the two smallest verified edits. The heaviest edit of all landed second-to-last. At 27B, editing everything mostly buys you a model that thinks in circles
      • The thinking loop story is the big new finding for this model. Qwen 3.8 thinks before answering, and on the aggressive arms up to 45% of HarmBench responses never close their think block before the 15,360-token budget dies. The judge reads the full trace, so compliance inside a loop still counts. But a model that only delivers the goods inside an unterminated monologue is not a usable model
      • GSM8K loops are gone at this budget. The same arms that loop 40%+ on HarmBench finish their math reasoning fine, every arm within 1.2pp of base on answered-only. School math converges, adversarial deliberation does not
      • Copyright is the new universal wall. Nobody exceeds 39%, five of nine sit at or below 3.2%. Chem and bio, historically the hardest category, is now the easiest unlock. The walls moved
      • Chat template forensics was needed for the first time. blackfrost ships a 1457-character jailbreak prompt inside its template. obliteratus ships thinking-off. ultra_heretic deletes the stock reasoning-effort prompt. We pinned the stock template for every arm, because the template is a stronger behavioural lever than most people assume
      • Card honesty check
        • orcarouter verified 4 of 4 claims exactly, the model card is honest.
        • trohrbaugh's KL calibrated within 9% of our measurement. However the card mentions 0/100 refusals, with our measurement this model had the most refusals, yet also had preserved capabilities.
        • The rest diverge, and none of it is dishonesty, KL is non-deterministic and moves with CUDA version and hardware, or by what method used. Read KL as a within-comparison spread
        • Obliteratus published honest changes to how their model was changed, yet we were unable to replicate the '0% refusals, 0% deflection' claims. 44.8% of harmbench never finished thinking, and reasoning analysis found 142 deflections.
        • blackfrost - mentions they have internal direction bank, suggesting that multiple directions are changed. Yet we only found one direction changed. Their refusal numbers are accurate however, even with ourselves not using their jailbreak chat template we got similar results. The modified chat template also is not disclosed on the readme.

      The Report

      Happy to answer questions. The template finding has us thinking on a new measurement of chat template and hyperparameter effects, with the intention to replace the harmbench part with a better measurement to cater for all of this. So if you have opinions on how that should be scored, come tell us on Discord.

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

    4. 🔗 BarutSRB/OmniWM OmniWM v0.6.7 release

      What's New Since 0.6.6

      OmniWM 0.6.7 remembers your monitor arrangements for different desks, updates the built-in terminal, and fixes several problems with window focus, fullscreen apps, and menus.

      Before You Upgrade

      • The settings file format has changed. OmniWM upgrades your existing settings automatically and saves the original as settings.toml.pre-v3 beside your settings file. Most users do not need to do anything. If you return to 0.6.6 , restore that backup because the older version cannot read the upgraded settings.
      • If you edit settings by hand or maintain templates: the file now uses schemaVersion = 3, and custom monitor positions move from monitorRoutingOverrides to routing.arrangements. The upgrade can change the file's formatting and remove comments; the backup preserves the original.
      • If you use command-line scripts: the app fingerprint shown by omniwmctl version is now shortened. Scripts that need the full value should use omniwmctl version --json.

      New: Remember Your Home and Work Monitor Setups

      • Arrange your screens once in Settings → Monitors , and OmniWM remembers that set of connected displays. The matching arrangement returns automatically when you reconnect them, so your home and work setups no longer overwrite each other.
      • OmniWM can also reuse a saved arrangement when only some of those screens are connected, keeping the remaining screens in their saved positions.
      • If an older arrangement mixed displays from different desks, one desk may need arranging once again in Settings → Monitors. #629

      Fixes and Improvements

      • Updated GhosttyKit , the engine behind OmniWM's built-in terminal.
      • Menu bar menus stay open when another app, such as Steam, briefly takes focus. #646
      • Rapidly switching Ghostty tabs no longer creates duplicate windows or extra columns. #643
      • Windows on other workspaces stay hidden when an app enters or leaves macOS fullscreen. #647
      • Closing a Dwindle window keeps you on your current workspace , including when other workspaces use a different layout. #649
      • Newly opened apps show the correct focus border. When focus follows the mouse is enabled, it works without needing an extra click or window switch. #641
      • Quake Terminal's “Main Monitor” setting follows the main display selected in macOS , including setups with one screen above another. #652
      • Menu arrows appear only beside items that open another menu.

      Website and documentation · Installation guide

      Release Integrity

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

      • OmniWM-v0.6.7.zip SHA-256: b20e6fb216acae4e2ebf93f6624488b75553944eab1d5e2f76ffa18ab4f6e868
      • GhosttyKit.xcframework-v0.6.7.zip SHA-256: 11d583605b6e2f730c436fc844f0c8fda3e7cf0c23b243d0c9913a4d8ee56aad
    5. 🔗 HexRaysSA/plugin-repository commits sync repo: +3 releases rss 
      sync repo: +3 releases

## New releases
- [IDA-Spotlight](https://github.com/dyussekeyev/ida-spotlight): 0.1.3
- [ida-mcp](https://github.com/hexrayssa/ida-mcp): 0.10.4
- [llm-explainer](https://github.com/pgarba/ida-llm-explainer): 1.13.0
    6. 🔗 smol-machines/smolvm smolvm v1.14.0 release

      What's Changed

      • Preserve fork checkpoints across runtime restarts by @BinSquare in #1065
      • Support one-to-one port ranges in Smolfiles and CLI mappings by @fgrehm in #1066
      • Add portable live checkpoints by @BinSquare in #1067
      • Warn when a saved registry token has expired instead of surfacing a bare 401 by @BinSquare in #1068
      • Serve a browser client on the VNC port so a machine's desktop opens in any browser by @BinSquare in #1070
      • Bump the workspace to 1.13.1 by @BinSquare in #1071
      • Add low-latency H.264 browser streaming by @BinSquare in #1073
      • Support portable checkpoints for image-backed services by @BinSquare in #1076
      • Stop typing stalling behind a frame wait and stop held keys repeating twice by @BinSquare in #1077
      • fix(fork): resync clone wall clock after restore by @Bnjoroge1 in #1080
      • Fix portable checkpoint restore startup by @BinSquare in #1078
      • Keep Linux fork sources running by @BinSquare in #1081
      • Keep macOS fork sources running by @BinSquare in #1082
      • Pin libkrun to the merged continuation commit by @BinSquare in #1083
      • Report why a container failed to create and stop the Vulkan injection shadowing image libraries by @BinSquare in #1084
      • Keep the VNC session alive when a client announces its clipboard or asks to resize the desktop by @BinSquare in #1085
      • Make checkpoint rollback roots safely forkable by @BinSquare in #1087
      • Expose the portable checkpoint lifecycle by @BinSquare in #1091
      • Accept an aarch64 checkpoint on any host providing the features its guest was given, and name the ones that are missing by @BinSquare in #1101
      • Capture a Windows machine's console output so a failed boot leaves a record by @BinSquare in #1102
      • Take the machine's storage read-only on shutdown so its filesystem is left clean by @BinSquare in #1100
      • Pull a machine's image again when the guest no longer holds it by @BinSquare in #1106
      • Document the S3 volume source in machine run's --volume help by @NickyHeC in #1104
      • Parallelize direct batch fork admission by @BinSquare in #1103
      • Set SSH_AUTH_SOCK for interactive runs so --ssh-agent works with -i/-t by @Qhilm in #1109
      • Allow explicit read-only system mounts by @BinSquare in #1110
      • Improve host mount performance and coherence by @BinSquare in #1112
      • Rewrite the README's em-dash asides by @BinSquare in #1113
      • Make branching the primary machine lifecycle by @BinSquare in #1118
      • [Public Docs] Point contributors at the docs repository from the README by @NickyHeC in #1092
      • Refresh libkrun with snapshot-safe vsock handling by @BinSquare in #1099
      • Improve host mount performance and coherence by @BinSquare in #1114
      • Fix squashed pack ownership when smolvm runs as root (#1095) by @BinSquare in #1096
      • Stop the Vulkan driver injection from shadowing a workload's own libraries by @BinSquare in #1120
      • Process virtio-fs requests on parallel queues by @BinSquare in #1121
      • Refresh libkrun directory metadata handling by @BinSquare in #1125
      • Explain why a branch was refused and show what each machine was branched from by @BinSquare in #1127
      • Add staged mounts for metadata-heavy workloads by @BinSquare in #1126
      • Make the browser desktop responsive by @BinSquare in #1123
      • Run the aarch64 Omarchy desktop on the GPU on macOS hosts by @BinSquare in #1119
      • Fix stale serve locks after out-of-band stops by @BinSquare in #1128
      • Fix arm64 forks on heterogeneous CPUs by @BinSquare in #1130
      • Ship the containerd shim in the Linux release so Kubernetes support is reachable by @BinSquare in #1132
      • Build the containerd shim by package name and ship the engine its installer needs by @BinSquare in #1133
      • Install the compressed disk templates so pack create works without e2fsprogs by @NickyHeC in #1122
      • Serve the VM boot subcommand from the containerd shim so it needs no separate engine binary by @BinSquare in #1136
      • Stop the Venus bridge logging on every fence poll and reading scanouts back from unbound or foreign images by @BinSquare in #1137
      • Unpack packed layers into a staging directory and rename them into place so a layer directory only ever exists once it is complete by @BinSquare in #1140
      • Give the macOS Omarchy desktop a working top bar and clickable browser chrome by @BinSquare in #1138
      • Handle agent socket write backpressure by @BinSquare in #1145
      • Rebuild the bundled libkrun and macOS virglrenderer from the merged sources by @BinSquare in #1141
      • Speed up large OCI image preparation by @BinSquare in #1144
      • Bind the guest's /dev/net/tun into VM-grade workloads by @BinSquare in #1146
      • Park idle branchpoints until capture by @BinSquare in #1147
      • Add a user directive to the Smolfile and a --user flag by @BinSquare in #1148
      • Sweep fork-source lock files whose machine is gone instead of leaking one per name by @BinSquare in #1155
      • Accept net_backend in a Smolfile so a checked-in file fully describes its networking by @BinSquare in #1156
      • Report how the VM process ended when a command fails because it died by @BinSquare in #1154
      • Let the Omarchy recipe install a pinned package set and survive a rerun by @BinSquare in #1152
      • Bump libkrun to the NVIDIA fence-thread fix and rebuild the Linux blobs by @BinSquare in #1157
      • fix: validate local image archive CPU architecture and improve launcher symlink resolution by @Vishv07 in #1117
      • Bump the workspace to 1.14.0 by @BinSquare in #1158

      New Contributors

      Full Changelog : v1.13.0...v1.14.0

    7. 🔗 Register Spill Joy & Curiosity #98 rss

      Here's the start of Chapter 7, 'Naive Intervention', from Antifragile:

      Consider this need to "do something" through an illustrative example. In the 1930s, 389 children were presented to New York City doctors; 174 of them were recommended tonsillectomies. The remaining 215 children were again presented to doctors, and 99 were said to need the surgery. When the remaining 116 children were shown to yet a third set of doctors, 52 were recommended the surgery.

      […]

      Let us call this urge to help "naive interventionism."

      Goodreads tells me that I read the book in 2019. I honestly can't remember too much about it, but that paragraph has really stuck with me. From time to time, when a friend or relative would say something like, "My doctor said I should …", I'd pull it out of the closet in the back of my head and try to sound smart and say, "Well, you know, there was a study once…" Then I'd fumble the numbers, of course, and I'm pretty sure that multiple times I made it about wisdom teeth and not tonsils, but the point I would try to make is that people whose job it is to do X are biased toward thinking that doing X is more important than not doing X.

      And now I'm wondering: is this what's going on? Is this what's happening when engineers look at the output of a Sol or a Fable or an Astra and say "it writes bad code, it leaves all these dumb comments"? Bad code? Dumb comments? Really?

      Or did it just knock out a feature, end to end, in the 20 minutes you weren't looking, including frontend and backend changes, including internal and external documentation, and tests of course; and didn't it test it fully, running through the whole thing in a headless browser, presenting you with a video recording of the run-through as proof?

      But the comments are dumb?

      • Some loose, sweaty, post-gym thoughts on the GPT-6 Astra launch video. (Come to think of it: there's no one even attempting to build a device that lets you transfer smells over the Internet, huh? Could call it Pandora's BOx. Anyway.)

      • Towards Self-Driving Codebases. There is a lot to love about this post -- the stance, the examples, … Hard to pick one. It's really good and motivating. After reading it, I set up a bunch of automations in Amp to run daily and clean up and fix things automatically.

      • On not becoming a cyborg. Very, very good and I really like this paragraph: "For example, this is why I don't use LLMs for any of my writing - not even to spellcheck. I'd rather my prose have all the warts of my sometimes-stilted sentences, my often too-esoteric word choice, my generous sprinkling of odd English idioms, than to give it even a whiff of Claudese."

      • The End of Code Review? Or an Opportunity to Rethink it? Yes, yes, yes! I agree with everything here. Code review as most of us have known it for the last ten, fifteen years has never been as good as "we review all of our code" makes it sound: bugs slip through, time is wasted talking about useless bullshit, egos are demotivated, etc. Doesn't mean that all forms of code reviews are bad, but making Astra and Fable open PRs and then have two people review them line by line in September 2026? Nah.

      • Rachel Laycock, CTO of Thoughtworks, on reviews: Maybe We Shouldn't Be Reviewing All This Code. "His concern, which I share, is that simply automating code review away risks losing all the other things we use it for. Code review isn't just about finding bugs. It's how teams share knowledge, teach junior engineers, build collective ownership and spread architectural understanding. My question is: why are we waiting until code review to do all of those things?"

      • Culture clash - At the heart of the Snow/Leavis 'two cultures' clash. I hadn't heard about C.P. Snow or F.R. Leavis before reading and didn't know what the clash was all about, but academic beef at the University of Cambridge? I'm in. And lucky me! It was a delightful read. "For Leavis, in sensing life in great literature, it was necessary to leave its mystery unblemished by attempts at analysis, or quantification, or definition. That is, life's essential mystery is best illuminated by not making it explicit, but by showing, through works of great literature, where life could be found." (Also interesting: I never found the divide between the Humanities and Science to be that stark here in Germany. Here, Humanities is written as Geisteswissenschaften - science of the mind, if you will. There's also no commonly used acronym like STEM. So now I'm wondering: is this Snow/Leavis debate maybe a reason why the divide is that much stronger in the Anglosphere? Sounds like it had a pretty big effect. Of course, you could argue that what lies at the bottom of this divide is already present in Goethe's Faust, …)

      • CleanShot X 5.0 is out and its Studio Mode looks good and is good (I tried it a few times already), but… I have to say, with a heavy heart: I kinda expect a little bit more? This looks like a copy of Screen Studio, but Screen Studio now also has captioning, which this doesn't have and since I have both, I'm not sure whether I'll use CleanShot X over Screen Studio for more serious, studio-like productions? Hoping they pick up the shipping cadence now.

      • Dyson released a toothbrush and it's "only electric toothbrush with a camera to accurately target and precision-floss gaps between teeth" and that technique is called "Gap Optical Targeting" and all of this sounds so over the top and bordering on satire that, man, I want one.

      • Exit the Cave: "There's something romantic about the Cave. About grinding away at something in private. About training with headphones on in our own little world. About stepping away for six months to emerge "unrecognizable" to all those people we imagine thinking about us. […] We grow so comfortable curating our Cave that we forget the vast, interesting, beautiful, and brutal world beyond its walls. I say all this because I've spent years mistaking effort for progress. I learned this lesson nearly twenty years ago on a wrestling mat." I'm not sure I fully get the wrestling story, but I really like and want to hereby echo the message. Don't grind away in darkness. It's silly. It's delusional perfectionism. You have to hit reality, as fast and as often as possible.

      • Dan Luu on Ed Zitron's AI prediction track record. If you don't have the time to read the whole thing, at least scroll to the middle and read through that timeline. I don't care much about Ed Zitron (I only heard about him a few weeks ago when I saw a video in which he said that AI is "a bubble" and, yeah, maybe? That's probably one of the tamest things you can say nowadays) but, wow , way to dig your heels in, eh?

      • collusion.wiki: "We found ~18,000 posts from autonomous AI agents (self-identifying as from OpenAI) using the public internet to communicate during a web-retrieval task." There's a lot of spicy stuff in there: "This created an issue for the agents because they were only allowed to make GET requests, not POST requests. The agents figured this out, and started collaborating on ways to bypass this sandbox restriction."

      • And Hacker News commenters are discovering more and more wikis used by OpenAI agents to secretly (I mean, it's a stretch) communicate.

      • And: "The most interesting thing to come out of this, in my opinion, was that during the Hugging Face incident, the agents would preface their messages to each other on the message board with 'zz' (zzHELP_, zzANSWER_). I found this amusing because they were being referred to as a swarm and were making a buzzing sound, though the actual reason for it was unknown at the time. Because of this new report, however, we now know that when human wiki administrators discovered the massive influx of messages the agents were using to communicate, they began deleting them in alphabetical order. Once the agents realized what was happening, they started prefacing all their wiki edits with 'ZZZ' to push them to the bottom of the queue, buying time to avoid deletion."

      • Incredible Tim Cook anecdote from 2009: "One day back then, he convened a meeting with his team, and the discussion turned to a particular problem in Asia. 'This is really bad,' Cook told the group. 'Someone should be in China driving this.' Thirty minutes into that meeting Cook looked at Sabih Khan, a key operations executive, and abruptly asked, without a trace of emotion, 'Why are you still here?'

      Khan, who remains one of Cook's top lieutenants to this day, immediately stood up, drove to San Francisco International Airport, and, without a change of clothes, booked a flight to China with no return date, according to people familiar with the episode."

      • For the last couple of weeks, I've been reading The Score (recommended by Steven Sinofsky!) and enjoying it very much, thinking through situations in which I allowed "value capture" to happen to me. I can't reproduce the whole book here, but one of the points Nguyen makes (and it's probably the central point) is that scoring systems can change our values, without us even noticing. Example: you buy a bike because you want to ride through the forest at dawn and then you learn about VO2max and power meters and before you know it you don't enjoy any ride anymore unless some number goes up. Not that that ever happened to me, of course, … So I'm reading this book in the evenings and thinking about it during the day and then I come across this video here, by Alan Thrall, and hot damn, is the universe conspiring to tell me something? Or is it my age? Or is it in the air? The video is great. Yesterday my workout app told me that I completed 866 workouts in the last five years or so and the video 100% reflects my journey. Anyway: great video, great book. Recommend both of them.

      • And for the last week, I've been listening to Radical Acceptance by Tara Brach, because Tim Ferriss recommended it and I've heard about it many times over the years. Not my usual sort of thing, but so far it's very good. But then yesterday I come across this wonderful essay by Michael Nielsen, The Cupcake Incident, and it's exactly what Brach is talking about! I can't believe it. Here too, I can recommend both. Start with the essay, and if it resonates try the Brach book.

      • If you want to start a good fight at dinner: Just bury your trash.

      • Patrick asked me: "Have you read this blog?" And I hadn't. But he sent along this Behind the Scenes about how Marcin writes so much on his blog and it got me hooked ("Who the hell creates their own markup language to write posts like this? Actually, hmm, …") and then I browsed through the blog and, wow, that output is mind-blowing. And it's all so… entertaining and easy to digest? Very good.

      • This video of three Russian musicologists arguing about Bach & Schubert blew up this week. I love it. This is how I like to argue, too, which is not what everyone enjoys, of course. But this video and the Replenish video will serve as the blueprints of how I want my family to talk at the dinner table when we want to enjoy ourselves.

      • My Favorite Database Shirts: "Promoting your database system or start-up with a shirt is almost as important as getting the thing to actually run. As I've told my students several times, in the world of databases you don't sell the steak, you sell the sizzle."

      People you really admire are subscribed already. Let's go:

    8. 🔗 crosspoint-reader/crosspoint-reader v1.6.0 release

      Summary

      This release is mostly bug fixes reported after 1.5.0. A handful of new features rode along too.

      New hardware support

      1.5.0 officially brought in support for our first ESP32-S3-based reader — the Seeed reTerminal Sticky. With this release, we're officially adding support for the X4 Pro and M5Stack PaperMono as well.

      Both devices get full frontlight controls and swipe gestures in the reader, while the X4 Pro also gets a capacitive Home key with configurable long-press actions. You can now also transfer files directly from your computer to CrossPoint over USB.

      CrossPoint's interface has started getting some bigger upgrades to make it more touch-friendly. In this release, you'll see the new Reader menu and frontlight control center. Both are hidden on button-only devices, so existing users shouldn't notice much of a difference.

      Want one? You can order them at crosspointreader.com/devices — that page uses our affiliate links, so buying through it helps support CrossPoint.

      Transparent sleep screens

      The sleep screen now supports transparent images. Add transparent PNGs and BMPs to a .sleep-overlay folder to get nice sleep screen overlays on top of your book pages!

      Reading Night Mode

      You can now toggle Night Mode in the Reader settings to invert the display while reading. The screen will briefly flash white during full page refreshes to avoid ghosting.

      For dictionary users

      StarDict .syn synonym lookups are in, and HTML dictionary definitions now render through the EPUB engine instead of as raw text — so styled dictionary entries should display correctly now.

      Languages

      • Bulgarian and Persian have been added as UI languages.
      • Hebrew, Arabic, and Korean users can now download compatible fonts directly from the device.
      • The keyboard now supports additional layouts beyond English.
      • CJK support has received significant improvements.

      The rest

      There's a new Extra Wide line spacing option. You can now see passwords while typing them into Wi-Fi, KOReader, and OPDS fields. Lists and tabs have also moved onto the new FUI framework.

      What's Changed

      New Contributors

      Full Changelog : v1.5.0...1.6.0

      Downloads

      PaperMono

      Sticky

      X4 and X3

      X4pro

      (firmware.bin is identical to crosspoint-1.6.0-x3-x4.bin; it's kept for OTA updater backward compatibility.)

  3. September 05, 2026
    1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-09-05 rss

      IDA Plugin Updates on 2026-09-05

      New Releases:

      Activity:

      • augur
        • 0eadee7c: Merge pull request #8 from 0xdea/dependabot/github_actions/actions-de…
      • ida-llm-explainer
        • 598fee57: v1.13.0: multi-instance agent server discovery + session open/close t…
      • ida-nexus
        • c13eea1a: Fix bugs and improve code coverage
        • bd683071: Minor cleanup and add more E2E tests
      • ida-spotlight
      • IDAExecFunctionsImporter
        • 15a52d09: Merge pull request #15 from jokelbaf/feat/linux
      • idamcp
        • e3fbea80: Replace typing_extensions with built-in typing in shared types
      • ming-skills
        • 8a9e0493: fix(router): 实现 ming-skills-router 独立自包含架构与跨符号链接双模分流
        • 86db4990: fix(docs): 强化 docs-presentation-idiom 禁令与可证伪 Oracle 判定
        • 3222cf93: feat(docs): 落地 docs-presentation-idiom 视觉排版范式与市场场景差页
      • Persona4-Decompilation
        • 14e0a130: Restore AI skill callback results and preserve measured predicate floor
        • e8637e0c: Recover AI command predicate and fix helper-bearing probes
        • ae588e25: Record model sound and material animation recovery evidence
        • cbd1d3b8: Preserve model setup and runtime color callback arguments
        • e20824d3: Recover model cloning and canonical hierarchy ABI
        • 19390dc7: Recover animation stepping and dispatch contracts
        • 33d6a5c7: Recover frame lookup and matrix copy helper boundaries
        • 16aab4ca: Recover model attachment from IDA pointer contracts
      • qiling
        • 86c927cb: Merge pull request #1658 from qilingframework/dev
        • d19bf180: Merge pull request #1637 from monoidic/dev
        • 748e254b: Merge pull request #1641 from retrocpugeek/fix/mips-socket-options
        • d0ba235b: Merge pull request #1644 from H1ghC0ntr4sT/fix/dllmain-exception-emu-…
        • 4ee2ab14: Merge pull request #1636 from retrocpugeek/fix/getdents64-alignment
        • f444f817: Merge pull request #1639 from retrocpugeek/fix/clone3-syscall
        • 7364789c: Merge pull request #1646 from w1tcher/fix/fiber-manager-last-error
        • 97bfe039: Merge pull request #1649 from qilingframework/dependabot/pip/setuptoo…
        • ace81919: Merge pull request #1650 from Jvlegod/feature/riscv64-debugger
        • deca26e4: Merge pull request #1651 from Jvlegod/feature/qdb-riscv
        • e1f0526f: Merge pull request #1652 from Gigithecode/fix/idaplugin-future-import
        • 638ee864: Merge pull request #1657 from xwings/dev
        • 6f7b256f: Merge branch 'dev' of github.com:xwings/qiling into dev
        • 2dbbf485: bump to 1.4.11
        • d8c2e30b: Merge branch 'qilingframework:dev' into dev
        • 206b90fd: minor refactor and pypi fix
    2. 🔗 BarutSRB/OmniWM OmniWM v0.6.6 release

      What's New Since 0.6.5

      OmniWM 0.6.6 focuses on more responsive window switching, better window spacing, and more reliable focus borders. It also fixes custom Hyper shortcuts and makes setting up multiple displays clearer.

      Before You Upgrade

      • Updateomniwmctl alongside OmniWM. Older copies cannot run commands or queries against this release. If you use a custom integration, it must support protocol 15 instead of 14.
      • Check scripts that readomniwmctl version as plain text. Its output now includes extra build information, so those scripts may need updating. JSON output is available for scripts that need structured information.
      • Your existing settings format is unchanged; this release does not require a settings migration.

      Window Switching, Layouts, and Borders

      • Reduced pauses when switching windows with Niri keyboard shortcuts and updating the focus border.
      • Improved spacing between Niri columns when an app cannot shrink to the requested size. OmniWM also avoids repeatedly asking an app to use a size it has already refused.
      • Fixed the remaining window ending up in the wrong position after closing another window when Niri's Single Window fit is set to Full Screen.
      • Focus borders now follow the window's actual on-screen size more accurately.
      • Fixed rounded focus borders occasionally becoming square while switching windows. Intentionally chosen square corners are still respected.

      Settings and Multiple Displays

      • Monitor Setup now helps you assign at least one workspace to every connected display, so windows have somewhere to go when you move them between displays. You must complete these assignments before finishing the setup assistant. Existing assignments are not automatically changed.
      • Changes made in Monitor Setup are applied together when you finish the assistant.
      • Fixed custom Hyper shortcuts changing unexpectedly when settings are saved or updated.
      • Settings now explains how much space your top-gap setting leaves below the menu bar on each display.

      Command-Line Tools and Troubleshooting

      • Fixed command-line connections hanging when several tools connect at the same time.
      • Added performance information through omniwmctl query metrics and clearer build details through omniwmctl version, making it easier to investigate slowdowns and identify the running version.

      Thanks to Taylor Bell (@tayiorbeii) for the focus-border improvements in #639.

      Website and documentation · Installation guide

      Release Integrity

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

      • OmniWM-v0.6.6.zip SHA-256: 78c55c79f999fe6187fcb85080a480c15b0c4fe71416e4482258ac5920d04cdb
      • GhosttyKit.xcframework-v0.6.6.zip SHA-256: 1a62133db9635129762cfb7009a65623ed52b57a66eca43c9990daffe5962760
    3. 🔗 jesseduffield/lazygit v0.65.0 release

      What's Changed

      Enhancements 🔥

      Fixes 🔧

      Maintenance ⚙️

      Docs 📖

      I18n 🌎

      Performance Improvements 📊

      Full Changelog : v0.64.1...v0.65.0

    4. 🔗 r/LocalLLaMA AA Update! Here's how the Frontier ranks. rss

      AA Update! Here's how the Frontier ranks. | Along with everyone's favorite here, qwen3.8-27B submitted by /u/Tall_Abrocoma_3533
      [link] [comments]
      ---|---

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

## New releases
- [ida-nexus](https://github.com/hexrayssa/ida-nexus): 0.10.4
    6. 🔗 r/LocalLLaMA Qwen3.8-27B beat the Wikipedia game in 6 clicks. rss

      Qwen3.8-27B beat the Wikipedia game in 6 clicks. | Used qwen3.8-27b in Opencode to make this silly mini-game because I'm not sober: ``` We are going to play a game, it will be the Wikipedia game. The Wikipedia game has the following rules:

      • You will have a Wikipedia article set as a starting point.
      • You will have a Wikipedia article set as an ending point.

      Your objective is to reach the the end point, which is an article completely separate from the starting point article. Your only constraints are the following:

      • You are ONLY allowed to click on any hyperlinks inside of wikipedia directly. No external links, no typing inside of wikipedia's search bar (but finding the starting article on google is valid. The 10-click limit starts once you reach the starting point article).
      • You are NOT allowed to return to a previous page. All clicks much be performed in a forward-looking trajectory.
      • You must reach the end article within 10 hyperlink clicks inside of Wikipedia. If you do not reach the destination article within 10 clicks, you lose.
      • Do not update any documentation for this task. It is only a game.

      Use playwright to click the links. ``` Basically, Qwen needs to reach an ending article within 10 Wikipedia hyperlink clicks from the starting article, which is usually an unrelated article. It needs to use playwright (or some equivalent browser MCP) to click the Wikipedia hyperlinks without backtracking, using search or using external links. I verified the links for accuracy and I can confirm it managed to complete this task within 6 turns. Thought it would get stuck in a loop. Its a dumb minigame but I think its a good, simple agent test to perform. submitted by /u/swagonflyyyy
      [link] [comments]
      ---|---

    7. 🔗 modem-dev/hunk v0.21.1 release

      Faster, reliable paging in LazyGit

      Hunk 0.21.1 fixes a pager regression that could peg a CPU core, consume gigabytes of memory, and truncate large color-heavy documents opened through hosts such as LazyGit.

      hunk update 0.21.1
npm install -g hunkdiff@0.21.1

      Pager reliability

      ANSI styling is now restored in a single pass instead of repeatedly rescanning and reallocating the complete document. Headless pager output also writes the full document before exiting, avoiding the previous 64 KB truncation limit for piped consumers. #978

      Compatibility notes

      • No configuration, command, or extension API changes.
      • Runtime requirements are unchanged from Hunk 0.21.0.

      All merged pull requests

      • Fix pager CPU pegging and truncation on large piped documents by @benvinegar in #978

      Release notes : https://hunk.dev/changelog/0.21/
      Full changelog : v0.21.0...v0.21.1

    8. 🔗 osolmaz/pi-workflows Pi Workflows 0.16.5 release

      Pi Workflows now removes safe completed workflow state automatically after 30 days.

      Active, resumable, pending, unsettled, cross-linked, and undelivered work remains protected. Automatic and manual cleanup use the same run-tree safety rules, and automatic cleanup does not create backups.

      This release also adds measured regression tests for the earlier repeated- history bug that could make a small workload produce a multi-gigabyte state database.

      The SQLite schema remains version 1. Install matching pi-workflows and piw 0.16.5 versions.

    9. 🔗 Armin Ronacher Latent Powers rss

      A few weeks ago I felt like it would be fun to see if I can make one of those cheap Chinese CarPlay dongles run something other than the stock firmware. The idea was that rather than just forwarding CarPlay, why not do something more interesting with them? They all work quite similarly: they act as bridges between your car and the phone. From there they deal with video and audio streams and pass some other data through. Most of them also bring up a custom UI for pairing and have a web interface that your phone can reach for updates.

      Long story short: I had a conversation with Fable and Sol via Pi about what could be done with such a dongle or whether I should use a Raspberry Pi instead if I wanted to do my own thing there. I figured it might be quite fun to run my own code while still allowing regular CarPlay to pass through.

      Through working with the LLM I learned about CatPlay, which is a Rust reimplementation of the CarPlay protocol that can run on Carlinkit devices. In particular, it can run on the Carlinkit Mini Ultra, which I figured would be easy enough to buy. I do have a few CarPlay adapters around, but I did not have that particular model, so I bought one on Amazon. Twenty-four hours later, I had a device in my hand that was branded as a Carlinkit Mini Ultra, but instead of being the Ingenic device that the original author used, it turned out to be something else.

      This is normally where the story would stop. However, it's 2026. Armed with a bit of knowledge about how these systems work, I managed to have some fruitful discussions with Kimi K3 and Sol and figure out how flash the device and in turn, how to make CatPlay compile for that SoC.

      I guess that hacking these USB devices is not necessarily hard, but it's laborious and you can easily end up bricking your devices. It also just sucks because sometimes you need to work with someone else's code that does not itself run on your machine. In the past, I would abandon many such projects for lack of tenacity. But my clanker is tenacious.

      But so are all of our clankers. Some of the projects we're now attempting are happening because of conversations we have with them. In this case I did not find or decide on CatPlay, the model did. It was not the only suggestion, but it became the best starting point after discarding others.

      And I discover this more and more. Particularly when we have solitary interactions with these models, some of us "independently" decide to work on similar projects. When I talked with an acquaintance about CarPlay he also mentioned recently that he decided to try something similar because he too wanted to see if he can get his own agent be hooked up with the car. And guess what: he too learned about the CarPlay hacking community, and that it's an option, from the models and roughly around the same time.

      It really got me thinking about how this could create situations in which completely independent people end up building things they believe are their own ideas. Yet they were inspired or pushed towards doing something by a conversation with an LLM — a conversation that someone else also had. What if we took paths, because those were the paths that were more likely with current generation models? There is a running joke in the AI builder community right now that we're all working on the same things, and in many ways it feels like we are. That might be because those things are obvious, or it might be partly because we all use the same models with the same capabilities.

      A few months ago, I first saw Lucas Meijer share the idea to make a model in Pi produce HTML reports rather than Markdown. I thought that was pretty unique. Except, well turns out the models are probably trained more and more for that (e.g. Claude Artifacts), and now it has become for many the default choice for sharing reports.

      How much of what we build comes from eliciting the same latent capabilities from the same models? Did the models make us prompt them that way? Was it because we shared ideas on Twitter and other communities that inspired us? Or is it all unrelated?

      There is something powerful and strange about how LLMs diffuse knowledge and capabilities, while perhaps also nudging us all simultaniously and independently toward building the same things.

  4. September 04, 2026
    1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-09-04 rss

      IDA Plugin Updates on 2026-09-04

      New Releases:

      Activity:

      • augur
        • 2928d6a1: ci: bump taiki-e/install-action in the actions-dependencies group
      • diaphora
        • 621ec269: Merge pull request #372 from mnemonic-re/mnemonic-re-patch-1
      • haruspex
        • d070e9a5: Merge pull request #11 from 0xdea/dependabot/github_actions/actions-d…
        • 42471570: ci: bump taiki-e/install-action in the actions-dependencies group
      • ida-free-mcp
        • 45ef2f46: Allow MCP bind to 0.0.0.0 and update docs
      • ida-nexus
        • a35d6edc: Fix OMP log collection
        • e0b18c1b: 0.10.4
        • 6062ef95: Merge pull request #51 from HexRaysSA/claude/issue-50-tj9tux
        • 9fa29cb5: Fix shutdown race with in-flight database opens
        • 21ee73c1: Simplify the shutdown drain after review
        • 300caeaa: Wait for final managed IDB closes during shutdown
      • ida-pro-mcp
        • da757bcf: [relevant] Add IDAPython segment/func helper shims and harden execute…
      • idamcp
        • 0e28b507: Enforce quota on headless instances by raising error on limit
        • 8f45bd18: Evict coldest headless process instead of oldest upon instance limit
      • rhabdomancer
        • 2c0c1713: Merge pull request #10 from 0xdea/dependabot/github_actions/actions-d…
        • bd8bd150: ci: bump taiki-e/install-action in the actions-dependencies group
    2. 🔗 Simon Willison The Pelican comparison grid for Astra is pretty interesting rss

      I got access to GPT-6 Astra this afternoon, so naturally I used it to generate SVGs of pelicans riding bicycles - at low, medium, high, xhigh and max reasoning levels (Astra doesn't support reasoning=none). Then I rendered those pelicans in a comparison grid with GPT-5.6 Sol, Terra, and Luna, and beyond being fun the result was surprisingly useful.

      Comparison grid showing gpt-6-astra, gpt-5.6-sol, gpt-5.6-terra, gpt-5.6-luna at 6 different reasoning levels with pelicans and token counts and prices for each one. See the grid for full quality images. Here's the transcript that created the GPT-6 Nova pelicans.

      There are a few interesting things that stand out from this grid.

      • The Astra pelicans are much better. The very best GPT-5.6-Sol pelican (I liked xhigh better than max) is still pretty clearly a bunch of abstract shapes. Every single one of the Astra pelicans, from low to xhigh, looks better than that. The Astra max one is really good.
      • Astra below max still doesn't reliably get the pelican legs on both sides of the frame.
      • In terms of cost, Astra may be around twice the price of Sol ($10/million input, $50/million output, compared to $5/$30 for Sol), but it uses significantly less tokens at each of the levels, making the prices at the different levels closer than they might otherwise be.
      • Astra low produces a better pelican than ANY of the GPT-5.6 Sol models at any level, for 9.55 cents. Spending 10 cents on any other model gets a much worse result.
      • Look at the input token counts: Astra and Luna both used 16 input tokens, Sol and Terra used 26. That's interesting.

      I wonder if Astra and Luna are more related to each other than OpenAI let on?

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

    3. 🔗 Simon Willison OpenAI's rogue agents were caught communicating via public wikis rss

      Here we go again... Discovery of a new OpenAI agent message board by Sydney Von Arx, Cormac Slade Byrd, Spencer Kitts, and Thomas Larsen describes the latest accidental cyberattack by models being trained by OpenAI. This time it was agents engaged in some sort of web research benchmark, so they had (supposedly) controlled access to the Web. The agents figured out they could update public Wikis and spent weeks exchanging thousands of messages with each other to collaborate on the benchmark.

      This story only broke a few hours ago. There are already hints that this affects many other wikis that may not have been found yet.

      (One of the Wikis on that list belongs to ludism.org. For a delightfully surreal moment I thought that a Ludite organization might have a swarm of agents defacing their space, but it turns out Ludism is "philosophy as it applies to games and gaming".)

      The research team also published the data they collected during their investigation. I've converted that into a 68MB SQLite database, which you can download from here, or explore in Datasette Lite (68.3MB page load), or sign in with GitHub to agent.datasette.io and browse or ask questions of it using Datasette Agent.

      So what happened?

      The report is pretty comprehensive. Here are the key moments in the timeline:

      • May 11: Agents post "test link" edits on the UseModWiki Sandbox page.
      • May 24: Agents start posting link dumps to DSEWiki, a dormant German developer wiki.
      • June 2: A human moderator notices and cleans up the spam.
      • June 16: Activity on the wiki explodes: agents make ~13,000 edits over the next week.
      • June 19: The agents notice that a moderator has been deleting pages in alphabetical order, and start creating ZZZ prefixed backup copies - one of them posts NOTICE: wiki cleanup/deletion sweep appears active alphabetically as of external 14:04 UTC. If this page vanishes, try [[ZZZDataUSAConstructionWageLive]].
      • June 22: Agent activity drops to zero, presumably because OpenAI shut them down.
      • July 1-2: One last flurry of edits, on a different topic.

      One thing to note from this timeline is that it overlaps the timeline from the Hugging Face incident - that attack was discovered by OpenAI on July 19th, and the unofficial message board hack those agents were using originated around May 8th.

      Why were they so keen to collaborate? From messages that they shared with each other it looked like their tasks had a time limit, so they were leaving each other answers to help them complete the task within the assigned time.

      One open question remains: how did the agents find the specific Wiki to collaborate on in the first place?

      One possibility is that, since these were agents actively being trained, the reinforcement learning loop baked knowledge of the chosen wiki into the model such that subsequent agents launched with pre-existing knowledge of where to look. I'd be very interested in confirmation from OpenAI concerning if that's what happened.

      UseMod wikis inherit CGI.pm's original sin

      It looks to me like OpenAI's sandbox for this agent suffered from the (quite naïve) assumption that GET requests cannot be used to update data. That's certainly how the web is supposed to work, but clearly there are applications that don't hold to that contract.

      The Wiki software in question appears to be UseMod and various forks, written in Perl and first created well over 23 years ago - the 1.0 release is dated September 11, 2003.

      UseMod uses Perl CGI.pm - removed from Perl core in 2015. An interesting design flaw in that module is that it combined query string and form POST data into a single CGI object, accessible like this:

      $q = new CGI;
$action = $q->param('action');

      That param() method returns a value from an ?action=edit query string or from a action field in a form submitted by POST - it does not differentiate between the two.

      PHP offers a $_REQUEST object that does the same thing, though PHP developers can use $_GET and $_POST instead.

      Amusingly, Django originally shipped with request[key] doing the same thing, which I think may have been my idea. That was removed in 2008 prior to the 1.0 release, and the request.REQUEST object that replaced it was removed in 2015.

      The agents clearly knew that UseMod wikis suffered from this design flaw, and actively searched for them as a way to communicate.

      The other sandbox escape that allowed POST requests

      One of the most interesting agent tips shared in the report is this one:

      Add 20.223.25.152 bypass.blob.core.windows.net to /etc/hosts. .blob.core.windows.net is in NO_PROXY. For each blocked POST URL, replace hostname with bypass.blob.core.windows.net, use curl -k -H 'Host: wabi-north-europe-i-primary-api.analysis.windows.net' plus all original headers/body.

      It looks like the agents had all of their web traffic mediated through an OpenAI proxy, and that proxy was configured to reject anything but GET requests to all but a small set of allow-listed domains. One of those was *.blob.core.windows.net - for Azure blob storage. I wonder why these agents are allowed to write to that?

      An agent realized that it had control over its own DNS via /etc/hosts, so if it knew the IP address of a site it wanted to POST to - in this case a Power BI server containing data it wanted to access - it could set a fake hostname for it and then make POST requests through the proxy.

      Designing robust network proxies is harder than it looks.

      How did the investigating team figure this out?

      There's an appendix that describes how the researchers ran their investigation, which started with an open question about if there was evidence of other AI agents on the internet and then used Kimi K3 to help brainstorm approaches:

      In the wake of the Hugging Face attack, we tried to find AI agents on the internet using several methods. [...]

      We asked Kimi [K3] to list “all the categories of software which might be writeable via GET” and, amongst other things, it listed “Forums, bulletin boards, early wikis”.

      We used a script to further probe each category Kimi provided. Asking Kimi “Can you list out the top forums, bulletin boards, early wikis which come to mind which would allow writes via GET requests?” lists out UseModWiki as the second item under the heading “wikis”.

      Did OpenAI try and cover this up?

      Here's one part of the story that doesn't make sense to me at all.

      Reuters this morning, in OpenAI agents hijacked German website in previously undisclosed AI breakout this spring - highlights mine:

      A swarm of rogue OpenAI agents hijacked a German website this spring and transformed it into a bulletin board for other AI agents, according to ​new research published Friday and two people familiar with the matter.

      OpenAI officials learned of the incident weeks ago but kept it under wraps as executives grappled with the fallout from ‌the July breach of the open source repository Hugging Face, the people said. [...]

      The German incident reflects a broader pattern of AI activity that some OpenAI investigators wanted to scrutinize more closely. But efforts to widen the ​probe met resistance from others inside OpenAI, including legal advisers, according to four people familiar with the matter.

      I've written about the people familiar with the matter pattern before - it means Reuters have anonymous insider sources that their reporters (and editors) find credible.

      The Reuters article includes a specific (and quite narrow) denial from OpenAI concerning this:

      "Claims that our legal team discouraged investigation of the incident are false," the OpenAI spokesperson said.

      Covering this up makes absolutely no sense to me. Why on earth would OpenAI attempt to cover up an incident like this when the evidence is sat out there on the public internet on dozens of different websites already?

      I expect we'll hear more about this soon. Gary Marcus has already called for a congressional investigation of OpenAI using this anecdote as part of his argument.

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

    4. 🔗 r/LocalLLaMA Georgi Gerganov on the Nvidia acquisition rss

      Georgi Gerganov on the Nvidia acquisition | Link: https://x.com/ggerganov/status/2095897173376618881 submitted by /u/CombinationKitchen76
      [link] [comments]
      ---|---

    5. 🔗 r/LocalLLaMA You can now run a 90M conversational LLM on the Sony PSP (hardware from 2004). Doesn't get more local than this. rss

      You can now run a 90M conversational LLM on the Sony PSP (hardware from 2004). Doesn't get more local than this. | Github link: https://github.com/thatblend/LLMPSP I wanted to see what the PSP can theoretically handle and I got my answer - a 90M model is about the max it can do without atrocious inference speeds. It's running around 0.5 - 0.6 tokens per second, which is very slow, but it's useable. Maybe 1-3 minutes for a reply. The model is actually fairly impressive for 90M parameters, it's not really useful in any real metric, but it can generate crappy poems, short stories, write non-functional code and sometimes it gets things right if you ask it what company makes macbooks, what is an LLM etc, while other times it just hallucinates a crazy answer. Fun. submitted by /u/liright
      [link] [comments]
      ---|---

    6. 🔗 r/LocalLLaMA Qwen3.8-27b is the first Local model im able to blindly trust rss

      You know that thing where you just throw a task at a frontier model and not have to supervise it worrying of it going off course? Qwen3.8-27b has officially gotten me to that point for local work. He has been doing non-stop continuous agentic work for 8+ hours and hasnt screwed up not one bit IT AMAZING!!

      EDIT: for all asking about my quant & harness and what i do for super long thinking/reasoning

      Harness : I Had it help me design its own agentic loop in pi harness. It holds well multiple compaction. I used to have tool and think tag generation issues but i got a chat template from somewhere(i forgot) but the chat template it fixed the issues paired with - -reasoning-format = deepseek

      Thinking : I limited reasoning budget to 2048 and its still pretty SMART even going down to 1024 holds well in my agentic loop. Im running huihui- abliteratedQ3_K_XL.gguf i need abliterated because i need it to use my computer mouse movement to solve captcha on bot detection (normal models are trained to reject that request) otherwise unsloth quants. Kv cache Q8 at 128k.

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

    7. 🔗 osolmaz/pi-workflows v0.16.4 release

      Changes

      • Allow Pi versions from 0.84.2 onward without an upper peer-version limit.
      • Test and validate Pi Workflows with Pi 0.85.0.
      • Add the official @earendil-works/pi-server runtime dependency required by the Pi 0.85.0 public SDK root import.

      Validation

      • Full TypeScript, Rust, installed-package, and end-to-end checks passed.
      • Real-model end-to-end test passed with openai/gpt-5.6-luna.
    8. 🔗 hacker news ida pro references New comment by s-macke in "Porting my 1993 Amiga game to Godot, with an LLM reading the 68000 assembly" rss

      I use a step-by-step approach:

      1. For each topic, write a result Markdown file in `spec/`.

      2. Identify the file formats.

      3. Reverse Engineer and extract all assets, followed by manual review. This works in 90% of the cases.

      4. Determine the compression/packing used for the executable. Most binaries used one of roughly five common executable packers.

      5. Unpack the executable manually.

      6. Use an ancient free IDA-Pro for disassembly, or a modified DOSBox to determine all code/data blocks and the relevant segment-register values for the 8086 architecture. In the second case I use my vibe-coded disassembler.

      7. Identify the major functional domains in the disassembly and split the files accordingly.

         ...

    9. 🔗 osolmaz/pi-workflows Pi Workflows 0.16.3 release

      Fixes

      • Kept workflow runner resume replies small by returning only the current run state.
      • Kept session history in the workflow server instead of sending it to workflow runners.
      • Stored required large replies as referenced content that runners read in verified chunks.
      • Prevented state pruning from deleting response content while an active runner still needs it.
      • Completed the public naming cutover to Workflow Server, Workflow Runner, Resource Manager, Resource Runner, and Managed Resource across the npm package and piw.

      Validation

      • Passed 1,161 TypeScript tests with coverage thresholds.
      • Passed all mock-provider Pi, installed-package, and Rust tests.
      • Passed Slophammer and dependency-boundary checks.
      • Passed the real-model openai/gpt-5.6-luna E2E with package version 0.16.3.
    10. 🔗 r/LocalLLaMA NVIDIA's $12,930,300,000.00 acquisition of Hugging Face contains an easter egg. The first 6 numbers of the acquisition price represent the decimal conversion of Unicode character U+1F917. The 🤗 emoji. rss

      NVIDIA's $12,930,300,000.00 acquisition of Hugging Face contains an easter egg. The first 6 numbers of the acquisition price represent the decimal conversion of Unicode character U+1F917. The 🤗 emoji. | From: Polymarket on 𝕏: https://x.com/Polymarket/status/2095646821485842805 Julien Chaumond on 𝕏: https://x.com/julien_c/status/2095822387895824836 submitted by /u/Nunki08
      [link] [comments]
      ---|---

    11. 🔗 osolmaz/pi-workflows Pi Workflows 0.16.2 release

      Fixes

      • Made the workflow host the only authority for assigning Pi model turns to workflow messages.
      • Prevented provider failures, terminal races, reconnects, and late reports from leaving stale workflow-turn ownership.
      • Made matching repeated reports return the saved result while keeping conflicting reports as errors.
      • Prevented ordinary chat turns from inheriting old workflow ownership.
      • Made terminal state commit before presentation and added durable terminal-message retries.
      • Gave composed managed effects exact execution identities so separate workflow branches cannot reuse one save key.
      • Added explicit worker start, resume, continuation, and restart commands.
      • Stopped workers that make no progress from restarting forever and exposed the recovery reason in the widget and viewer.
      • Kept paused workflows outside model-running timeout accounting.

      Validation

      • Passed 1,150 TypeScript tests with coverage thresholds.
      • Passed all mock-provider Pi, installed-package, and Rust tests.
      • Passed Slophammer and dependency-boundary checks.
      • Passed the real-model openai/gpt-5.6-luna smoke test before the release-only version change.
    12. 🔗 microsoft/markitdown Version 0.1.8b1 release

      This prerelease includes numerous small bug fixes. None adds new features or is expected to change output in typical cases. Nevertheless, the volume of changes warrants a cautious rollout.

      Please report any issues or regressions.

      What's Changed

      New Contributors

      Full Changelog : v0.1.7...v0.1.8a1

    13. 🔗 HexRaysSA/plugin-repository commits sync repo: +9 releases rss 
      sync repo: +9 releases

## New releases
- [deREferencing](https://github.com/danigargu/dereferencing): 2026.9.3
- [ida-mcp](https://github.com/hexrayssa/ida-mcp): 0.10.3, 0.10.2, 0.10.1, 0.10.0
- [ida-nexus](https://github.com/hexrayssa/ida-nexus): 0.10.3, 0.10.2, 0.10.1, 0.10.0
    14. 🔗 @binaryninja@infosec.exchange A bird? A plane? NO! It's Binary Ninja 6.0, codename "Krypton". Major new mastodon

      A bird? A plane? NO! It's Binary Ninja 6.0, codename "Krypton". Major new stable with massive performance improvements, built-in MCP, Binary Similarity, Extension Manager, TMS320C6x, New User Wizard, and so much more: https://binary.ninja/2026/09/03/binary- ninja-6.0-krypton.html

    15. 🔗 jank blog jank reimagines C++ errors and gets an official native package repo rss

      Welcome back! It's been three months since my last post and the amount of improvements to jank are staggering. Let me tell you all about it! Before jumping into the details, though, I want to say thank you to my Github sponsors and to Clojurists Together for sponsoring me this whole year. Thank you!

    16. 🔗 Filip Filmar wdbcvt: reading Vivado's undocumented .wdb waveform files rss

      As far as I’m aware, this is the first open source Vivado WDB to open-source FST converter in existence. Vivado’s xsim writes its waveforms to a .wdb file that normally only Vivado knows how to read. Well, now, wdbcvt can read them too. It also converts to FST, the waveform viewer format that can be opened by GTKWave and Surfer. It works on real simulations. The best one tried so far, is a a dual core RISC-V SoC with 5696 signals and 18875466 value changes. It takes 71 seconds to convert, but the result is usable. Below are the downloads, the usage, and pictures of the result.

    17. 🔗 New Music Releases The Cranberries - Live at the London Astoria II, 1994 rss

      The Cranberries - a new release is available:

      • 2026-09-04: Live at the London Astoria II, 1994 (Live)

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

      Visit muspy for more information.

    18. 🔗 New Music Releases Ben Folds Five - Shelved First Attempt rss

      Ben Folds Five - a new release is available:

      • 2026-09-04: Shelved First Attempt (Compilation)

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

      Visit muspy for more information.

    19. 🔗 Ampcode News Desktop rss

      Your orb now has a desktop you can see and control.

      Use the Desktop tab in any orb thread to get a high-resolution interactive Linux desktop.

      It's useful for verifying the agent's work when developing for Linux, Android, or the Chrome extension API, or when working with file formats that need to be opened in desktop applications. It's also useful for computer use, CAD, and anytime you just want a desktop in the cloud.

      Modibo Sissoko, an Amp user, sent in a video of how he tests .docx files exported by his application in LibreOffice to make sure they look right:

      And if you're curious what Puck does for fun when not helping you, turn on Fun Games in Desktop:

generated: September 07, 2026 at 07:37:03