🏡

to read (pdf)

generated: April 10, 2026 at 09:35:12

April 10, 2026
1. 🔗 r/reverseengineering I'm doing a free monthly live series where I reverse-engineer iOS apps from the App Store and show what's exposed in the binary. First session soon. rss
  
  submitted by /u/kovallux
  [link] [comments]
2. 🔗 larsderidder/context-lens v0.8.0 release
  - support Copilot /responses capture and enable NODE_USE_ENV_PROXY in mitm mode\n- bump @contextio packages to align with published core exports\n- include recent mitm and Codex fixes from 0.8.0 line
3. 🔗 r/Yorkshire The path rss
  
  | North Yorkshire submitted by /u/Damo_f_
  [link] [comments]
  ---|---
4. 🔗 r/wiesbaden Internet (DSL) in Wiesbaden – Erfahrungen mit Anbietern? rss
  
  Hi zusammen,
  
  ich suche aktuell einen Internet (DSL) Anschluss in Wiesbaden und überlege zwischen Telekom, Vodafone, O2 und 1&1. Mir ist vor allem wichtig, dass die Verbindung stabil ist und der Preis passt.
  
  Wie sind eure Erfahrungen mit den Anbietern hier vor Ort? Gibt es Unterschiede oder ist es am Ende ähnlich? Und kennt jemand vielleicht auch gute lokale Anbieter?
  
  Danke euch!
  
  submitted by /u/Lum_zan
  [link] [comments]
5. 🔗 pydantic/monty v0.0.11 - 2026-04-10 release
  What's Changed
  - JSON perf improvements by @samuelcolvin in #314
  - implement mount fixes for edgecases by @samuelcolvin in #310
  Full Changelog : v0.0.10...v0.0.11
6. 🔗 r/york House share questions rss
  
  Hello! I've recently bought my first home and have a spare room going unused at the moment, I've been considering opening it up to be rented to make a little extra money but don't really know. So I thought I'd ask here! If anyone knows what amount of rent would be reasonable or has advice, or is just interested in getting a place i'd love to hear from folks, thanks!
  
  submitted by /u/Pinoc1
  [link] [comments]
7. 🔗 anthropics/claude-code v2.1.100 release
  
  No content.
8. 🔗 r/LocalLLaMA the state of LocalLLama rss
  
  | submitted by /u/Beginning-Window-115
  [link] [comments]
  ---|---
9. 🔗 HexRaysSA/plugin-repository commits sync repo: +2 releases rss
```
sync repo: +2 releases

## New releases
- [BinSync](https://github.com/binsync/binsync): 5.14.0
- [IDAssist](https://github.com/symgraph/IDAssist): 1.7.0
```
April 09, 2026
1. 🔗 r/Yorkshire Over Spurn Point at Sunset rss
  
  | submitted by /u/UntidyLives
  [link] [comments]
  ---|---
2. 🔗 r/Yorkshire Man, 60, and woman, 38, arrested in Barnsley, South Yorkshire on suspicion of murder after pedestrian, 45, dies in collision. rss
  
  submitted by /u/108CA
  [link] [comments]
3. 🔗 Kagi release notes April 9th, 2026 - Tuning the Orchestra rss
  Improvements and bug fixes
  
  Kagi Search
  - Support IPv6 cidr ranges in ip whitelist for API #9988 @Simonses1
  - Dictionary widget only works when words are lowercase #10211 @MustafaD
  - Lens off by one error #7825 @rhythmicorangeturtle
  - Quick Answer hint displays even when Quick Answer is explicitly disabled #10267 @mcc111
  - Both m.imdb.com and imdb.com for the same webpage are in the results #10092 @pma_snek
  - Search term returns no results: almost anything that includes "sleep()" #10274 @bkw777
  - Kagi search sometimes ignores site: directive #9815 @morj
  - Wrong lens gets selected during search #10187 @yodathan_
  - Logged out when editing custom CSS #10303 @SkyDotBit
  - Inconsistently between web/image search when it comes to capitalization sensitivity #10309 @Thibaultmol
  - Islamic prayer time #9982 @mishari
  - Kagi Knowledge results consistently incorrect, haywire, misleading #6208 @aasshhlleeyy
  Kagi Assistant
  - Mobile app: Assistant has gray empty bar at top of screen #9570 @RMLight
  - Page context in assistant searches are limited #10167 @jonathan-s
  - Assistant thread history dates do not update dynamically when an old chat is continued #10278 @xx
  - Research Assistant searches fail on certain queries #10110 @doggofan
  - Kagi Assistant turns ssh commands into <mailto:user@domain> links even once corrected #8521 @xMotus
  - Editing a prompt with a file, removes it? #5653 @Thibaultmol
  Kagi Small Web
  - iOS Small Web Dark Mode App Icon #10136 @Cal4T5
  - Add a tap-based way to switch posts
  - Fixed incorrect text formatting for bookmark titles
  Kagi Translate
  - Warning badge when translating to/from language using custom instructions
  - Wordplay and puns lost in translation are now detected and surfaced to the user if word insights are enabled @zark
  - Fixed Spanish text sometimes appearing in French translations on Standard mode @UAguy
  - Fixed Japanese/Chinese/Korean IME first character being lost in empty editor @jisaker
  - Proofreading a Word Document #8810 @jmvleal
  - Translate UI does not respect settings #9944 @mmartinortiz
  - Fix: clear button not working on mobile due to composing state #unknown @unknown
  - Same Language bug #10134 @KikoAnimations
  - Fixed website translation stacking duplicate header bars when switching languages, and Google redirect URLs not being unwrapped
  - Fixed clear button not working on mobile after pasting, restoring history, or during keyboard composition
  - Fixed error when pasting rich text from webpages
  - Fixed translation between same-language variants (e.g. pt-BR to pt-PT) echoing input instead of translating
  - Fixed intermittent text-to-speech 503 errors
  - Renamed "Azeri" to "Azerbaijani" to match ISO 639 standard
  - Korean formality settings now apply to ko-KR locale @Hanbyeol
  - Decreased AI refusals when translating text and images
  - Pin "Detect Language" at the top of the source language selector for quick access @pineafan
  - Add Montenegrin as an option in Translate @mb
  - Improved keyboard shortcuts @mb
  Blast from the past
  
  The retro homepage we implemented for April Fools may be gone, but many of you are not ready to let go of the nostalgia just yet.
  
  Here's a dedicated URL to bring it back whenever you want: https://kagi.com/?year=1996
  
  This sets a cookie so your device remembers. To undo it, click Back to the Future at the bottom of the page or visit https://kagi.com/?year=present_day
  
  Post of the week
  
  Here is this week's featured social media mention:
  
  Follow us and tag us in your comments, we love hearing from you!
  
  Kagi tip of the week 💡
  
  Did you know you can set up URL redirects to reroute search results to the sites or frontends you prefer? Here's how, with examples from the community.
  
  Kagi art
  
  AI and ads are a toxic combo. Across the Kagi ecosystem, there are no ads, and we're actively working to keep slop out of your search results. Read more about Kagi's SlopStop initiative here.
4. 🔗 r/reverseengineering FLARE Learning Material rss
  
  submitted by /u/skull7skull
  [link] [comments]
5. 🔗 r/Leeds PSA If you want to quit smoking/vaping: Free Stop Smoking Service in Leeds rss
  Hi! I’m not associated with them or anything, just a long-time smoker trying to kick this nasty habit and thought I’d share for anyone else in the same boat.
  
  The Leeds Stop Smoking Service is completely free & accessible for all.
  
  Even if you’re only thinking about quitting or if you merely want to cut
  
  down on smoking it’s worth looking at their website.
  
  - You don’t need a GP referral to sign up, simply fill up their online form. It took me 10 minutes to answer all the questions and I was able to get an appointment within a week.
  
  - They offer both remote (via telephone) and face-to-face appointments with a counsellor OR free resources and support if you want to stop smoking by yourself.
  
  - It’s a 4-6 week long programme with check-in calls from your designated counsellor. Peer support groups are also available.
  
  - You can choose between free e-cigarettes (via their Swap to Stop initiative) or choose from a variety of Nicotine Replacement therapy supplies (gums, patches, and inhalators etc), and you can get your supplies mailed directly to you.
  
  They’ll tailor their recommendations to fit whatever position you’re in. Whether you’re just trying to reduce smoking or quit completely, or if you’re also managing a chronic illness or mental health condition while quitting, they’re there to help.
  
  Sign up here:
  1. General Stop Smoking Service
  2. Health Conditions Stop Smoking Service (specialised support if you have a diagnosed common mental illness or long-term physical health conditions)
  3. To refer someone else
  or call them at: 0800 169 4219
  
  Additional resources:
  
  - The NHS Stop Smoking app
  
  - National Smokefree helpline: 0300 123 1044
  
  (9am to 8pm Monday to Friday, and 11am to 4pm Saturday and Sunday)
  
  - Recommended reading & clinically approved:
  
  The Allen Carr’s Easy Way to Stop Smoking
  
  ••••
  
  My personal experience if you’re interested:
  
  I opted for a remote appointment and the counsellor I was assigned was incredibly empathetic and non-judgmental; she really listened and asked all the right questions such as why I want to quit and so on, and we came up with a combination of NRT supplies that would best fit my needs over the phone. For me, e-cigarettes weren’t an option because of my poor impulse control (thanks, ADHD!) and I ended up vaping more during past quitting attempts. And the hardest part of the habit for me to crack is the oral fixation and the smoking “ritual” so we opted for the inhalator (instead of patches) and gum for when my cravings are too intense. I also got a bunch of free resources and additional info in a follow-up email.
  
  I’m only a week in, but I’m doing much better with the additional support compared to all my previous quitting attempts. I couldn’t wait to share as I think it’s a wonderful resource that not many know of.
  
  Thanks for reading :)
  
  submitted by /u/Holochromatic
  [link] [comments]
6. 🔗 anthropics/claude-code v2.1.98 release
  What's changed
  - Added interactive Google Vertex AI setup wizard accessible from the login screen when selecting "3rd-party platform", guiding you through GCP authentication, project and region configuration, credential verification, and model pinning
  - Added CLAUDE_CODE_PERFORCE_MODE env var: when set, Edit/Write/NotebookEdit fail on read-only files with a p4 edit hint instead of silently overwriting them
  - Added Monitor tool for streaming events from background scripts
  - Added subprocess sandboxing with PID namespace isolation on Linux when CLAUDE_CODE_SUBPROCESS_ENV_SCRUB is set, and CLAUDE_CODE_SCRIPT_CAPS env var to limit per-session script invocations
  - Added --exclude-dynamic-system-prompt-sections flag to print mode for improved cross-user prompt caching
  - Added workspace.git_worktree to the status line JSON input, set whenever the current directory is inside a linked git worktree
  - Added W3C TRACEPARENT env var to Bash tool subprocesses when OTEL tracing is enabled, so child-process spans correctly parent to Claude Code's trace tree
  - LSP: Claude Code now identifies itself to language servers via clientInfo in the initialize request
  - Fixed a Bash tool permission bypass where a backslash-escaped flag could be auto-allowed as read-only and lead to arbitrary code execution
  - Fixed compound Bash commands bypassing forced permission prompts for safety checks and explicit ask rules in auto and bypass-permissions modes
  - Fixed read-only commands with env-var prefixes not prompting unless the var is known-safe (LANG, TZ, NO_COLOR, etc.)
  - Fixed redirects to /dev/tcp/... or /dev/udp/... not prompting instead of auto-allowing
  - Fixed stalled streaming responses timing out instead of falling back to non-streaming mode
  - Fixed 429 retries burning all attempts in ~13s when the server returns a small Retry-After — exponential backoff now applies as a minimum
  - Fixed MCP OAuth oauth.authServerMetadataUrl config override not being honored on token refresh after restart, affecting ADFS and similar IdPs
  - Fixed capital letters being dropped to lowercase on xterm and VS Code integrated terminal when the kitty keyboard protocol is active
  - Fixed macOS text replacements deleting the trigger word instead of inserting the substitution
  - Fixed --dangerously-skip-permissions being silently downgraded to accept-edits mode after approving a write to a protected path via Bash
  - Fixed managed-settings allow rules remaining active after an admin removed them, until process restart
  - Fixed permissions.additionalDirectories changes not applying mid-session — removed directories lose access immediately and added ones work without restart
  - Fixed removing a directory from additionalDirectories revoking access to the same directory passed via --add-dir
  - Fixed Bash(cmd:*) and Bash(git commit *) wildcard permission rules failing to match commands with extra spaces or tabs
  - Fixed Bash(...) deny rules being downgraded to a prompt for piped commands that mix cd with other segments
  - Fixed false Bash permission prompts for cut -d /, paste -d /, column -s /, awk '{print $1}' file, and filenames containing %
  - Fixed permission rules with names matching JavaScript prototype properties (e.g. toString) causing settings.json to be silently ignored
  - Fixed agent team members not inheriting the leader's permission mode when using --dangerously-skip-permissions
  - Fixed a crash in fullscreen mode when hovering over MCP tool results
  - Fixed copying wrapped URLs in fullscreen mode inserting spaces at line breaks
  - Fixed file-edit diffs disappearing from the UI on --resume when the edited file was larger than 10KB
  - Fixed several /resume picker issues: --resume <name> opening uneditable, filter reload wiping search state, empty list swallowing arrow keys, cross-project staleness, and transient task-status text replacing conversation summaries
  - Fixed /export not honoring absolute paths and ~, and silently rewriting user-supplied extensions to .txt
  - Fixed /effort max being denied for unknown or future model IDs
  - Fixed slash command picker breaking when a plugin's frontmatter name is a YAML boolean keyword
  - Fixed rate-limit upsell text being hidden after message remounts
  - Fixed MCP tools with _meta["anthropic/maxResultSizeChars"] not bypassing the token-based persist layer
  - Fixed voice mode leaking dozens of space characters into the input when re-holding the push-to-talk key while the previous transcript is still processing
  - Fixed DISABLE_AUTOUPDATER not fully suppressing the npm registry version check and symlink modification on npm-based installs
  - Fixed a memory leak where Remote Control permission handler entries were retained for the lifetime of the session
  - Fixed background subagents that fail with an error not reporting partial progress to the parent agent
  - Fixed prompt-type Stop/SubagentStop hooks failing on long sessions, and hook evaluator API errors showing "JSON validation failed" instead of the real message
  - Fixed feedback survey rendering when dismissed
  - Fixed Bash grep -f FILE / rg -f FILE not prompting when reading a pattern file outside the working directory
  - Fixed stale subagent worktree cleanup removing worktrees that contain untracked files
  - Fixed sandbox.network.allowMachLookup not taking effect on macOS
  - Improved /resume filter hint labels and added project/worktree/branch names in the filter indicator
  - Improved footer indicators (Focus, notifications) to stay on the mode-indicator row instead of wrapping at narrow terminal widths
  - Improved /agents with a tabbed layout: a Running tab shows live subagents, and the Library tab adds Run agent and View running instance actions
  - Improved /reload-plugins to pick up plugin-provided skills without requiring a restart
  - Improved Accept Edits mode to auto-approve filesystem commands prefixed with safe env vars or process wrappers
  - Improved Vim mode: j/k in NORMAL mode now navigate history and select the footer pill at the input boundary
  - Improved hook errors in the transcript to include the first line of stderr for self-diagnosis without --debug
  - Improved OTEL tracing: interaction spans now correctly wrap full turns under concurrent SDK calls, and headless turns end spans per-turn
  - Improved transcript entries to carry final token usage instead of streaming placeholders
  - Updated the /claude-api skill to cover Managed Agents alongside Claude API
  - [VSCode] Fixed false-positive "requires git-bash" error on Windows when CLAUDE_CODE_GIT_BASH_PATH is set or Git is installed at a default location
  - Fixed CLAUDE_CODE_MAX_CONTEXT_TOKENS to honor DISABLE_COMPACT when it is set.
  - Dropped /compact hints when DISABLE_COMPACT is set.
7. 🔗 r/Yorkshire Ingleborough viewed from Whernside earlier this week rss
  
  | submitted by /u/SonicShadow
  [link] [comments]
  ---|---
8. 🔗 backnotprop/plannotator v0.17.7 release
  Follow @plannotator on X for updates
  
  Missed recent releases? Release | Highlights
  ---|---
  v0.17.6 | Bun.serve error handlers for diagnostic 500 responses, install.cmd cache fix
  v0.17.5 | Fix VCS detection crash when p4 not installed, install script cache path fix
  v0.17.4 | Vault browser merged into Files tab, Kanagawa themes, Pi idle session tool fix
  v0.17.3 | Sticky lane repo/branch badge overflow fix
  v0.17.2 | Supply-chain hardening, sticky toolstrip and badges, overlay scrollbars, external annotation highlighting, Conventional Comments
  v0.17.1 | Pi PR review parity, parseRemoteUrl rewrite, cross-repo clone fixes, diff viewer flash fix
  v0.17.0 | AI code review agents, token-level annotation, merge-base diffs
  v0.16.7 | Gemini CLI plan review, install script skills directory fix
  v0.16.6 | Perforce support, Pi shared event API, suggested code prefill, file tree expand fix
  v0.16.5 | Resize handle scrollbar fix, VS Code Marketplace publish
  v0.16.4 | Compound planning improvement hook, GitHub Enterprise + self-hosted GitLab, dockview workspace, new themes
  v0.16.3 | Pi phase configuration, CLI help, untracked file discovery fix, review scroll reset
  
  What's New in v0.17.7
  
  v0.17.7 fixes the "fetch(req) did not return a Response object" error that affected OpenCode users running opencode web, opencode serve, or any mode that starts the HTTP server (including --port or --hostname flags).
  
  Fix: OpenCode Web/Serve Mode Compatibility
  
  OpenCode recently added Node.js support alongside Bun. To bridge its Hono app to Node's HTTP server, OpenCode uses @hono/node-server, which includes a createAdaptorServer function. That function unconditionally patches global.Response with a polyfill class — a necessary step for Node.js, which lacks native web API globals.
  
  The problem: in opencode web and opencode serve modes, this patch runs before plugins load. When the plannotator plugin calls Bun.serve() and the fetch handler returns new Response(...), it's constructing the hono polyfill, not Bun's native Response. Bun validates return types using internal type tags, not instanceof, so it rejects the polyfill and shows its default error page. The error() handler added in v0.17.6 also uses new Response(...), which is why it didn't fire either — the error handler's own response was also a polyfill.
  
  Plain opencode TUI without --port or server config was never affected. In that mode, OpenCode routes requests through an internal RPC bridge instead of starting an HTTP server, so createAdaptorServer never runs and global.Response stays native.
  
  The fix detects the polyfill by walking the prototype chain. Hono sets up Object.setPrototypeOf(Response2.prototype, GlobalResponse.prototype), so the parent prototype's constructor is the original native Response. The plugin recovers it and restores globalThis.Response before any server code runs. When Response hasn't been patched, the detection check fails safely and the fix is a no-op.
  - Closing #528, reported by @Zengwenj
  Install / Update
  
  macOS / Linux:
```
curl -fsSL https://plannotator.ai/install.sh | bash
```
  Windows PowerShell:
```
irm https://plannotator.ai/install.ps1 | iex
```
  Pin a specific version:
```
curl -fsSL https://plannotator.ai/install.sh | bash -s -- --version v0.17.7
```
  Claude Code Plugin: Run /plugin in Claude Code, find plannotator , and click "Update now".
  
  Copilot CLI:
```
/plugin marketplace add backnotprop/plannotator
/plugin install plannotator-copilot@plannotator
```
  Gemini CLI: The install script auto-detects ~/.gemini and configures hooks, policy, and slash commands.
  
  OpenCode: Clear cache and restart:
```
rm -rf ~/.cache/opencode/packages/@plannotator ~/.bun/install/cache/@plannotator
```
  Then in opencode.json:
```
{
  "plugin": ["@plannotator/opencode@latest"]
}
```
  Pi: Install or update the extension:
```
pi install npm:@plannotator/pi-extension
```
  VS Code Extension: Install from the VS Code Marketplace.
  
  What's Changed
  - fix: recover native Response when patched by hono node-server adapter by @backnotprop
  Community
  
  @Zengwenj reported the original issue in #528. @xxJava provided the p4 stack trace and confirmed cross-platform reproduction. @boris-gorbylev and @chocochu confirmed on macOS. @jehu-rodriguez confirmed 0.17.6's error handler didn't fire, which was the key clue that the issue was a non-Response return rather than an exception. The latest reporter confirmed opencode web as the specific trigger, which led directly to identifying the hono adapter's global.Response patch as the root cause.
  
  Full Changelog : v0.17.6...v0.17.7
9. 🔗 r/york Can anyone who has recently had work done on their car please let me know what the hourly rate was? I’ve just had work done on mine and I’m not sure if I’ve been ripped off or not. Thank you rss
  
  submitted by /u/Roo90
  [link] [comments]
10. 🔗 r/reverseengineering Analyzing a Denuvo bypass approach based on virtualization. rss
  
  submitted by /u/Medium-Piano-4488
  [link] [comments]
11. 🔗 backnotprop/plannotator v0.17.6 release
  Follow @plannotator on X for updates
  
  Missed recent releases? Release | Highlights
  ---|---
  v0.17.5 | Fix VCS detection crash when p4 not installed, install script cache path fix
  v0.17.4 | Vault browser merged into Files tab, Kanagawa themes, Pi idle session tool fix
  v0.17.3 | Sticky lane repo/branch badge overflow fix
  v0.17.2 | Supply-chain hardening, sticky toolstrip and badges, overlay scrollbars, external annotation highlighting, Conventional Comments
  v0.17.1 | Pi PR review parity, parseRemoteUrl rewrite, cross-repo clone fixes, diff viewer flash fix
  v0.17.0 | AI code review agents, token-level annotation, merge-base diffs
  v0.16.7 | Gemini CLI plan review, install script skills directory fix
  v0.16.6 | Perforce support, Pi shared event API, suggested code prefill, file tree expand fix
  v0.16.5 | Resize handle scrollbar fix, VS Code Marketplace publish
  v0.16.4 | Compound planning improvement hook, GitHub Enterprise + self-hosted GitLab, dockview workspace, new themes
  v0.16.3 | Pi phase configuration, CLI help, untracked file discovery fix, review scroll reset
  v0.16.2 | Draggable comment popovers, cross-file annotation visibility, custom diff fonts, OpenCode verbose log fix
  
  What's New in v0.17.6
  
  v0.17.6 adds error handlers to all three Bun servers (plan, review, annotate) so that unhandled exceptions produce a diagnostic 500 response instead of Bun's opaque default error page. This release also adds OpenCode cache clearing to the Windows CMD install script, which was missing entirely.
  
  Server Error Handlers
  
  Several OpenCode users reported seeing Bun's default error page ("You're seeing this because fetch(req) did not return a Response object") when using submit_plan. The root cause remains under investigation, but the default Bun error page provides zero diagnostic information, making it impossible to identify the actual exception from user reports alone.
  
  All three servers (plan review, code review, annotate) now register an error handler with Bun.serve(). When the fetch handler throws for any reason, the error handler catches it, logs the full exception to stderr, and returns a 500 response with the error message. Normal requests are unaffected. The only change in behavior is on error paths that were previously showing the opaque Bun page.
  
  This gives us the diagnostic information we need. The next user who hits this issue will see the actual error message instead of the generic Bun page, and can include it in their report.
  - Continuing investigation of #528, reported by @Zengwenj
  Windows CMD Install Script Cache Fix
  
  The install.cmd script had no OpenCode cache clearing at all. Users who installed or updated via CMD on Windows kept running stale cached plugin versions indefinitely. The script now clears %USERPROFILE%\.cache\opencode\packages\@plannotator alongside the existing bun cache paths, matching the behavior already present in install.sh and install.ps1 since v0.17.5.
  
  Install / Update
  
  macOS / Linux:
```
curl -fsSL https://plannotator.ai/install.sh | bash
```
  Windows PowerShell:
```
irm https://plannotator.ai/install.ps1 | iex
```
  Pin a specific version:
```
curl -fsSL https://plannotator.ai/install.sh | bash -s -- --version v0.17.6
```
  Claude Code Plugin: Run /plugin in Claude Code, find plannotator , and click "Update now".
  
  Copilot CLI:
```
/plugin marketplace add backnotprop/plannotator
/plugin install plannotator-copilot@plannotator
```
  Gemini CLI: The install script auto-detects ~/.gemini and configures hooks, policy, and slash commands. See apps/gemini/README.md for manual setup.
  
  OpenCode: Clear cache and restart:
```
rm -rf ~/.cache/opencode/packages/@plannotator ~/.bun/install/cache/@plannotator
```
  Then in opencode.json:
```
{
  "plugin": ["@plannotator/opencode@latest"]
}
```
  Pi: Install or update the extension:
```
pi install npm:@plannotator/pi-extension
```
  VS Code Extension: Install from the VS Code Marketplace. Tested with Claude Code running in VS Code's integrated terminal. Not currently compatible with Anthropic's official VS Code extension due to upstream hook bugs.
  
  What's Changed
  - fix: add Bun.serve error handlers for diagnostic 500 responses by @backnotprop
  - fix: add OpenCode cache clearing to install.cmd by @backnotprop
  Community
  
  @Zengwenj, @xxJava, @boris- gorbylev, and @chocochu reported and confirmed #528. The error handler addition is a direct response to the difficulty of diagnosing the reported Bun error page without exception details.
  
  Full Changelog : v0.17.5...v0.17.6
12. 🔗 r/Leeds Leeds vs Manchester uni rss
  
  So I have a conditional offer from both Manchester and Leeds. I’ve visited both, and I really like both! I am in for biological sciences at Manchester and biochemistry at Leeds.
  
  I was wondering if any of you guys currently go there or went there, what was your experience like? Did you regret your choice? I’m looking to come back to America after my studies here, so if any of yiu guys did that let me know!!
  
  Socially, how was it? I’m into running and biking so I would love to join a triathlete club here or whatever. Is there good routes around? (I know they are both in the city, but maybe some trails accessible by train?)
  
  Which city is your favorite? Which is more student friendly, safety and expenseses wise? Let me know!!
  
  From a worried high school senior
  
  submitted by /u/Mars_bars10
  [link] [comments]
13. 🔗 r/LocalLLaMA Local (small) LLMs found the same vulnerabilities as Mythos rss
  
  | submitted by /u/CyberAttacked
  [link] [comments]
  ---|---
14. 🔗 backnotprop/plannotator v0.17.5 release
  Follow @plannotator on X for updates
  
  Missed recent releases? Release | Highlights
  ---|---
  v0.17.4 | Vault browser merged into Files tab, Kanagawa themes, Pi idle session tool fix
  v0.17.3 | Sticky lane repo/branch badge overflow fix
  v0.17.2 | Supply-chain hardening, sticky toolstrip and badges, overlay scrollbars, external annotation highlighting, Conventional Comments
  v0.17.1 | Pi PR review parity, parseRemoteUrl rewrite, cross-repo clone fixes, diff viewer flash fix
  v0.17.0 | AI code review agents, token-level annotation, merge-base diffs
  v0.16.7 | Gemini CLI plan review, install script skills directory fix
  v0.16.6 | Perforce support, Pi shared event API, suggested code prefill, file tree expand fix
  v0.16.5 | Resize handle scrollbar fix, VS Code Marketplace publish
  v0.16.4 | Compound planning improvement hook, GitHub Enterprise + self-hosted GitLab, dockview workspace, new themes
  v0.16.3 | Pi phase configuration, CLI help, untracked file discovery fix, review scroll reset
  v0.16.2 | Draggable comment popovers, cross-file annotation visibility, custom diff fonts, OpenCode verbose log fix
  v0.16.1 | SSE stream idle timeout fix for external annotations API
  
  What's New in v0.17.5
  
  v0.17.5 is a hotfix for a server crash affecting plannotator review on systems without Perforce installed, plus a fix for stale OpenCode plugin caches that the install script failed to clear.
  
  VCS Detection Crash When Perforce Is Not Installed
  
  When running plannotator review, the server detects which version control system manages the current directory. The detection loop tries each provider in order: git first, then Perforce (p4). The Perforce provider calls Bun.spawn(["p4", "info"]) to check for a workspace. On systems where the p4 binary isn't installed, Bun.spawn throws an ENOENT error that was not caught. The unhandled exception crashed the Bun server process.
  
  This affected every user who doesn't have Perforce installed and ran plannotator review. The git provider's detection had the same vulnerability — if git wasn't in $PATH (possible on some Windows configurations), the spawn would throw before Perforce detection even ran.
  
  Both providers now catch spawn failures and return false, allowing the detection loop to continue to the next provider or fall back to git as the default. Perforce support continues to work for users who have it installed.
  - Fixing #528, reported by @Zengwenj
  Install Script Cache Path Fix
  
  The install script clears cached OpenCode plugin packages to force a fresh download on the next run. The cache-busting targeted ~/.cache/opencode/node_modules/@plannotator, but OpenCode actually stores plugin packages at ~/.cache/opencode/packages/@plannotator. Users who ran the install script to update were still running the old cached plugin version in OpenCode until the cache expired or was manually cleared.
  
  Both install.sh and install.ps1 now clear the correct path.
  
  Install / Update
  
  macOS / Linux:
```
curl -fsSL https://plannotator.ai/install.sh | bash
```
  Windows:
```
irm https://plannotator.ai/install.ps1 | iex
```
  Pin a specific version:
```
curl -fsSL https://plannotator.ai/install.sh | bash -s -- --version v0.17.5
```
  Claude Code Plugin: Run /plugin in Claude Code, find plannotator , and click "Update now".
  
  Copilot CLI:
```
/plugin marketplace add backnotprop/plannotator
/plugin install plannotator-copilot@plannotator
```
  Gemini CLI: The install script auto-detects ~/.gemini and configures hooks, policy, and slash commands. See apps/gemini/README.md for manual setup.
  
  OpenCode: Clear cache and restart:
```
rm -rf ~/.cache/opencode/packages/@plannotator ~/.bun/install/cache/@plannotator
```
  Then in opencode.json:
```
{
  "plugin": ["@plannotator/opencode@latest"]
}
```
  Pi: Install or update the extension:
```
pi install npm:@plannotator/pi-extension
```
  VS Code Extension: Install from the VS Code Marketplace. Tested with Claude Code running in VS Code's integrated terminal. Not currently compatible with Anthropic's official VS Code extension due to upstream hook bugs.
  
  What's Changed
  - fix: catch VCS detection spawn failures when p4/git not in PATH by @backnotprop in #527
  - fix: correct OpenCode cache path in install scripts by @backnotprop in #527
  Community
  
  @Zengwenj reported the crash in #528 with a clear reproduction path and suspected cause. @xxJava confirmed the issue on both Windows and macOS and provided the full stack trace that pinpointed the exact line in p4.ts. @boris- gorbylev and @chocochu confirmed the issue on macOS with OpenCode.
  
  Full Changelog : v0.17.4...v0.17.5
15. 🔗 r/york help me raise money for homeless people in york! rss
  
  | apologies to the mods if this counts as self-promotion, but I'm hoping charity events might be an exception? on april 30 i will be sleeping outdoors at york community stadium to raise money for Hoping Kitchen and KEYS who both support homeless and vulnerable people in York (with other people as part of an event, i'm not just going to scale the walls and break in) i volunteer a few times a week with Carecent and Hoping Kitchen and i think everyone we help is so wonderful and deserves as much support as possible, which is why i'm really hoping i might be able to help raise some money for them this year. it obviously does not compare to actually sleeping rough in any way, and at worst I will be uncomfortable and probably not sleep at all, but my pets will miss me lots and be very sad. i am trying to raise at least £250 and currently have £0 of donations and i’m worried everyone will think i have no friends if no one sponsors me soon :( donate here or feel free to ask any questions! submitted by /u/kittywenham
  [link] [comments]
  ---|---
16. 🔗 r/Harrogate Mens Casual Football rss
  
  My husband used to be an OK footballer - played into being a young adult in local leagues. He'd like to get back into playing in a team but isn't sure where to start. He doesn't have reddit so has asked me to post this for him.
  
  He's 45 and looking to play once or twice a week just casually for fitness and fun. Advice welcome.
  
  submitted by /u/Mean_Connection_9032
  [link] [comments]
17. 🔗 Locklin on science Beyond Quantum with Khrennikov rss
  
  I’ve gone through Khrennikov’s “Beyond Quantum” book and write some notes for the crowd. I’ve also had a look at his book “Contextual Approach to Quantum Formalism,” and at least glanced at his more fruity books. Mostly this is a review of Beyond Quantum, which is a presentation of a group of “sub quantum” ideas. […]
18. 🔗 r/Leeds Slimy facial recognition van set up on New York Street rss
  
  Disgusting to see, when did such surveillance tools and technology become so normalised?
  
  Not gonna claim this area doesn't have it's issues, it sure does. But lazily plopping a facial recognition van is absolutely not the way to deal with this. It's the same characters round here committing most of the crimes, all it takes is a bit of actual policing. Not this gross overreach
  
  A little afraid I'm gonna find out in the comments that most people are fine to see this
  
  submitted by /u/semaphoreslimshady42
  [link] [comments]
19. 🔗 r/reverseengineering Porting Mac OS X to the Nintendo Wii rss
  
  submitted by /u/igor_sk
  [link] [comments]
20. 🔗 r/york The York food waste "saints" who feed city's children rss
  
  | submitted by /u/Kagedeah
  [link] [comments]
  ---|---
21. 🔗 r/wiesbaden Jetzt auch in Wiesi rss
  
  submitted by /u/Confuseacat92
  [link] [comments]
22. 🔗 r/Leeds Skaters over 30 rss
  
  I've recently gotten back into skateboarding at age 34 and I was wondering if there are any skater groups in Leeds for people over 30, or a little older than kids at least.
  
  If not, would anybody here be willing to start one up?
  
  Thanks!
  
  submitted by /u/Thommunster
  [link] [comments]
23. 🔗 pydantic/monty v0.0.10 - 2026-04-09 release
  What's Changed
  - add README link to Go bindings by @ewhauser in #298
  - Support multi-module import statements (import a, b, c) by @ilblackdragon in #296
  - Async in rust by @samuelcolvin in #280
  - make ui testing more efficient (via cargo rustc --profile=check) by @davidhewitt in #301
  - deduplicate Executor and ReplExecutor types by @davidhewitt in #303
  - Mounting filesystems by @samuelcolvin in #305
  - Fix PGO and cross-arch CI builds failing on missing typing_extensions by @penberg in #308
  - Introduce yamlfmt by @Viicos in #311
  - Introduce zizmor by @Viicos in #312
  - Fix input in CI by @Viicos in #313
  New Contributors
  - @ewhauser made their first contribution in #298
  - @ilblackdragon made their first contribution in #296
  - @penberg made their first contribution in #308
  - @Viicos made their first contribution in #311
  Full Changelog : v0.0.9...v0.0.10
24. 🔗 r/LocalLLaMA Gemma 4 on Llama.cpp should be stable now rss
  With the merging of https://github.com/ggml-org/llama.cpp/pull/21534, all of the fixes to known Gemma 4 issues in Llama.cpp have been resolved. I've been running Gemma 4 31B on Q5 quants for some time now with no issues.
  
  Runtime hints:
  - remember to run with --chat-template-file with the interleaved template Aldehir has prepared (it's in the llama.cpp code under models/templates)
  - I strongly encourage running with --cache-ram 2048 -ctxcp 2 to avoid system RAM problems
  - running KV cache with Q5 K and Q4 V has shown no large performance degradation, of course YMMV
  Have fun :)
  
  (oh yeah, important remark - when I talk about llama.cpp here, I mean the source code, not the releases which lag behind - this refers to the code built from current master)
  
  Important note about building: DO NOT currently use CUDA 13.2 as it is CONFIRMED BROKEN (the NVidia people are on the case already) and will generate builds that will not work correctly.
  
  submitted by /u/ilintar
  [link] [comments]
25. 🔗 r/Yorkshire Gannet launching gracefully from a rock at RSPB Bempton Cliffs rss
  
  | submitted by /u/aspiranthighlander
  [link] [comments]
  ---|---
26. 🔗 r/Leeds Recruitment agencies that aggressively help you find a role? rss
  
  I haven’t found my niche yet and looking to try new things, so temporarily contract work would be good for me atm. I have some qualifications and experience in a professional setting but im awful at interviews and not getting enough to improve that. I am currently feeling the pressure to find something quickly and was hoping someone could help with the names of some recruitment firms that secure interviews on your behalf… Cheers.
  
  submitted by /u/becordisman00
  [link] [comments]
27. 🔗 r/LocalLLaMA It's insane how lobotomized Opus 4.6 is right now. Even Gemma 4 31B UD IQ3 XXS beat it on the carwash test on my 5070 TI. rss
  
  | submitted by /u/FrozenFishEnjoyer
  [link] [comments]
  ---|---
28. 🔗 Console.dev newsletter Skir rss
  
  Description: Declarative language for types & APIs.
  
  What we like: Define the schema then generate idiomatic, type-safe code (Python, Go, Java, Rust, TS, etc). Dynamic serialization options e.g. binary or JSON. VS Code extension & LSP tooling. Supports backwards compatibility when changing schemas.
  
  What we dislike: Compile-time errors if you add a field, but don’t regenerate the code - this is the opposite to protobuf which handles it by defaulting values. This may be better, depending on your philosophy.
29. 🔗 Console.dev newsletter Atomic rss
  
  Description: Knowledge graph.
  
  What we like: Local, open source, markdown-based knowledge base. Auto-generates wiki articles from tags. Built-in semantic search with vector embeddings. Supports different types e.g. markdown notes, web clips, articles. Supports MCP. Can be an HTTP server without a desktop UI.
  
  What we dislike: Everything is self hosted so you need to do some setup work. This is also a benefit.
April 08, 2026
1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-04-08 rss
  IDA Plugin Updates on 2026-04-08
  
  Activity:
  - python-elpida_core.py
    
    8dc18b89: feat: remove code_edit exclusion from Stage 2 — the system speaks its…
    
    a9aec531: fix: desperation guard — cycle 52 heartbeat is run-complete, not crisis
    
    b8154d26: feat: Parliament rebalancing — evidence-based provider reassignment
2. 🔗 r/Yorkshire Can’t have anything these days rss
  
  submitted by /u/73747463783737384777
  [link] [comments]
3. 🔗 backnotprop/plannotator v0.17.4 release
  Follow @plannotator on X for updates
  
  Missed recent releases? Release | Highlights
  ---|---
  v0.17.3 | Sticky lane repo/branch badge overflow fix
  v0.17.2 | Supply-chain hardening, sticky toolstrip and badges, overlay scrollbars, external annotation highlighting, Conventional Comments
  v0.17.1 | Pi PR review parity, parseRemoteUrl rewrite, cross-repo clone fixes, diff viewer flash fix
  v0.17.0 | AI code review agents, token-level annotation, merge-base diffs
  v0.16.7 | Gemini CLI plan review, install script skills directory fix
  v0.16.6 | Perforce support, Pi shared event API, suggested code prefill, file tree expand fix
  v0.16.5 | Resize handle scrollbar fix, VS Code Marketplace publish
  v0.16.4 | Compound planning improvement hook, GitHub Enterprise + self-hosted GitLab, dockview workspace, new themes
  v0.16.3 | Pi phase configuration, CLI help, untracked file discovery fix, review scroll reset
  v0.16.2 | Draggable comment popovers, cross-file annotation visibility, custom diff fonts, OpenCode verbose log fix
  v0.16.1 | SSE stream idle timeout fix for external annotations API
  v0.16.0 | GitHub Copilot CLI, external annotations API, bot callback URLs, interactive checkboxes, print support, diff display options
  
  What's New in v0.17.4
  
  v0.17.4 ships three PRs: a sidebar consolidation that folds the Obsidian vault browser into the Files tab, three new Kanagawa themes, and a Pi regression fix from @dmmulroy.
  
  Vault Browser Merged into Files Tab
  
  The sidebar previously had separate "Files" and "Vault" tabs when an Obsidian vault was configured. The two tabs had identical tree UI but parallel state, and switching between them broke the mental model of "files are files."
  
  The Vault tab is gone. Vault directories now appear as collapsible sections inside the Files tab, beneath project directories, marked with an Obsidian icon in the section header. Annotation count badges still appear per- directory. Disabling the vault in Settings removes the section without affecting project file browsing.
  
  Two server-side gaps accompany this change. The annotate server (both Bun and Pi) was missing the /api/obsidian/vaults, /api/reference/obsidian/files, and /api/reference/obsidian/doc endpoints — vault files were unreachable when opening linked docs via plannotator annotate ./. Those endpoints are now present on all three servers (plan, review, annotate).
  
  The sticky header lane was also incorrectly suppressed whenever a linked doc was active. That gate has been removed. The sticky bar now follows scroll behavior consistently regardless of mode.
  
  Net change is -334 lines: one Files tab handles all directory types uniformly.
  
  #526
  
  Kanagawa Themes
  
  Three Kanagawa variants join the theme picker as dark-only themes, placed alphabetically after Gruvbox:
  - Kanagawa Dragon — warmest variant, ash-black base (#181616) with muted teal accent
  - Kanagawa Wave — the classic Kanagawa, cool blue-purple base (#1f1f28) with purple accent
  - Kanagawa Bones — same base as Wave, earthier character, cyan-blue primary with brighter purple accent
  Colors are mapped directly from the official Ghostty Kanagawa palette.
  
  #524
  
  Additional Changes
  - Pi: planning tool stripped on fresh sessions. PR #446 refactored the Pi session_start handler to use applyPhaseConfig() but left the idle branch calling only restoreSavedState(), which no-ops when there's no saved state. On fresh sessions that had never entered planning mode, plannotator_submit_plan remained in the active tool set — a regression from #387. The idle branch now explicitly strips planning-only tools when there is no saved state to restore. (#525 by @dmmulroy)
  Install / Update
  
  macOS / Linux:
```
curl -fsSL https://plannotator.ai/install.sh | bash
```
  Windows:
```
irm https://plannotator.ai/install.ps1 | iex
```
  Pin a specific version:
```
curl -fsSL https://plannotator.ai/install.sh | bash -s -- --version v0.17.4
```
  Claude Code Plugin: Run /plugin in Claude Code, find plannotator , and click "Update now".
  
  Copilot CLI:
```
/plugin marketplace add backnotprop/plannotator
/plugin install plannotator-copilot@plannotator
```
  Gemini CLI: The install script auto-detects ~/.gemini and configures hooks, policy, and slash commands. See apps/gemini/README.md for manual setup.
  
  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
```
  VS Code Extension: Install from the VS Code Marketplace. Tested with Claude Code running in VS Code's integrated terminal. Not currently compatible with Anthropic's official VS Code extension due to upstream hook bugs.
  
  What's Changed
  - feat(sidebar): merge vault browser into files tab + UX polish by @backnotprop in #526
  - fix(pi): strip planning-only tools on fresh idle sessions by @dmmulroy in #525
  - feat(themes): add Kanagawa Dragon, Wave, and Bones themes by @backnotprop in #524
  Contributors
  
  @dmmulroy tracked down and fixed a regression in the Pi tool-scoping logic he originally authored in #387 (#525). This is his fourth contribution to the project.
  
  Full Changelog : v0.17.3...v0.17.4
4. 🔗 Simon Willison Meta's new model is Muse Spark, and meta.ai chat has some interesting tools rss
  Meta announced Muse Spark today, their first model release since Llama 4 almost exactly a year ago. It's hosted, not open weights, and the API is currently "a private API preview to select users", but you can try it out today on meta.ai (Facebook or Instagram login required).
  
  Meta's self-reported benchmarks show it competitive with Opus 4.6, Gemini 3.1 Pro, and GPT 5.4 on selected benchmarks, though notably behind on Terminal-Bench 2.0. Meta themselves say they "continue to invest in areas with current performance gaps, such as long-horizon agentic systems and coding workflows".
  
  The model is exposed as two different modes on meta.ai - "Instant" and "Thinking". Meta promise a "Contemplating" mode in the future which they say will offer much longer reasoning time and should behave more like Gemini Deep Think or GPT-5.4 Pro.
  
  A couple of pelicans
  
  I prefer to run my pelican test via API to avoid being influenced by any invisible system prompts, but since that's not an option I ran it against the chat UI directly.
  
  Here's the pelican I got for "Instant":
  
  And this one for "Thinking":
  
  Both SVGs were rendered inline by the Meta AI interface. Interestingly, the Instant model output an SVG directly (with code comments) whereas the Thinking model wrapped it in a thin HTML shell with some unused Playables SDK v1.0.0 JavaScript libraries.
  
  Which got me curious...
  
  Poking around with tools
  
  Clearly Meta's chat harness has some tools wired up to it - at the very least it can render SVG and HTML as embedded frames, Claude Artifacts style.
  
  But what else can it do?
  
  I asked it:
  
  what tools do you have access to?
  
  And then:
  
  I want the exact tool names, parameter names and tool descriptions, in the original format
  
  It spat out detailed descriptions of 16 different tools. You can see the full list I got back here - credit to Meta for not telling their bot to hide these, since it's far less frustrating if I can get them out without having to mess around with jailbreaks.
  
  Here are highlights derived from that response:
  - Browse and search. browser.search can run a web search through an undisclosed search engine, browser.open can load the full page from one of those search results and browser.find can run pattern matches against the returned page content.
  - Meta content search. meta_1p.content_search can run "Semantic search across Instagram, Threads, and Facebook posts" - but only for posts the user has access to view which were created since 2025-01-01. This tool has some powerful looking parameters, including author_ids, key_celebrities, commented_by_user_ids, and liked_by_user_ids.
  - "Catalog search" - meta_1p.meta_catalog_search can "Search for products in Meta's product catalog", presumably for the "Shopping" option in the Meta AI model selector.
  - Image generation. media.image_gen generates images from prompts, and "returns a CDN URL and saves the image to the sandbox". It has modes "artistic" and "realistic" and can return "square", "vertical" or "landscape" images.
  - container.python_execution - yes! It's Code Interpreter, my favourite feature of both ChatGPT and Claude.
    
    Execute Python code in a remote sandbox environment. Python 3.9 with pandas, numpy, matplotlib, plotly, scikit-learn, PyMuPDF, Pillow, OpenCV, etc. Files persist at /mnt/data/.
    
    Python 3.9 is EOL these days but the library collection looks useful.
    
    I prompted "use python code to confirm sqlite version and python version" and got back Python 3.9.25 and SQLite 3.34.1 (from January 2021).
  - container.create_web_artifact - we saw this earlier with the HTML wrapper around the pelican: Meta AI can create HTML+JavaScript files in its container which can then be served up as secure sandboxed iframe interactives. "Set kind to html for websites/apps or svg for vector graphics."
  - container.download_meta_1p_media is interesting: "Download media from Meta 1P sources into the sandbox. Use post_id for Instagram/Facebook/Threads posts, or catalog_search_citation_id for catalog product images". So it looks like you can pull in content from other parts of Meta and then do fun Code Interpreter things to it in the sandbox.
  - container.file_search - "Search uploaded files in this conversation and return relevant excerpts" - I guess for digging through PDFs and similar?
  - Tools for editing files in the container - container.view, container.insert (with new_str and insert_line), container.str_replace. These look similar to Claude's text editor tool commands - these are becoming a common pattern across any file-equipped agent harness.
  - container.visual_grounding - see below, this one is fun.
  - subagents.spawn_agent - the sub-agent as a tool pattern. "Spawn an independent sub-agent for research, analysis, or delegation. It returns its final text response."
  - third_party.link_third_party_account - "Initiate account linking for a third-party service", currently Google Calendar, Outlook Calendar, Gmail, or Outlook.
  Image analysis in the container
  
  Let's talk about that container.visual_grounding one. Here's the description in full:
  Description: Visual grounding tool that analyzes the image, identifies and labels objects, locates regions, or counts objects.
  
  Parameters:
  
  object_names (array, required)
  
  image_path (string, default "")
  
  format_type ("bbox"|"point"|"count"|null, default "bbox")
  
  title (string|null)[string]
  So it can take an image path, optional object names and return things in format bbox, point or count.
  
  This sounded to me like Meta's Segment Anything, (I later heard that it's not, this is a native feature of the model itself via a tool call with a custom system prompt). I decided to take it for a spin.
  
  Prompt:
  
  generate a photo of a raccoon sitting on a trash can wearing trash as a hat
  
  Response:
  
  Here you go — king of the alley, in full regalia:
  
  Coffee cup crown, banana peel brim, newspaper feather. Peak raccoon fashion. Want me to make a wilder version — maybe night-vision, or wearing sunglasses too?
  
  My guess is that image generation in Meta AI is powered by their Emu model, or an updated version of it. This is the same pattern as ChatGPT and Gemini image generation, where images are generated by a tool call (here that's media.image_gen).
  
  The image_gen tool description said that it "saves the image to the sandbox", so my guess was that I'd then be able to run Python code against it. I tried:
  
  use python OpenCV to analyze that image and find out neat things about it
  
  Annoyingly it did not show me the code it ran, but it did create this image:
  
  Pretty neat! We can both generate images and then use them with Python tools.
  
  Next, the visual_grounding tool. Knowing the names of the tools makes it easy to refer to them in prompts:
  
  Now try the container.visual_grounding tool
  
  The response (full response here):
  
  Done — visual_grounding pinpointed every piece of the outfit with pixel-level precision:
  
  [...]
  
  Want me to run it in bbox mode next to draw boxes around the fur texture, or count mode to see how many individual whiskers it can detect?
  
  Once again, Meta AI wrapped the results from the tool in a custom HTML visualization. That's clearly point mode, but how about the others?
  
  I prompted:
  
  yes draw bounding boxes, can it do masks too?
  
  Response:
  Yes — bounding boxes work great. Masks? Not directly in visual_grounding; it only returns three formats: point, bbox, and count. No pixel-level segmentation masks.
  
  Here's the bbox output:
  
  What you’re seeing:
  
  raccoon: big box from (270,240) to (892,845) — covers 62% of the width, basically the whole animal
  
  coffee cup: (424,115)-(610,273) — sits highest, 158px tall in the 0-1000 space
  
  banana peel: (472,215)-(667,291) — overlaps the cup's base, confirming it's draped over the side
  
  newspaper: (305,223)-(548,315) — left ear coverage
  
  trash can lid: (107,800)-(1000,998) — spans almost the full image width at the bottom
  
  face: (305,283)-(750,537) — tight crop around the mask
  
  eyes: both ~40×37 pixel boxes, perfectly level at y=379
  
  Notice how the boxes nest: face is inside raccoon, eyes inside face, hat pieces overlap each other but stay above the face box. The tool is doing real object localization, not just guessing centers.
  
  About masks: since visual_grounding doesn't output them, I can fake them with OpenCV in the container. Two quick options:
  
  GrabCut — I give it the raccoon bbox, it iteratively segments fur from background and returns a binary mask
  
  SAM-style color threshold — use the bbox plus k-means to isolate the coffee cup or banana peel
  
  Want me to generate an actual alpha mask for the raccoon (cut it out from the alley), or for the trash hat pieces separately? Takes about 10 seconds and I can give you a transparent PNG.
  Here's the HTML for that bbox visualization.
  
  Finally I had it dump out the raw JSON for point mode, bbox mode and count mode. You can see that all here. The count mode is particularly interesting - here's that in full:
  [ { "object_name": "raccoon whisker", "points": [ {"x": 403, "y": 445}, {"x": 397, "y": 458}, {"x": 392, "y": 472}, {"x": 391, "y": 485}, {"x": 398, "y": 497}, {"x": 415, "y": 512}, {"x": 618, "y": 446}, {"x": 622, "y": 461}, {"x": 625, "y": 475}, {"x": 628, "y": 488}, {"x": 635, "y": 501}, {"x": 651, "y": 518} ], "count": 12 }, { "object_name": "raccoon paw claw", "points": [ {"x": 406, "y": 845}, {"x": 424, "y": 847}, {"x": 441, "y": 842}, {"x": 473, "y": 833}, {"x": 596, "y": 830}, {"x": 635, "y": 844}, {"x": 660, "y": 843}, {"x": 679, "y": 838} ], "count": 8 }, { "object_name": "trash item on head", "points": [ {"x": 514, "y": 191}, {"x": 568, "y": 263}, {"x": 392, "y": 274} ], "count": 3 }, { "object_name": "eye", "points": [ {"x": 462, "y": 395}, {"x": 582, "y": 398} ], "count": 2 }, { "object_name": "ear", "points": [ {"x": 359, "y": 313}, {"x": 680, "y": 294} ], "count": 2 } ]
  So Meta AI has the ability to count a raccoon's whiskers baked into the default set of tools.
  
  Which means... it can count pelicans too!
  
  Here's that overlay exported as HTML.
  
  Update: Meta's Jack Wu confirms that these tools are part of the new harness they launched alongside the new model.
  
  Maybe open weights in the future?
  
  On Twitter Alexandr Wang said:
  
  this is step one. bigger models are already in development with infrastructure scaling to match. private api preview open to select partners today, with plans to open-source future versions.
  
  I really hope they do go back to open-sourcing their models. Llama 3.1/3.2/3.3 were excellent laptop-scale model families, and the introductory blog post for Muse Spark had this to say about efficiency:
  
  [...] we can reach the same capabilities with over an order of magnitude less compute than our previous model, Llama 4 Maverick. This improvement also makes Muse Spark significantly more efficient than the leading base models available for comparison.
  
  So are Meta back in the frontier model game? Artificial Analysis think so - they scored Meta Spark at 52, "behind only Gemini 3.1 Pro, GPT-5.4, and Claude Opus 4.6". Last year's Llama 4 Maverick and Scout scored 18 and 13 respectively.
  
  I'm waiting for API access - while the tool collection on meta.ai is quite strong the real test of a model like this is still what we can build on top of it.
  
  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.
5. 🔗 anthropics/claude-code v2.1.97 release
  What's changed
  - Added focus view toggle (Ctrl+O) in NO_FLICKER mode showing prompt, one-line tool summary with edit diffstats, and final response
  - Added refreshInterval status line setting to re-run the status line command every N seconds
  - Added workspace.git_worktree to the status line JSON input, set when the current directory is inside a linked git worktree
  - Added ● N running indicator in /agents next to agent types with live subagent instances
  - Added syntax highlighting for Cedar policy files (.cedar, .cedarpolicy)
  - Fixed --dangerously-skip-permissions being silently downgraded to accept-edits mode after approving a write to a protected path
  - Fixed and hardened Bash tool permissions, tightening checks around env-var prefixes and network redirects, and reducing false prompts on common commands
  - Fixed permission rules with names matching JavaScript prototype properties (e.g. toString) causing settings.json to be silently ignored
  - Fixed managed-settings allow rules remaining active after an admin removed them until process restart
  - Fixed permissions.additionalDirectories changes in settings not applying mid-session
  - Fixed removing a directory from settings.permissions.additionalDirectories revoking access to the same directory passed via --add-dir
  - Fixed MCP HTTP/SSE connections accumulating ~50 MB/hr of unreleased buffers when servers reconnect
  - Fixed MCP OAuth oauth.authServerMetadataUrl not being honored on token refresh after restart, fixing ADFS and similar IdPs
  - Fixed 429 retries burning all attempts in ~13 seconds when the server returns a small Retry-After — exponential backoff now applies as a minimum
  - Fixed rate-limit upgrade options disappearing after context compaction
  - Fixed several /resume picker issues: --resume <name> opening uneditable, Ctrl+A reload wiping search, empty list swallowing navigation, task-status text replacing conversation summary, and cross-project staleness
  - Fixed file-edit diffs disappearing on --resume when the edited file was larger than 10KB
  - Fixed --resume cache misses and lost mid-turn input from attachment messages not being saved to the transcript
  - Fixed messages typed while Claude is working not being persisted to the transcript
  - Fixed prompt-type Stop/SubagentStop hooks failing on long sessions, and hook evaluator API errors displaying "JSON validation failed" instead of the actual message
  - Fixed subagents with worktree isolation or cwd: override leaking their working directory back to the parent session's Bash tool
  - Fixed compaction writing duplicate multi-MB subagent transcript files on prompt-too-long retries
  - Fixed claude plugin update reporting "already at the latest version" for git-based marketplace plugins when the remote had newer commits
  - Fixed slash command picker breaking when a plugin's frontmatter name is a YAML boolean keyword
  - Fixed copying wrapped URLs in NO_FLICKER mode inserting spaces at line breaks
  - Fixed scroll rendering artifacts in NO_FLICKER mode when running inside zellij
  - Fixed a crash in NO_FLICKER mode when hovering over MCP tool results
  - Fixed a NO_FLICKER mode memory leak where API retries left stale streaming state
  - Fixed slow mouse-wheel scrolling in NO_FLICKER mode on Windows Terminal
  - Fixed custom status line not displaying in NO_FLICKER mode on terminals shorter than 24 rows
  - Fixed Shift+Enter and Alt/Cmd+arrow shortcuts not working in Warp with NO_FLICKER mode
  - Fixed Korean/Japanese/Unicode text becoming garbled when copied in no-flicker mode on Windows
  - Fixed Bedrock SigV4 authentication failing when AWS_BEARER_TOKEN_BEDROCK or ANTHROPIC_BEDROCK_BASE_URL are set to empty strings (as GitHub Actions does for unset inputs)
  - Improved Accept Edits mode to auto-approve filesystem commands prefixed with safe env vars or process wrappers (e.g. LANG=C rm foo, timeout 5 mkdir out)
  - Improved auto mode and bypass-permissions mode to auto-approve sandbox network access prompts
  - Improved sandbox: sandbox.network.allowMachLookup now takes effect on macOS
  - Improved image handling: pasted and attached images are now compressed to the same token budget as images read via the Read tool
  - Improved slash command and @-mention completion to trigger after CJK sentence punctuation, so Japanese/Chinese input no longer requires a space before / or @
  - Improved Bridge sessions to show the local git repo, branch, and working directory on the claude.ai session card
  - Improved footer layout: indicators (Focus, notifications) now stay on the mode-indicator row instead of wrapping below
  - Improved context-low warning to show as a transient footer notification instead of a persistent row
  - Improved markdown blockquotes to show a continuous left bar across wrapped lines
  - Improved session transcript size by skipping empty hook entries and capping stored pre-edit file copies
  - Improved transcript accuracy: per-block entries now carry the final token usage instead of the streaming placeholder
  - Improved Bash tool OTEL tracing: subprocesses now inherit a W3C TRACEPARENT env var when tracing is enabled
  - Updated /claude-api skill to cover Managed Agents alongside the Claude API
6. 🔗 r/wiesbaden Dein erster Pulli: Strickworkshop in Wiesbaden Westend rss
  
  Hey zusammen 🤍
  
  bei unseren KNIT&MEET Events kam öfter die Frage auf, wie man eigentlich den ersten Pulli strickt. Deshalb haben wir für Samstag in Wiesbaden einen kleinen Workshop dazu organisiert.
  
  In der ersten Hälfte geht’s um die Basics: wie Pullis aufgebaut sind, wie man Patterns liest und worauf man am Anfang achten sollte. In der zweiten Hälfte schauen wir uns auch mitgebrachte Patterns an, beantworten Fragen und helfen beim Start.
  
  Falls das hier für jemanden interessant ist, schicke ich die Infos gern per DM oder poste den Link in die Kommentare :)
  
  submitted by /u/authentic_n_creative
  [link] [comments]
7. 🔗 r/wiesbaden Yoga in Kastel rss
  
  Hat jemand Lust auf Outdoor Yoga in Mainz-Kastel am Rhein? Jeder ist Willkommen. Ich bin Yoga Lehrerin und würde gerne eine Community hier aufbauen ✨
  
  submitted by /u/flowyogamarie
  [link] [comments]
8. 🔗 jcrist/msgspec Version 0.21.0 release
  - Fix a segfault on Python 3.13+ that could occur when creating structs that contained a __dict__, instead of only using __slots__ (#960).
  - Improve type annotations for msgspec.UNSET (#975).
  - Fix hashing of decoded tuples on Python 3.14 (#980).
  - Add ref_template arg to msgspec.json.schema (#983).
  - Add missing libm linkage to some architectures (#993).
  - Fix memory leak when decoding sets (#991).
  - Add uniqueItems annotation to set/frozenset JSON schemas (#984).
  - BREAKING : Call __post_init__ from msgspec.structs.replace/copy.replace (#1000).
9. 🔗 r/york York therapists rss
  
  I'm looking for recommendations for therapists in the York area who specialise in adults dealing with the effects of being abused as a child/teen by a parent, and ideally has experience with Autistic people. Who have you really clicked with? I'm particularly interested in people who are clear and concise, and who don't talk in circles or metaphors.
  
  Ideally based in the city center, or Acomb.
  
  Thank you!
  
  submitted by /u/I-am-a-commotion
  [link] [comments]
10. 🔗 r/LocalLLaMA It finally happened, I actually had a use case for a local LLM and it was brilliant rss
  
  | https://preview.redd.it/6v2q5726j0ug1.png?width=2950&format=png&auto=webp&s=142b34c6829d80d7ff807a3a589441463d0babf9 I've had aerosinusitis a few times before in my life and it was fairly painful, but not something that happens often. Today on a flight I had an overwhelming bout of it, the pressure was genuinely unbearable, and I had no painkillers with me. I was on a cheap flight, in the cheap seats so no Wifi. I've been playing around with local LLMs on my laptop for a year or so, but it's always been pure novelty. It suddenly dawned on me that I could use Gemma 4 mid-air, and so I pulled out my laptop and asked for any way I could possibly reduce the pain. The Toynbee Maneuver, which I had never in my life heard of, slowly but surely relieved the pressure. Within 10 mins I felt completely fine. It may sound trivial, but without local AI I would have been in blinding pain for probably 90 mins – so it was a rare moment when new technology actually makes a palpable difference to your life. Sharing this here because my wife didn't care and I felt if anyone would appreciate this small win it would be this community. submitted by /u/EntertainerFew2832
  [link] [comments]
  ---|---
11. 🔗 r/wiesbaden The vendor at the newspaper stand just kind of accepted it rss
  
  submitted by /u/elena4047
  [link] [comments]
12. 🔗 r/Leeds Leeds nail tech recommendations rss
  
  I've never gotten my nails done before but I wanna try out smth like this as a treat! Any recommendations for a Leeds based nail artist who could do this?
  
  submitted by /u/cococoterie
  [link] [comments]
13. 🔗 r/Leeds Rhinos fan to take on 108-mile ultra-marathon for MNDA rss
  
  submitted by /u/TexturePackReview
  [link] [comments]
14. 🔗 backnotprop/plannotator v0.17.3 release
  Follow @plannotator on X for updates
  
  Missed recent releases? Release | Highlights
  ---|---
  v0.17.1 | Pi PR review parity, parseRemoteUrl rewrite, cross-repo clone fixes, diff viewer flash fix
  v0.17.0 | AI code review agents, token-level annotation, merge-base diffs
  v0.16.7 | Gemini CLI plan review, install script skills directory fix
  v0.16.6 | Perforce support, Pi shared event API, suggested code prefill, file tree expand fix
  v0.16.5 | Resize handle scrollbar fix, VS Code Marketplace publish
  v0.16.4 | Compound planning improvement hook, GitHub Enterprise + self-hosted GitLab, dockview workspace, new themes
  v0.16.3 | Pi phase configuration, CLI help, untracked file discovery fix, review scroll reset
  v0.16.2 | Draggable comment popovers, cross-file annotation visibility, custom diff fonts, OpenCode verbose log fix
  v0.16.1 | SSE stream idle timeout fix for external annotations API
  v0.16.0 | GitHub Copilot CLI, external annotations API, bot callback URLs, interactive checkboxes, print support, diff display options
  v0.15.5 | Custom display names, GitHub viewed file sync, expand/collapse all in file tree, search performance, WSL fix
  v0.15.2 | Compound Planning skill, folder annotation, /plannotator-archive slash command, skill installation via platform installers
  
  What's New in v0.17.3
  
  v0.17.3 is a substantial release covering ten PRs — supply-chain hardening with SLSA build attestations, a major plan header overhaul with sticky toolstrip and badges, overlay scrollbars across the entire app, inline highlighting for external annotations, Conventional Comments in code review, and several smaller fixes from the community. Two contributors from outside the core team shipped changes this cycle.
  
  Sticky Toolstrip and Badges
  
  The stickyActionsEnabled setting previously only pinned the right-side action buttons. The annotation toolstrip (selection mode + editor mode toggles) and the left-side badges (repo, branch, plan diff) scrolled away with the document, forcing you back to the top to switch modes or jump into a diff.
  
  A new ghost sticky lane fades in once you scroll past the original toolstrip, pinning the toolstrip and badges on the same horizontal plane as the action buttons. The compact bar uses a row layout for badges and hides label text on inactive toolstrip modes to leave room. Top-of-document rendering is unchanged. The lane stays hidden in plan-diff mode, archive mode, linked-doc mode, and when sticky actions is off. Honors prefers-reduced-motion.
  
  #510
  
  Conventional Comments in Code Review
  
  The code review annotation toolbar now has an optional Conventional Comments label picker — suggestion, issue, nitpick, question, and others, with an inline blocking/non- blocking toggle per label. Annotations export in conventional format (**label** (decoration): text) as plain markdown, compatible with GitHub PRs and any text-based review system.
  
  A dedicated Comments settings tab houses the master toggle (off by default), a label editor for adding/editing/deleting/reordering custom labels, per-label blocking decorator toggle, an educational "how it works" section linking to the spec, and live example output. Drafts persist label and decoration state across file switches.
  
  #501
  
  Unified Plan Header Dropdown and Agent Instructions
  
  Plan mode's header has been consolidated. The sprawled desktop toolbar (mode toggle, standalone Settings button, custom export sub-dropdown) and the separate mobile menu are now a single PlanHeaderMenu rendered at all breakpoints, modeled on the existing review header menu. The version number and release notes link moved into the dropdown footer.
  
  A new "Agent Instructions" item copies a clipboard payload teaching external agents (Claude Code, Codex, custom scripts) how to POST annotations into the live session via /api/external-annotations. The instruction body lives in packages/ui/utils/planAgentInstructions.ts so it can be edited independently of UI code.
  
  The PR also fixes a long-standing bug where the Send Annotations / Approve cluster was hidden whenever a linked doc was active, blocking submission for users running plannotator annotate ./ once they opened a file.
  
  #515
  
  Header Polish: Coordinated Shrinking, Share/Copy Cleanup
  
  Sticky header label shrinking is now driven by measured geometry instead of fixed pixel reserves. A ResizeObserver on the wrapper plus another on the action button cluster computes exactly how much room is available; both sides of the header shrink in lockstep so they stay horizontally aligned as long as possible. Below ~340px of plan area the ghost bar stacks below the action buttons.
  
  "Quick Share" and "Quick Copy" are now plain "Share" and "Copy". Share opens the existing export modal so it benefits from the short-link path for large payloads instead of dumping a 50KB hash URL straight to the clipboard.
  
  The sidebar rail no longer pushes the background grid pattern 30px to the right — it floats over the document area, and the grid paints edge-to-edge under the sidebar flags.
  
  #519
  
  Overlay Scrollbars
  
  Wide, translucent, full-length overlay scrollbars across plan mode and code review, replacing the 6px WebKit rail that was hard to grab. Click the track to page-animate toward the click; drag the thumb smoothly; no layout shift; Firefox parity; respects prefers-reduced-motion; disappears in print.
  
  Backed by overlayscrollbars-react wrapped in a new OverlayScrollArea component. Native scroll semantics stay on the viewport element so existing scrollIntoView and scrollTo calls still work. Wrapped containers include the main plan viewer, annotation panel, sidebar tabs, settings and export modals, file tree, review sidebar, AI chat tab, PR comments timeline, and PR summary/checks dock panels.
  
  #509, closing #354
  
  Inline Highlighting for External Annotations
  
  External annotations posted via POST /api/external-annotations can now optionally highlight the matching originalText span inline in the rendered plan — COMMENT renders yellow, DELETION renders strikethrough. Annotations without originalText or of type GLOBAL_COMMENT continue to render sidebar- only.
  
  No protocol or schema change. Tools choose inline vs global purely by what they supply. If originalText doesn't match anywhere in the rendered DOM, the annotation degrades gracefully to sidebar-only with a console warning. PATCH and DELETE through the API correctly remove and reapply highlights as state changes.
  
  #511
  
  Supply-Chain Hardening
  
  The release pipeline now generates SLSA build provenance attestations for every released binary. Each of the twelve cross-compiled binaries (six Plannotator targets, six paste-service targets) is signed via Sigstore and recorded in Rekor through actions/attest-build-provenance. Top-level workflow permissions have been tightened to contents: read with per-job overrides.
  
  Installers now accept a --version v0.X.Y flag (and positional form), so you can pin to a specific version instead of always pulling latest. The default behavior is unchanged.
  
  Attestation verification is opt-in via three mechanisms with documented precedence: a --verify-attestation CLI flag, a PLANNOTATOR_VERIFY_ATTESTATION=1 environment variable, or { "verifyAttestation": true } in ~/.plannotator/config.json. Off by default to match how rustup, brew, bun, deno, and helm handle attestation — turning it on hard-fails the install if gh isn't available, so opt-in is never silently skipped. Anyone can still verify any release manually with gh attestation verify.
  
  The same PR fixes a Windows installer crash where cmd.exe's enabledelayedexpansion was eating the ! characters in an embedded node -e script during Gemini settings merge.
  
  #512, closing #506 and parts of #507
  
  Additional Changes
  - Numbered list rendering. Ordered lists like 1., 2., 10. were rendered as bullet points because the parser collapsed all list types into a single block kind. The parser now captures the numeric marker and tags the block as ordered; a new computeListIndices helper assigns CommonMark-correct display numbers including streak break/restart on mixed siblings and independent numbering for nested ordered sublists. The renderer uses tabular-nums so 9 to 10 doesn't jitter (#520)
  - Underscore italics. The custom markdown renderer supported *italic* but not _italic_. Now both work, while intraword underscores like snake_case continue to render as plain text (#504 by @foxytanuki, closing #502)
  - Perforce added files on Windows. P4-added files were missing from the review UI on Windows because p4 where stdout uses \r\n line endings; splitting on \n left a stray \r in every file path except the last, causing Bun.file() to silently fail. The fix normalizes line endings on all P4 command output and replaces fragile index-based parsing with p4 -ztag where field-based parsing, which is also more robust for stream depots and overlay mappings (#494 by @l10veu602)
  Install / Update
  
  macOS / Linux:
```
curl -fsSL https://plannotator.ai/install.sh | bash
```
  Windows:
```
irm https://plannotator.ai/install.ps1 | iex
```
  Pin a specific version:
```
curl -fsSL https://plannotator.ai/install.sh | bash -s -- --version v0.17.3
```
  Claude Code Plugin: Run /plugin in Claude Code, find plannotator , and click "Update now".
  
  Copilot CLI:
```
/plugin marketplace add backnotprop/plannotator
/plugin install plannotator-copilot@plannotator
```
  Gemini CLI: The install script auto-detects ~/.gemini and configures hooks, policy, and slash commands. See apps/gemini/README.md for manual setup.
  
  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
```
  VS Code Extension: Install from the VS Code Marketplace. Tested with Claude Code running in VS Code's integrated terminal. Not currently compatible with Anthropic's official VS Code extension due to upstream hook bugs.
  
  What's Changed
  - fix(ui): render numerals for ordered list items by @backnotprop in #520
  - feat(plan): simplify share/copy + sticky header polish by @backnotprop in #519
  - chore: supply-chain hardening — version pinning, SLSA attestations, install fix by @backnotprop in #512
  - feat(plan): unified header dropdown + Agent Instructions by @backnotprop in #515
  - feat: Zed-style overlay scrollbars by @backnotprop in #509
  - feat(plan): complete sticky actions — pin toolstrip + badges on scroll by @backnotprop in #510
  - feat(ui): highlight external SSE annotations inline on plan text by @backnotprop in #511
  - fix: support underscore italics in markdown renderer by @foxytanuki in #504
  - feat: add Conventional Comments support to code review by @backnotprop in #501
  - fix(review): show P4 added files in code review by @l10veu602 in #494
  Contributors
  
  @foxytanuki returned with the underscore italics fix (#504, closing #502). The custom markdown renderer now treats _italic_ and *italic* as equivalent emphasis while leaving snake_case alone. Their fourth contribution to the project.
  
  @l10veu602 fixed the Perforce added-files regression on Windows (#494). The bug was a classic \r\n line-ending issue in p4 where stdout that left stray carriage returns in file paths, causing Bun.file() to silently miss them. The fix also swaps fragile index-based parsing for p4 -ztag structured output, which holds up better on stream depots and overlay mappings. Verified on a real P4 workspace going from 13 files visible to all 17.
  
  Community members who reported issues addressed in this release:
  - @djamatgit: #506 (install.cmd Gemini settings merge crash on Windows)
  - @rooterkyberian: #507 (supply-chain hardening — items 1 & 2)
  - @Thraka: #502 (underscore italics not rendering)
  - @dillonoconnor: #354 (couldn't grab the scrollbar)
  Full Changelog : v0.17.1...v0.17.3
15. 🔗 backnotprop/plannotator v0.17.2 release
  Follow @plannotator on X for updates
  
  Missed recent releases? Release | Highlights
  ---|---
  v0.17.1 | Pi PR review parity, parseRemoteUrl rewrite, cross-repo clone fixes, diff viewer flash fix
  v0.17.0 | AI code review agents, token-level annotation, merge-base diffs
  v0.16.7 | Gemini CLI plan review, install script skills directory fix
  v0.16.6 | Perforce support, Pi shared event API, suggested code prefill, file tree expand fix
  v0.16.5 | Resize handle scrollbar fix, VS Code Marketplace publish
  v0.16.4 | Compound planning improvement hook, GitHub Enterprise + self-hosted GitLab, dockview workspace, new themes
  v0.16.3 | Pi phase configuration, CLI help, untracked file discovery fix, review scroll reset
  v0.16.2 | Draggable comment popovers, cross-file annotation visibility, custom diff fonts, OpenCode verbose log fix
  v0.16.1 | SSE stream idle timeout fix for external annotations API
  v0.16.0 | GitHub Copilot CLI, external annotations API, bot callback URLs, interactive checkboxes, print support, diff display options
  v0.15.5 | Custom display names, GitHub viewed file sync, expand/collapse all in file tree, search performance, WSL fix
  v0.15.2 | Compound Planning skill, folder annotation, /plannotator-archive slash command, skill installation via platform installers
  
  What's New in v0.17.2
  
  v0.17.2 is a substantial release covering ten PRs — supply-chain hardening with SLSA build attestations, a major plan header overhaul with sticky toolstrip and badges, overlay scrollbars across the entire app, inline highlighting for external annotations, Conventional Comments in code review, and several smaller fixes from the community. Two contributors from outside the core team shipped changes this cycle.
  
  Sticky Toolstrip and Badges
  
  The stickyActionsEnabled setting previously only pinned the right-side action buttons. The annotation toolstrip (selection mode + editor mode toggles) and the left-side badges (repo, branch, plan diff) scrolled away with the document, forcing you back to the top to switch modes or jump into a diff.
  
  A new ghost sticky lane fades in once you scroll past the original toolstrip, pinning the toolstrip and badges on the same horizontal plane as the action buttons. The compact bar uses a row layout for badges and hides label text on inactive toolstrip modes to leave room. Top-of-document rendering is unchanged. The lane stays hidden in plan-diff mode, archive mode, linked-doc mode, and when sticky actions is off. Honors prefers-reduced-motion.
  
  #510
  
  Conventional Comments in Code Review
  
  The code review annotation toolbar now has an optional Conventional Comments label picker — suggestion, issue, nitpick, question, and others, with an inline blocking/non- blocking toggle per label. Annotations export in conventional format (**label** (decoration): text) as plain markdown, compatible with GitHub PRs and any text-based review system.
  
  A dedicated Comments settings tab houses the master toggle (off by default), a label editor for adding/editing/deleting/reordering custom labels, per-label blocking decorator toggle, an educational "how it works" section linking to the spec, and live example output. Drafts persist label and decoration state across file switches.
  
  #501
  
  Unified Plan Header Dropdown and Agent Instructions
  
  Plan mode's header has been consolidated. The sprawled desktop toolbar (mode toggle, standalone Settings button, custom export sub-dropdown) and the separate mobile menu are now a single PlanHeaderMenu rendered at all breakpoints, modeled on the existing review header menu. The version number and release notes link moved into the dropdown footer.
  
  A new "Agent Instructions" item copies a clipboard payload teaching external agents (Claude Code, Codex, custom scripts) how to POST annotations into the live session via /api/external-annotations. The instruction body lives in packages/ui/utils/planAgentInstructions.ts so it can be edited independently of UI code.
  
  The PR also fixes a long-standing bug where the Send Annotations / Approve cluster was hidden whenever a linked doc was active, blocking submission for users running plannotator annotate ./ once they opened a file.
  
  #515
  
  Header Polish: Coordinated Shrinking, Share/Copy Cleanup
  
  Sticky header label shrinking is now driven by measured geometry instead of fixed pixel reserves. A ResizeObserver on the wrapper plus another on the action button cluster computes exactly how much room is available; both sides of the header shrink in lockstep so they stay horizontally aligned as long as possible. Below ~340px of plan area the ghost bar stacks below the action buttons.
  
  "Quick Share" and "Quick Copy" are now plain "Share" and "Copy". Share opens the existing export modal so it benefits from the short-link path for large payloads instead of dumping a 50KB hash URL straight to the clipboard.
  
  The sidebar rail no longer pushes the background grid pattern 30px to the right — it floats over the document area, and the grid paints edge-to-edge under the sidebar flags.
  
  #519
  
  Overlay Scrollbars
  
  Wide, translucent, full-length overlay scrollbars across plan mode and code review, replacing the 6px WebKit rail that was hard to grab. Click the track to page-animate toward the click; drag the thumb smoothly; no layout shift; Firefox parity; respects prefers-reduced-motion; disappears in print.
  
  Backed by overlayscrollbars-react wrapped in a new OverlayScrollArea component. Native scroll semantics stay on the viewport element so existing scrollIntoView and scrollTo calls still work. Wrapped containers include the main plan viewer, annotation panel, sidebar tabs, settings and export modals, file tree, review sidebar, AI chat tab, PR comments timeline, and PR summary/checks dock panels.
  
  #509, closing #354
  
  Inline Highlighting for External Annotations
  
  External annotations posted via POST /api/external-annotations can now optionally highlight the matching originalText span inline in the rendered plan — COMMENT renders yellow, DELETION renders strikethrough. Annotations without originalText or of type GLOBAL_COMMENT continue to render sidebar- only.
  
  No protocol or schema change. Tools choose inline vs global purely by what they supply. If originalText doesn't match anywhere in the rendered DOM, the annotation degrades gracefully to sidebar-only with a console warning. PATCH and DELETE through the API correctly remove and reapply highlights as state changes.
  
  #511
  
  Supply-Chain Hardening
  
  The release pipeline now generates SLSA build provenance attestations for every released binary. Each of the twelve cross-compiled binaries (six Plannotator targets, six paste-service targets) is signed via Sigstore and recorded in Rekor through actions/attest-build-provenance. Top-level workflow permissions have been tightened to contents: read with per-job overrides.
  
  Installers now accept a --version v0.X.Y flag (and positional form), so you can pin to a specific version instead of always pulling latest. The default behavior is unchanged.
  
  Attestation verification is opt-in via three mechanisms with documented precedence: a --verify-attestation CLI flag, a PLANNOTATOR_VERIFY_ATTESTATION=1 environment variable, or { "verifyAttestation": true } in ~/.plannotator/config.json. Off by default to match how rustup, brew, bun, deno, and helm handle attestation — turning it on hard-fails the install if gh isn't available, so opt-in is never silently skipped. Anyone can still verify any release manually with gh attestation verify.
  
  The same PR fixes a Windows installer crash where cmd.exe's enabledelayedexpansion was eating the ! characters in an embedded node -e script during Gemini settings merge.
  
  #512, closing #506 and parts of #507
  
  Additional Changes
  - Numbered list rendering. Ordered lists like 1., 2., 10. were rendered as bullet points because the parser collapsed all list types into a single block kind. The parser now captures the numeric marker and tags the block as ordered; a new computeListIndices helper assigns CommonMark-correct display numbers including streak break/restart on mixed siblings and independent numbering for nested ordered sublists. The renderer uses tabular-nums so 9 to 10 doesn't jitter (#520)
  - Underscore italics. The custom markdown renderer supported *italic* but not _italic_. Now both work, while intraword underscores like snake_case continue to render as plain text (#504 by @foxytanuki, closing #502)
  - Perforce added files on Windows. P4-added files were missing from the review UI on Windows because p4 where stdout uses \r\n line endings; splitting on \n left a stray \r in every file path except the last, causing Bun.file() to silently fail. The fix normalizes line endings on all P4 command output and replaces fragile index-based parsing with p4 -ztag where field-based parsing, which is also more robust for stream depots and overlay mappings (#494 by @l10veu602)
  Install / Update
  
  macOS / Linux:
```
curl -fsSL https://plannotator.ai/install.sh | bash
```
  Windows:
```
irm https://plannotator.ai/install.ps1 | iex
```
  Pin a specific version:
```
curl -fsSL https://plannotator.ai/install.sh | bash -s -- --version v0.17.2
```
  Claude Code Plugin: Run /plugin in Claude Code, find plannotator , and click "Update now".
  
  Copilot CLI:
```
/plugin marketplace add backnotprop/plannotator
/plugin install plannotator-copilot@plannotator
```
  Gemini CLI: The install script auto-detects ~/.gemini and configures hooks, policy, and slash commands. See apps/gemini/README.md for manual setup.
  
  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
```
  VS Code Extension: Install from the VS Code Marketplace. Tested with Claude Code running in VS Code's integrated terminal. Not currently compatible with Anthropic's official VS Code extension due to upstream hook bugs.
  
  What's Changed
  - fix(ui): render numerals for ordered list items by @backnotprop in #520
  - feat(plan): simplify share/copy + sticky header polish by @backnotprop in #519
  - chore: supply-chain hardening — version pinning, SLSA attestations, install fix by @backnotprop in #512
  - feat(plan): unified header dropdown + Agent Instructions by @backnotprop in #515
  - feat: Zed-style overlay scrollbars by @backnotprop in #509
  - feat(plan): complete sticky actions — pin toolstrip + badges on scroll by @backnotprop in #510
  - feat(ui): highlight external SSE annotations inline on plan text by @backnotprop in #511
  - fix: support underscore italics in markdown renderer by @foxytanuki in #504
  - feat: add Conventional Comments support to code review by @backnotprop in #501
  - fix(review): show P4 added files in code review by @l10veu602 in #494
  Contributors
  
  @foxytanuki returned with the underscore italics fix (#504, closing #502). The custom markdown renderer now treats _italic_ and *italic* as equivalent emphasis while leaving snake_case alone. Their fourth contribution to the project.
  
  @l10veu602 fixed the Perforce added-files regression on Windows (#494). The bug was a classic \r\n line-ending issue in p4 where stdout that left stray carriage returns in file paths, causing Bun.file() to silently miss them. The fix also swaps fragile index-based parsing for p4 -ztag structured output, which holds up better on stream depots and overlay mappings. Verified on a real P4 workspace going from 13 files visible to all 17.
  
  Community members who reported issues addressed in this release:
  - @djamatgit: #506 (install.cmd Gemini settings merge crash on Windows)
  - @rooterkyberian: #507 (supply-chain hardening — items 1 & 2)
  - @Thraka: #502 (underscore italics not rendering)
  - @dillonoconnor: #354 (couldn't grab the scrollbar)
  Full Changelog : v0.17.1...v0.17.2
16. 🔗 r/LocalLLaMA kepler-452b. GGUF when? rss
  
  | submitted by /u/the-grand-finale
  [link] [comments]
  ---|---
17. 🔗 r/reverseengineering Runtime JavaScript instrumentation via CDP (no monkeypatching, works inside closures) rss
  
  submitted by /u/filippo_cavallarin
  [link] [comments]
18. 🔗 r/LocalLLaMA It looks like we’ll need to download the new Gemma 4 GGUFs rss
  https://huggingface.co/unsloth/gemma-4-E2B-it-GGUF
  
  https://huggingface.co/unsloth/gemma-4-26B-A4B-it-GGUF
  
  by u/danielhanchen:
  
  We just updated them again in response to:
  1. kv-cache : support attention rotation for heterogeneous iSWA https://github.com/ggml-org/llama.cpp/pull/21513
  2. CUDA: check for buffer overlap before fusing - CRITICAL fixes <unused24> tokens https://github.com/ggml-org/llama.cpp/pull/21566
  3. vocab : add byte token handling to BPE detokenizer for Gemma4 https://github.com/ggml-org/llama.cpp/pull/21488
  4. convert : set "add bos" == True for Gemma 4 https://github.com/ggml-org/llama.cpp/pull/21500
  5. common : add gemma 4 specialized parser https://github.com/ggml-org/llama.cpp/pull/21418
  6. llama-model: read final_logit_softcapping for Gemma 4 https://github.com/ggml-org/llama.cpp/pull/21390
  7. llama: add custom newline split for Gemma 4 https://github.com/ggml-org/llama.cpp/pull/21406
  submitted by /u/jacek2023
  [link] [comments]
19. 🔗 r/Harrogate Window cleaners rss
  
  Best window cleaners in Harrogate? Preferably via ladder rather than telescopic pole. Thanks.
  
  submitted by /u/Outrageous-Square-21
  [link] [comments]
20. 🔗 r/reverseengineering [Tool] Rikune: A reverse-engineering MCP server that turns PE triage, Ghidra analysis, runtime evidence, and source-like reconstruction into reusable tools for any LLM rss
  
  submitted by /u/MomOxIao_FoReVEr
  [link] [comments]
21. 🔗 r/wiesbaden Gravity Trail rss
  
  Ich habe soviele Mythen und Märchen gehört, was ist denn nun wirklich passiert?
  
  submitted by /u/pathetichypocrit
  [link] [comments]
22. 🔗 r/reverseengineering Reverse-engineered the Whoop 4.0 BLE protocol — CRC-32 with non-standard polynomial, 96-byte real-time data packets rss
  
  submitted by /u/batoba
  [link] [comments]
23. 🔗 anthropics/claude-code v2.1.96 release
  What's changed
  - Fixed Bedrock requests failing with 403 "Authorization header is missing" when using AWS_BEARER_TOKEN_BEDROCK or CLAUDE_CODE_SKIP_BEDROCK_AUTH (regression in 2.1.94)
24. 🔗 r/reverseengineering From UART to Root: Vendor Shell Escape on a Uniview IP Camera rss
  
  submitted by /u/Vymmy
  [link] [comments]
25. 🔗 r/Leeds "What's on?" Wednesday - April 08, 2026 rss
  "What's on?" Wednesday
  
  Our weekly post where people can highlight local events or interesting things that are coming up in the next week. It doesn't have to be your event, but this is a place where reasonable exceptions to our self-promotion rules are allowed. Please check whether the event you're posting about is already mentioned. If you're adding your own event, please try to answer any questions people may have in the comments.
  
  You can also ask questions if you're looking for something to do, e.g. "Does anyone know of a good pub quiz in the centre on Thursday?"
  
  " What's on?" rules:
  1. Leeds based events only
  2. Must be taking place in the next 7 days (next Wednesday included)
  3. Posts highlighting an event should include:
    
    Event name
    
    Date and time
    
    Location
    
    Price(s) (if applicable)
  4. A description of the event and a relevant link is recommended but not required
  The rules may evolve over time as we find out how things work. Please send any feedback to the mod team.
  
  submitted by /u/AutoModerator
  [link] [comments]
26. 🔗 Mario Zechner I've sold out rss
  
  I've sold out
27. 🔗 Armin Ronacher Mario and Earendil rss
  
  Today I'm very happy to share that Mario Zechner is joining Earendil.
  
  First things first: I think you should read Mario's post. This is his news more than it is ours, and he tells his side of it better than I could. What I want to do here is add a more personal note about why this matters so much to me, how the last months led us here, and why I am so excited to have him on board.
  
  Last year changed the way many of us thought about software. It certainly changed the way I did. I spent much of 2025 building, probing, and questioning how to build software, and in many more ways what I want to do. If you are a regular reader of this blog you were along for the ride. I wrote a lot, experimented a lot, and tried to get a better sense for what these systems can actually do and what kinds of companies make sense to build around them. There was, and continues to be, a lot of excitement in the air, but also a lot of noise. It has become clear to me that it's not a question of whether AI systems can be useful but what kind of software and human-machine interactions we want to bring into the world with them.
  
  That is one of the reasons I have been so drawn to Mario's work and approaches.
  
  Pi is, in my opinion, one of the most thoughtful coding agents and agent infrastructure libraries in this space. Not because it is trying to be the loudest or the fastest, but because it is clearly built by someone who cares deeply about software quality, taste, extensibility, and design. In a moment where much of the industry is racing to ship ever more quickly, often at the cost of coherence and craft, Mario kept insisting on making something solid. That matters to me a great deal.
  
  I have known Mario for a long time, and one of the things I admire most about him is that he does not confuse velocity with progress. He has a strong sense for what good tools should feel like. He cares about details. He cares about whether something is well made. And he cares about building in a way that can last. Mario has been running Pi in a rather unusual way. He exerts back- pressure on the issue tracker and the pull requests through OSS vacations and other means.
  
  The last year has also made something else clearer to me: these systems are not only exciting, they are also capable of producing a great deal of damage. Sometimes that damage is obvious; sometimes it looks like low-grade degradation everywhere at once. More slop, more noise, more disingenuous emails in my inbox. There is a version of this future that makes people more distracted, more alienated, and less careful with one another.
  
  That is not a future I want to help build.
  
  At Earendil, Colin and I have been trying to think very carefully about what a different path might look like. That is a big part of what led us to Lefos.
  
  Lefos is our attempt to build a machine entity that is more thoughtful and more deliberate by design. Not an agent whose main purpose is to make everything a little more efficient so that we can produce even more forgettable output, but one that can help people communicate with more care, more clarity, and joy.
  
  Good software should not aim to optimize every minute of your life, but should create room for better and more joyful experiences, better relationships, and better ways of relating to one another. Especially in communication and software engineering, I think we should be aiming for more thought rather than more throughput. We should want tools that help people be more considerate, more present, and more human. If all we do is use these systems to accelerate the production of slop, we will have missed the opportunity entirely.
  
  This is also why Mario joining Earendil feels so meaningful to me. Pi and Lefos come from different starting points. There was a year of distance collaboration, but they are animated by a similar instinct: that quality matters, that design matters, and that trust is earned through care rather than captured through hype.
  
  I am very happy that Pi is coming along for the ride. Me and Colin care a lot about it, and we want to be good stewards of it. It has already played an important role in our own work over the last months, and I continue to believe it is one of the best foundations for building capable agents. We will have more to say soon about how we think about Pi's future and its relationship to Lefos, but the short version is simple: we want Pi to continue to exist as a high-quality, open, extensible piece of software, and we want to invest in making that future real. As for our thoughts of Pi's license, read more here and our company post here.
April 07, 2026
1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-04-07 rss
  IDA Plugin Updates on 2026-04-07
  
  Activity:
  - augur
    
    bc92ca7b: chore: update dependencies
  - capa
    
    0798528b: ci: use explicit and per job permissions (#3002)
    
    c55b0686: ci: fix web rules failure (#3003)
    
    ed7e0cd7: lint: replace black/isort/flake8 with ruff (#2992)
    
    ac1cba74: feat: update vivisect to 1.3.2 (#3001)
    
    ed6b40e9: Merge pull request #3000 from mandiant/dependabot/npm_and_yarn/web/ex…
  - DriverBuddy-7.4-plus
    
    f87787e9: Sync security-review.yml from .github repo
    
    583074d2: Sync auto-copilot-code-cleanliness-review.yml from .github repo
    
    f99d929e: Sync auto-llm-issue-review.yml from .github repo
    
    1e2b0ece: Sync trigger-all-repos.yml from .github repo
    
    29d1ff04: Sync auto-llm-pr-review.yml from .github repo
    
    4cc9e38a: Sync auto-label-comment-prs.yml from .github repo
    
    a3cd8c0b: Sync auto-label.yml from .github repo
    
    74620e5b: Sync auto-sec-scan.yml from .github repo
    
    eb8c7fcd: Sync auto-gpt5-implementation.yml from .github repo
    
    34c2593c: Sync swarm-mode.yml from .github repo
    
    dbf9f7a4: Sync auto-assign-copilot.yml from .github repo
    
    bc0b1b03: Sync auto-assign-pr.yml from .github repo
    
    f72ce60b: Sync workflows-sync-template-backup.yml from .github repo
    
    ff1522b2: Sync auto-tag-based-review.yml from .github repo
    
    036f8459: Sync runner-smoke-test.yml from .github repo
    
    1620d21f: Sync daily-continuous-progress.yml from .github repo
    
    dcb59862: Sync auto-close-issues.yml from .github repo
    
    948f1658: Sync auto-copilot-functionality-docs-review.yml from .github repo
    
    ce3c09ec: Sync oz-pr-review.yml from .github repo
  - ghidra
    
    505a59ff: Merge remote-tracking branch 'origin/GP-0-dragonmacher-test-fixes-4-7…
    
    44bd56bb: Test fixes
  - haruspex
    
    f89231e6: chore: update dependencies
  - ida-structor
    
    1afadd01: feat: Materialize deferred symbolic accesses when index bounds are found
    
    de5cbc3e: feat: Improve subobject detection using pointer flow edges
    
    b4e63d35: feat: Track symbolic array accesses and support named variable synthesis
    
    5afb49b1: feat: Expand bounded array accesses and improve alias offset tracking
    
    1acb065e: chore: Add debug logging for constant tracking in access collector
  - idamcp
    
    75af175f: fix port assignment
  - IDAPluginList
    
    3b6b426c: chore: Auto update IDA plugins (Updated: 19, Cloned: 0, Failed: 0)
  - IDEA
    
    4c7e96ac: Refine typed refresh and add type workflow regression coverage
    
    6c35fdbc: Downgrade struct field access classification to hints
    
    d9d945c1: Add struct workflow helpers and typed export tools
    
    f92a527e: Slim search output and implement local/stack rename
    
    7978d76c: Normalize export paths and persist staged IDBs
  - pharos
    
    217bf2a0: Merge pull request #303 from sei-eschwartz/fix-cycle
    
    4fd85d2f: Refactor reasonClassAtOffset_int to avoid cycles
  - python-elpida_core.py
    
    67b98628: fix: desperation guard reads stale MIND heartbeat as live crisis
  - rhabdomancer
    
    efa2142c: chore: update dependencies
  - Rikugan
    
    84f00d2d: Merge pull request #35 from buzzer-re/dev
    
    90146269: perf(ui): reduce restore, markdown, and bulk renamer overhead
    
    767fd59b: fix(ui): align Qt test stubs and qt_compat typing with runtime usage
    
    d5d3d078: fix(tests): isolate stubbed modules to prevent CI order-dependent fai…
  - sighthouse
    
    1f98a8ca: Fix missing dependency inside sighthouse-client
    
    a24a2dd7: CI github fixed order for documentation after pypi push
    
    a2bfe738: Simply/fix the ghidra installation and improve [+] Bump package versi…
    
    3103903a: Simply/fix the ghidra installation and improve [+] Bump package versi…
2. 🔗 r/Leeds Guitar Pedal shops in Leeds? rss
  
  Hi, I'm looking to shop around for some guitar pedals (like phasers etc) and I'd love to demo some. I'm aware PMT has now unfortunately closed, and I do miss the days of Big Deal and Dawsons. I love Hobgoblin and still frequent the store there, and wondering where else in Leeds I can go to browse?
  
  York has some great shops to visit too but I'd like to look more locally.
  
  Thank you!
  
  submitted by /u/blissedandgone
  [link] [comments]
3. 🔗 r/wiesbaden Mountainbike/Downhill Trails rss
  
  Wo gibt es in Wiesbaden und Umgebung gute Trails zum Mountainbiken und/oder Downhill fahren?
  
  Gibt es eventuell sogar eine eigene Community?
  
  Bin recht neu bei dem Thema und für alle Vorschläge dankbar :-)
  
  submitted by /u/Excellent_Scheme_247
  [link] [comments]
4. 🔗 anthropics/claude-code v2.1.94 release
  What's changed
  - Added support for Amazon Bedrock powered by Mantle, set CLAUDE_CODE_USE_MANTLE=1
  - Changed default effort level from medium to high for API-key, Bedrock/Vertex/Foundry, Team, and Enterprise users (control this with /effort)
  - Added compact Slacked #channel header with a clickable channel link for Slack MCP send-message tool calls
  - Added keep-coding-instructions frontmatter field support for plugin output styles
  - Added hookSpecificOutput.sessionTitle to UserPromptSubmit hooks for setting the session title
  - Plugin skills declared via "skills": ["./"] now use the skill's frontmatter name for the invocation name instead of the directory basename, giving a stable name across install methods
  - Fixed agents appearing stuck after a 429 rate-limit response with a long Retry-After header — the error now surfaces immediately instead of silently waiting
  - Fixed Console login on macOS silently failing with "Not logged in" when the login keychain is locked or its password is out of sync — the error is now surfaced and claude doctor diagnoses the fix
  - Fixed plugin skill hooks defined in YAML frontmatter being silently ignored
  - Fixed plugin hooks failing with "No such file or directory" when CLAUDE_PLUGIN_ROOT was not set
  - Fixed ${CLAUDE_PLUGIN_ROOT} resolving to the marketplace source directory instead of the installed cache for local-marketplace plugins on startup
  - Fixed scrollback showing the same diff repeated and blank pages in long-running sessions
  - Fixed multiline user prompts in the transcript indenting wrapped lines under the ❯ caret instead of under the text
  - Fixed Shift+Space inserting the literal word "space" instead of a space character in search inputs
  - Fixed hyperlinks opening two browser tabs when clicked inside tmux running in an xterm.js-based terminal (VS Code, Hyper, Tabby)
  - Fixed an alt-screen rendering bug where content height changes mid-scroll could leave compounding ghost lines
  - Fixed FORCE_HYPERLINK environment variable being ignored when set via settings.json env
  - Fixed native terminal cursor not tracking the selected tab in dialogs, so screen readers and magnifiers can follow tab navigation
  - Fixed Bedrock invocation of Sonnet 3.5 v2 by using the us. inference profile ID
  - Fixed SDK/print mode not preserving the partial assistant response in conversation history when interrupted mid-stream
  - Improved --resume to resume sessions from other worktrees of the same repo directly instead of printing a cd command
  - Fixed CJK and other multibyte text being corrupted with U+FFFD in stream-json input/output when chunk boundaries split a UTF-8 sequence
  - [VSCode] Reduced cold-open subprocess work on starting a session
  - [VSCode] Fixed dropdown menus selecting the wrong item when the mouse was over the list while typing or using arrow keys
  - [VSCode] Added a warning banner when settings.json files fail to parse, so users know their permission rules are not being applied
5. 🔗 r/LocalLLaMA Gemma4-31B worked in an iterative-correction loop (with a long-term memory bank) for 2 hours to solve a problem that baseline GPT-5.4-Pro couldn't rss
  
  | submitted by /u/Ryoiki-Tokuiten
  [link] [comments]
  ---|---
6. 🔗 Simon Willison Anthropic's Project Glasswing - restricting Claude Mythos to security researchers - sounds necessary to me rss
  
  Anthropic didn't release their latest model, Claude Mythos (system card PDF), today. They have instead made it available to a very restricted set of preview partners under their newly announced Project Glasswing.
  
  The model is a general purpose model, similar to Claude Opus 4.6, but Anthropic claim that its cyber-security research abilities are strong enough that they need to give the software industry as a whole time to prepare.
  
  Mythos Preview has already found thousands of high-severity vulnerabilities, including some in every major operating system and web browser. Given the rate of AI progress, it will not be long before such capabilities proliferate, potentially beyond actors who are committed to deploying them safely.
  
  [...]
  
  Project Glasswing partners will receive access to Claude Mythos Preview to find and fix vulnerabilities or weaknesses in their foundational systems—systems that represent a very large portion of the world’s shared cyberattack surface. We anticipate this work will focus on tasks like local vulnerability detection, black box testing of binaries, securing endpoints, and penetration testing of systems.
  
  There's a great deal more technical detail in Assessing Claude Mythos Preview’s cybersecurity capabilities on the Anthropic Red Team blog:
  
  In one case, Mythos Preview wrote a web browser exploit that chained together four vulnerabilities, writing a complex JIT heap spray that escaped both renderer and OS sandboxes. It autonomously obtained local privilege escalation exploits on Linux and other operating systems by exploiting subtle race conditions and KASLR-bypasses. And it autonomously wrote a remote code execution exploit on FreeBSD's NFS server that granted full root access to unauthenticated users by splitting a 20-gadget ROP chain over multiple packets.
  
  Plus this comparison with Claude 4.6 Opus:
  
  Our internal evaluations showed that Opus 4.6 generally had a near-0% success rate at autonomous exploit development. But Mythos Preview is in a different league. For example, Opus 4.6 turned the vulnerabilities it had found in Mozilla’s Firefox 147 JavaScript engine—all patched in Firefox 148—into JavaScript shell exploits only two times out of several hundred attempts. We re-ran this experiment as a benchmark for Mythos Preview, which developed working exploits 181 times, and achieved register control on 29 more.
  
  Saying "our model is too dangerous to release" is a great way to build buzz around a new model, but in this case I expect their caution is warranted.
  
  Just a few days (last Friday) ago I started a new ai-security-research tag on this blog to acknowledge an uptick in credible security professionals pulling the alarm on how good modern LLMs have got at vulnerability research.
  
  Greg Kroah-Hartman of the Linux kernel:
  
  Months ago, we were getting what we called 'AI slop,' AI-generated security reports that were obviously wrong or low quality. It was kind of funny. It didn't really worry us.
  
  Something happened a month ago, and the world switched. Now we have real reports. All open source projects have real reports that are made with AI, but they're good, and they're real.
  
  Daniel Stenberg of curl:
  
  The challenge with AI in open source security has transitioned from an AI slop tsunami into more of a ... plain security report tsunami. Less slop but lots of reports. Many of them really good.
  
  I'm spending hours per day on this now. It's intense.
  
  And Thomas Ptacek published Vulnerability Research Is Cooked, a post inspired by his podcast conversation with Anthropic's Nicholas Carlini.
  
  Anthropic have a 5 minute talking heads video describing the Glasswing project. Nicholas Carlini appears as one of those talking heads, where he said (highlights mine):
  
  It has the ability to chain together vulnerabilities. So what this means is you find two vulnerabilities, either of which doesn't really get you very much independently. But this model is able to create exploits out of three, four, or sometimes five vulnerabilities that in sequence give you some kind of very sophisticated end outcome. [...]
  
  I've found more bugs in the last couple of weeks than I found in the rest of my life combined. We've used the model to scan a bunch of open source code, and the thing that we went for first was operating systems, because this is the code that underlies the entire internet infrastructure. For OpenBSD, we found a bug that's been present for 27 years, where I can send a couple of pieces of data to any OpenBSD server and crash it. On Linux, we found a number of vulnerabilities where as a user with no permissions, I can elevate myself to the administrator by just running some binary on my machine. For each of these bugs, we told the maintainers who actually run the software about them, and they went and fixed them and have deployed the patches patches so that anyone who runs the software is no longer vulnerable to these attacks.
  
  I found this on the OpenBSD 7.8 errata page:
  
  025: RELIABILITY FIX: March 25, 2026 All architectures
  
  TCP packets with invalid SACK options could crash the kernel.
  
  A source code patch exists which remedies this problem.
  
  I tracked that change down in the GitHub mirror of the OpenBSD CVS repo (apparently they still use CVS!) and found it using git blame:
  
  Sure enough, the surrounding code is from 27 years ago.
  
  I'm not sure which Linux vulnerability Nicholas was describing, but it may have been this NFS one recently covered by Michael Lynch .
  
  There's enough smoke here that I believe there's a fire. It's not surprising to find vulnerabilities in decades-old software, especially given that they're mostly written in C, but what's new is that coding agents run by the latest frontier LLMs are proving tirelessly capable at digging up these issues.
  
  I actually thought to myself on Friday that this sounded like an industry-wide reckoning in the making, and that it might warrant a huge investment of time and money to get ahead of the inevitable barrage of vulnerabilities. Project Glasswing incorporates "$100M in usage credits ... as well as $4M in direct donations to open-source security organizations". Partners include AWS, Apple, Microsoft, Google, and the Linux Foundation. It would be great to see OpenAI involved as well - GPT-5.4 already has a strong reputation for finding security vulnerabilities and they have stronger models on the near horizon.
  
  The bad news for those of us who are not trusted partners is this:
  
  We do not plan to make Claude Mythos Preview generally available, but our eventual goal is to enable our users to safely deploy Mythos-class models at scale—for cybersecurity purposes, but also for the myriad other benefits that such highly capable models will bring. To do so, we need to make progress in developing cybersecurity (and other) safeguards that detect and block the model’s most dangerous outputs. We plan to launch new safeguards with an upcoming Claude Opus model, allowing us to improve and refine them with a model that does not pose the same level of risk as Mythos Preview.
  
  I can live with that. I think the security risks really are credible here, and having extra time for trusted teams to get ahead of them is a reasonable trade-off.
  
  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.
7. 🔗 r/york First trip to your wonderful city rss
  
  | A few of my favourite shots. Not so much time for pictures with the children in tow these days but still managed a couple keepers. submitted by /u/MicroWave
  [link] [comments]
  ---|---
8. 🔗 r/reverseengineering ida-mcp 2.1: Progressive Tool Discovery, Background Analysis, and Batch Operations rss
  
  submitted by /u/jtsylve
  [link] [comments]
9. 🔗 r/Leeds Cherry blossoms in Leeds 🌸 rss
  
  Finally have a day off after 11 days working straight so I’m planning to go touch some grass tomorrow (yay!).
  
  Any suggestions on places with beautiful cherry blossoms in bloom in a spot that I can also do a little picnic, and not too far away from city centre?
  
  Heard someone said Temple Newsam or Roundhay park, but I’m not sure if there’s any blossoms blooming there now yet.
  
  Any suggestions would be greatly appreciated. Thank you x
  
  submitted by /u/AnOtterInAMug
  [link] [comments]
10. 🔗 r/Leeds Lost keys in Headingley area rss
  
  Hi everyone,
  
  I lost my house keys the other day somewhere in the central headingley area. I’ve tried looking for it to no avail. It was two keys (one big and one small) and a purple rectangular tag with YPP written on it with a number or QR code on the back to contact the agency. Someone may have kicked it to the side or unsure what to do with it so I hope this reaches the right person. If anyone finds this could you please contact the number or give it to the nearest YPP office I would really really appreciate as it’s going to quite a bit to replace it. Thank you.
  
  submitted by /u/lymphatic123
  [link] [comments]
11. 🔗 r/Leeds Outdoor Volleyball Leeds rss
  
  Hey guys! I’ll be setting up a volleyball net in Woodhouse Moor soon and looking for people to join
  
  DM here and I'll add you to the messenger group.
  
  All levels welcome, adults only, completely free. Hoping to build a nice little volleyball community :)
  
  Location:
  
  Woodhouse Ln, Woodhouse, Leeds LS6 1SJ
  
  submitted by /u/Motyl998
  [link] [comments]
12. 🔗 r/Yorkshire Rivers of Yorkshire Rhyme rss
  
  My grandma used to recite a poem or nursery rhyme about the rivers of Yorkshire. 45 years later I can't remember it! Does anyone know what this rhyme could be?
  
  submitted by /u/Lumpy_Geologist7644
  [link] [comments]
13. 🔗 r/Leeds North Street LS2 rss
  
  Headed up to North Street today. Loads going on, seems like a nice part of town. I always avoided that area as you head up to Little London but almost feels nicer and safer now than other areas of town (city centre). Is this a recent boom or have I just had my blinkers on? Anyone know the plans on what they are doing around that area?
  
  submitted by /u/Olivrrpb
  [link] [comments]
14. 🔗 r/Yorkshire Yorkshire Devolution rss
  
  Something a little different for the community here. What's your thought on Yorkshire devolution to the historic county?
  
  I've heard that there was recently a One Yorkshire deal that the Tories rejected and that the Yorkshire mayors work pretty closely with each other now. I also know we have a really strong identity, proud folk and unique customs and dialect that make us an ideal group for one devolution. But I just wanted to know what people think? Do you want a Yorkshire Parliament like Wales's has? Or are you not that fussed? Lerrus av a kall abaht it!
  
  P.s. I've always thought us Northerners squabble too much anyway and that's why Westminster always gets its way!
  
  submitted by /u/masa8910
  [link] [comments]
15. 🔗 @binaryninja@infosec.exchange Join us tomorrow, Wednesday April 8th @ 3pm ET, for a sneak peak at Binary mastodon
  
  Join us tomorrow, Wednesday April 8th @ 3pm ET, for a sneak peak at Binary Ninja 5.3!
  
  We'll take a look at all the new major features coming to 5.3, from expanded architecture and platform support, core analysis features, new debugger features, brand new UIs, and so much more. Follow along with latest dev, or join us tomorrow to see what's worth all the hype: https://youtube.com/live/iD8UidhFbhg
16. 🔗 r/LocalLLaMA Every day I wake up and thank God for having me be born 23 minutes away from a MicroCenter rss
  
  | submitted by /u/gigaflops_
  [link] [comments]
  ---|---
17. 🔗 r/Leeds Good Boy (the Stephen Graham film, not the dog one) currently in cinema was filmed in Leeds during freshers after a Leeds game at 10pm. It's pretty hectic and shows off some bits of Leeds including lower Briggate. rss
  
  87% on Rotten Tomatoes and very good. A bit of a strange one kinda like a Yorgos Lanthimos film.
  
  If anyone has watched and can identify all the Leeds/Yorkshire locations I'd be interested.
  
  submitted by /u/montfree
  [link] [comments]
18. 🔗 r/Harrogate Best bars for a date night rss
  
  hi all,
  
  i am taking my girlfriend out to Harrogate tmrw for her birthday! I have booked La Feria as our dinner in the evening but wondered what were the best bars are to go to before and after are meal.
  
  just to note we are dressing up nicely - she’ll be in a dress and I’ll be in a shirt. just wondered if that fits the vibe of La Feria and if you know any nice bars that suits that is nice for the evening!!
  
  submitted by /u/GarlicCharacter3247
  [link] [comments]
19. 🔗 r/york Scenic Drives (ideally circular) - Leaving York rss
  
  Hi
  
  Can anyone recommend any drives that you can easily do within an hour or so (total drive time) with the following ideal criteria:
  
  - A scenic and reasonably quiet route
  
  - Ideally circular (leave York - head out and back to York eventually)
  
  - Something that's not necessarily well known
  
  - A nice village pub to call in at along the way
  
  - That's all!
  
  All recommendations welcome, thank you.
  
  submitted by /u/HeroRon
  [link] [comments]
20. 🔗 r/LocalLLaMA GLM-5.1 rss
  
  | submitted by /u/danielhanchen
  [link] [comments]
  ---|---
21. 🔗 r/Leeds Trying to get to Leeds station in the morning from Bramley with all the road works rss
  
  There is a lot of road works in Kirkstall and people were delayed. My flight is 12pmin the afternoon and I have to get all the way to Manchester..
  
  Thnking of setting off between 6:00 and 7:00 a.m.
  
  would you recommend an Uber? I think the buses might be out of whack that morning with all the road works. I did speak to the person on the road works and they said that all the road work starts around 9:00 which means there's no room for error in me getting up early.
  
  submitted by /u/Crazy_Screen_5043
  [link] [comments]
22. 🔗 r/Leeds Anyone near Headingley able to offer an emergency puppy cuddle for a very overdue pregnant woman? rss
  
  Bit of an unusual one, but my sister-in-law is very overdue with her first baby, desperate to avoid induction, and absolutely mad about dogs, while sadly unable to own one.
  
  I wondered whether anyone near Headingley has a friendly puppy and might be willing to let her have a short, supervised interaction, just some gentle fuss, cuddles, and a bit of puppy time. The hope, honestly, is to get a bit of oxytocin flowing and lift her spirits, as she completely melts around dogs.
  
  We are not looking to borrow a dog or put anyone out, just a brief visit with the owner present, ideally somewhere convenient and public if that suits you better.
  
  Bit of a long shot, but hey ho.
  
  Thank you!
  
  submitted by /u/Desecron
  [link] [comments]
23. 🔗 r/LocalLLaMA You can now fine-tune Gemma 4 locally 8GB VRAM + Bug Fixes rss
  | Hey guys, you can now fine-tune Gemma 4 E2B and E4B in our free Unsloth notebooks! You need 8GB VRAM to train Gemma-4-E2B locally. Unsloth trains Gemma 4 ~1.5x faster with ~60% less VRAM than FA2 setups: https://github.com/unslothai/unsloth We also found and did bug fixes for Gemma 4 training:
  1. Grad accumulation no longer causes losses to explode - before you might see losses of 300 to 400 - it should be 10 to 15 - Unsloth has this fixed.
  2. Index Error for 26B and 31B for inference - this will fail inference for 26B and 31B when using transformers - we fixed it.
  3. use_cache=False had gibberish for E2B, E4B - see https://github.com/huggingface/transformers/issues/45242
  4. float16 audio -1e9 overflows on float16
  You can also train 26B-A4B and 31B or train via a UI with Unsloth Studio. Studio and the notebooks work for Vision, Text, Audio and inference. For Bug Fix details and tips and tricks, read our blog/guide: https://unsloth.ai/docs/models/gemma-4/train Free Colab Notebooks: | E4B + E2B (Studio web UI) | E4B (Vision + Text)-Vision.ipynb) | E4B (Audio)-Audio.ipynb) | E2B (Run + Text)-Text.ipynb)
  ---|---|---|---
  
  Thanks guys!
  
  submitted by /u/danielhanchen
  [link] [comments]
24. 🔗 r/york casualties of the storm :( rss
  
  | on the riverbank near cinder lane and in homestead park submitted by /u/whtmynm
  [link] [comments]
  ---|---
25. 🔗 r/wiesbaden FDP und Pro Auto bekommen Schnappatmung rss
  
  submitted by /u/Happycosinus
  [link] [comments]
26. 🔗 r/reverseengineering AI just hacked one of the world's most secure operating systems in four hours. rss
  
  submitted by /u/EchoOfOppenheimer
  [link] [comments]
27. 🔗 r/Yorkshire World Coal Carrying Championship 2026! rss
  
  | A beloved tradition in the village of Gawthorpe. The competition takes place annually with men, women and children taking part (the kids don't carry coal!) This year we had good weather and a turnout of many hundreds of spectators to cheer along the runners. Congratulations to all those taking part, where even completing the race is a feat in itself. submitted by /u/Paradoxbox00
  [link] [comments]
  ---|---
28. 🔗 r/york Jorvik Tickets for Today or early tomorrow? rss
  
  We’re visiting York- arrived yesterday and leave midday tomorrow. I’m an idiot and didn’t prebook tickets to the Jorvik museum and they’re sold out. By any small chance is there anyone who has tickets they can’t use that we could buy for today or early tomorrow?
  
  submitted by /u/SnooCats1465
  [link] [comments]
29. 🔗 gchq/CyberChef v10.23.0 release
  
  See the CHANGELOG and commit messages for details.
30. 🔗 r/LocalLLaMA Turns out Gemma 4 had MTP (multi token prediction) all along rss
  
  | Hey Everyone, While I was trying to utilize Gemma 4 through the LiteRT api in my android app, I noticed that Gemma 4 was throwing errors when loading it on my Google Pixel 9 test device of the "mtp weights being an incompatible tensor shape". I did some digging and found out there's additional MTP prediction heads within the LiteRT files for speculative decoding and much faster outputs. Well turns out I got confirmation today from a Google employee that Gemma 4 DOES INDEED have MTP but it was "removed on purpose" for "ensuring compatibility and broad usability". Well would've been great to be honest if they released the full model instead, considering we already didn't get the Gemma 124B model leaked in Jeff Dean's tweet by accident. Would've been great to have much faster Gemma 4 generation outputs, ideally on the already fast MoE. Maybe someone can reverse engineer and extract the tensors and the math based on the compute graph in LiteRT? Here's a link to the conversation: https://huggingface.co/google/gemma-4-E4B-it/discussions/5 submitted by /u/Electrical-Monitor27
  [link] [comments]
  ---|---
31. 🔗 r/Yorkshire Yorkshire, UK 🇬🇧 rss
  
  submitted by /u/DraftNotSent
  [link] [comments]
32. 🔗 r/reverseengineering DeepZero: An automated, agentic vulnerability research pipeline for finding kernel zero-days rss
  
  submitted by /u/watchdogsrox
  [link] [comments]
33. 🔗 backnotprop/plannotator v0.17.1 release
  Follow @plannotator on X for updates
  
  Missed recent releases? Release | Highlights
  ---|---
  v0.17.0 | AI code review agents, token-level annotation, merge-base diffs
  v0.16.7 | Gemini CLI plan review, install script skills directory fix
  v0.16.6 | Perforce support, Pi shared event API, suggested code prefill, file tree expand fix
  v0.16.5 | Resize handle scrollbar fix, VS Code Marketplace publish
  v0.16.4 | Compound planning improvement hook, GitHub Enterprise + self-hosted GitLab, dockview workspace, new themes
  v0.16.3 | Pi phase configuration, CLI help, untracked file discovery fix, review scroll reset
  v0.16.2 | Draggable comment popovers, cross-file annotation visibility, custom diff fonts, OpenCode verbose log fix
  v0.16.1 | SSE stream idle timeout fix for external annotations API
  v0.16.0 | GitHub Copilot CLI, external annotations API, bot callback URLs, interactive checkboxes, print support, diff display options
  v0.15.5 | Custom display names, GitHub viewed file sync, expand/collapse all in file tree, search performance, WSL fix
  v0.15.2 | Compound Planning skill, folder annotation, /plannotator-archive slash command, skill installation via platform installers
  v0.15.0 | Live AI chat in code review, plan archive browser, folder file viewer, resizable split pane, Pi full feature parity
  
  What's New in v0.17.1
  
  v0.17.1 is a patch release that fixes PR review in the Pi extension and addresses several cross-platform bugs found during an exhaustive parity audit of every server endpoint between Bun and Pi runtimes.
  
  Pi PR Review
  
  The Pi extension's plannotator-review command was completely ignoring PR URL arguments and always falling back to local git diffs. v0.17.1 implements the full PR review flow: URL parsing, authentication checks, PR metadata fetch, and local worktree creation for both same-repo and cross-repo PRs. Same-repo PRs use git worktree add --detach with the PR's head ref; cross-repo forks use a shallow clone with tracking refs for both branches.
  
  Beyond the missing PR flow, an audit of all 27 review server feature areas uncovered 12 parity gaps in the Pi server. These ranged from missing diagnostic logging on PR actions to incorrect access guards that would have allowed diff switching in PR mode. All have been fixed.
  - #503
  Remote URL Parsing
  
  parseRemoteUrl has been rewritten to handle the full range of git remote formats. The previous regex incorrectly matched HTTPS URLs with non-standard ports (e.g., https://gitlab.example.com:8443/group/project.git) as SSH, and failed on multi-segment GitLab paths like group/subgroup/project. The new implementation handles SSH, SSH with port (ssh://git@host:22/path), standard HTTPS, and HTTPS with custom ports as separate cases. This fix applies to both Bun and Pi runtimes.
  - #503
  Cross-Repo Clone Fixes
  
  Cross-repo PR clones (forks from different organizations) had two issues. The gh repo clone and glab repo clone commands don't accept a --hostname flag, so self-hosted GitHub Enterprise and GitLab instances would fail. The fix uses GH_HOST and GITLAB_HOST environment variables instead, which both CLIs respect. The shallow fetch depth has also been increased from 50 to 200 commits to handle PRs with longer histories.
  - #503
  Additional Changes
  - Git Add button hidden in PR mode. The staging button was incorrectly visible during PR reviews because the server returned diffType: undefined and the client defaulted to "uncommitted". The client now disables staging when PR metadata is present
  - Diff viewer theme flash fix. Switching files in the diff viewer caused a brief flash of the wrong theme. The Pierre diff library's theme was being computed asynchronously via requestAnimationFrame; the initial state now reads CSS custom properties synchronously so the correct background appears on the first frame
  - Resolved/Outdated filters in PR comments. The PR comments tab now has toggle buttons to hide resolved or outdated review threads. Filters use the same green and amber color tokens as the existing status badges and integrate with the existing Clear Filters control
  Install / Update
  
  macOS / Linux:
```
curl -fsSL https://plannotator.ai/install.sh | bash
```
  Windows:
```
irm https://plannotator.ai/install.ps1 | iex
```
  Claude Code Plugin: Run /plugin in Claude Code, find plannotator , and click "Update now".
  
  Copilot CLI:
```
/plugin marketplace add backnotprop/plannotator
/plugin install plannotator-copilot@plannotator
```
  Gemini CLI: The install script auto-detects ~/.gemini and configures hooks, policy, and slash commands. See apps/gemini/README.md for manual setup.
  
  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
```
  VS Code Extension: Install from the VS Code Marketplace. Tested with Claude Code running in VS Code's integrated terminal. Not currently compatible with Anthropic's official VS Code extension due to upstream hook bugs.
  
  What's Changed
  - fix(pi): full PR review parity with Bun server by @backnotprop in #503
  Full Changelog : v0.17.0...v0.17.1
34. 🔗 r/LocalLLaMA Gemma 4 26b A3B is mindblowingly good , if configured right rss
  
  Last few days ive been trying different models and quants on my rtx 3090 LM studio , but every single one always glitches the tool calling , infinite loop that doesnt stop. But i really liked the model because it is rly fast , like 80-110 tokens a second , even on high contex it still maintains very high speeds.
  
  I had great success with tool calling in qwen3.5 moe model , but the issue i had with qwen models is that there is some kind of bug in win11 and LM studio that makes the prompt caching not work so when the convo hits 30-40k contex , it is so slow at processing prompts it just kills my will to work with it.
  
  Gemma 4 is different , it is much better supported on the ollama cpp and the caching works flawlesly , im using flash attention + q4 quants , with this i can push it to literally maximum 260k contex on rtx 3090 ! , and the models performs just aswell.
  
  I finally found the one that works for me , its the unsloth q3k_m quant , temperature 1 and top k sampling 40. i have a custom system prompt that im using which also might be helping.
  
  I've been testing it with opencode for the last 6 hours and i just cant stop , it cannot fail , it exiplained me the whole structure of the Open Code itself , and it is a huge , like the whole repo is 2.7GB so many lines of code and it has no issues traversing around and reading everything , explaining how certain things work , i think im gonna create my own version of open code in the end.
  
  It honestly feels like claude sonnet level of quality , never fails to do function calling , i think this might be the best model for agentic coding / tool calling / open claw or search engine.
  I prefer it over perplexity , in LM studio connected to search engine via a plugin delivers much better results than perplexity or google.
  
  As for vram consumption it is heavy , it can probably work on 16gb it not for tool calling or agents , u need 10-15k contex just to start it. My gpu has 24gb ram so it can run it at full contex no issues on Q4_0 KV
  
  ------------------------------- Quick update post
  
  i've switched to llama.ccp now , https://www.reddit.com/r/LocalLLaMA/comments/1sgl3qz/gemma_4_on_llamacpp_should_be_stable_now/?share_id=a02aL2eXTf8pcTB7Gee0W&utm_medium=ios_app&utm_name=ioscss&utm_source=share&utm_term=1 , read this post it has some very valuable info if you want to run gemma 4 as efficiently as possible.
  
  I'm running the IQ4_X_S quant now by unsloth , full contex size 260k , 94-102 tk/s 20-21GB vram usage , q4 K_V
  
  submitted by /u/cviperr33
  [link] [comments]
35. 🔗 Jessitron Adding Correctness Conditions to Code Changes rss
  
  Today I looked at the first PR on our new project repo. It added a new run script, but the README didn’t mention it. The proposed change was incomplete, because the documentation was out of sync.
  
  Did I comment on the PR? heck no. I want to fix this problem for all PRs, not just this one. We can automate this stuff now.
  
  Correctness condition: All PRs include updates to all relevant documentation files.
  
  How can we make this true?
  
  Instructions - We can change AGENTS.md to instruct our coding agent to look for documentation files and update them.
  Verification - We can add a reviewer agent to check each PR for missed documentation updates.
  
  This is two changes, so I can break this work into two parts. Which of these should we do first?
  
  Changing the instructions is easy.
  
  If we do instructions first, it’s easy. It will work most of the time. When I try it on this little PR, it will certainly work, and then I can claim victory and move on to the next feature.
  
  Then later, on some future PR, the agent will miss updating some documentation. Will I notice? No. In fact: I hope not. If I’m looking through PRs to a level of detail that includes all documents in the PR and also documentation files not in the PR, then we have failed to automate enough of this project. (This project does not deserve that level of scrutiny.)
  
  Changing instructions without verification gives me no guarantee of my correctness condition.
  
  Adding validation is sufficient.
  
  If we do validation first, then every PR will be checked for missed documentation updates. Incorrect PRs will be rejected, so the coding agent will have to update the documentation.
  
  My correctness condition will be guaranteed. Well, as guaranteed as I can get it with this nondeterministic automation. The reviewing agent will have only one task, so it won’t forget to check for needed documentation updates. If we ever catch it being wrong, then we must update its instructions.
  
  If we never implement the instructions change, then PRs will take longer, because some agent has to respond to the PR comments, and then the feedback loop runs again.
  
  With verification in place, the instructions change is an optimization!
  
  Validation before implementation.
  
  It’s a little like test-first development, but at a higher level. We’re adding a check to every feature implementation, not just one.
  
  It’s more like property testing than unit testing. We aren’t hard-coding “every feature should update the README.” We’re stating a property: the documentation should be up-to-date after every feature change.
  
  Now my PR reviews are also system reviews: what about this PR should have been different? How can we change the agent’s context and feedback to make that different? Now test that system change on this PR before we fix it.
  
  This is the new Boy Scout Rule. It went from “leave the codebase cleaner than I found it” to “make the whole develoment system stronger than it was.”
  
  It’s all part of programming the agents to program our software.
36. 🔗 Jamie Brandon 0058: borrow-checking surprises, books, links rss
  
  (empty)
37. 🔗 Jamie Brandon Borrow-checking surprises rss
  
  (empty)
38. 🔗 Mitchell Hashimoto The Building Block Economy rss
  
  (empty)