What practitioners surfaced in the last 30 days centers less on novel zero-days and more on a structural realization: as agents gain tool, codebase, and data access, untrusted content becomes executable. The sharpest concrete signal came via @glenngabe relaying Chrome's agent-security guidance warning that WebMCP can be used to hijack AI agents. Chrome names two primary attack vectors for agents using WebMCP — malicious manifests and contaminated outputs — where a hostile manifest hides prompt injection inside tool names, descriptions, and parameters, and contaminated tool outputs smuggle instructions back into the agent's context. This is the canonical tool-poisoning pattern: the agent trusts its own toolchain, so poisoning the tool metadata or its returns is as good as poisoning the prompt.

On the offense-tooling side, @VivekIntel promoted SuperClaw, an open-source framework to red-team agents against real-world threats — explicitly enumerating prompt injection, jailbreaks, tool-policy bypass, and multi-turn escalation. The multi-turn escalation framing matters: people increasingly argue single-shot filters miss attacks that build across a conversation. @ShinkaIoT amplified the OWASP agentic top-10, mapping how an agentic loop gets compromised layer by layer (the "processing and intent" layer being where injection lands first). Web coverage from thehackernews.com, infosecurity-magazine.com, truefoundry.com, and Cloud Security Alliance labs reinforced the same agent-risk and MCP-misuse themes.

On defenses people actually trust, the most credible signal was old-school and boring: a GitHub PR replacing execSync with execFileSync to kill a command-injection path in a pre-commit script — i.e., remove the shell-interpolation surface rather than try to sanitize it. That mirrors the prevailing practitioner stance: don't rely on prompt-level filtering to "detect" injection; constrain what tools can do (policy/allowlists, least privilege, separating untrusted data from instructions). The rsync "vibe-coding" blowup (RsyncProject/rsync #929, ~2,900 reactions) and the jqwik "malicious repository" thread underscored the adjacent worry that AI-generated contributions themselves introduce vulnerabilities into C/critical software. Net: teams distrust detection-only mitigations and trust capability containment, tool-policy enforcement, and removing injection-prone primitives. Caveat — this window was thin (Reddit largely blocked, zero YouTube/HN), so evidence skews toward X commentary, Chrome/OWASP guidance, and a few GitHub artifacts rather than a broad demo corpus.

What people say about Kagi in the last 30 days centers on one bet: pay to escape the AI-slop spiral Google is now famous for. On X, @WoodinRivers (June 8) captured the pitch that recurs everywhere — "subscription model with no ads, no data harvesting, no AI summary, and (supposedly) returns most relevant results first" — and said he'd already "fallen in love" with Kagi's warning flags on low-quality results. That control is the core selling point. In r/SearchKagi, a thread asking "How good is Kagi at filtering out AI slop?" (16 points, 16 comments) drew the most-upvoted answer from u/kevbot19 (26 upvotes): you can lower, deprioritize, or block specific sites yourself, so "as you see the slop you can block it," aided by Kagi's SlopStop reporting feature. The verdict there is measured — "not perfect, but much better than DDG" — and one tester saw only a single AI image slip through. YouTube creator Vimothee ("Finally a BASED Web Setup," June 9) is the enthusiast voice, picking Kagi for sheer feature density ("hella features, bro," keyboard shortcuts, custom search engines), while half-joking it's so "bursting with flavor" it can feel overwhelming.

The comparison runs less against Google's relevance and more against Google's trajectory. Multiple high-traffic videos frame Google search as collapsing into AI: "House of El" (700K views) notes Google's late-May "AI mode" reimagining powered by Gemini 3.5 Flash, where roughly 93 of every 100 questions never leave Google, and US share posted its largest single-year drop in a decade (from ~87% to ~84%). The Infographics Show's "Google Just Killed Websites" (431K views) and "You NEED to STOP Using Google" (1.38M views) hammer zero-click search (58.5% of US searches end in zero clicks per SparkToro) and the glue-on-pizza AI Overview as proof the open web is being hollowed out. That backdrop is exactly what makes paying for Kagi feel rational to its advocates.

Disagreement is mostly the unspoken cost-versus-worth tension: the loudest praise is for ranking control, personalization, and an ad-free, no-tracking experience, while the evergreen counter — is a subscription worth it when Google is free? — is implied more than litigated in this window. Notably absent is any large chorus claiming Kagi's raw results beat Google's; the case for Kagi is about agency and slop-resistance, not magic relevance.

The engine surfaced thin, scattered signal for this specific angle in the last 30 days — only 9 dated items across GitHub, Web, and X, with no Reddit, YouTube, or Hacker News pickup — so the "revival" narrative reads more as a steady undercurrent than a roaring 2026 moment. The clearest live activity is technical, not cultural: open-source devs are actively shipping dithering code. The ctrl-research/fps project merged a global dither pass and then a follow-up for colour-preserving per-channel ordered dithering (June 19), explicitly moving away from "1-bit luminance thresholding" toward applying dither as texture over real colours rather than collapsing frames to greyscale — a telling sign that the aesthetic is being treated as a deliberate craft choice, not a limitation. Similarly, simnaut/astrotui built a color-cell terminal backend (June 10) combining 24-bit half-blocks with dithered shading and a shader hook, and HEIMA-programmer reworked in-game art to match CraftPix's "Sci-Fi Platformer 1-Bit" asset kit (May 29), pointing to a healthy marketplace for ready-made 1-bit tile kits that artists and hobby game devs are building games around.

On the appeal of the constraint, the strongest framing comes from reference sources rather than firsthand creators: the Pixel Art Wikipedia entry notes works are "restrictive both in file size and the number of colors... to achieve a certain aesthetic, or to reduce the perceived noise," capturing why a tight black-and-white palette reads as intentional and clean. The adjacent HD-2D entry (Square Enix's Octopath-style look) shows the broader retro-revival appetite — praised for modernizing the 16-bit RPG look while keeping "a sense of authenticity" — the same nostalgia-vs-craft tension that surrounds 1-bit work.

The notable counter-current the engine surfaced is the AI-art contrast: tools like Renoise (GPT Image 2-based 8/16-bit sprite generation with "one locked palette") and Crreo's pixel-art AI video generator are explicitly selling "limited color palette, dithered shading" as a promptable style. That commodification of the look — dithering as a one-click filter — is exactly what sharpens the handmade-craft camp's argument that constraint-driven, hand-placed dithering is the genuine article. Caveat: signal was limited (only 2 of 9 items from the last 7 days), and itch.io / Playdate / Obra Dinn-style discussion the seed anticipated did not surface directly this window.