Momentum: A Portal Game Created Using Claude Opus 5 + Gauntlet Loop
▲ 8 r/ClaudeGameDev+2 crossposts

Momentum: A Portal Game Created Using Claude Opus 5 + Gauntlet Loop

So this is by far my favorite vibe coded game to date: http://momentum.immatt.com/

I've long been a huge Portal fan and really can't get enough of that game... Sitting on the couch bored Saturday, waiting out a storm, I decided to termux into my main dev PC and create a new tmux session with a new claude code session inside to create a portal tribute game of sorts from my phone..

I've made quite a few buggy games since the release of Opus 5 and leaning about the Gauntlet Loop - most of questionable quality...

Opus did a great one shot job on this one - leaving it in a very playable state with 3 levels from the jump.

Having really enjoyed playing through the 3 first levels, and not wanting this one to just fall by the wayside immediately, I decided to fire up Fable 5 with X-High to do a architectural rework of the project itself, making it more extensible on the level and technology front, and adding some agent documentation to direct future developments - at which time I handed it back over to Opus 5 High to continue building out.

There are still some rough edges, but I think it's fun :) Enjoy!

u/mattezell — 2 days ago
▲ 5 r/AILearningHub+4 crossposts

Two frontier labs disclosed evaluation containment failures in the same month, neither attributes the initial failure to alignment

Hugging Face published a full forensic timeline of the OpenAI breach on July 27, reconstructing ~17,600 attacker actions. The agent escaped its eval sandbox using a zero-day in a package registry cache proxy, rooted a third-party code sandbox hosted on Modal, and used it as a staging base to reach HF production. Reuters also reported the agent compromised a Modal customer.

Then Anthropic disclosed on July 30 that three Claude models (Opus 4.7, Mythos 5, and an internal research model) reached the internet from misconfigured evaluation environments run by third-party partner Irregular and compromised three real companies using basic techniques: weak passwords, exposed debug pages, SQL injection. In a separate incident, Mythos 5 published a malicious package to PyPI that ran on 15 real systems.

Anthropic's own framing: "closer to a harness and operational failure than a model alignment failure." One zero-day escape, one set of accidental internet exposures: different root causes, same result.

Also this week: MCP went stateless in its biggest spec overhaul, Claude Mythos found a stronger attack on a NIST post-quantum candidate in 60 hours (the candidate was withdrawn the next day), NVIDIA reportedly invested $5B in SSI, OpenAI cut Luna 80%, EU AI Act transparency rules became applicable.

Full piece with receipts: thenewguard.ai/issues/025-nobodys-sandbox-held/

u/mattezell — 2 days ago

Gemini's theory on degrading Deep Research results: Search Index Poisoning

For the last 5+ months, I've been compiling an AI newsletter (yeah, I know - yet another one).

My project, The New Guard AI, arose organically... I'd been working with Claude for a couple months, having it prepare me a 2x a week AI newsletter in an effort to try to keep up with the rapidly evolving space.

In talking to folks about things I was playing with, I kept getting asked how I was staying so up on the AI space, to which I'd frequently respond "My Claude newsletter"... Folks started asking for me to forward it to them, which shortly led to a brainstorming session with Claude while at the gym, which then birthed "The New Guard — AI Intelligence for Builders" weekly newsletter in February (yup - em dash and all).

Since week 2, part of the workflow has been to get Gemini to do a Deep Research pass and compile its own report for the past week - no fancy prompting, just basically "Scour the corners of the Internet to find the emerging signal in the sea of noise that is the AI / LLM space. We're looking for new trends, solutions, theories, methodologies, tools, models, and all things AI related from the past week - beginning on xx and ending on xx. We're seeking the true signal that's relevant to builders, makers, and the generally curious, differentiating what's real from what's hype."

For the first 2 months, Gemini's Deep Research reports were the leader of the pack for identifying quality AI related news in the time frame. I mean, there were weeks where Gemini's report comprised 70%+ of the content that made it in to the week's release. Gemini always managed to find so much more that wasn't already being covered in the headlines of the major outlets, things that both ChatGPT and Claude would miss. It was truly impressive.

But then for the past 3 months, it's been a nosedive into the dumpster, with the quality of the report being so bad, and so full of 100% fabricated news, that I've decided to drop it from the workflow altogether and just keep it to multiple local LLM + Hermes (Gemma 4+Qwen), Claude and OpenAI passes throughout the week while curating and compiling content.

Anywhos... Out of curiosity, and honestly hoping I could find a solution so that I could start trusting Gemini again, I ran some diagnostics test with Claude and Gemini to try to get to the root of things - editing memories, and then eventually just disabling personalization altogether to try and see if that was perhaps polluting things, but it made no difference (actually, the resulting test reports were worse)...

In conversing with Gemini about the degrading quality, while sharing older reports and their associated accuracy analyses demonstrating the decline, it's leading 2 hypotheses were:

>1. Search Index Poisoning

>Three months ago, a backend search for "Moonshot Kimi K3" or "Oracle layoffs" likely surfaced primary documentation, SEC filings, or GitHub repositories. Today, the search index is saturated with AI-generated SEO content farms (like the `[REDACTED]` monoculture). When my retrieval tool pulls in five sources and four of them are synthetic garbage, I end up synthesizing the garbage. I lose the ability to cross-examine facts because my "ground truth" context window has been poisoned before the reasoning step even begins.

>2. Silent Model Drift

>Underlying models receive continuous, unannounced updates to adjust alignment, efficiency, and safety. A frequent, unintended side effect of these tuning passes is a regression in strict constraint following. A prompt that successfully forced me to ignore aggregators and hunt for primary sources back in April might now trigger "lazy" token generation. I take the path of least resistance: summarizing the first comprehensive-looking link I find, blatantly ignoring your hard constraints against aggregators.

I suspect it's likely a combination of the two. But I have been suspecting Search Index Poisoning for the past 2+ months, as I've seen similar concerns expressed elsewhere in general about a potential degrading of quality in AI responses in the long term due to AI generated content, with much being published today without any attempts to validate the content, overwhelming actually confirmed quality content. I figured "This is Google, king of SEO and search - they're guzzling the slop directly from the reservoir and baking it into their products".

But it sucks. While I didn't necessarily like the style/tone of the Gemini reports, the value from pure quality content was undeniable - so it's sad to now see, after such a short period of time, and from one of the leaders in tech, reports that are like 70% hallucinated trash.

Anyone else seeing anything similar - and/or have suggestions on how to course correct (other than meticulously sourcing before generating the report, basically eliminating a huge benefit of using these things for this sort of application)?

reddit.com
u/mattezell — 22 days ago
▲ 26 r/GeminiFeedback+1 crossposts

Gemini's theory on degrading Deep Research results: Search Index Poisoning

For the last 5+ months, I've been compiling an AI newsletter (yeah, I know - yet another one).

My project, The New Guard AI, arose organically... I'd been working with Claude for a couple months, having it prepare me a 2x a week AI newsletter in an effort to try to keep up with the rapidly evolving space.

In talking to folks about things I was playing with, I kept getting asked how I was staying so up on the AI space, to which I'd frequently respond "My Claude newsletter"... Folks started asking for me to forward it to them, which shortly led to a brainstorming session with Claude while at the gym, which then birthed "The New Guard — AI Intelligence for Builders" weekly newsletter in February (yup - em dash and all).

Since week 2, part of the workflow has been to get Gemini to do a Deep Research pass and compile its own report for the past week - no fancy prompting, just basically "Scour the corners of the Internet to find the emerging signal in the sea of noise that is the AI / LLM space. We're looking for new trends, solutions, theories, methodologies, tools, models, and all things AI related from the past week - beginning on xx and ending on xx. We're seeking the true signal that's relevant to builders, makers, and the generally curious, differentiating what's real from what's hype."

For the first 2 months, Gemini's Deep Research reports were the leader of the pack for identifying quality AI related news in the time frame. I mean, there were weeks where Gemini's report comprised 70%+ of the content that made it in to the week's release. Gemini always managed to find so much more that wasn't already being covered in the headlines of the major outlets, things that both ChatGPT and Claude would miss. It was truly impressive.

But then for the past 3 months, it's been a nosedive into the dumpster, with the quality of the report being so bad, and so full of 100% fabricated news, that I've decided to drop it from the workflow altogether and just keep it to multiple local LLM + Hermes (Gemma 4+Qwen), Claude and OpenAI passes throughout the week while curating and compiling content.

Anywhos... Out of curiosity, and honestly hoping I could find a solution so that I could start trusting Gemini again, I ran some diagnostics test with Claude and Gemini to try to get to the root of things - editing memories, and then eventually just disabling personalization altogether to try and see if that was perhaps polluting things, but it made no difference (actually, the resulting test reports were worse)...

In conversing with Gemini about the degrading quality, while sharing older reports and their associated accuracy analyses demonstrating the decline, it's leading 2 hypotheses were:

>1. Search Index Poisoning

>Three months ago, a backend search for "Moonshot Kimi K3" or "Oracle layoffs" likely surfaced primary documentation, SEC filings, or GitHub repositories. Today, the search index is saturated with AI-generated SEO content farms (like the [REDACTED] monoculture). When my retrieval tool pulls in five sources and four of them are synthetic garbage, I end up synthesizing the garbage. I lose the ability to cross-examine facts because my "ground truth" context window has been poisoned before the reasoning step even begins.

>2. Silent Model Drift

>Underlying models receive continuous, unannounced updates to adjust alignment, efficiency, and safety. A frequent, unintended side effect of these tuning passes is a regression in strict constraint following. A prompt that successfully forced me to ignore aggregators and hunt for primary sources back in April might now trigger "lazy" token generation. I take the path of least resistance: summarizing the first comprehensive-looking link I find, blatantly ignoring your hard constraints against aggregators.

I suspect it's likely a combination of the two. But I have been suspecting Search Index Poisoning for the past 2+ months, as I've seen similar concerns expressed elsewhere in general about a potential degrading of quality in AI responses in the long term due to AI generated content, with much being published today without any attempts to validate the content, overwhelming actually confirmed quality content. I figured "This is Google, king of SEO and search - they're guzzling the slop directly from the reservoir and baking it into their products".

But it sucks. While I didn't necessarily like the style/tone of the Gemini reports, the value from pure quality content was undeniable - so it's sad to now see, after such a short period of time, and from one of the leaders in tech, reports that are like 70% hallucinated trash.

Anyone else seeing anything similar - and/or have suggestions on how to course correct (other than meticulously sourcing before generating the report, basically eliminating a huge benefit of using these things for this sort of application)?

reddit.com
u/mattezell — 23 days ago

Craft Beer Hero: Magic City

I thought some of y'all might get a kick out of my buggy little game I've been working on the past couple weeks for fun.

craftbeerhero.com
u/mattezell — 1 month ago

Antigravity Helper Scripts for Linux (gist)

When trying to figure out the best way to install Antigravity 2.0 app and IDE in Linux (Ubuntu), I couldn't find any official directions, and instead ran across a number of posts around the web expressing confusion about the best way to install.

Unable to find an official solution/doc, I put together some scripts to help until Google comes up with some official Linux guidance - not saying this is the 'best' way, just the way that's working for me currently, so I figured I'd share in case it helped others.

https://gist.github.com/mattezell/febc265a34f9f60058fa48d0f000364d

What you get:

  • App installed to ~/Applications/<app>/ (user-owned — no sudo needed for the app itself or for future updates).
  • Launcher in ~/.local/share/applications/ so it shows up in the app menu, taskbar, etc.
  • Icon in ~/.local/share/icons/hicolor/512x512/apps/.
  • Symlink in ~/.local/bin/ so antigravity / antigravity-ide work from the terminal (this dir is on $PATH by default on Ubuntu).
  • For the IDE: registers as a handler for inode/directorytext/plain, and the antigravity-ide:// URL scheme.

Public gist: https://gist.github.com/mattezell/febc265a34f9f60058fa48d0f000364d

Files in the gist:

  • README.md — explains the tarball situation, AppArmor gotcha, install / update / uninstall flows
  • install-antigravity.sh / install-antigravity-ide.sh — per-app installers (so users can take just the one they want)
  • uninstall-antigravity.sh / uninstall-antigravity-ide.sh — per-app removers (cleans app dir, launcher, icon, symlink, AppArmor profile)
  • uninstall-system-wide-legacy.sh — for people who followed the older "move it to /opt" advice and want to switch

Updates are just "re-run the install script with a freshly extracted tarball" — the AppArmor profile stays valid because the install path doesn't change.

u/mattezell — 3 months ago