Vibe Coding Radar: Agents Get More Autonomy, Same Risks

Three things moved in the AI-builder world this cycle: agents are running more of the workflow by default, one platform picked up a formal compliance standard, and founders are asking a question that should worry anyone shipping fast — do AI-written tests actually catch bugs? None of this is a single incident. It's a shift in how much control you're handing to a tool that writes your code.

TL;DR

• Vibe Coding Weekly #38 reports background agents are now the default mode in at least one major workflow, but the permission default reset to Manual — meaning the agent runs continuously but still needs a human nod before it acts. (vibecodingweekly.substack.com)
• Lovable adopted AIUC-1, described as a SOC-2-style standard for AI agents, and separately added a per-user opt-out from AI model training in account settings. (aiuc-1.com, docs.lovable.dev)
• A widely-discussed r/cursor thread asks how often AI-generated tests pass while missing the actual bug — a real workflow gap, not a hypothetical. (reddit.com)
• Cursor is reportedly being acquired by SpaceX for $60B (WSJ), a business change worth tracking if you build on Cursor's roadmap. (wsj.com)

Background agents are now the default — read the permission setting

Vibe Coding Weekly #38 flags a quiet but important change: background agents becoming the default mode, while the permission setting resets to Manual. (vibecodingweekly.substack.com) In plain terms, your agent can now keep working on tasks without you sitting there watching it — but it's still supposed to ask before it takes an action. That's the right default. The risk shows up when teams flip Manual to Auto for speed and forget to flip it back. If you or a contractor uses Cursor, Windsurf, or a similar tool with background agents, check what permission mode is actually set. An agent with standing approval to run commands, push code, or touch your database is a different risk profile than one that pings you first.

AI-generated tests are passing over real bugs

A widely-discussed r/cursor thread asks a question that should worry anyone shipping fast: how often does an AI-generated test suite go green while the actual bug sits a few lines away? (reddit.com) Commenters describe exactly that pattern — a generated test that checks the happy path, misses the edge case, and never touches the thing that's actually exploitable. This is not an argument against AI-written tests. It's a reminder that a green test suite answers "does the code do what I asked," not "is the code safe." Those are different questions, and only one of them is about security. If an agent wrote your tests, someone still has to ask what they don't cover.

Lovable adds a compliance standard and an opt-out

Lovable adopted AIUC-1, a standard the project describes as a SOC-2-style baseline for agentic development (aiuc-1.com). Separately, its July 31 changelog adds a per-user opt-out from AI model training in account settings. (docs.lovable.dev) Neither change fixes a specific bug in a specific app — a compliance standard is a floor, not a guarantee, and an opt-out only covers what you explicitly flip. But both are useful signals if you're picking a platform: a builder that's willing to be measured against a named standard is worth more trust than one that isn't.

Cursor's ownership is changing hands

The Wall Street Journal reports Cursor is being acquired by SpaceX for $60B. (wsj.com) That's not a security event by itself, but it's worth tracking if you build on Cursor day to day — a change in ownership can mean a change in roadmap, support, or default settings, and the agent permission defaults covered above are exactly the kind of thing that can shift quietly during a transition.

FAQ

Why do AI-generated tests miss bugs that seem obvious in hindsight?

Because the agent generates tests from the same understanding of the code that produced the bug in the first place. If it didn't reason about an edge case (or an attacker's input) while writing the feature, it usually won't think to test for it either. A passing suite tells you the code does what was asked, not that it's safe against input nobody asked about.

What is the AIUC-1 compliance standard, and does it matter for a solo founder?

AIUC-1 is a proposed SOC-2-style baseline for agentic development that Lovable has adopted. For a solo founder it's a signal, not a guarantee: it says the platform is willing to be measured against a named bar, but it doesn't audit your specific app. You still need to check your own access rules.

Should AI agents be allowed to rewrite code without a human checking first?

Not when the change touches data access, authentication, or permissions. That's exactly the category covered by the background-agent permission mode above — fast iteration is the appeal, but access-control changes are the one category that benefits from a second look before it ships.

The bottom line

Nothing here is a single incident. It's three small shifts in the same direction: agents doing more without asking, a platform formalizing what "trustworthy" means, and a live reminder that a passing test suite isn't the same thing as a secure one. If your agent runs in the background, check its permission mode. If it wrote your tests, ask what they don't cover.