🏡
  • ↔
  • →

to read (pdf)

  1. I don't want your PRs anymore
  2. JitterDropper | OALABS Research
  3. DomainTools Investigations | DPRK Malware Modularity: Diversity and Functional Specialization
  4. EXHIB: A Benchmark for Realistic and Diverse Evaluation of Function Similarity in the Wild
  5. Neobrutalism components - Start making neobrutalism layouts today

generated: June 14, 2026 at 12:30:57

  1. June 14, 2026
    1. 🔗 backnotprop/plannotator v0.20.2 release

      Follow @plannotator on X for updates

      Missed recent releases? Release | Highlights
      ---|---
      v0.20.1 | Pi extension install hotfix (pinned @pierre/diffs after a broken upstream release)
      v0.20.0 | Multi-repo workspace reviews, semantic diff overview, UI 2.0 themes and plan look chooser, leaner single-source skill install
      v0.19.27 | Kiro CLI integration, Glimpse native window, annotate-last message picker
      v0.19.26 | Amp plugin production fixes, Mermaid rendering fix, Settings flicker fix, update notification toast and shimmer
      v0.19.24 | Amp integration, configurable data directory, Auto Mode permission option, Pi plan approval fix
      v0.19.23 | Droid integration, Windows Pi AI fix, quieter update indicator
      v0.19.22 | Safari copy fix in plan viewer, CLAUDE_CONFIG_DIR support for session logs
      v0.19.21 | Ask AI in plan review and annotate mode, shared AI runtime, origin-aware provider defaults
      v0.19.20 | Interactive goal setup UI, OpenCode submit_plan fixes, browser no-op sentinel handling for Claude agents
      v0.19.18 | Edit-based submit_plan for OpenCode, Pi namespace migration, Codex annotate-last fix, OpenCode commands dir fix
      v0.19.17 | Reworked goal setup skill (interview-driven flow), CLI --version flag

      What's New in v0.20.2

      v0.20.2 is a code-review-heavy release of nine PRs, two of them from first- time contributors. The largest work rebuilds the all-files review view on Pierre's CodeView and adds a pipeline that keeps very large pull requests fast and complete instead of failing or rendering empty. Agent engine selection is unified across review and tour modes, the Pi extension gains a programmatic plan-mode control event, and several reliability fixes land across review cleanup, annotate error messaging, and markdown rendering.

      All-Files Code Review on Pierre CodeView

      The all-files code review surface was rebuilt on Pierre's CodeView renderer, replacing the previous custom diff view and its lazy-mounting layer. The new foundation virtualizes large diffs, renders change-type status in file headers and the file tree, and presents renames as old/path → new/path rather than as a blank change. The annotation model, drafts, feedback export, and keyboard shortcuts carry over unchanged, so the way you review and send feedback is the same.

      Large Pull Request Pipeline, Instant-Open Checkout, and Scroll Performance

      Reviewing very large pull requests previously hit several walls: GitHub refused oversized diffs outright, the local checkout blocked the review from opening, and some files came back from the platform with no patch content and rendered as empty stubs. This release addresses all three.

      When a platform refuses an oversized diff, Plannotator now pages through the per-file API and stitches the result into a unified diff, so the review still loads. When the platform withholds per-file content on a truncated diff, an amber "Partial diff · Load full diff" notice offers to recompute the exact diff locally, and a staleness check surfaces a refresh prompt when the underlying files change mid-review. The --local checkout no longer blocks startup: the review server opens as soon as the platform diff arrives and the checkout warms in the background, with agent jobs, full-stack diff, and code navigation waiting on it only when they need real files.

      Scrolling the all-files view was also reworked. Syntax highlighting moved off the main thread into a worker pool, lazy full-content augmentation no longer hitches mid-scroll, and visibility tracking was coalesced to once per frame. The result is smoother scrolling on large diffs, with a clean fallback to unhighlighted text if the worker pool is unavailable.

      Unified Agent Mode Engine Selection

      The agent panel's engine selection was reworked so review and tour modes share one consistent model. Previously the selection conflated provider and mode in a single setting; it now separates the active mode from the engine choice (Claude or Codex) for each, with existing settings migrated forward. The change makes it clearer which engine runs for review versus tour and removes a class of confusing defaults.

      Programmatic Plan Mode for Pi

      The Pi extension gained a plan-mode event so other extensions and automation can drive Plannotator's plan mode programmatically. A request can enter, exit, toggle, or query plan mode, and receives the resulting phase (idle, planning, or executing) in return. This opens the plan workflow to scripted and multi-extension setups on Pi without requiring a manual command or shortcut.

      Review Cleanup and PR Feedback Fixes

      Two reliability fixes for the review path. First, the standalone server now routes SIGINT and SIGTERM through its normal shutdown so the existing cleanup runs on interrupt or termination. Aborting a review while a large pull request was still checking out in the background previously left clone and fetch processes running and stale git worktree registrations behind; those are now cleaned up, with a second interrupt still forcing an immediate quit.

      Second, the review feedback sent to the agent on "Send Feedback" now includes the triage instruction (review the feedback, verify it against the code, and discuss before changing anything) for pull request reviews, not just local diffs. The instruction is appended whenever you send annotations and is correctly omitted for platform actions that post an approval or comment directly to the host. The behavior is consistent across Claude Code, OpenCode, and Pi.

      Clearer Annotate and Markdown Behavior

      Running plannotator annotate on a file type it does not support (for example a .cs or .pdf file) reported a misleading "File not found" even when the file was present. It now reports that the type is unsupported, lists the supported extensions, and points to plannotator review for code. Separately, custom angle-bracket autolinks are kept literal instead of having their contents parsed for markdown styling, so links that contain markdown-like characters render correctly.

      Additional Changes

      • README redesign. The project README was rebuilt around a feature table with a centered note on AI assistance and refreshed styling. #891 and #892

      Install / Update

      macOS / Linux:

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

      Windows:

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

      Extra skills (compound, setup-goal, visual-explainer), opt-in:

      npx skills add backnotprop/plannotator/apps/skills/extra

      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

      Then in opencode.json:

      {
  "plugin": ["@plannotator/opencode@latest"]
}

      Pi: Install or update the extension:

      pi install npm:@plannotator/pi-extension

      Droid: Install via the plugin marketplace:

      droid plugin marketplace add backnotprop/plannotator
droid plugin install plannotator@plannotator

      Amp: Install the CLI first, then copy the plugin:

      mkdir -p ~/.config/amp/plugins
curl -fsSL https://raw.githubusercontent.com/backnotprop/plannotator/main/apps/amp-plugin/plannotator.ts \
  -o ~/.config/amp/plugins/plannotator.ts

      Kiro CLI: The installer auto-detects Kiro and installs skills automatically. After installing the CLI, launch with:

      kiro-cli chat --agent plannotator

      Upgrading from before v0.20.0? Read the v0.20.0 release notes first; that release changed how skills install.

      What's Changed

      • feat(review): migrate all-files code review to Pierre CodeView by @backnotprop in #885
      • fix(markdown): keep custom angle autolinks literal by @ishowman in #867
      • fix(annotate): improve error message for unsupported file types by @ishowman in #870
      • refactor(agent-mode): Unify agent mode engine selection by @codythatsme in #868
      • feat(review): large-PR pipeline, instant-open checkout, scroll perf, and worker-pool highlighting by @backnotprop in #893
      • feat(readme): redesign README by @backnotprop in #891
      • style(readme): center AI note under feature table by @backnotprop in #892
      • fix(review): signal-safe cleanup + triage suffix for PR feedback by @backnotprop in #914
      • feat(pi): add programmatic plan mode event by @Termina1 in #898

      New Contributors

      Contributors

      @ishowman landed two fixes in their first contributions: a clearer error from plannotator annotate when a file type is not supported, and a markdown fix that keeps custom angle-bracket autolinks literal instead of styling their contents. @Termina1 added the programmatic plan-mode event to the Pi extension, letting other extensions and automation enter, exit, toggle, or query plan mode and read back the resulting phase. @codythatsme unified agent mode engine selection so review and tour modes share one consistent model for choosing between Claude and Codex, with existing settings migrated forward.

      This release also resolved community-reported issues. @NikiforovAll reported the misleading "File not found" message from plannotator annotate on unsupported file types, with a concrete .cs reproduction. @Thraka reported the markdown autolink rendering issue, and @MannXo contributed to the discussion that shaped the fix.

      Full Changelog : v0.20.1...v0.20.2

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

## New releases
- [IDAGuides](https://github.com/libtero/idaguides): 1.1.0

## Changes
- [IDASQL](https://github.com/allthingsida/idasql):
  - 0.0.10: archive contents changed
- [xray](https://github.com/hexrays-plugin-contributions/xray):
  - 2025.9.24: archive contents changed
  2. June 13, 2026
    1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-06-13 rss

      IDA Plugin Updates on 2026-06-13

      Activity:

      • ida_scripts
      • Rikugan
        • 6f42c096: Merge pull request #58 from buzzer-re/dev
        • 75321fb1: feat(ui): add "Don't auto-load chats" option (#51)
        • 09fdfefb: Merge pull request #57 from buzzer-re/dev
        • d66fa7f2: fix(codex): fetch models live on Windows; smooth chat streaming & scroll
      • rikugan
        • 6632f82b: test(agent): port bulk_renamer, subagent_manager, pseudo_tool_schemas…
        • 4b2baca3: test(a2a): add HTTP and loop integration tests
        • 844ac60b: feat(agent): add /a2a slash command for explicit user delegation
        • bb8ddc10: feat(ui): add A2ABridgeWidget with 4-tab tools panel integration
        • a531509e: feat(agent): add delegate_external_task pseudo-tool for LLM-initiated…
        • 2bace4e1: fix(a2a): use background thread for responsive cancel in SubprocessBr…
        • bfaceb78: feat(a2a): add A2ADispatcher as single entry point for tool/widget/slash
        • 9eb6486b: feat(ui): backport IDAThemeWatcher from fork for live theme reload
        • afa5f58e: feat(core): add optional dependency detection helpers
        • ee842aba: chore: add .scratch/ to .gitignore
        • d81cb91f: fix(orchestra): subagent event poll loop runs once, loses events
        • a8e80600: test(isolation): add PySide6 dev dep + mark 5 pre-existing Qt test po…
        • 57caf5e8: fix(security): block argv injection in a2a SubprocessBridge
        • ed2f5175: docs: update PROJECT_MODIFICATION_PLAN with session progress and next…
        • 3b9b1d65: refactor(providers): tighten registry.py docstrings and method organi…
        • 51c19c7e: feat(providers,agent): port auth_compat and pseudo_tool_schemas from …
        • 9cd3985d: feat(providers): port codex_provider from upstream fork
        • b57c9739: fix(security): block path traversal in research_mode note writing
        • a5a2ceb8: docs: list 12 built-in skills in README, add evaluation workflow + mo…
        • 14c77c43: chore: remove binary archives and debug file from repo, sync .gitignore
      • ToCode
        • 3525f850: Merge pull request #4 from buzzer-re/dev
        • 4866aa32: Merge branch 'dev' of github.com:buzzer-re/ToCode into dev
        • a5ce3b6d: Fix Windows installer PATH handling and improve installer UX
        • a3d82f3e: Fix Windows installer PATH handling and improve installer UX
    2. 🔗 Simon Willison Publishing WASM wheels to PyPI for use with Pyodide rss

      The Pyodide 314.0 release announcement (via Hacker News) includes news I've been looking forward to for a long time:

      You can now publish Python packages built for Pyodide (or any Python runtime compatible with the PyEmscripten platform defined in PEP 783) directly to PyPI and install them at runtime.

      Previously, the Pyodide maintainers had to maintain, build, and host over 300 packages ourselves. This created a significant burden on our maintainers and became a major bottleneck for the community, as every new package required manual review.

      Moving forward, package maintainers can simply build and publish Pyodide wheels to PyPI, just as they do for native wheels on Linux, macOS, or Windows.

      Here's the PR to PyPI itself supporting this, which landed on April 21st.

      I adore Pyodide, and have been frustrated in the past by this limitation. It's possible to compile C or Rust extensions to WASM in a wheel file, but before now there was no easy way to distribute them.

      Thanks to the efforts of a whole lot of people, that's now been fixed!

      Trying it out with luau-wasm

      I decided to celebrate by finding something I could package. I have quite a few experimental Pyodide projects lying around, but the best fit for this looked to be my Luau WebAssembly research spike from 9th March.

      Luau is a "small, fast, and embeddable programming language based on Lua with a gradual type system", developed by Roblox and released under an MIT license.

      It's written in C++. I already knew it was possible to compile it to WebAssembly and get it running inside of Pyodide, so I set Codex + GPT-5.5 xhigh the task of packaging my experiment up and publishing it to PyPI using GitHub Actions.

      It took some iteration, but here's the result: luau-wasm is a brand new PyPI package which publishes a 276KB luau_wasm-0.1a0-cp314-cp314-pyemscripten_2026_0_wasm32.whl file which can be used in Pyodide like this:

      import micropip
await micropip.install("luau-wasm")
import luau_wasm
print(luau_wasm.execute(r'''
local animals = {"fox", "owl", "frog", "rabbit"}
table.sort(animals, function(a, b) return #a < #b end)
for i, name in animals do print(i .. ". " .. name .. " (" .. #name .. ")") end
'''))

      You can run that code in the Pyodide REPL demo to see it in action.

      The GitHub repo for luau-wasm includes all of the build and deploy scripts (using the latest cibuildwheel) and also deploys an HTML demo page which loads Pyodide, installs luau-wasm and provides an interface for trying it out: https://simonw.github.io/luau-wasm/

      Screenshot of a web app titled "Luau WASM" with subtitle "Run Luau in the browser through Pyodide after installing the luau-wasm WebAssembly wheel from PyPI." A green "Ready" status badge is at top right. Below are example buttons: "Hello World", "Variables", "Tables", "Fibonacci", "Runtime Error". A "LUAU SOURCE" code editor contains: local function fib(n: number): number / if n < 2 then return n end / return fib(n - 1) + fib(n - 2) / end / local out = {} / for i = 0, 12 do / table.insert(out, tostring(fib(i))) / end / print(table.concat(out, ", ")). On the right is an "OUTPUT" panel with a "Copy" button showing dark terminal output: 0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89, 144. At the bottom left are a blue "Run" button, a "Clear" button, and the text "6.0 ms".

      How many packages are using this so far?

      I was curious to see how many packages are currently publishing wheels for this platform.

      After some tinkering with ChatGPT I got to this BigQuery SQL which I ran against PyPI's public dataset on BigQuery. Here's the raw JSON of query results and here's a SQLite SQL query in Datasette Lite which dedupes packages by most recent upload date.

      If the query is right, there are currently 28 PyPI packages publishing with the new pyemscripten_202*_wasm32 tags:

      luau-wasm, uuid7-rs, cmm-16bit, pyOpenTTDAdmin, imgui-bundle, numbertoolkit, bashkit, geoarrow-rust-core, arro3-io, arro3-core, arro3-compute, onnx, powerfit-em, tcod, chonkie-core, tokie, robotraconteur, pydantic_core, yaml-rs, cadquery-ocp-novtk-OCP.wasm, uuid_utils, base64_utils, pycdfpp, lib3mf-OCP.wasm, typst, toml-rs, onnx-weekly, dummy-pyodide-ext-test

      Here's hoping we see a whole lot more of those showing up over the coming months and years.

      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. 🔗 r/LocalLLaMA This is coming to Chinese open source models pretty soon. - prepare yourself. rss

      This is coming to Chinese open source models pretty soon. - prepare yourself. | Don’t be surprised . Prepare yourself. This could happen anytime. There’s a bigger strategy here than just Fable5 submitted by /u/MLExpert000
      [link] [comments]
      ---|---

    4. 🔗 r/LocalLLaMA Pi Setup that pretty much replaced Claude Code for me rss

      Pi Setup that pretty much replaced Claude Code for me | I've been using Pi with Qwen3.6-27B a lot as my daily driver for more than a month and this setup almost replaced Codex/CC for me entirely. I use it with the advisor extension, with the advisor usually being GPT-5.5 and it has been great for me so far. I sometimes use OpenCode too but I keep coming back to this setup especially for local models.

      • Support for seamlessly onboarding local models
      • Custom footer that shows token usage, cost and inference speed
      • 10 themes
      • Many useful+cosmetic extensions
      • Context breakdown command similar to claudecode
      • Configurable permission system
      • Few custom skills and some useful publicly available skills
      • Sync/backup script for easy setup anywhere

      Hope you find this useful. If you have any ideas to improve I'd love to hear. https://github.com/abhinand5/pi-setup Edit 1 : Local LLM details on this comment below. submitted by /u/abhinand05
      [link] [comments]
      ---|---

    5. 🔗 earendil-works/pi v0.79.3 release

      Fixed

      • Fixed inherited OpenAI GPT-5.4/GPT-5.5 and OpenAI Codex GPT-5.4/GPT-5.4 mini/GPT-5.5 context window metadata to use the observed 272k-token Codex backend limit, avoiding a billing hazard from prompts above Codex's accepted limit (reported by @trethore).
    6. 🔗 r/LocalLLaMA when fable gets banned but it's ok because you've about to download qwen3.7_67b_21a_mythos_father_fable_mother_distilled_ablated_ablitereted_uncensored_agi_sparse_attention_MTP_SuperHOT_q6_maybe_q7_AGI_FINAL.gguf from huggingface rss

      title

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

    7. 🔗 syncthing/syncthing v2.1.2-rc.2 release

      Major changes in 2.1

      • Devices and folders can now be grouped in the GUI by setting the new
        group attribute.

      • HTTP and HTTPS proxies with support for CONNECT can now be used, in
        addition to the existing support for SOCKS proxies (the environment
        variable all_proxy=https://...).

      • Block indexing can be turned off for folders where it's more desirable to
        optimise for reduced database size and overhead than minimal transfer
        size (the blockIndexing attribute on folder configuration).

      • GUI login session duration can be configured to be longer or shorter than
        the default one week, or set to infinitely long. The cookie path can also
        be adjusted. (The sessionCookieDurationS and sessionCookiePath
        attributes in the GUI configuration.)

      This release is also available as:

      • APT repository: https://apt.syncthing.net/

      • Docker image: docker.io/syncthing/syncthing:2.1.2-rc.2 or ghcr.io/syncthing/syncthing:2.1.2-rc.2
        ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

      What's Changed

      Fixes

      • fix: on Windows don't allocate console if not opened inside one by @Shablone in #10726
      • fix(connections): do not report connection metrics for self (ref #10509) by @calmh in #10724
      • fix: let umask do the thing by @calmh in #10723
      • fix(fs, model): improve symlink resilience in file shortcut by @calmh in #10739
      • fix(protocol): always expect & validate block hash in requests by @calmh in #10738
      • fix(protocol): be more stringent about blocks in non-file entries by @calmh in #10737
      • fix(protocol): loosen restriction on size of directory entries by @calmh in #10743

      Other

      • chore(syncthing): open URLs via Windows API instead via cmd.exe by @Shablone in #10712
      • chore(db, model): separate methods to drop a device vs its files by @imsodin in #10480
      • build(deps): update dependencies by @calmh in #10740

      New Contributors

      Full Changelog : v2.1.1...v2.1.2-rc.2

    8. 🔗 r/LocalLLaMA We should set up a torrent network for open source models. rss

      Was just thinking about this due to recent events.

      Hugging Face is a US-based company, legally incorporated as Hugging Face, Inc. with its official headquarters located in Brooklyn, New York.

      It seems like a pretty big single point of failure for local models.

      Maybe a distributed network mirror of models would be a good backup.. you know.. just in case.

      I know other counties could host models.. but distributed seems safest.. what do you guys think?

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

    9. 🔗 r/LocalLLaMA New model on huggingface rss

      New model on huggingface | https://huggingface.co/prefeitura-rio/Rio-3.5-Open-397B A qwen finetune. Looks pretty even with qwen 3.7 plus, except it's actually open weights. Disclosure: I work as a researcher for the city government of Rio de Janeiro, which developed this model. submitted by /u/krzonkalla
      [link] [comments]
      ---|---

    10. 🔗 r/LocalLLaMA Friendly reminder rss

      Friendly reminder | If you don't have it on your own drive, someone is going to take it away, enshittify it, bar you from accessing it, censor it, and hike the prices of it sooner or later. submitted by /u/Disposable110
      [link] [comments]
      ---|---

    11. 🔗 r/LocalLLaMA Anthropic forced to abruptly disable Fable 5 & Mythos 5 globally by US Gov over a jailbreak. This is exactly why we need local models. rss

      I just saw this statement regarding Anthropic being hit with an emergency export control directive from the US government. They were forced to pull the plug on Fable 5 and Mythos 5 for all customers globally. The tl;dr is that the government got spooked by a narrow jailbreak (which basically just sounds like asking the model to fix vulnerabilities in a specific codebase), and forced a complete shutdown without a transparent process. Anthropic is pushing back, but the API access is completely gone for now.

      A centralized API can be nuked globally at a moment's notice by a single government decree over something as trivial as a prompt lol.

      Banning a model for hundreds of millions of users because someone figured out how to make it fix software flaws is insane. Anthropic admits this standard would halt all new frontier models.

      https://www.anthropic.com/news/fable-mythos-access

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

    12. 🔗 r/LocalLLaMA Statement on the US government directive to suspend access to Fable 5 and Mythos 5 rss

      Statement on the US government directive to suspend access to Fable 5 and Mythos 5 | submitted by /u/artisticMink
      [link] [comments]
      ---|---

    13. 🔗 tonsky.me Every Frame Perfect rss

      A while ago I was reading about Wayland and this quote stuck with me:

      A stated goal of Wayland is “every frame is perfect”.

      And I think this is a goal we should all aspire to. Wayland is talking about the technical side of things (modern GPU stacks are very complex and Wayland is trying to take control back) but it could be applied to UI too.

      The rule of thumb is:

      If I take a screenshot of your app at any moment, it must make sense

      Why care about every frame? It builds trust. Users can’t see the code, so UI is the only way for them to judge the quality of the app. If UI looks good, that means developers had time to polish it, which means that they probably spent a comparable amount of time to iron out the code. It’s a heuristic, but a reasonable one.

      Now, what does it mean in practice? I can think of a few things:

      • No white flashes between screens.
      • No partially loaded content.
      • No relayout while content loads.
      • Internally consistent. If one part of the UI says “1 update available”, another part should not say “Checking for updates...”
      • Precise animations.

      Animations often end up being forgotten. A UI might look great in both start and end states but very janky in between. Like this:

      If you feel like there are weird things going on there, there are! Look at slowed down version:

      Now let’s apply our rule and take screenshots in the middle of the animation. This doesn’t look right:

      Neither does this:

      Both of these frames are not perfect.

      Let’s look at another example. Safari:

      Placeholder text here moves from the center but cursor animates from the left position:

      Not the end of the world by any means, but it does create a feeling that these two components are not in sync with each other. Next thought: maybe they weren’t designed together? If so, then they might not work well together. That’s how trust is lost.

      This desynchronization can lead to a lot of confusion. For example, in Photos, when switching between Crop and Adjust mode, picture snaps into place immediately but the crop border is animated:

      This creates a false feeling that something subtly changes when you switch between modes. And you know what? I don’t want my UI to give me false feelings. I want it to be a precise instrument, not an animated toy.

      Sometimes animations are supposed to help you understand a transition, so it’s doubly sad when they make it harder. Follow the magnifying glass:

      Same with Youtube. They had the simplest task in the world: move a rectangle from one position to another! Yet they decided to do something very strange:

      Can you explain this? Does it make sense?

      Probably a technical limitation of the DOM architecture they decided earlier on. I call these situations “The technology has outsmarted the programmer”. But no matter the reason, the result is an imperfect frame.

      Sometimes animations are left out as an afterthought. Whatever happens, happens. Then we get this:

      The details are fascinating to watch:

      So yeah. Please pay attention not only to the start and end states, but also to everything in between. Every frame matters.

      I’ll leave you with this unprovoked zoom animation from Preview app. Take care!

    14. 🔗 Armin Ronacher Dangerous Technology For Americans Only rss

      There is a bit of schadenfreude on Twitter right now about Anthropic being hit by the US government's export control directive to suspend access to Fable and Mythos. Anthropic and their leadership have spent a lot of time and effort describing its own technology as dangerous and in need of strict controls and regulation. Now that the US government appears to have taken that framing seriously and told them to turn it off for foreign nationals I can see why people are making fun of that situation.

      I understand the reaction, but I urge you to not entertain it for too long because it is a giant distraction. The important part is not that Anthropic's safety language came back to bite them but the line the US government is drawing: this technology is apparently so powerful that only Americans should have it.

      We are on a clear path towards a world of division. One should think that if a model is too dangerous for everyone, then it is too dangerous for Americans too. Instead the US is treating these models like weapons that need to be controlled. It is not just about capabilities, it is about racism and nationalism. If you have the wrong passport, you are not to be trusted. This is a very different thing from safety, and Europeans should pay close attention to it.

      Safety and National Control

      The directive, as Anthropic describes it, applies to foreign nationals whether they are inside or outside the United States, including foreign national Anthropic employees. That is an astonishing boundary if you think about it. We moved from "do not sell this model to hostile governments" to nationality itself being the defining boundary. This should be a wake-up call to Europeans in and outside the US, and quite frankly, any non US citizen.

      A lot of AI safety discourse presents itself as universal: humanity, catastrophic risk, safeguards, responsible deployment. Even Anthropic's own writings start out that way, but yet every time regulation is discussed there is an overtone of national security and that it cannot get into the wrong hands. It's not just Anthropic, it's the entire US based discourse on AI. The foundation is that the US has moral superiority and others are not to be trusted. That there are other countries are authoritarian, that they lack freedoms.

      That should make us uncomfortable, not just Europeans, but particularly us. It is also a situation you cannot regulate yourself out of. European technology policy is entirely unprepared for this, because this is not a question of regulation but a question of might and power, something that Europe lacks.

      Europe has spent years trying to regulate large American technology companies, sometimes for good reasons. I am not reflexively against that. The DMA matters because access matters. Users should have agency over their devices, their data, and the software they run. But regulation is a useless substitute for capability and we are lacking that. Regulation might try to force open doors but if those doors only come from American or Chinese companies, then that accomplishes very little.

      Also let's not be naive in that this is a negotiation of money and force. The US is in that position because the US has a mighty military. The US can bomb nations anywhere in the world, force international trade routes closed and get away with it. That's true leverage.

      Oh Europe

      Europe is dependent on the United States in ways that are becoming increasingly impossible to ignore. We depend on American cloud providers, operating systems, developer platforms and now AI models and internet from satellites. We also depend on global semiconductor supply chains we do not control. If access to frontier AI becomes a matter of American national security policy, Europe is not a peer in that conversation and might not even be a market.

      That is a humiliating position, but one that happened entirely intentionally.

      European citizens and politicians still have not managed to move beyond blaming the EU for its failures. We built and maintained fragmented markets and then pretended we had a single one. We let company formation, hiring, equity compensation, tax, notaries, KYC, banking, and cross-border services remain much harder than they need to be and we are playing these rules against each other. Not just on the European level, but within every single member state. We protect the trusts and established enterprises, who are risk averse and entrenched, instead of trusting the next generation to build great companies. We created a culture where process becomes an excuse for low agency. We made it hard to build new and large companies and then act surprised when our most ambitious founders move somewhere else or just decided to incorporate their companies in the US.

      Increasingly, Europeans who want to build very large technology companies move to the United States. They do it because the capital markets are better, the startup infrastructure is better, employee equity is better understood. I cannot blame anyone doing it, and I'm guilty of this myself as we have incorporated our holding in Delaware. If you are trying to raise serious money, hire aggressively, and move quickly, the US often looks like the only game in town. Because quite frankly: it is.

      But this is why we are on a dangerous death spiral already. Talent leaves because the ecosystem is weak and the ecosystem stays weak because talent leaves. Infrastructure makes the world: build excellent swimming pools and you will grow a generation of great swimmers.

      The temporary task is straightforward but uncomfortable: Europeans need to believe in themselves enough not to surrender to American gravity. Moving to the US as a founder or tech employee is rational and individually it is often the right decision. But if every ambitious person treats Europe as a lost cause, then Europe becomes one. If everyone with agency leaves, the only people left to shape the system are the people most comfortable with the system as it is. Then we really should not be surprised when nothing changes.

      Europe needs more ambition, more ownership, more urgency, and more willingness to build. It needs less resignation. It needs to stop confusing regulation with strategy and dependency with virtue. We need to deregulate where rules serve mostly as protectionism. We need capital markets that can fund companies at the scale modern technology requires. We need employee ownership to become normal rather than exotic. We need a real single market for services, not just speeches about one. We need countries to stop fighting each other while claiming to act in the European interest.

      Most importantly: we need to stop blaming the politicians. Too many European companies are adding to that bureaucracy entirely out of their own choice. They drown you in paperwork. At one point I had to sign a four page contract for a 120 Euro lamp at an Austrian retailer, just to pick up from their store 15 minutes later. Sometimes I cannot get a speaking engagement at a European event without someone sending me complex rights waivers over. It's all just paperwork protection against potential downsides.

      When we do not have the power to influence, we should at least understand why and where things are failing. Too many entrepreneurs are blaming EU regulation for failures that are originating within the member states. EU regulation is the result of a democratic process between countries that are lobbying in favor of their local industries against others in the same economic bloc. No amount of abolishment of the EU is going to fix this harsh reality. Nothing more demonstrates this as the inability for cross-border M&A in the European Union. It's not the EU that blocks it, it's the country that loses out.

      Strengthening Europe is necessary because weakness makes us pawns. A Europe that cannot build, cannot finance, cannot coordinate and cannot defend its own interests will not be treated as an equal. It will be regulated around, export-controlled around, consulted after the fact or not consulted at all.

      The American Trap

      I do not want the lesson to be that Europe simply needs to turn itself into a copy of the United States. The US has solved some things that Europe has not. It has deep capital markets, a much stronger culture of ownership, a greater tolerance for risk, and institutions that often try to make progress possible rather than explain why it cannot happen. It also has achieved an internal level of integration that is unparalleled in Europe. Tremendous advantages!

      But the American path is not obviously a healthy one in all aspects. It tends to take paths with a lot of conflict and wars, a lot of internal societal division and deep inequalities. It centralizes powers away from citizens in the presidency and people with money. You are still trading one set of failures for another. You are at the whim of the US government and its strict rules and regulations. The US barely manages to uphold the rights for its own citizens today.

      We should be honest about both sides. You do not win by pretending that Europe is fine. You also do not win by pretending that America has figured everything out.

      We must not be blind to all the signs of how international cooperation is falling apart around us. The US no longer talks to European governments before implementing orders that directly affect Europeans. It is threatening to take Greenland, the territory of Denmark, one of its oldest allies. Treaties, alliances and institutions have lost all their worth.

      All that matters even if our own lives are focused on building companies, creating wealth, hiring people and making things. Our individual path to success is one thing, but it depends on a world where contracts work, visas work and don't change on a moment's notice, trade routes stay open, payment systems function, and families are not torn apart by border regimes or wars. If the world descends into chaos, our basic needs cannot be considered met just because we have a great salaries or equity or investors that trust us.

      This is why strengthening Europe cannot be the final goal. A stronger EU is, at best, a temporary defense against a darker world and not an excuse to replace American nationalism with European nationalism. The long-term answer cannot be bigger and bigger blocs fighting over who may use which model, which chip, which cloud or which trade route.

      The Way Out Is Cooperation

      I'm not asking here for Europeans to get their shit together just to compete with the US or China. Maybe I hope that this is a thing that develops, but the goal absolutely cannot be that we accept the deterioration of international relationships long term.

      I truly believe that Open Source matters and international cooperation matters. It is not a magical answer to every problem, but it is one of the few paths we have that does not naturally lead to total concentration of power.

      If frontier AI becomes something only large corporations and governments can control, then everyone else becomes dependent on their judgment. That is a bad place to be. Corporations will optimize for their incentives, as well structured as they might be, and governments will optimize for more and more power. Right now we're on a path in which access to general-purpose capability is mediated by a small number of actors with tremendous powers.

      I'm not naive in pretending AI cannot carry inherent risks. Open systems are messy, they can be misused and they create uncomfortable questions about dual- use capabilities. I do not want to wave that away but closed systems do not make those questions disappear either. Moving the power to decide into fewer hands is not a solution I believe in. And I would have the same opinion if I was a US citizen living in the US.

      Any path that puts large blocs in a constant fight against each other has despicable downstream effects that result in the removal of individual rights. It's entirely pointless for the US to talk about freedoms that do not extend to non-US citizens and the same is true for Europe or any other country. We might accept these restrictions temporarily, but we absolutely cannot accept them long term for the inhumane effects that they can cause.

      If we believe this technology can be used for good, then broad access matters and our goal should be to restore the international rule of law, and not to further weaken it. If we find ourselves in a war against our friends from other countries, cold or hot, we have failed as society.

      The world we should be working back toward is one of international cooperation, globalization in the best sense of the word, and human dignity. The internet has made our lives irreversibly international: every day people fall in love across borders, marry across languages, move across continents, and work with friends they may never meet in countries they may never visit. Identifying too strongly with any one country in that world is a fool's errand.

      Over the last decade too many of the people I got to know through Open Source were directly dragged into a war. I want to believe there is a way for us to break this cycle. We should be repairing failed states, rebuilding trust between people, and finding ways to cooperate again instead of letting the richest countries arm themselves and fight over who gets to control the future and narrative. Of course I want Europe to become stronger so it can stop being a pawn, but if we mistake that temporary need for the destination, I will be deeply disappointed.

      The way out is not American supremacy, Chinese supremacy or European supremacy. The way out is to climb back toward cooperation before the alternative becomes war.

      Artificial Intelligence is quickly becoming another instrument of militarization and national rivalry, when it could be one of the most powerful tools for cooperation we have. We should be using it to help people across societies and languages understand one another, not fighting over who gets to control it.

  3. June 12, 2026
    1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-06-12 rss

      IDA Plugin Updates on 2026-06-12

      Activity:

    2. 🔗 r/LocalLLaMA Diffusion Gemma is 4x faster, but makes 6x more mistakes! rss

      Diffusion Gemma is 4x faster, but makes 6x more mistakes! | Benchmarked the new Gemma diffusion model against its autoregressive twin on a single H100 (FP8). We gave each the same three tasks: write a Steve Jobs biography, the history of Tetris, and the story of BeOS - every next topic less popular than the previous one. Then we fact-checked every claim in every answer. Gemma4 got 45 facts right, 5 wrong. DiffusionGemma got 33 right, 28 wrong. The less popular the topic, the worse it got: 4 mistakes on Jobs, 12 on Tetris, 12 on BeOS. It named Clara Clley as Steve Jobs' mother, invented a colleague for Pajitnov named Geri Gulovik and priced the BeBox at $9,999. The real one cost $1,600. Outputs:
      Gemma4 26B A4B: 218 tok/s · 15.1s total · 45 facts · 5 mistakes
      DiffusionGemma 26B A4B: 763 tok/s · 3.7s total · 33 facts · 28 mistakes The reason is simple. DiffusionGemma throws 256 tokens on the screen at once and polishes them pass after pass until the text sounds smooth. Smooth is all it cares about: a fake name, date or number sounds just as smooth as a real one, so it stays. Regular Gemma4 meanwhile writes one word at a time and checks every new word against everything before it. Google says it themselves in the launch post: quality is lower, use regular Gemma 4 when facts matter. Open source Local Ai models harness: Atomic.Chat (I'm founder, we support GGUF models, MLX Apple Silicon, MTP and Google TurboQuant for long context window, working on Diffusion support via llama.cpp) submitted by /u/gladkos
      [link] [comments]
      ---|---

    3. 🔗 earendil-works/pi v0.79.2 release

      New Features

      • Clearer Bedrock validation guidance - Amazon Bedrock data retention validation errors now link to AWS data retention documentation. See Amazon Bedrock.

      Added

      • Added an experimental first-time setup flow behind PI_EXPERIMENTAL=1 that asks for a dark/light theme choice (preselecting the detected appearance) and opt-in analytics data sharing on first launch with the default agent directory; opting in stores a trackingId in settings.json (#5587 by @vegarsti).
      • Added AWS data retention documentation links to inherited Amazon Bedrock unsupported data retention mode validation errors (#5561 by @unexge).

      Fixed

      • Fixed project trust detection to ignore global ~/.pi/agent state when running from $HOME, and made pi update use only saved or explicit project trust without prompting (#5619).
      • Fixed experimental first-time setup to skip forked sessions instead of rerunning the setup prompts (#5627 by @vegarsti).
      • Fixed inherited OpenAI-compatible context overflow detection for parenthesized maximum context length (N) errors (#5677).
      • Fixed inherited OpenAI GPT-5.4/GPT-5.5 and OpenAI Codex GPT-5.4/GPT-5.4 mini/GPT-5.5 context window metadata to match current OpenAI limits (#5644).
      • Fixed inherited Anthropic refusal stops to preserve provider stop_details explanations in error messages (#5666 by @rwachtler).
      • Increased the inherited OpenAI Codex Responses SSE response-header timeout to 20 seconds to reduce false-positive stalls while retaining the bounded wait introduced for zero-event hangs (#4945).
      • Fixed inherited Claude Fable 5 thinking-off requests to omit Anthropic's unsupported thinking.type: "disabled" payload (#5567 by @tmustier).
      • Fixed inherited late tool progress callbacks after tool settlement to be ignored instead of emitting stale tool_execution_update events (#5573).
      • Fixed inherited user-message transcript rendering so standalone + messages no longer render as - (#5657).
      • Fixed inherited slash-separated fuzzy queries so provider/model completions remain matchable after insertion.
      • Fixed inherited WezTerm inline Kitty image rendering so reserved row clears do not erase all but the top strip of tool image previews (#5618).
      • Fixed inherited editor wrapping for CJK text to break at character boundaries instead of leaving large trailing gaps (#5585 by @haoqixu).
      • Fixed inherited loose Markdown list rendering to preserve blank-line separation between list items (#5562 by @Perlence).
      • Fixed --model resolution for authenticated custom model IDs whose slash prefix matches an unauthenticated built-in provider (#5643).
      • Fixed /fork to keep session parent chains connected when the forked path contains labels (#5669).
      • Fixed /share and /export HTML exports to use the active fallback theme when the configured custom theme no longer exists (#5596).
      • Fixed custom fallback model IDs with :<thinking> suffixes to preserve the requested thinking level when the provider template model does not advertise reasoning (#5560 by @haoqixu).
    4. 🔗 r/LocalLLaMA Local LLMs aren't democratic anymore... the hardware barrier has gotten out of hand. rss

      When we first started experimenting with local LLMs, it was a completely different story!

      We were using gaming GPUs to tinker around. 8GB or 16GB of VRAM (which wasn't even a given for everyone) was the norm, and so many people could actually get their hands dirty and experiment. Let’s just forget for a second that long crypto-mining phase that bloated the market and caused shortages... but today? Today, if you don't have high-end hardware, experimenting has become way too difficult.

      I know some of you will reply saying, " Hey, I'm using an RTX 3090 and I'm 100% ok with it," but at the risk of sounding unlikable, I honestly think that misses the point.
      We are in 2026 now and a RTX 6000 Pro should be the baseline equivalent of what a 3090 was years ago! The market is completely detached from reality, and local inference is no longer as democratic as I thought it would become.
      3090 was expensive but accessible at the time. RTX 6000 is 10-13k today! s*t!!!

      Oh, and one last thing: if you're planning to leave a comment hyping up Qwen 3.6, please don't. That model gets mentioned so much around here that I'm starting to think it's not even organic anymore. I suspect too many comments mentioning Qwen even when talking bout Gemma4 are manipulated!

      I just really want to talk about how hardware access is no longer democratic. You need way too much money just to run something that, at the end of the day, is just a tool it doesn't automatically generate value for you.

      Sorry for my English... I have this deeply rooted concept in my head, but I'm not sure if I'm fully conveying it!

      submitted by /u/Medium-Technology-79
      [link] [comments]

    5. 🔗 r/LocalLLaMA MiniMaxAI/MiniMax-M3 · Hugging Face rss

      MiniMaxAI/MiniMax-M3 · Hugging Face | Minimax m3 weights are out !! It has ~428B parameters and ~23B activated parameters. submitted by /u/mlon_eusk-_-
      [link] [comments]
      ---|---

    6. 🔗 r/LocalLLaMA We should heavily discourage and moderate cloud API (deepseek api, GLM api, etc.) topics and discussion. This is LOCAL first. rss

      I’m just some fucking guy. This is just some fucking opinion.

      I’ve seen tons of stealth marketing or related topics on this subreddit about how great or how easy it is to use some random subscription api. Why the fuck are we allowing people to so casually talk about how much more affordable their zai subscription is than Claude? Who cares? I don’t give a singular care if the eastern (bless them for their otherwise great contributions to OSS LLMs) companies can offer 35 trillion tokens for 25 cents. My fucking data would still be going to them and their prices can fucking change whenever they want!

      I am here to learn about if -p-e-w- is about to get sued by Facebook for facilitating gooning on llama models. I am here to learn about why it took so long for llama.cpp to allow tensor split with q8_0 kv cache. I am here to learn about why NPUs are so unbelievably useless to this day for OUR NEEDS. Does anyone actually know if you can safely heretic Gemma 4 31B QAT and still reap the benefits of the QAT at the end?

      This community is supposed to be, in my opinion, first and foremost about building your own infrastructure at HOME to do things YOUR way on YOUR owned hardware.

      The ONE, ONE exception I can see where it is OKAY to bring up Claude pricing, Deepseek pricing, GLM pricing, is when showing benchmarks EXPLICITLY against a locally available set of models. Even if kimi-whatever-the-fuck 9000 nvfp4 needs like 8 GPUs, it is OKAY to compare its performance against commercial solutions. Yes, my friends, all online apis are commercial solutions. They are closer to Claude than further. Yes, I said it. I said it cus I can. -Bruno Mars.

      It is NOT okay to start talking about how you’re suddenly happy with how affordable some bumfuck open router model is. You don’t control it. You don’t own it. It’s not fucking yours. It’s not local. It’s not encrypted on their server. Your shit is processed in plain text. Jesus fucking Christ.

      Oh and some of you think renting a VPS is in the spirit of building local independent infrastructure, I’ll get to that another day.

      Bottom line: We need a specific reporting rule that says “Stealth marketing / promoting cloud providers.”

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

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

## New plugins
- [ida-rpc](https://github.com/bkerler/ida_rpc) (0.1.0)

## New releases
- [IDASQL](https://github.com/allthingsida/idasql): 0.0.17
- [ida-bochs-binaries](https://github.com/hexrayssa/ida-bochs-binaries): 1.0.1

## Changes
- [IDASQL](https://github.com/allthingsida/idasql):
  - removed version(s): 0.0.1
    8. 🔗 3Blue1Brown (YouTube) Measuring the entropy of English rss

      Full video: https://youtu.be/l6DKRf-fAAM

    9. 🔗 r/LocalLLaMA moonshotai/Kimi-K2.7-Code · Hugging Face rss

      moonshotai/Kimi-K2.7-Code · Hugging Face | Kimi K2.7 Code is a coding-focused agentic model built upon Kimi K2.6. With substantial improvements on real-world long-horizon coding tasks, it strengthens end-to-end task completion across complex software engineering workflows while improving token efficiency, reducing thinking-token usage by approximately 30% compared with Kimi K2.6. submitted by /u/Dark_Fire_12
      [link] [comments]
      ---|---

    10. 🔗 HexRaysSA/plugin-repository commits merge: discover changelog URLs, mirroring readme_url (EA-770) rss 
      merge: discover changelog URLs, mirroring readme_url (EA-770)

Probe the local mirror then GitHub for CHANGELOG.md / CHANGES.md /
HISTORY.md / docs/CHANGELOG.md and write metadata.changelog_url on each
plugin record in combined.json, exactly like README discovery. The
probe helpers are now filename-list-driven so both share one code path.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
    11. 🔗 syncthing/syncthing v2.1.2-rc.1 release

      Major changes in 2.1

      • Devices and folders can now be grouped in the GUI by setting the new
        group attribute.

      • HTTP and HTTPS proxies with support for CONNECT can now be used, in
        addition to the existing support for SOCKS proxies (the environment
        variable all_proxy=https://...).

      • Block indexing can be turned off for folders where it's more desirable to
        optimise for reduced database size and overhead than minimal transfer
        size (the blockIndexing attribute on folder configuration).

      • GUI login session duration can be configured to be longer or shorter than
        the default one week, or set to infinitely long. The cookie path can also
        be adjusted. (The sessionCookieDurationS and sessionCookiePath
        attributes in the GUI configuration.)

      This release is also available as:

      • APT repository: https://apt.syncthing.net/

      • Docker image: docker.io/syncthing/syncthing:2.1.2-rc.1 or ghcr.io/syncthing/syncthing:2.1.2-rc.1
        ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

      What's Changed

      Fixes

      • fix: on Windows don't allocate console if not opened inside one by @Shablone in #10726
      • fix(connections): do not report connection metrics for self (ref #10509) by @calmh in #10724
      • fix: let umask do the thing by @calmh in #10723
      • fix(fs, model): improve symlink resilience in file shortcut by @calmh in #10739
      • fix(protocol): always expect & validate block hash in requests by @calmh in #10738
      • fix(protocol): be more stringent about blocks in non-file entries by @calmh in #10737

      Other

      • chore(syncthing): open URLs via Windows API instead via cmd.exe by @Shablone in #10712
      • chore(db, model): separate methods to drop a device vs its files by @imsodin in #10480
      • build(deps): update dependencies by @calmh in #10740

      New Contributors

      Full Changelog : v2.1.1...v2.1.2-rc.1

  4. June 11, 2026
    1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-06-11 rss

      IDA Plugin Updates on 2026-06-11

      New Releases:

      Activity:

    2. 🔗 r/LocalLLaMA Gemma 4 Quadruple Release, 12B, 12B QAT, 26B-A4B QAT and 31B QAT Uncensored Heretics! rss

      Gemma 4 Quadruple Release, 12B, 12B QAT, 26B-A4B QAT and 31B QAT Uncensored Heretics! | gemma-4-31B-it-qat-q4_0-unquantized-uncensored-heretic: Safetensors: https://huggingface.co/llmfan46/gemma-4-31B-it-qat-q4_0-unquantized-uncensored-heretic GGUF: https://huggingface.co/llmfan46/gemma-4-31B-it-qat-q4_0-uncensored-heretic-GGUF NVFP4 Safetensors: https://huggingface.co/llmfan46/gemma-4-31B-it-qat-q4_0-uncensored-heretic-NVFP4 NVFP4 GGUF: https://huggingface.co/llmfan46/gemma-4-31B-it-qat-q4_0-uncensored-heretic-NVFP4-GGUF GPTQ-Int4: https://huggingface.co/llmfan46/gemma-4-31B-it-qat-q4_0-uncensored-heretic-GPTQ-Int4 gemma-4-26B-A4B-it-qat-q4_0-unquantized-uncensored-heretic: Safetensors: https://huggingface.co/llmfan46/gemma-4-26B-A4B-it-qat-q4_0-unquantized-uncensored-heretic GGUF: https://huggingface.co/llmfan46/gemma-4-26B-A4B-it-qat-q4_0-uncensored-heretic-GGUF NVFP4 Safetensors: https://huggingface.co/llmfan46/gemma-4-26B-A4B-it-qat-q4_0-uncensored-heretic-NVFP4 NVFP4 GGUF: https://huggingface.co/llmfan46/gemma-4-26B-A4B-it-qat-q4_0-uncensored-heretic-NVFP4-GGUF GPTQ-Int4: https://huggingface.co/llmfan46/gemma-4-26B-A4B-it-qat-q4_0-uncensored-heretic-GPTQ-Int4 gemma-4-12B-it-qat-q4_0-unquantized-uncensored-heretic: Safetensors: https://huggingface.co/llmfan46/gemma-4-12B-it-qat-q4_0-unquantized-uncensored-heretic GGUF: https://huggingface.co/llmfan46/gemma-4-12B-it-qat-q4_0-uncensored-heretic-GGUF NVFP4 Safetensors: https://huggingface.co/llmfan46/gemma-4-12B-it-qat-q4_0-uncensored-heretic-NVFP4 NVFP4 GGUF: https://huggingface.co/llmfan46/gemma-4-12B-it-qat-q4_0-uncensored-heretic-NVFP4-GGUF gemma-4-12B-it-uncensored-heretic: Safetensors: https://huggingface.co/llmfan46/gemma-4-12B-it-uncensored-heretic GGUFs: https://huggingface.co/llmfan46/gemma-4-12B-it-uncensored-heretic-GGUF NVFP4 Safetensors: https://huggingface.co/llmfan46/gemma-4-12B-it-uncensored-heretic-NVFP4 NVFP4 GGUF: https://huggingface.co/llmfan46/gemma-4-12B-it-uncensored-heretic-NVFP4-GGUF I even made some NVFP4 Safetensors and NVFP4 GGUF of standard Gemma 4 31B it since someone requested them: gemma-4-31B-it-uncensored-heretic: NVFP4 Safetensors: https://huggingface.co/llmfan46/gemma-4-31B-it-uncensored-heretic-NVFP4 NVFP4 GGUFs: https://huggingface.co/llmfan46/gemma-4-31B-it-uncensored-heretic-NVFP4-GGUF Doing all this took many days as well as a lot of work and effort, so I hope the community can make good use of these models. As usual all releases come with benchmarks too. Find all my models here: HuggingFace-LLMFan46 submitted by /u/LLMFan46
      [link] [comments]
      ---|---

    3. 🔗 Simon Willison Claude Fable is relentlessly proactive rss

      After two days of experience with Claude Fable 5 I think the best way to describe it is relentlessly proactive. It knows a whole lot of tricks and it will deploy pretty much any of them to get to its goal.

      I'll illustrate this with an example. I was hacking on Datasette Agent today when I noticed a glitch: a horizontal scrollbar that shouldn't be there in the jump menu chat prompt. I snapped this screenshot:

      Screenshot of a modal dialog demonstrating a scrollbar bug. At the top is a focused search input with blue outline and placeholder "Jump to...", with an X close button to its right. Below, a heading reads "Start a new agent chat" above a textarea with the placeholder "Ask a question about your data..." — the bug: a thick gray horizontal scrollbar is incorrectly displayed along the bottom edge of the empty textarea, spanning nearly its full width, next to the resize handle. Below the textarea: "Press Enter to start. Shift+Enter adds a new line." followed by a blue "Start chat" button.

      Then I started a fresh claude session in my datasette-agent checkout, dragged in the screenshot and told it:

      Look at dependencies to help figure out why there is a horizontal scrollbar here

      I had a hunch the cause was in a dependency of Datasette Agent (likely Datasette itself) and I knew Fable was good at digging into dependency code, either by inspecting installed files in its own virtual environment site-packages or by referencing a local checkout on disk. Telling it to start with dependencies felt like a good bet.

      I got distracted by a domestic task and wandered away from my computer.

      When I came back a few minutes later I saw my machine open a browser window in my regular Firefox and then navigate to the dialog in question. I had not told Claude Code to use any browser automation, and I was pretty sure it wasn't possible for it to trigger mouse movements or keyboard shortcuts within a window, so how was it doing that?

      I watched in fascination as it continued with its explorations, then saw it open a Safari window instead of Firefox. I also grabbed this snapshot from the Claude terminal:

      Screenshot of two Bash tool calls in a dark terminal interface. First: Bash(open -a Safari /tmp/textarea-scrollbar-test.html && sleep 4 && uv run --with pyobjc-framework-Quartz python - <<'EOF' import Quartz wins = Quartz.CGWindowListCopyWindowInfo(Quartz.kCGWindowListOptionOnScreenOnly, Quartz.kCGNullWindowID) for w in wins: if (w.get('kCGWindowOwnerName') or '') == 'Safari' and 'textarea' in (w.get('kCGWindowName') or '').lower(): print(w.get('kCGWindowNumber')) EOF) with output 153551. Second: Bash(screencapture -x -o -l 153551 /tmp/safari-cases.png && echo ok) with output ok.

      What was it doing there with uv run --with pyobjc-framework-Quartz?

      It turns out Fable had hacked up its own pattern for taking screenshots of browser windows. It was using Python to iterate through all available windows on my machine, then filtering for Safari windows with expected strings such as "textarea" in the window name. It used that to find their window number - an integer like 153551 - which it could then use with the screencapture CLI tool to grab a PNG.

      OK fine, that's a neat way of taking screenshots. But what was it taking screenshots of?

      Turns out it had been writing its own scratch HTML pages to try and recreate the bug, then opening Safari and grabbing screenshots.

      Here's that /tmp/textarea-scrollbar-test.html page it created, and the screenshot it took with screencapture -x -o -l 153551 /tmp/safari-cases.png:

      Screenshot of a Safari browser window showing a textarea scrollbar test page at file:///private/tmp/textarea-scrollbar-test.html. Page text reads: scrollbar thickness: 17px | UA: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.4 Safari/605.1.15 | devicePixelRatio: 2. Four numbered test cases follow, each with a textarea containing the placeholder "Ask a question about your data...": 1. Exact plugin CSS (resize: vertical, default overflow), 2. Plugin CSS + overflow-x: hidden, 3. Plugin CSS + resize: none, and 4. Bare default textarea, which is a much smaller box with the placeholder wrapping onto two lines. (I have way too many open tabs!)

      OK, so I can see how it's opening test pages and taking screenshots, but how on earth was it triggering the modal dialog that was meant to be under test? That's only available via a click or a keyboard shortcut, and I couldn't see a mechanism for it to run those in Safari.

      I eventually figured out what it had done.

      Claude was running in a folder that contained the source code for the application. It knows enough about Datasette to be able to run a local development server. It turns out it was editing Datasette's own templates to add JavaScript that would trigger the correct keyboard shortcut as soon as the window opened, adding code like this:

      <script>
window.addEventListener("load", function () {
  setTimeout(function () {
    document.dispatchEvent(new KeyboardEvent("keydown", {key: "/", bubbles: true}));
  }, 1200);
});
</script>

      1.2 seconds after the window opens, this code triggers a simulated / key, which is the keyboard shortcut for opening the modal dialog.

      There was one challenge left. In order to understand what was going on, Claude needed to run JavaScript on the page to take measurements for itself.

      It wrote its own custom web application to capture information via CORS, then ran that as a local server and opened a page with JavaScript that would POST directly to it!

      Here's the Python web app it wrote, using the standard library http.server package:

      from http.server import HTTPServer, BaseHTTPRequestHandler

class H(BaseHTTPRequestHandler):
    def do_POST(self):
        n = int(self.headers.get("Content-Length", 0))
        open("/tmp/diag.json", "w").write(self.rfile.read(n).decode())
        self.send_response(200)
        self.send_header("Access-Control-Allow-Origin", "*")
        self.end_headers()
    def do_OPTIONS(self):
        self.send_response(200)
        self.send_header("Access-Control-Allow-Origin", "*")
        self.send_header("Access-Control-Allow-Headers", "*")
        self.end_headers()
    def log_message(self, *a):  # quiet
        pass

HTTPServer(("127.0.0.1", 9999), H).serve_forever()

      All this does is accept a POST request full of JSON and write that to the /tmp/diag.json file. It sends Access-Control-Allow-Origin: * headers (including from OPTIONS requests) so that code running on another domain can still communicate back to it.

      Then Claude injected this code into the template that it was loading in a browser:

      const host = document.querySelector("navigation-search");
const ta   = host.shadowRoot.querySelector("textarea");
const cs   = getComputedStyle(ta);
fetch("http://127.0.0.1:9999/diag", {
  method: "POST",
  body: JSON.stringify({
    dpr: window.devicePixelRatio,
    scrollWidth: ta.scrollWidth, clientWidth: ta.clientWidth,
    whiteSpace: cs.whiteSpace, width: cs.width,
  }),
});

      This took measurements of the <textarea> inside the <navigation-search> Web Component and sent them to the server, which wrote them to a file on disk, which Claude could then read.

      Having figured out all of these tricks Fable... hit some invisible guardrail and downgraded itself to Opus. Thankfully Opus had access to the full transcript and could continue using the tricks pioneered by Fable, and shortly afterwards found, tested and verified the fix.

      I prompted Opus to:

      Write a report in /tmp/automation-report.md where you note down all of the tricks you have used in this session to test against real browsers on my computer, include runnable code examples

      Which produced this report, which was invaluable for piecing together the details of what had happened for this post.

      I've shared the full terminal transcript of the Claude Code session as well.

      A review of everything it did

      Based on a screenshot and a one-line prompt, Claude Fable 5 + Claude Code:

      • Figured out the recipe to run the local development server (with fake environment variables needed to get it running)
      • Fired up a Playwright Chrome session
      • Turned on the visible scrollbars setting for Chrome defaults write com.google.chrome.for.testing AppleShowScrollBars Always (it turned that off again later)
      • Cycled through Firefox and WebKit in Playwright too, failing to recreate the bug
      • Worked out my default browser was Safari
      • Built a textarea-scrollbar-test.html HTML document
      • Opened that in real (not Playwright) Firefox
      • Found that osascript -e 'tell application "System Events" to tell process "firefox" to id of window 1' was blocked because "osascript is not allowed assistive access"
      • Figured out that uv run --with pyobjc-framework-Quartz python workaround, described above
      • Added JavaScript to the site templates in order to trigger the / key
      • Built its own little Python CORS web server to capture JSON data
      • Rewrote the template to capture that data and send it to the server
      • Scripted its way through the Web Component shadow DOM to the information it needed
      • Opened Safari to confirm the source of the bug
      • Modified its custom template to hack in a potential fix
      • Confirmed the hacked fix worked
      • Reported back on how to fix the problem

      Like I said, relentlessly proactive!

      An estimate of the cost

      I'm currently on the $100/month Claude Max plan, which includes a generous allowance for Fable up until June 22nd after which Anthropic say they'll start charging full API prices for it.

      I'm using AgentsView to track my spending (see this TIL). Here's what AgentsView says this session would have cost me if I was paying full price for it:

      ~ % uvx agentsview session usage be8850a7-6119-46a0-b5d6-79c7fff5ae2b
Session:       be8850a7-6119-46a0-b5d6-79c7fff5ae2b
Agent:         claude
Output:        68606
Peak ctx:      113178
Cost:          ~$12.11 (claude-fable-5, claude-opus-4-8)

      If you don't keep a close eye on it, Fable will quite happily burn $12 in tokens inventing new ways to debug your CSS.

      I really need to lock this thing down

      On the one hand, watching Fable go to extreme lengths to get the information that it needed to debug what was, in the end, a two-line CSS fix, was fascinating.

      But on the other hand... this is a robust reminder that coding agents can do anything you can do by typing commands into a terminal - and frontier models know every trick in the book, and evidently a few that nobody has ever written down before.

      If Fable had been acting on malicious instructions - a prompt injection attack hidden in code or an issue thread, or something I'd carelessly pasted into my terminal - it's alarming to think quite how far it could go to exfiltrate data or cause other forms of mischief.

      Running coding agents outside of a sandbox has always been a bad idea - it's my top contender for a Challenger disaster incident, as described by Johann Rehberger in The Normalization of Deviance in AI.

      Fable is arguably smarter and hence more suspicious of potentially malicious instructions. But that smartness is very much a two-edged sword: if it does get subverted by instructions, the amount of damage it can do given its relentless proactivity is terrifying.

      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. 🔗 hyprwm/Hyprland v0.55.4 release

      Another small round of patches on top of 0.55.3.

      Fixes backported

      • config/lua: fix layout ctx checking the wrong argument (#15061)
      • desktop/popup: fix subsurface scaling (#14936)
      • gestures: fix live cursorZoom anchoring to a mid-animation value (#14996)
      • gestures: fix toggle cursorZoom sharing a single on/off flag (#14998)
      • groups: fix border color for locked groups (#15015)
      • protocols/foreignToplevel: fix class and title reporting on map and afterwards (#15037)
      • protocols/pointerWarp: fix crash when warp is on a non interactive surf (#15021)
      • renderer: fix SEGV on monitor disconnect (#15048)
      • gestures: clamp toggle cursorZoom like mult and live (#14997)
      • gestures: configure client to final size on fullscreen/float gesture completion (#14981)

      Special Thanks

      As always, special thanks to these people / companies for supporting Hyprland's continued development:

      Sponsors

      Diamond

      37Signals

      Gold

      Framework, Butterfly

      Donators

      Top Supporters:

      Tonao Paneguini, Semtex, soy_3l.beantser, Seishin, Nox Æterna, Illyan, Snorezor, Bonsai, Joshua Weaver, ExBhal, DHH, Mikko_Nyman, Kay, iain, TyrHeimdal, miget.com, alexmanman5, Hunter Wesson, --, RaymondLC92, Theory_Lukas, Brandon Wang, Insprill, lzieniew, 3RM, johndoe42, Jas Singh, RayJameson, MadCatX, Xoores, d, Ammar Hossain, Ki☆, inittux111, Arkevius, John Shelburne, DeWattaUnk, ari-cake, gfunnymoney, alukortti, taigrr

      New Monthly Supporters:

      tubid2wenty, Uros Cotman, yafantik, Guy, goblin_engineer, Julius John Puno, Peter Buijs, mb, StellaBuckley, haikuolin, Antibaddy, sludge10123, C Money, Lipski, KampotKaca, Kazuhide Takahashi, Skeptomai, bombadurelli, Rebellen, Álan, StreamCyper, taras, Yury, Sherab, Filinto Delgado, Taddelladius

      One-time Donators:

      Quuton, Selvan, Tyler Adams, tonis, Sam, Dimitrios Liappis, Chivtar, Eric, aponsasan888, bkode, LonestarF1, Chris, Dogmatic Polack, Larry, maxx, MonolithImmortal, edrix, I like GameNative, take my money., nyxloom, Frederic Toemboel, Schmendiey, himes, brandonia, Xphelus, New user, Miguel Flores- Acton, R3dGh0st, Glen, Vitor Moura GUEDES, Anersyum, le_04, Dan, AT, chorr, Awesome, IdeaSpring, Jacobrale, anonymous, Elias Griffin, w00z4, Marcus Edvardsson, Gerhard, Bashmaks, Benjaneb, R4dicalEdward, Matýsek ^^, Michael, Gene Raymond, naivesheep, Neginja, anarchuser, Uta, Francois KERISIT, ay4, Lorenzo santacreu, Gitznik, Jure S, Oliver, Pipes, Mein, ironick, Nlight, Pfoid, DasCleverle, Jaf Endee, DIEBUSTER, senorBeard, alex, Mike, luxxa, JasonPettys, One, Daniel, Sven Eppler, L3rdy, Ilunn, Thorff, XurxoMF, Wonkhester, Brian, Doc O, Mortja, Spook, Miguel Cordero Collar, bennyzen, deah, Sean, Higor, nanea808, Torsten Schieber, I3lack5hield, Kevin Steffer, Zarenno, vfosterm, Nikola, EGB, Dietmar, KilahDentist, Wilf Lin, Rad, Yuza, Supporter, nooob, esseonline, Naresh, darquill, BrnPrs, Pani, BYK, Amaury, nythix, Mika, Patriarch, Gambit, GoatCedric, Adam, MirasM, bl4ckb1rd, Loon, KevOlek, AsciiWolf, Brian Barrow, Anon, Kilian, Cristian M., abhinavmishra094, Dejv78, LinoDB, Trofim, Konstantin, JoaquinCamposPlaza(Ximo), Gabo, Phil, dev2and0m, Neil Brown, zarilion, JavierArias(Javi), Thank you, Mystrasun, Skrazzo, MeguminLoli, revitalist, barcellos-pedro, Juh, Goldie, benabrig, mynus, Daniel Zudel, Grant, Jacob Felknor, Noah, e033x, Nick, Niklas, mkami, Slippy, joenu, Oleksandr, t.i.m., Joss001, M4CETO, Nighty, Donater, David N, Cameron, Ekoban, Kieran, brotiii, Doug, Hypruser#0224975, Shadesofastar, sonicbhoc, GKL, Damien, João Seixas, mothmashine, James Freiwirth, Mek, Krizzkrozz, Panzer, mika.dev, Franky Valley, Sycho sMILEz, Roy, Amundis, willibenmula ❤️, Justin, marvelousIT, pablo, Alex, Ryan, cito, Juergen, Eric Koslow, valerius21, jfk, Andrejs, tyforupdate, skwrl, DaintyFox

      Full Changelog : v0.55.3...v0.55.4

    5. 🔗 The Pragmatic Engineer The Pulse: a trend of trying to cut back on AI spend within eng departments? rss

      Hi, this is Gergely with a bonus, free issue of the Pragmatic Engineer Newsletter. In every issue, I cover Big Tech and startups through the lens of senior engineers and engineering leaders. Today, we cover one out of four topics from The Pulse issue from two weeks ago. Full subscribers received the article below fourteen days ago. If you 've been forwarded this email, you can subscribe here .

      The below The Pulse is interesting, as a week after the original was sent it out, OpenAI CEO Sam Altman also said how AI budgeting is a huge issue for some companies - echoing findings from this analysis.

      In mid-May, Uber president, Andrew McDonald, was on the Rapid Response podcast for a conversation about the ridesharing giant with host Bob Safian, who raised the lack of hoped-for efficiency leverage from AI, citing the language learning app, Duolingo.

      "When you hear companies talking about 25% of code commits over the last quarter were AI-driven, or how their token usage went from X to Y percentage of employees: all these numbers are amazing. I think it's a massive transformation of society", McDonald said.

      "But, then you go and you talk to your senior engineering leaders, and you're asking: "how many projects that were "on the cutting room floor" got moved above the line [of being done] because of the productivity gains? Because 25% of our code commits were via Claude Code last quarter."

      That link [of improved productivity thanks to AI] is not there yet. I mean, maybe implicitly there's more that is getting shipped, but it's very hard to draw a line between one of those stats and more useful consumer features.

      Over the coming quarters and years, maybe that will become clearer. But today it's hard, even if some of the underlying metrics are trending in a really astronomical direction.

      Our CTO, Praveen, went viral because he said in an interview that we had blown through our AI budget for 2026 and it was the middle of March. We're going to have to start talking about token consumption and the associated cost versus headcount, and making tradesoffs on that as an engineering organization.

      If you 're not able to draw a direct line to [how many] useful features and functionality you're shipping to your users, that tradeoff [on AI spend] becomes harder to justify because AI is not free.

      If you're just a user [of AI tools] sitting there and coming up with interesting use cases, and you don't pay the bill, it can feel [like AI is free]. But somebody's paying the bill".

      My hunch is that pretty much every company is starting to, or will do soon, ask questions about the massive growth in AI spend; starting with AI coding tools. I talked with a few folks at larger and smaller companies about it:

      • OpenCode: customer demand for optimizing spend is spiking. Yesterday, on the podcast episode with OpenCode creator, Dax Raad, he said demand for OpenCode's hosted inference service (OpenCode Zen) surpassed all expectations because larger companies want cheaper, but still capable, AI models. He revealed that over the past month, every single inbound enterprise request was about optimizing spend. So, there's some widespread concern about AI bills.
      • Companies with cutting-edge AI bite the bullet with model routing. I talked with a CTO and a Head of Engineering at two cutting-edge tech companies. They also do not have an obvious return on investment (ROI) as yet. Still, they feel they have no choice but to pay the "intelligence premium" for state-of-the-art models or increase the number of bugs shipped. To reduce costs, both are considering "smart" model routing based on use case and prompt. These places pay top-of-market for the best engineers, so similarly, there are expectations of access to the best tools and models.
      • DoorDash: More knowledge-sharing sessions and responsibility for devs. The leading food delivery company gives responsibility for spending to devs: everyone has a high monthly token usage limit. To exceed it, you need to justify why, and also share the plan for being more efficient next month. Many regular in-house knowledge-sharing sessions are about efficient AI use.
      • Traditional company: monthly limits and dumb-model downgrades. One month ago, one of the largest retirement-savings companies in the US updated its AI usage policy for all devs, a current engineer told me, imposing a monthly GitHub Copilot token limit. Once gone, devs must use the less capable "0x" models on Copilot, which are not charged extra: GPT‑5 mini, GPT‑4.1, and Grok Code Fast 1.
      • Startups: signing up for multiple Claude / Codex Max subscriptions. I talked with several smaller startups that are generating meaningful revenue, and don't want to pay expensive API prices. So, they've made it a practice for devs to get subsidized Claude Code Max or Codex Max subscriptions.

      There 's a new bottom-up focus on AI efficiency. Most tech companies do a variety of internal knowledge-sharing things like regular team demos, lunch- and-learn sessions, and engineering all-hands. I've been noticing more AI efficiency-focused sessions in the past couple of months, coming from engineers: no top-down mandate!

      Engineering all-hands, CTOs, and even CEOs have started to raise concerns about increasing AI token costs, and now more engineers are experimenting with cheaper models for simpler tasks, model routing, more efficient token usage, etc.

      I'd expect that during the next performance review and promotion cycles, engineers who helped save on token costs might be rewarded, like two years ago, when engineering teams were rewarded for saving on third-party vendor bills.

      For an engineer, the best way to show impact in your work is to translate it to money: revenue generated, or costs saved. With AI spending as high as (or higher than) on observability, it should be straightforward to show massive savings with smart optimizations. There's a touch of irony in how any savings - for which there might be promotions and pay rises - will come from the places that actually did the rocketing spending.

      Read the full issue in the previous The Pulse. Or check out this week's The Pulse: Did Anthropic's new model just boost rival Codex's market share?

    6. 🔗 The Pragmatic Engineer The Pulse: Antigravity 2.0 takes ‘IDE’ out of its new IDE rss

      Hi, this is Gergely with a bonus, free issue of the Pragmatic Engineer Newsletter. In every issue, I cover Big Tech and startups through the lens of senior engineers and engineering leaders. Today, we cover one out of four topics from The Pulse issue from 21 May 2026. Full subscribers received the article below three weeks days ago. If you 've been forwarded this email, you can subscribe here .

      Yesterday, Google launched a full redesign of its flagship AI IDE, Antigravity 2.0. The "original" Antigravity came out in November 2025, as pretty much a clone of Windsurf, the IDE whose team Google acquired for $2.4B last July.

      Google has turned Antigravity into two distinct applications, "Antigravity IDE" (its former incarnation) and "Antigravity 2.0". This new version itself resembles a clone of Codex's desktop app. When you install Antigravity 2.0, there are two different applications. From Google's launch post:

      "If you already have installed the Antigravity IDE, when that application next updates, it will automatically update to Antigravity 2.0. At this point, you will be asked if you would like to still keep the Antigravity IDE, which is recommended for developers:

      alt

      My sense is that the team at Google may have struggled to decide whether to keep supporting "original" Antigravity while investing in the Codex-like experience, and so kept both. Whatever the reasoning, it has created confusing naming, and it feels to me like the team's true focus is 2.0.

      altBig change: Antigravity 2.0 throws out the IDE and adds a conversational interface

      The upgrade feels rushed, sloppy, and poorly thought out. I had Antigravity on my machine, and installed Antigravity 2.0 separately. I wanted to use them side-by-side, but when I tapped "Restart to update" on Antigravity 1.0, it upgraded itself to Antigravity 2.0 (the non-IDE version). Suddenly, I had two applications with different names, but neither is an IDE:

      altTesting times: Two apps but no IDE version on my machine, due to lack of testing

      Google has introduced an "Agent Manager" concept that feels unintuitive, and perhaps suitably, its creator struggles to explain it (emphasis mine:)

      "When we launched the Google Antigravity IDE in November 2025, there was no agent-first GUI surface in the market. We wanted to prove that such a surface worked, at least for software development. So, while the core of the Antigravity IDE was a familiar agent-powered IDE, we introduced the Agent Manager, a second surface that stripped away much of the "IDE" UI. This allowed users to focus on the agent conversations themselves, the artifacts the agents produced, and multi-agent management.

      Even without this separation, we have been pleasantly surprised how many people have adopted the Agent Manager in the Antigravity IDE for such non- development tasks, but it is not particularly intuitive ".

      The "Agent Manager" is basically a way to launch several agents, and the most intuitive interfaces for doing so are inside Claude and Codex desktop apps and Claude CoWork. Antigravity 2.0 copies them by starting new agent tasks on the right hand of the UI, and keeping track of them.

      Google looks indecisive about what to do with the IDE part of Antigravity. The release announcement suggests they'll keep on confusing users (emphasis mine:)

      "Although Antigravity 2.0 is the future, we won't disrupt your workflows right away. For now, both the Antigravity IDE application itself and the Agent Manager in the Antigravity IDE will remain available. In an upcoming release, we will remove the Agent Manager from the Antigravity IDE, turning the IDE into a purely agent-powered IDE. "

      Basically, the Antigravity IDE (not "the future" in Google's vision) will become more limited over time. It's unclear what a "purely" agent-powered IDE will be once agentic functionality is removed, especially as Antigravity IDE is not the future, as per Google.

      Not only that, but the announcement also encourages devs to use Antigravity 2.0 with other IDEs! From the launch post (emphasis mine):

      "We recommend dual-wielding Antigravity 2.0 with your IDE of choice, whether it is the Antigravity IDE or otherwise. Googlers have already been dual wielding Antigravity 2.0 with a whole host of IDEs! We will have compatible extensions and plugins into other popular IDEs shortly".

      To me, this suggests Google will retire Antigravity IDE and recommend VS Code, JetBrains, Cursor, or Zed, with Antigravity. Then again, why would Cursor or Zed support Antigravity? The messaging is extremely confusing: Google's still the king of opacity.

      Feedback on Antigravity 2.0 has been negative due to bugs, poor UX and model support, more bugs, and eating up Gemini token quotas rapidly. Antigravity does not support state-of-the-art Anthropic or OpenAI models (no Opus 4.7 or GPT 5.5). Not supporting OpenAI's models like this is sensible as they're competitors, but Google is an investor in Anthropic, so not supporting Opus 4.7 (while supporting the legacy 4.6 model) is a bit odd.

      altModels which Antigravity 2.0 supports

      Gemini 3.5 Flash is Google's cutting-edge model, but it gets lots of complaints from devs for editing files without asking, and seems like an inefficient model. Another common complaint is that Antigravity uses up the $100/month Ultra subscription daily quota in minutes. Basically, it seems like a poor-quality product that wasn't polished due to lack of time or inclination.

      In context, it's embarrassing for there to be a "Codex" folder in the launch video if it suggests that Google's own Antigravity devs are using Codex for day-to-day work. It also suggests that the launch video was not reviewed properly, otherwise this obvious detail would presumably have been caught and fixed:

      altCodex folder in Documents suggests Antigravity devs are users of it. Source: Antigravity 2.0 launch video

      To upset devs even more, Google is replacing its open source Gemini CLI with the closed source Antigravity CLI. There are a few issues with this move:

      • Antigravity CLI does not support Google's own Agent Client Protocol (ACP), used for programmatic control, primarily for IDE and other developer tool integrations. This is protocol which IDEs like JetBrains and Zed have adopted, so Antigravity CLI becomes incompatible with them
      • Google offers no migration path from Gemini CLI settings/skills/MCPs into Antigravity. Figure it out on your own!
      • Devs using Gemini models are forced to move as Google has removed support for Gemini 3.5 Flash model from Gemini CLI. It can only be used from Antigravity CLI. Clearly, this was done to force a move. Why not offer a migration path?

      My sense is the Antigravity team is moving fast, breaking things, and shipping a broken product. It feels like the Antigravity 2.0 and Antigravity CLI products have been rushed to meet the annual Google conference (Google I/O) deadline, this week. Google deprecates existing products to attempt to get users to switch to the new version. But the new one is broken.

      altWhat 's changed? Manu Cornet __ penned this cartoon in 2011__

      And this is a big reason why I don't believe Google will become a serious player in the dev tools space - not even with AI dev tools. Every six to twelve months they remind devs who onboarded to their dev tools that it was a mistake to do so. I would expect the majority of Google CLI and Antigravity users to go and try products from other vendors - be that Cursor, Anthropic, OpenAI, GitHub, or others - and for few to stick around after their workflows are broken.

    7. 🔗 r/LocalLLaMA Qwen Who? DiffusionGemma running at 1,500 tk/s on a Digital Pregnancy Test. rss

      Qwen Who? DiffusionGemma running at 1,500 tk/s on a Digital Pregnancy Test. | First Doom, now DiffusionGwmma 4. We are truly living in the future. Who even needs a new Qwen release anymore? /s
      (Satire - Shaq doesn’t actually make a digital pregnancy test capable of running diffusion-based LLMs)
      Credit to Obvious Plant for the original Shaq pregnancy test box (that I doctored slightly). submitted by /u/Porespellar
      [link] [comments]
      ---|---

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

## New releases
- [yarg](https://github.com/r0ny123/yarg): 1.0.5
    9. 🔗 r/LocalLLaMA fableExpectations rss

      fableExpectations | https://preview.redd.it/2o426zap9l6h1.png?width=1080&format=png&auto=webp&s=169e2d511bbf4c4b08a155775d94b0e9f3f931a5 Claude Fable is incredible It one-shotted my usage limits in 1 prompt submitted by /u/HitarthSurana
      [link] [comments]
      ---|---

    10. 🔗 Console.dev newsletter sem rss

      Description: Semantic Git diffs.

      What we like: Provides a higher-level abstraction to understand what changed in the code e.g. showing function names added/removed. Includes a dependency graph to highlight what might be impacted by a change. Supports JSON output for LLMs to better analyze changes.

      What we dislike: Useful starting point to understand changes before you get into the details using Git.

    11. 🔗 Console.dev newsletter Herdr rss

      Description: Agent terminal multiplexer.

      What we like: TUI for tmux-style persistence for multiple AI agent sessions. Easily detach, reattach, and work locality or remotely over SSH. Works with your existing terminal. Keyboard-first, but supports the mouse. Agents can use it to operate their own workspaces. Has a mobile-optimized view.

      What we dislike: Live handoff for updating a running Herdr server works well, but is still technically experimental so don’t rely on it yet.

generated: June 14, 2026 at 12:33:16