Virex Deep Dives

Product writing, updates, trust pages, and the broader company story around owned repos.

UpdatesLate May 2026 release4 min read

Late May 2026: clearer signals, safer accounts, sharper builds

The biggest shift this round is that the engine spends credits more carefully — most Premium builds now use a small fraction of what they did a week ago. On top of that, you can now see at a glance how much of your monthly pool you've used, the safety check runs in any language before any work happens, and the build chat got a noticeable refresh.

updatesproductsafety

Credit pool warning you can actually see

A small banner now appears at the top of every page once you're past 80% of your monthly credit pool. It tells you how many credits are left, when the pool resets, and gives you a one-click path to upgrade if you want more headroom.

Each level (80%, 90%, 95%, 100%) is dismissable on its own, so dismissing the gentle 80% warning doesn't suppress the firmer 90% one. At 100% the banner stays visible until your pool resets — no chance of forgetting and getting surprised by a half-built result.

  • Visible across the dashboard, build, and settings pages.
  • Shows credits remaining and renewal date.
  • Free tier doesn't see it — only paid plans have a pool to track.

Builds refuse cleanly when the pool is empty

Previously, starting a build when you were essentially out of credits could still produce a result — but the result was a generic template with placeholder copy, not your product. Easy to mistake for a real build, hard to spot from the outside.

Now if you don't have enough headroom to run a meaningful build, the engine refuses to start and tells you when your pool resets. Cosmetic edits on existing projects stay free as always, so you can keep iterating on what you already have.

Multilingual safety check at the front of every build

A safety review now runs before any credits move. It works in English, Dutch, German, French, Spanish, Italian, Portuguese — plus a second-pass check that handles any other language including Russian, Chinese, Arabic, and obfuscated phrasing.

If your prompt is fine, the check is invisible and adds about a second. If something is off, you see a clear card explaining what was flagged and what happens next — never a vague error mid-build.

  • Two layers: fast keyword pass + a smarter intent check that catches euphemisms and unusual phrasings.
  • Zero-tolerance categories (illegal-content involving minors, terrorism support) result in an immediate account hold with a clear path to contact us if it was an error.
  • Lesser categories (malware, phishing, fraud-tool building) get a warning first, then a hold if it happens again.

Chat refresh: mascot, glisten, expandable files

The build chat looks closer to what people expect from a polished AI workspace. The mascot head now sits next to every message instead of a small dot, the line the engine is currently working on glistens with a soft animated gradient so you can see it's alive, and long messages collapse under a single "show / hide" line so the timeline doesn't sprawl.

File edits show up as coloured pills ("Created /app/page.tsx"). Click one and it drops down inline to show the actual code the engine wrote. No more wondering what landed in that file — it's right there.

  • Works on both the V2 build workspace and the demo flow.
  • File pill expand uses the build's actual file map, so the code matches exactly what's in your downloaded repo.
  • Hover any pill to see the full file path even when it's truncated.

Quieter under the hood: 80% less credit burn

The engine validates every page after generation. A small bug in that validator was rejecting many valid Next.js patterns — async components, generic typed components, and any sensible-but-different function name — which triggered an expensive rescue model to re-do the page. On a typical Premium build that could mean 5–10 rescues, each costing 1,500 credits.

After fixing the validator, the same builds now do 0–2 rescues. Premium pool burn per build dropped roughly 80% with no change in output quality. You don't see anything different; you just notice your pool lasts a lot longer.

Account safety: clearer states, easier contact

If an account ever gets held for review, the experience is now clear and respectful. A red panel explains the state. A button pre-fills an email to support with your account details (you only type your message) so you don't have to gather information. Accounts kept in the lighter "under review" state can still log in and browse their projects read-only — only build/edit is paused.

Reserved for the rare cases where it's needed; for everyday users, none of this is visible.