🏡


  1. August 15, 2026
    1. đź”— VoidNullable/lific v2.6.0 release

      Who is acting is now resolved one way everywhere: connected AI agents get identities of their own and act as themselves, login-free mode genuinely works, and lific init asks how you want to sign in instead of leaving that decision to a hand-edited config file. Alongside the identity work: two security fixes worth upgrading for on their own, comments you can edit and link to, and identifiers you can copy from wherever you see them.

      Sign-in, identity, and agents (PR

      #23 by @zorro432)

      • Login-free mode now works end to end. Running with required = false used to be half-broken: project reads passed while admin endpoints answered 403, because the "no auth here" signal never reached the handler-level gates. Identity is now resolved in one place for REST, MCP, and CLI alike, every request carries a real user, and a login-free instance can administer itself.
      • lific init asks how you want to sign in. On a fresh install it offers Login-free or Passwords, states plainly what login-free means (anyone who can reach the server can administer it), binds login-free instances to loopback so that promise actually holds, and persists the choice to the config file. --auth-mode and --password cover scripted setups.
      • Connected AI agents act as themselves. Approving a tool over OAuth mints a per-tool bot identity, stdio agents connected via lific connect --stdio carry their own token, and the audit log attributes their writes to the tool rather than to you. Disconnecting or deleting a bot revokes its OAuth tokens too, and reconnecting remembers which tool a client picked last time.
      • lific connect grew a transport menu, with stdio preselected and remote and OAuth on offer. The flags (--stdio, --oauth, --url) behave exactly as before for scripted runs.
      • MCP enforces the same authorization as REST. An agent can no longer do more through MCP than the same account could through the web UI.
      • Hardening around the edges. Failed credentials now fail instead of quietly falling back to the first admin's identity; a server with web_auto_login enabled refuses to start on a non-loopback bind; connector configs that embed credentials are written with 0600 permissions; a new API key is bound to its user in the same insert that creates it; OAuth device-code redemption is atomic with the token mint.

      Security

      • An uploaded SVG can no longer run script on your instance. SVG is on the upload allowlist, and every image type was served with Content-Disposition: inline. Because an SVG is an XML document that may contain <script>, opening one directly (the "open image in new tab" path, not the rendered <img> in a comment) executed its script on Lific's own origin, where it could read the session token the web UI holds and act as whoever opened the file. Any account permitted to upload could use this to escalate against an admin who viewed the attachment. SVG uploads still work and still render in comments and pages; they now download rather than render when opened as a page of their own, and every attachment response carries Content-Security-Policy: default-src 'none'; sandbox as a second layer. Reported by @mjc.

      • A malformed config file now stops the server instead of silently reverting to defaults. A config that failed to parse, including one broken by a single typo, produced a warning on stderr and then booted from the built-in defaults. Those defaults bind 0.0.0.0, allow self-service signup, and treat an empty cors_origins as "any origin", so an operator who had set host = "127.0.0.1" and allow_signup = false could be left running a materially more exposed instance with nothing but a log line to say so. A config file that exists but cannot be read or parsed is now a hard startup failure naming the file and the error. Unknown keys are rejected for the same reason: allow_signupp = false used to be ignored silently and now fails loudly. A missing config file is still perfectly fine and still starts on defaults. Reported by @mjc.

      API

      • "Authentication required" is now always a 403. Nineteen places in the REST API each wrote their own version of the "is anyone signed in?" check, and roughly half of them reported the failure as 400 Bad Request while the rest reported 403 Forbidden. The endpoints for your profile, password, sessions, API keys, connected tools, and comments were in the 400 group; they now answer 403 like everything else, with the message authentication required. If you have a client that treats a 400 from those endpoints as "you are signed out", it needs to look for 403 instead.

      Web UI

      • Comments have their own links, and#N becomes one. A comment can be linked directly and the browser scrolls to it, and a bare #12 in issue text resolves to that issue. (PR #24 by @unger1984)
      • Edit and delete your own comments. Editing is inline with the full composer (markdown, mentions, quoting, attachments), deleting asks for confirmation in place, and an edited comment carries an edited label with the exact time in its tooltip. (PR #25 by @unger1984)
      • Home shows a live activity rate. It seeds from the last 24 hours of activity you are allowed to see, then ticks along over the websocket instead of starting from a misleading zero. (PR #26 by @mjc)
      • Copy an identifier from wherever you are looking at it : the detail-page breadcrumbs, a board card, or a list row. (PR #22 by @lardissone) The copy and peek buttons are reachable by keyboard, not hover alone, and pills name the identifier they copy so a screen reader announces something useful.
      • Copy selected text from the selection toolbar , instead of reaching for the mouse to select and copy by hand.
      • The desktop sidebar collapses , giving the board and the issue list the full width.
      • The status chip in the issue topbar is a picker. Changing status no longer means opening the field below it.

      Fixes

      • Starter label presets no longer vanish after you add the first one.
      • Editing a label no longer reloads the entire settings page.
      • #N inside a numeric HTML entity is left alone rather than linkified into nonsense.
      • Deeply nested plan steps stay readable instead of squeezing themselves into an ever-narrower column.
      • Attachment links stay in sync on every MCP write path, not just some of them.
      • A restore whose rollback fails now names the path the old database survives at, instead of leaving you to hunt for it.
      • lific doctor checks the router production actually serves.
      • Test databases are named from a counter rather than the clock, so a fast machine no longer collides two of them in the same millisecond.

      Upgrading

      • Two migrations run automatically on first start; they add the per-tool identity plumbing behind connected agents. No manual steps.
      • Check that yourlific.toml parses before rolling this out, because a config Lific previously ignored will now stop it from starting. lific doctor reports the config as a normal check and keeps running the rest, which makes it the right tool for this. The strictness is the fix, not a side effect: a config that fails to load is exactly the case that used to degrade quietly.
      • If web_auto_login is enabled and [server] host is not loopback, the server now refuses to start rather than exposing a no-password login to the network. Bind 127.0.0.1 or turn auto-login off.
      • If your config sets secure_cookies under [auth], remove it. It has never been read from the file (it is derived from whether server.public_url is https://), and unknown keys are now an error rather than being ignored.
      • Audit entries written by connected tools are now attributed to the tool's own identity rather than to the operator who connected it.
    2. đź”— HexRaysSA/plugin-repository commits sync repo: +1 release rss
      sync repo: +1 release
      
      ## New releases
      - [IDA-MCP](https://github.com/captain-ai-hub/ida-mcp): 0.8.1
      
  2. August 14, 2026
    1. đź”— IDA Plugin Updates IDA Plugin Updates on 2026-08-14 rss

      IDA Plugin Updates on 2026-08-14

      New Releases:

      Activity:

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

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

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

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

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

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

    3. đź”— modem-dev/hunk v0.18.2 release

      What's Changed

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

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

    4. đź”— r/Harrogate Daytime concerts or session rss

      Hello! Does anyone know of any daytime classical concerts, or similar, or theatre... Or meet-ups of any kind - happening over the next month?

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

    5. đź”— HexRaysSA/plugin-repository commits sync repo: +1 plugin, +9 releases rss
      sync repo: +1 plugin, +9 releases
      
      ## New plugins
      - [eject_idb](https://github.com/allthingsida/eject_idb) (0.0.3)
      
      ## New releases
      - [IDA-MCP](https://github.com/captain-ai-hub/ida-mcp): 0.8.0, 0.7.1, 0.7.0
      - [QScripts](https://github.com/allthingsida/qscripts): 1.2.8
      - [SigMaker](https://github.com/mahmoudimus/ida-sigmaker): 1.14.3
      - [ida-codemode](https://github.com/hexrayssa/ida-codemode): 0.6.1, 0.6.0, 0.5.3
      
    6. đź”— earendil-works/pi v0.84.2 release

      New Features

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

      Added

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

      Changed

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

      Fixed

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

      What's Changed

      • Add labels to the embedded MachineSpec so SDK callers reach CLI parity by @BinSquare in #929
      • Move the label parser into the library so every front end shares one implementation by @BinSquare in #930
      • Pass the stub name to pack create -o in the README snapshot recipe by @NickyHeC in #934
      • Rejuvenate a forked clone's identity inside the workload rootfs so image clones stop inheriting the golden's SSH host keys by @BinSquare in #936
      • Record egress denials and surface them per machine through the CLI and serve API by @BinSquare in #937
      • Preserve container file ownership in packed machines by @BinSquare in #938
      • Move interactive-session writes to a dedicated thread so exec -i handles large piped stdin by @panta in #931
      • chore(nix): bump flake to 1.8.0 by @BinSquare in #928

      Full Changelog : v1.8.0...v1.8.1

    8. đź”— r/Harrogate Unwanted Lego rss

      If anyone has any Lego they want to get rid of drop me a message and I can pay in cash and collect

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

    9. đź”— matklad Printing Lists rss

      Printing Lists

      Aug 14, 2026

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

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

      Above & Beyond - a new release is available:

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

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

      Visit muspy for more information.

    11. đź”— New Music Releases Saliva - Breaking Through rss

      Saliva - a new release is available:

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

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

      Visit muspy for more information.

    12. đź”— New Music Releases Unprocessed - Lost Tapes rss

      Unprocessed - a new release is available:

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

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

      Visit muspy for more information.

  3. August 13, 2026
    1. đź”— IDA Plugin Updates IDA Plugin Updates on 2026-08-13 rss

      IDA Plugin Updates on 2026-08-13

      New Releases:

      Activity:

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

      Follow @plannotator on X for updates

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

      What's New in v0.27.3

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

      Folder annotate no longer freezes the session on large repos

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

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

      Reported by @abanoub-ashraf in #1313.

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


      What's New in v0.27.2

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

      Plan and code review on phones and tablets

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

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

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

      Codex review jobs work again on current Codex CLIs

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

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

      Folder annotate opens in milliseconds on large repos

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

      Annotate any markdown-like file with configurable extensions

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

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

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

      Security hardening across the supply chain

      Four security-focused changes landed in this cycle:

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

      Additional Changes

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

      Install / Update

      macOS / Linux:

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

      Windows:

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

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

      OpenCode: Clear cache and restart:

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

      What's Changed

      Community

      This release carries a lot of community fingerprints:

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

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

    3. đź”— backnotprop/plannotator v0.27.2 release

      Follow @plannotator on X for updates

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

      What's New in v0.27.2

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

      Plan and code review on phones and tablets

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

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

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

      Codex review jobs work again on current Codex CLIs

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

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

      Folder annotate opens in milliseconds on large repos

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

      Annotate any markdown-like file with configurable extensions

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

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

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

      Security hardening across the supply chain

      Four security-focused changes landed in this cycle:

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

      Additional Changes

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

      Install / Update

      macOS / Linux:

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

      Windows:

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

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

      OpenCode: Clear cache and restart:

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

      What's Changed

      Community

      This release carries a lot of community fingerprints:

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

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

    4. đź”— Jeremy Fielding (YouTube) Flexible Engineering at Open Sauce rss

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

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

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

      Social media, websites, and other channel

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

      Notes:

      Technical corrections

      Nothing yet

    5. đź”— r/Harrogate UFOs over Harrogate rss

      I’m finding that on a clear night, looking east / south east from Harrogate, I’m seeing lights (that look like distant stars) moving fast and changing direction. They must be at very high altitude and there is no sound, but they seem too fast to be planes, plus we don’t seem to be on a commercial flight path here (?) unlike Leeds.

      I saw them again last night - there’s no port/starboard red green wing lights and no flashing lights. Will these be military aircraft? I don’t know what they are.

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

    6. đź”— r/Harrogate The partial solar eclipse taken from Nidd Gorge viaduct yesterday rss

      The partial solar eclipse taken from Nidd Gorge viaduct yesterday | submitted by /u/namboozle
      [link] [comments]
      ---|---

    7. đź”— smol-machines/smolvm smolvm v1.8.0 release

      What's Changed

      • Bind ephemeral machine lifetime to the launching CLI and add machine labels by @BinSquare in #899
      • Fix cross-VM --mount-socket collisions when the guest path is inside a shared --volume by @Bnjoroge1 in #867
      • fix(machine): preserve egress policy for --from by @bft-codebot in #892
      • Fix relayed ping on macOS: compute the IPv4 echo checksum and strip the prepended IP header by @BinSquare in #915
      • Add declarative fork settings to Smolfile by @BinSquare in #914
      • Preserve forked rootfs state in CLI operations by @BinSquare in #904
      • Write the readiness marker only when the doorbell goes unanswered by @BinSquare in #916
      • Normalize the agent rootfs's owner-only Alpine paths at build time so pack create works for a non-root user on a packaged install by @NickyHeC in #872
      • Deploy package repositories without Git history by @BinSquare in #918
      • Bump the guest kernel to the build with the netfilter options Kubernetes services need by @BinSquare in #919
      • Wire image workloads through embedded forks by @BinSquare in #917
      • chore(nix): bump flake to 1.7.7 (#913) by @Ramblurr in #920
      • Fix from-vm packs dropping layers past the third and the image's environment by @BinSquare in #924
      • Restore every directory's mode after extracting a pack, not only unwritable ones by @BinSquare in #925
      • Bump the guest kernel to the truthful datagram connect fix so machines regain hostname egress by @BinSquare in #927
      • Restore net-enabled libkrun on macOS and document the real networkBackend default (fixes #884) by @panta in #905

      New Contributors

      Full Changelog : v1.7.7...v1.8.0

    8. đź”— WerWolv/ImHex Nightly Builds release

      Nightly

      875f94a Changelog

      • fix: Try to keep default window size smaller than screen
      • feat: Add HMAC Hash
    9. đź”— backnotprop/plannotator v0.27.1 release

      Follow @plannotator on X for updates

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

      What's New in v0.27.1

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

      Open in editor no longer breaks after repeated sessions

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

      File headers respect the Viewed and Git-add visibility toggles

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


      What's New in v0.27.0

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

      Important

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

      Call Flow: see the call paths your diff changes

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

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

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

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

      code

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

      plannotator review --tailscale
      

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

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

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

      The review panel remembers how you work

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

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

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

      Pi integration rebuilt: no more prompt-cache busting

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

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

      Focus mode from the keyboard

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

      Standing instructions for Guided Review

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

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

      Hardened release pipeline and security scanning

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

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

      Additional Changes

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

      Install / Update

      macOS / Linux:

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

      Windows:

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

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

      OpenCode: Clear cache and restart:

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

      What's Changed

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

      Community

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

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

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

    10. đź”— Console.dev newsletter SolidStart 2 rss

      Description: JS framework for web apps.

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

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

    11. đź”— Console.dev newsletter Amp rss

      Description: Agentic coding environment.

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

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

  4. August 12, 2026
    1. đź”— IDA Plugin Updates IDA Plugin Updates on 2026-08-12 rss

      IDA Plugin Updates on 2026-08-12

      New Releases:

      Activity:

      • capa
        • 758c9075: Sync capa-testfiles submodule
      • dotfiles
      • ida-codemode
        • ef7c39db: readme: more installation details
      • ida-pro-mcp
        • eb25a764: feat(live): full-surface integration suites + 9.3/9.4 API-drift fixes
        • 0ae0e2a3: feat(runtime): idalib backend behind IDA_MCP_RUNTIME=idalib
        • 64bd2393: docs(wiki): GP sreg seam is dead — RISC-V has no segment registers
        • 8ccf4096: fix(open): memory_model no longer silently dropped; processor_options…
        • fd8d283c: fix(riscv): GP-relative xrefs resolve headless via ref re-pointing
        • f8a22c52: feat(validation): close out the 9.4 work items with live runtime matrix
        • b46dfa41: feat(compat): tinfo-based stack-frame walk replaces removed get_frame
        • 904d022a: docs: mark func_t remnant + segment-mutation batches complete
        • 482d579f: feat(compat): migrate func_t-holding remnant + segment mutation to 9.…
        • 8e358908: docs: record EA-API migration completion + remnant audit scope
        • c26b22c3: feat(compat): migrate remaining getseg sites to 9.4 EA API
        • dc863399: feat(compat): migrate flat tools batch to 9.4 EA APIs
        • 734951d7: feat(compat): migrate search subtree + error_handling to 9.4 EA APIs
        • fd42cd24: feat(compat): migrate tools batch 2 to 9.4 EA function APIs
        • 20036c08: feat(compat): function + segment-attribute wrappers for 9.4 EA APIs
      • ida_kcpp
      • IDAPluginList
        • 15f1eda1: chore: Auto update IDA plugins (Updated: 19, Cloned: 0, Failed: 0)
      • project
      • qscripts
        • fd970966: Build on libidacpp; fix monitor deactivating after a .deps index change
    2. đź”— backnotprop/plannotator v0.27.0 release

      Follow @plannotator on X for updates

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

      What's New in v0.27.0

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

      Important

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

      Call Flow: see the call paths your diff changes

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

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

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

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

      code

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

      plannotator review --tailscale
      

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

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

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

      The review panel remembers how you work

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

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

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

      Pi integration rebuilt: no more prompt-cache busting

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

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

      Focus mode from the keyboard

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

      Standing instructions for Guided Review

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

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

      Hardened release pipeline and security scanning

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

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

      Additional Changes

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

      Install / Update

      macOS / Linux:

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

      Windows:

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

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

      OpenCode: Clear cache and restart:

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

      What's Changed

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

      Community

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

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

      Full Changelog : v0.26.8...v0.27.0

    3. đź”— jesseduffield/lazygit v0.64.1 release

      What's Changed

      This fixes a few regressions that were introduced in the last release, and some long-standing bugs that I didn't see any reason to hold back until the next big one.

      Fixes đź”§

      Maintenance ⚙️

      Full Changelog : v0.64.0...v0.64.1

    4. đź”— @binaryninja@infosec.exchange Sidekick 26.1 is out now! Sidekick finally has a proper home as a Binary Ninja mastodon

      Sidekick 26.1 is out now! Sidekick finally has a proper home as a Binary Ninja view, with each binary or project built around one continuing conversation with a lead agent. Also new: consolidated Resources, terminal access, transaction Revert, faster sidebars, lower first-response latency, and plenty more. Check out everything new in 26.1: https://sidekick.binary.ninja/blog/sidekick-26-1-a-proper-home-for- sidekick/

    5. đź”— r/Harrogate Rock/Metal/Alternative rss

      Rock/Metal/Alternative | Bottom Of The Bottle, one of Harrogate longest running nights is back and celebrating its 25th Birthday!!! At Bilton Club in October, it's not to be missed đź–¤ Tickets are ÂŁ8 or ÂŁ10 on the door Bilton club.co.uk submitted by /u/No-Chocolate9752
      [link] [comments]
      ---|---

    6. đź”— HexRaysSA/plugin-repository commits sync repo: +5 releases rss
      sync repo: +5 releases
      
      ## New releases
      - [IDA-MCP](https://github.com/captain-ai-hub/ida-mcp): 0.6.3, 0.6.2, 0.6.1
      - [ida-codemode](https://github.com/hexrayssa/ida-codemode): 0.5.2, 0.5.1
      
    7. đź”— r/Harrogate Beatiful video of old photos of Harrogate rss

      Beatiful video of old photos of Harrogate | submitted by /u/LowGuide2746
      [link] [comments]
      ---|---

    8. 🔗 r/Harrogate The perfect eclipse spot – am I missing something? rss

      I was on the stray yesterday at 7.15pm, and most of it was still in direct sunlight. You could certainly see the sun, relatively high in the sky, from most of Harrogate.

      There seems to be a lot of hand-wringing about where to stand to see the eclipse, going to Brimham Rocks, needing to be high up etc. Surely you can just stand on the Stray?

      submitted by /u/Much-Pickle-7047
      [link] [comments]

    9. đź”— smol-machines/smolvm Package repository archive release

      Preserves the complete package repository history before migrating GitHub Pages away from a binary branch.

    10. đź”— smol-machines/smolvm smolvm v1.7.7 release

      What's Changed

      Fixes

      • Rebuild the macOS libkrun so guests reach userspace instead of exiting at boot by @BinSquare in #911
      • Let a golden be forked more than once by retaining its RAM checkpoint by @BinSquare in #888
      • Set TERM for interactive exec sessions so a guest shell's line editor can redraw correctly by @BinSquare in #887
      • Retry transient KVM failures for fork bases by @BinSquare in #883
      • Coordinate forked rollout workers by @BinSquare in #879

      CUDA

      • Harden CUDA clone recovery by @BinSquare in #891
      • Harden post-training CUDA pools by @BinSquare in #886
      • Make CUDA clone recovery transactional, preserve CUDA in embedded runtimes, and support the CUDA 13 runtime ABI by @BinSquare

      Kubernetes

      • Add the k3s deployment for the smolvm Kubernetes runtime, without clobbering existing containerd config by @BinSquare in #876

      Docs and tests

      • Document the Smolfile as a top-level section and show how to snapshot a configured machine into a reusable image by @BinSquare in #897
      • Document the local archive, stdin and rootfs-directory forms of --image in the CLI help by @NickyHeC in #882
      • Increment the test harness counters with arithmetic expansion so a suite that does not use the || true idiom survives its first passing test by @NickyHeC in #874
      • Bump the workspace to 1.7.5 by @BinSquare in #910

      Note on 1.7.6

      1.7.6 was withdrawn: its macOS build could not start a machine at all. Anyone on 1.7.6 should move to 1.7.7. Linux was unaffected.

      Full Changelog : v1.7.5...v1.7.7

    11. đź”— seanmonstar Micro: A trait for fluent Durations rss

      I dislike the pattern in some languages to create durations by multiplying constants. It feels like a concession when it cannot be expressed more nicely. There’s a tracking issue to add such constants in libstd.

      How about a trait instead? (I suggested it in the tracking issue a long time ago, but it’s lost in the noise). Rust traits are awesome. They can be implemented on any other type, even primitives, without them needing to cooperate.

      A trait could allow us to write 5.seconds(), or 200.milliseconds(), etc. I think this is much better. I would rather this exist instead. Maybe std::time::TimeUnits, or pick a better name, doesn’t matter which, just that it’s easy to import.