Wundur

Native macOS app · open source

Make games with AI, honestly.

Wundur is a place to make games with AI. It won't turn you into a AAA studio, and it isn't trying to replace anyone who makes games for a living. It helps you, and your kids, build the world you've been imagining: simple, fun, and yours.

See how it works Download for Mac

The models make the pieces. The art is the world you put together.

Wundur assembling a gameAn isometric voxel scene. The little cube cursor from the Wundur icon stands on a periwinkle platform, beside a billboard with the app icon, while a golden crane lifts blocks labelled Code, Art, Audio, Models and Playtest into a row, one by one, until the game is complete. Two status tags read: Boss sprite, working; Jump sound, needs you.CodeArtAudioModelsPlaytestBoss sprite · workingJump sound · needs you
A game, one block at a time.

What Wundur looks like

The Wundur window. On the left, three sessions in demo-app on the main branch, each with a short preview. Next to them, the project's file tree and the Agent panel. In the middle, the chat: two finished subagent cards, one that read greet.py and one that read README.md, the agent's summary, a Read card, and an Edit card with a red and green diff that switches greet.py to argparse for a new --shout option. On the right, a terminal running python3 greet.py Ada --shout, which prints HELLO, ADA!
  1. 1Sessions Each one keeps its own folder, branch, conversation and layout.
  2. 2Project Files, skills and earlier sessions for the folder you are in.
  3. 3Agent Tool calls as cards, subagents as they run, real diffs.

From a sketch to a character

A guided path for each piece of your game.

Describe a character, or any other piece of your game, in the chat, and Wundur takes it through four steps. Nothing moves on until you've said yes to the step before.

  1. 1

    Concept

    Quick, low-resolution tries from your description. Pick one, ask for a change in your own words, or try again.

  2. 2

    Three views

    Front, side and back of the concept you chose, with a character standing in an A-pose. Redo any one of them on its own.

  3. 3

    Model

    A 3D model built from the approved views. Turn it around in a viewer beside the chat before you approve it.

  4. 4

    Rig

    Bones and simple animations, so a character can walk and run. This step joins the path next. Until then the agent can rig a model with the same service from the chat.

Every try is saved in your project, in a folder for that asset, with a record of what was asked, what it was made from and what you approved. The files are ordinary PNG, GLB and FBX, so they go into whatever engine you use: Godot, Unity, Unreal or a web game. Wundur isn't tied to an engine and doesn't try to be one.

The pictures and models come from AI services you connect with your own keys: OpenAI or Azure for images, Tripo for 3D models and rigging, and ElevenLabs for sound, voices and music.

Plain about AI

AI is good at pieces. The game is still yours to make.

AI can make a decent character, a sound effect or a rough 3D model now. It can't make a great game by itself, and it's nowhere near replacing the artists, designers and programmers who make games for a living. Wundur doesn't pretend otherwise, and it doesn't hide that the pieces are AI-made.

What it's good for is simple, fun games: the one your kid keeps describing at dinner, or the idea you never had time to draw. You decide what the world is, what goes in it and what stays out. The AI fills in pieces, and Wundur keeps a record of where every piece came from.

If your kids use it on their own, parent mode keeps the agent a tool rather than a friend, and alerts you when something needs a parent without ever showing you what they wrote.

The full story · What changed lately

Also a better home for your agent

A native window for Claude Code and Cursor.

You don't have to be making a game. Wundur works as a replacement for running an agent in a terminal, with the conversation, the changes and your project in one window.

Chat or Terminal, one conversation

Chat shows the session as it happens, with Markdown rendered, tool calls folded into cards, real diffs, clickable file references and subagents as they run. Terminal is the agent's own interface, for slash commands and anything else Chat doesn't cover. Switch between turns and the conversation picks up where it was.

Choose a view
Chat view: the request "Reply with just the word ok." and the answer, ok, in the chat style, with the model name above. Terminal view of the same session: Claude Code's own screen, with its banner, the same request and answer, and a line reading Baked for 1s. The working folder path is blurred.

Nothing waits unnoticed

When the agent wants to run a command, the chat shows the exact command with Allow and Deny. Questions come with their answers as buttons. The session's dot turns yellow in the list, and the Dock icon bounces once if you're looking at something else.

A permission prompt in the chat titled Allow Bash?, with the exact command, curl -sI https://example.com, the description Fetch HTTP headers from example.com, and Allow and Deny buttons. The Bash call waits above it with a spinner.

Start a session, or pick one back up

The New session screen starts from a folder. Pick one, name the session if you like, choose the agent, and tick a box to work in a new git worktree. The folder's previous sessions are listed underneath: resume one, switch to one that's already open, or fork it into a new session. Each session keeps its own folder, conversation, terminals and layout.

The New session screen. On the left, a folder sidebar with a filter, recent folders, Choose folder and the chosen folder's subfolders. On the right, the chosen folder, demo-app, with its git branch; an optional session name, the agent picker set to Claude Code, a Create in a new Git worktree checkbox and a Create session button. Below, the folder's previous sessions with a search box, each with Fork and Switch to it.

Know which skills the agent can load

One panel lists every skill the agent can load, from the project, your home folder and installed plugins. Open one to read it beside your work, or edit it in place.

The Skills panel listing the project's release-notes skill and the user's own skills, the conversation in the middle, and the release-notes skill file open on the right, rendered with its name, description and four steps.

Fix things without leaving

A file tree, an editor with syntax highlighting and go to definition, and real terminals share the window with the session. When something looks off, open the file and fix it. Panels dock and split by drag and drop.

The editor showing a TypeScript file, theme.ts, with syntax highlighting and line numbers: a type, a constant, and two functions that save and apply the theme.

Set it up your way

Settings is a page in the window, with a search box. Choose light or dark, a tab style, and any Google Font for the app, the chat and the terminals. MCP servers and your own command-line tools are set up once and every agent gets them. Terminals, notifications and turn summaries each have a page too.

Settings as a page in the window, open on General: Appearance, Tab style and Pressed-in look under Look; App font, Chat font and Terminal font under Fonts; and options for sessions. The sidebar has a search box and the pages General, Chat, MCP servers, Tools, Terminals, Notifications and Summaries.

Where it stands

Early, and used every day.

Works today

  • Claude Code and Cursor Agent
  • The asset path: concept, three views, 3D model
  • Images, sound, voices, music and rigging, with your own keys
  • Sessions as workspaces with live status
  • Chat and Terminal views of one conversation
  • Permission prompts, questions, diffs, subagents
  • Parent mode
  • Sessions on another machine over SSH

Rough edges

  • Mac only to download; Windows runs but isn't released
  • Rigging isn't in the guided path yet
  • The AI services need your own keys
  • Version 0.3, so expect changes

Next

  • Rigging in the guided path
  • Sign in with Wundur, a hosted service
  • More coding agents
  • A Windows release

Open source · Apache 2.0

Free, open source, and yours to change.

Wundur is written in Rust on gpui, the framework behind the Zed editor. There is no browser engine inside, so it opens quickly and stays small.

It started as one person's tool for making games. If it helps with yours, issues, ideas and pull requests are welcome.

github.com/wundur-dev/wundur