BuilderStudio v0.1.4 is now available.

Download it here: https://builderstudio.dev

This release is focused on making iteration more reliable.

Most AI app tools are optimized around one-shot generation. BuilderStudio is moving in the opposite direction: generate once, then keep improving the same working project without accidentally rebuilding, nesting, or drifting away from the your original intent.

What’s new in v0.1.4:

• Better /iterate behavior for active projects

• Safer in-place editing instead of creating nested project folders

• Smarter handling of /fresh for starting over from the parent workspace

• Improved AI intent planning so BuilderStudio can better distinguish between editing, regenerating, and migrating

• Stronger mutation guardrails to prevent unwanted package/runtime changes

• More reliable dependency-free static app runtime handling

• OpenRouter catalog UI improvements for better readability

• Release build auto-tagging so the app version is reflected more clearly in the UI

Our goal for this release is making AI-generated software feel less disposable.

One-shots are great demos.

Iteration is how real software gets built.

Download BuilderStudio v0.1.4: https://builderstudio.dev

Most LLMs and AI app builders focus on one-shots.

“Prompt once. Get an app.”

We are not big fans of this framing.

It makes for great demos, but it is not how real software gets built.

Real software is shaped through iteration. You try something, inspect it, change direction, fix what broke, polish the details, and keep moving. The first generation is only the starting point.

That is why we are building BuilderStudio around iteration-first development.

The goal is not just to generate a project once.

The goal is to let users keep working from the same active project, improve it in place, preserve context, avoid accidental rebuilds, and move from rough idea to something actually usable.

You will be able to change anything from the full page to fine grained details without touching code or having to reload the entire context window.

One-shots are a marketing gimmick.

Iteration is coming.

More soon.

Hello r/BuilderStudio 👋

Now that we are 7 days into our initial launch we'd like to gather some user feedback from the community 🎤

What worked for you and what didn't?

Any ways we can help improve your experience?

Did you run into any pitfalls or roadblocks along the way?

What features do you wish we had that is currently missing?

We welcome any feedback and look forward to improving your experience. We have many years of engineering experience and would like to help you with any challenges you are facing.

🚀 Latest Release: Full-Stack App Generation, Workflow Handoff, Iteration Mode, and Auto-Repair

Big update this week.

This release makes the builder experience feel much more like a real app-generation workflow from start to finish: design the process, hand it off to the AI builder, iterate module by module, wire backend services, and repair runtime issues with better context.

What’s new

1. /demo now teaches the full build flow

The in-product demo now walks through:

• Full-stack app prompts
• Workflow-to-builder handoff
• /iterate for module-by-module development
• Doctor / auto-heal repair behavior
• Hermes and Aurelius context
• Deployment and settings

First-run onboarding now gives users a clearer path from prompt → workflow → generated app → backend → repair loop.

2. Workflows can now become real app modules

Workflows now include clearer handoff guidance for turning a visual workflow into an actual product module.

That means workflow context can now carry over into app-building prompts with details like:

• UI expectations
• APIs
• persistence
• logs
• approvals
• backend state

The new “Send to AI builder” flow tells the agent to implement the workflow as part of a real product, not just as a standalone diagram.

3. New /iterate mode for follow-up builds

We added /iterate to support module-by-module development.

Follow-up prompts like:

>“Add billing settings”
“Wire approvals into this app”
“Extend the backend state model”

now target the latest generated app folder instead of creating a fresh one-shot project.

There is also a new action-menu toggle for iteration mode.

4. Hermes and Aurelius now receive richer build context

Agent run payloads now include:

• buildMode
• workflowContext
• iterationContext

Hermes prompt files now explicitly guide the agent to inspect existing code, patch the smallest coherent module, preserve unrelated behavior, and validate the increment.

Aurelius receives the same context through the request body.

Workflow context is also passed into /swarm/run when the swarm goal relates to the active workflow handoff.

5. Full-stack backend auto-wire is now smarter

The builder now detects prompts involving:

• full-stack apps
• backend services
• Supabase
• Postgres
• auth
• CRUD flows

When relevant, it adds backend guidance to the generation prompt, auto-scaffolds Supabase/Postgres into the generated app folder, and starts the backend runtime before preview when possible.

The /agent/run payload now supports:

• autoWireFullStackBackend
• backendStartAfterCreate
• backendWorkingDirectory
• originalPrompt

6. Repair-loop prompting is now context-aware

The new repair-loop mechanism gives /runtime/auto-heal better context from compiler, runtime, and preview evidence.

It now returns:

• diagnosticText
• repairPromptAppendix
• nextPrompt
• promptMemoryPath

The frontend appends the repair context back into the chat prompt so the next model pass includes both the original request and the actual fix needed.

It also writes repair memory to:

.builderstudio/runtime-repair-loop.md

Why it matters

This release moves the product closer to a true agentic app-building loop:

Design a workflow → hand it to the builder → generate the app → wire the backend → iterate safely → repair with context.

Less restarting from scratch.

More incremental development.

Better handoff between workflows, agents, backend services, and runtime repair.

More updates soon. 🚢 Download the latest client below:

https://builderstudio.dev

Build games with BuilderStudio 🕹️or build 100 games at once with agents 👾

Will you create the next AAA game?

Spin up an army of agents to handle different pieces of development. One for assets, one for sounds, one for motion dynamics. It is all possible with BuilderStudio.

The world is your oyster.

Get started today:
https://builderstudio.dev

Now live PostgreSQL and Supabase integrations to BuilderStudio!

Download/update to our latest release to access DB integration within your BuilderStudio apps to supercharge websites into powerful and capable SaaS apps.

Update available here:
https://builderstudio.dev

Just remember to not commit and push environment variables!

We hope you enjoy this new feature, please let us know if you run into any issues.

-TW

BuilderStudio is now available on Linux and Windows operating systems.

Private, containerized, and local. We aim to become the Protonmail and Signal of agentic development tools. Privacy-first, BYOK, local LLMs, and containerized.

We look forward to seeing what you build. Let us know if you run into any issues since this is our first experimental release on these platforms.

Download and try our agentic IDE experience
https://builderstudio.dev

Today we’re releasing Isaac, a new agent skill designed to help reduce pressure and burden on the App Store Review team by helping developers build iOS and iPadOS apps that are aligned with App Store Review Guidelines by default.

Isaac gives developers a practical .md skill file they can include in their app-building workflow to better understand Apple’s expectations, avoid common pitfalls, and prepare stronger submissions before review.

Our goal is simple: help developers catch issues earlier, reduce avoidable rejections and re-review cycles, and make the submission process smoother for everyone.

We hope this serves as a helpful resource for teams building great apps for the Apple ecosystem.

You can download and use the skill here: https://github.com/wundercorp/isaac-skill/tree/main

Markdown File: https://github.com/wundercorp/isaac-skill/blob/main/skills/isaac/SKILL.md

As an added bonus, today we are also open sourcing Awesome Prompts:

https://github.com/wundercorp/awesome-prompts

Awesome Prompts is a BuilderStudio-first collection of one-shot prompts you can copy, paste, and bring to life in https://builderstudio.dev.

It starts with a curated set of landing page, SaaS, portfolio, fintech, creative studio, visual effect, and hero-section prompts. New community-submitted prompts are welcome, and each submitted prompt should include a demo link so people can see what it creates.

If you are building agents, skills, MCP servers, or high-quality prompts, PRs are welcome.

Confirmed working with BuilderStudio in one shot using the GPT-5.3 Codex model, provided by u/OpenRouter.

Output: 3,425 tokens
Cost: $0.0546

Thanks for sharing Marc Product! Tag us if you have any other cool prompts to share.

Prompt provided by u/marcproduct you can find the prompt on his X account.
https://x.com/markproduct

We just launched three new WunderCorp community Github directories for the agentic Al ecosystem:

Awesome Agents https://github.com/wundercorp/awesome-agents

Awesome Skills https://github.com/wundercorp/awesome-skills

Awesome MCP https://github.com/wundercorp/awesome-mcp

Our goal is simple: make it easier to discover, submit, and maintain high-quality Al agents, installable skills, and MCP servers in a structured, PR-friendly way.

Awesome Agents starts with Aurelius Agent, our orchestration agent for decomposing complex work, preparing context, coordinating implementation lanes, and guiding focused execution.

Awesome Skills includes WunderCorp's individual skill repositories across accessibility, design, development, documentation, localization, security, deployment, media, and maintenance.

Awesome MCP is ready for community MCP server submissions, with metadata schemas, validation, contribution templates, and generated README listings.

Each repo is built so contributors can add one JSON entry per PR, run validation, regenerate the README, and keep the directory clean over time.

If you are building agents, skills, or MCP servers, PRs are welcome.

We apologize there have been reports of our GHCR repository not being available for agent installs. We have corrected the issue. Aurelius Agent should now be available here:

https://github.com/orgs/wundercorp/packages/container/package/aurelius-agent

Docker pulls should now be operational:

docker pull http://ghcr.io/wundercorp/aurelius-agent:0.3.9

docker run --rm http://ghcr.io/wundercorp/aurelius-agent:0.3.9 describe

docker run --rm http://ghcr.io/wundercorp/aurelius-agent:0.3.9 smoke

Learn more about Aurelius Agent:

https://aureliusagent.dev

If you encounter any issues please let us know.

-TW

Introducing Aurelius Agent by WunderCorp.

This is our first foray into building an autonomous agent for BuilderStudio: a strategic planning layer for our IDE that can reason about work, break it into actionable steps, and coordinate execution inside a developer workflow.

We designed Aurelius to work closely with Hermes by NousResearch.

Where Hermes is the capable coding agent, Aurelius is the planner and orchestrator around it. Aurelius helps define intent, map the work, decide what should happen next, and keep the development loop moving with more structure.

The goal is simple: make agentic software development feel less like prompting a chatbot and more like working with a system that understands the shape of a project.

Aurelius can help with:
- planning implementation paths
- coordinating coding tasks
- preparing project context
- guiding Hermes toward focused execution
- checking work against the broader product direction
- supporting repeatable build, smoke-test, and release flows

This is early, but it is an important step toward the kind of IDE we want BuilderStudio to become: one where autonomous agents are not bolted on as side panels, but designed into the core workflow.

You can test the agent runtime directly via Docker pull on our site.

Try it here:
https://aureliusagent.dev

When we released BuilderStudio we integrated Hermes into our IDE, and it quickly became clear that the agent workflow was powerful.

But there was one architectural gap we kept running into.

Hermes already has /goal, and that pattern works well when you want a focused agent to execute against a specific objective. But for BuilderStudio, we wanted something slightly different: a clean separation between orchestration and execution.

We did not want one agent to be responsible for every layer of the workflow.

We wanted an agent that could understand the broader intent, coordinate work, preserve context, decide when to delegate, and keep the system moving without collapsing everything into a single execution loop.

That is why we built Aurelius Agent.

Aurelius is our orchestration layer BuilderStudio.

Hermes remains the specialist execution agent.

The separation matters because it lets us build toward coordinated multi-agent workflows without blurring responsibilities. Aurelius can reason about the plan, the system state, and the next move. Hermes can focus on contained implementation tasks, code changes, tests, and repair loops.

In practice, that gives us a cleaner IDE-native agent model:

Aurelius coordinates while Hermes executes.
BuilderStudio provides the environment for them to work together.

This makes the whole system easier to reason about, easier to extend, and better suited for the kind of multi-agent product work we want to support.

Aurelius Agent is our answer to a simple question:

What should sit above the coding agent when the work becomes bigger than a single prompt?

For us, the answer is orchestration via Aurelius. We will be releasing the agent later this week on BuilderStudio and as a general agent download via Docker container.

Build full SaaS apps with BuilderStudio capable of handling your company's process and workflows. Additionally, you can build your SaaS with payment integrations to sell to others.

Our tool is a bit like Blender, there is a bit of a learning curve. However, the rewards are great when you get to unleash the full power of this agentic IDE.

One of the key benefits of BuilderStudio is that your app will look unlike anyone else's currently building with AI. If you have any questions or ideas for the app or if you run into any issues we are always listening https://github.com/orgs/wundercorp/discussions/1

-TW

As a fun little exercise we’re giving away a free prompt for this one-click generated site via a like and retweet on X here https://x.com/wundercorp/status/2062591257700897084?s=46

Since members here are already subscribed and BuilderStudio users just shoot us a Reddit DM and we’ll send you the prompt! If you don’t have an X account a simple comment here will suffice. We appreciate your support always.

-TW

We’re live on ProductHunt!

We’d love your support today. Every upvote, comment, and share means a lot to us and helps shape the future of BuilderStudio.

Check it out here:
https://www.producthunt.com/products/builderstudio?launch=builderstudio

We’ve been working hard to bring this vision to life, and your support would mean the world to us. Please take a look, leave feedback, and support the launch if you like what we’re building.

Awesome to see! Go check out the other awesome devtools they have to offer including BuilderStudio.

https://github.com/jamesmurdza/awesome-ai-devtools