Zugo Updates: What's New in July 2026

The July 2026 Zugo updates ship three interface themes, a community showcase, one-click publishing with custom domains on paid plans, Vercel and Stripe connectors, the built-in Zugo Cloud database, workspace skills, full GitHub repository export, and deep builds for complex multi-page projects. Everything is live for every account on zugo.dev, and free starter credits require no card.

Below, each item follows the same pattern: what shipped, why we built it, and how to try it right now.

What are the three interface themes?

What shipped: a theme switcher in workspace settings. There are now three themes: dark Phosphor (the default), Midnight Coral, and light Porcelain.

Why. People spend long stretches in the builder — writing prompts, reading the live log, refining results. A single dark theme didn't suit everyone: some work in daylight next to a window, others want warmer contrast. Phosphor stays the strict working theme, Midnight Coral adds coral accents on a dark background, and Porcelain is a calm light option for daytime work.

How to try it: open workspace settings and pick a theme. The choice is saved to your account and applies across all projects.

What is the community showcase?

What shipped: a public gallery at /showcase. These are projects users built in Zugo and chose to share: games, landing pages, small apps.

Why. The most common question from new users is "what can I actually build with this?" The answer is no longer abstract. Every entry in the showcase opens as a live build, not a screenshot. It also works as an idea bank: see a mechanic or page structure you like, then describe something similar in your own prompt. If it's a game that caught your eye, we have a step-by-step walkthrough on how to make a game with AI.

How to try it: browse the showcase and open any project. To get your own work in, publish your project and mark it for the gallery.

How does publishing work now: custom domains, zugo.run, isolated hosting

What shipped: one-click publishing to a <slug>.zugo.run address, plus custom domain support on paid plans. Under the hood, every published project now runs on isolated hosting.

Why. A link like my-game.zugo.run appears right after the build finishes, and it's presentable enough to send to friends or a client. A custom domain matters once a project stops being an experiment: a portfolio, a product, a promo page. Isolation solves a less visible but real problem: neighboring projects can't affect each other. Your published game doesn't share an environment with someone else's app — each publish gets its own separate boundary.

How to try it: build a project and hit Publish. The slug is editable. Custom domains are available on Pro, with instructions right in the publish settings.

What do the Vercel and Stripe connectors do?

What shipped: two new connectors. Vercel deploys a finished project to your own Vercel account; Stripe adds payment processing to the apps you build.

Why. Zugo already had connectors for Supabase (database and auth), Google Analytics, and Resend (email). Vercel covers the "I want to host this myself, with my own CI and settings" scenario — no manual file transfer. Stripe covers the reason many people build an app in the first place: taking payment. Describe what you're selling in the prompt, connect your Stripe keys, and the generated app takes payments into your account.

How to try it: the connectors section in project settings. Each connector uses your own keys — Zugo doesn't sit in the middle of your payments or your deploys.

What is Zugo Cloud?

What shipped: Zugo Cloud, a built-in database for apps generated in Zugo.

Why. Previously, any app that stored data — entries, a leaderboard, a task list — needed an external service: create a Supabase project, grab keys, wire it up. That's still the right path for production, and the Supabase connector isn't going anywhere. But for a quick start it was an extra step. With Zugo Cloud, an app gets working storage immediately: ask for "a task list that saves my tasks," and saving actually works from the first publish.

How to try it: simply describe an app that needs data. If the project outgrows it, moving to your own Supabase stays available through the connector.

What are workspace skills?

What shipped: named instructions for the agent, saved at the workspace level and applied to builds automatically.

Why. If you build a lot of projects, you probably repeat the same requirements in every prompt: brand colors, tone of voice, a preferred page structure. A skill is written once — say, "Brand style" with your palette and rules — and the agent respects it in every build without reminders. It pairs with Plan mode: you first see how the agent understood the task with your skills applied, then start the build.

How to try it: the skills section in workspace settings. Name the skill, describe the rules in plain text, save.

GitHub export: a real repository

What shipped: GitHub export now creates a full repository with proper project structure — src/, package.json, vite.config — instead of one merged page.

Why. Export matters when a project outgrows the builder or a developer joins it. Handing over code used to mean handing over a monolithic file that's awkward to work with. Now you clone the repository, install dependencies, run the dev server, and the project builds like a normal Vite app. No lock-in: the code is yours, the repository is yours. The full export flow is covered in how to export an AI app to GitHub, and if you're still exploring the path from prompt to working app, start with how to build an app with AI.

How to try it: the export button in your project, authorize GitHub, and the repository appears in your account.

What are deep builds, the live log, and checkpoints?

What shipped: a deep build mode for complex multi-page projects (a few minutes instead of the usual minute), a timer with a live process log, and checkpoints along the way.

Why. A regular Zugo build takes about a minute, which is enough for a game or a landing page. But a multi-page site with shared navigation, or an app with several screens, honestly needs more time — and we chose to give the agent those minutes rather than ship a cut-down result. So the wait isn't a black box, the live log shows which file the agent is writing at that moment. Checkpoints record intermediate states, so a long build doesn't burn down entirely because of one failed step. And the core rule hasn't changed: "verified" means the build actually loaded and rendered in a sandbox — not that the agent claimed success.

How to try it: describe a multi-page project and Zugo will offer a deep build. The log and checkpoints are visible in the process panel.

The whole update in one table

How can I try everything at once?

Starter credits are free and no card is required: sign up and build your first project. 25 templates across 5 categories help you start, and Plan mode shows how the agent understood your task before build credits are spent.

If you hit the limits, Pro is $25/month: 200 credits (roughly 16 full platforms or 33 quick builds) plus custom domains. For teams and agencies there's Business at $99/month. Details on the pricing page.

Questions and findings about the new features are welcome in the showcase and through support — the most useful feedback this cycle came from users.