The WizardGenie AI Agent

WizardGenie is the AI agent built into Sorceress for creating, testing, and improving game projects. It works like a project-aware coding partner: you describe what you want in plain language, and WizardGenie can inspect your project, make changes, test the result in the built-in preview, browse documentation, and help connect art and audio assets.

Open WizardGenie

What it does

WizardGenie is designed for iterative game development. You can ask it to build a new game, fix an existing bug, add a feature, improve visuals, explain how a project works, generate assets, or test gameplay in the preview.

Unlike a normal chatbot, WizardGenie can take visible project actions:

• Read and search your project files.
• Create new files and make targeted edits to existing files.
• List folders and understand the project structure.
• Build a high-level map of the codebase.
• Search code by meaning, not only by exact text.
• Remember important decisions, conventions, and discoveries across work sessions.
• Create rollback checkpoints before larger changes.
• Run one-time terminal commands for setup, builds, checks, and maintenance.
• Open the live project preview and interact with it using mouse, keyboard, scrolling, waiting, and screenshots.
• Browse websites and documentation in an agent-controlled browser.
• Generate or connect game assets through configured Sorceress and Pixel Lab tools.
• Add generated 3D models to the open scene when the project and editor state support it.

A typical session is conversational: ask for a change, let WizardGenie inspect and edit, review the preview, then ask for refinements.

Typical workflow

1. Open WizardGenie.
2. Open or create a Sorceress project.
3. Select or configure an AI model if prompted.
4. Type a request in natural language.
5. Let WizardGenie inspect files, edit code, run checks, and test the project as needed.
6. Review the changed files and live preview.
7. Ask for fixes, polish, or the next feature.

Good starter prompts include:

• “Create a small top-down dungeon crawler with keyboard movement, enemies, coins, and a win screen.”
• “Explain how this project is structured before changing anything.”
• “Find why the player can walk through walls and fix it.”
• “Add mobile touch controls.”
• “Make the main menu more polished and add a settings screen.”
• “Generate a laser sound effect and connect it to the shooting action.”
• “Open the preview, test the jump controls, and fix anything broken.”
• “Create a checkpoint, then refactor the combat system.”

Project-aware editing

WizardGenie can work directly with normal project files inside the open project. File access is sandboxed to the project, so it is intended to operate within the project folder rather than elsewhere on your computer.

For existing code, WizardGenie is guided to make small, targeted edits instead of rewriting whole files unnecessarily. This helps preserve your work and reduces the chance of accidental regressions. When it creates or modifies JavaScript files, it performs basic validation and can immediately correct common syntax or code issues it introduces.

Scene layout files managed by the visual Scene Editor are protected by default. If WizardGenie says a scene file is locked, ask it to put gameplay logic in scripts instead. If you intentionally want the agent to edit a protected scene layout, unlock that scene file from the Explorer context menu first.

Code understanding and search

WizardGenie has several ways to understand your project:

Codebase map

WizardGenie can generate a compact overview of the project: file tree, broad file statistics, likely frameworks or engines, and key files. This helps it get oriented before making large changes.

Ask:

• “Map this codebase before editing.”
• “Refresh your understanding of the project structure.”
• “Which files are most important for gameplay?”

Semantic code search

WizardGenie can search supported text and code files by meaning. This is useful for questions like:

• “Where is player movement handled?”
• “Find the inventory UI logic.”
• “What controls enemy spawning?”
• “Where is audio loaded?”

The search covers common web, scripting, game, and systems languages, including JavaScript, TypeScript, Python, CSS, HTML, JSON, Rust, Go, Java, C/C++, Ruby, PHP, Lua, Swift, Kotlin, C#, Scala, Dart, and shell scripts.

To keep search fast and relevant, WizardGenie skips common dependency folders, build output, caches, hidden folders, binary assets, media files, archives, fonts, documents, environment files, lock files, minified files, and very large files. Extremely large projects may be capped during indexing.

If WizardGenie misses something, ask it to search by exact text, file name, or a known symbol, or ask it to refresh its project map.

Working knowledge during a session

During a conversation, WizardGenie remembers files it has already read or changed. If the same file has not changed, it may use a compact structure summary instead of rereading the entire file. When exact code is needed, it can still read specific line ranges.

This makes long sessions more efficient while keeping edits targeted.

Long-term project memory

WizardGenie can store and recall important project knowledge, such as:

• Design decisions.
• Debugging discoveries.
• Repeated errors and fixes.
• Project conventions.
• User preferences.

This memory helps it avoid repeating old investigations and maintain consistency across sessions. You can ask it directly:

• “Remember that enemies should never spawn within two tiles of the player.”
• “What did we decide about the save system?”
• “Recall any previous notes about the rendering bug.”

Live preview testing

WizardGenie can test your game in the built-in Sorceress preview. It can open the current project preview, interact with it, and inspect screenshots.

It can perform actions such as:

• Click at coordinates or on visible interface elements.
• Move the mouse.
• Press keys and key combinations.
• Hold keys down and release them.
• Scroll.
• Wait for animations, loading, or timed events.
• Capture a visual result after interaction.

Ask for preview testing when you want confidence that a change actually works:

• “Open the preview and test the start menu.”
• “Play for 20 seconds and see whether enemies spawn.”
• “Take a screenshot after collecting a coin.”
• “Test keyboard movement and fix any errors you see.”

You normally do not need to ask WizardGenie to start a separate development server. Sorceress provides the built-in preview, and WizardGenie is instructed to use that for normal testing.

Browser and documentation research

WizardGenie includes an agent-controlled browser for web research and interactive pages. It can:

• Navigate to a URL.
• Treat a search phrase as a web search.
• Read page text.
• Capture a page structure and screenshot.
• Click elements.
• Type into form fields.
• Clear fields and submit forms.
• Scroll up or down.
• Go back.
• Press browser keys such as Enter, Escape, Tab, or shortcuts.

Browser sessions can preserve normal browser state such as cookies and logins. Only authorize logins or account actions you are comfortable with the agent using.

Use this when you want WizardGenie to read documentation or compare behavior against a web reference:

• “Look up the current docs for this library and implement the recommended setup.”
• “Open the documentation page and summarize the input API.”
• “Search for examples of this error and suggest a fix.”

For simple documentation pages, WizardGenie can also fetch readable page text directly without opening the interactive browser.

Terminal commands

WizardGenie can run one-time terminal commands in the project folder for tasks such as:

• Installing dependencies.
• Running setup scripts.
• Running builds, tests, or checks.
• Performing project maintenance.
• Running version-control commands when appropriate.

For safety, it blocks obviously dangerous commands and common long-running development or preview server commands. Long-running interactive processes are not a good fit for the agent because commands have a time limit and can stall the work session.

Use prompts like:

• “Install the missing dependency, then run the build check.”
• “Run the test command and fix failures.”
• “Check whether the project builds.”

Avoid asking it to start a local dev server unless you have a specific reason. For game testing, ask it to use the built-in preview.

Checkpoints and rollback

WizardGenie can create project checkpoints before significant changes. A checkpoint captures the current project state so you have a safer point to return to if an experiment goes wrong.

Good checkpoint prompts:

• “Create a checkpoint before changing movement.”
• “Checkpoint the current working version.”
• “Make a rollback point, then try a new enemy AI system.”

Use checkpoints before broad refactors, replacing systems, or asking for large multi-file changes.

Asset generation and project integration

When the relevant Sorceress or Pixel Lab integrations are configured, WizardGenie can generate assets and save them into your project. After generating assets, it is instructed to connect them to the game where appropriate, such as loading images or audio in the relevant game code.

Available asset workflows shown in the current toolset include:

Images

WizardGenie can list available image-generation options for your configured Sorceress access, including supported model options, aspect ratios, quality or resolution choices, and reference-image support. It can then generate images and save them into the project.

Use images for:

• Sprites.
• Backgrounds.
• UI panels.
• Icons.
• Portraits.
• Concept art.
• Texture references.

Helpful prompts:

• “List the available image models and help me choose one for pixel-art UI icons.”
• “Generate a 16:9 fantasy forest background and wire it into the title screen.”
• “Create three item icons for potion, key, and coin.”

Sound effects

WizardGenie can generate sound effects from a text prompt and save them into the project. It can request loopable audio when you need ambience or repeating environmental sound.

Helpful prompts:

• “Generate an 8-bit coin pickup sound and play it when the player collects a coin.”
• “Create a loopable rain ambience track and add it to the forest level.”
• “Make a short laser firing sound for the player weapon.”

Speech

WizardGenie can list available preset and account voices, generate spoken audio from text, and save the result into the project. Speech options include speed, pitch, and an optional emotion.

Supported emotion choices are:

• none
• happy
• calm
• sad
• angry
• fearful
• disgusted
• surprised

Helpful prompts:

• “List voices, choose a narrator voice, and generate the intro line.”
• “Generate a happy shopkeeper greeting and trigger it when the shop opens.”
• “Make this line slower and calmer.”

Music

WizardGenie can generate music from a description, or in an advanced workflow from lyrics plus style and title options. It can request instrumental tracks and save returned variations into the project.

Helpful prompts:

• “Generate an instrumental battle loop for a retro dungeon crawler.”
• “Create calm menu music and connect it to the main menu.”
• “Generate two variations of a cheerful victory song.”

Pixel-art workflows

Pixel Lab tools are available when configured for pixel-art asset generation and editing workflows. WizardGenie can use them when your prompt calls for pixel-art style assets or animation-oriented asset work.

Model selection

WizardGenie supports multiple model backends, including cloud models, compatible gateway models, self-hosted endpoints, and local models. The exact model list depends on your configuration and what the selected provider reports as available.

Some models handle tool use, long projects, image attachments, reasoning, or local inference better than others. In practice:

• Use a strong tool-capable coding model for large edits or full game creation.
• Use a vision-capable model when you want WizardGenie to inspect screenshots or image attachments.
• Use local or self-hosted models when you want local inference, understanding that tool reliability varies by model.
• If a model repeatedly plans but does not edit, emits strange tool-like text, or fails to apply changes, switch to a stronger tool-capable model.

The model picker may dynamically discover available models from configured services. Some entries may be text-only; if you attach images to a text-only model, WizardGenie may not be able to use those images.

Tips for best results

• Be specific about gameplay, controls, camera, art style, and target platform.
• Ask for a checkpoint before major changes.
• Ask WizardGenie to test in the preview after implementing a feature.
• For bugs, describe expected behavior and actual behavior.
• For visual issues, ask it to open the preview and take a screenshot.
• For hard-to-find code, ask it to search by meaning first, then inspect exact lines.
• For asset generation, ask it to list available options before choosing a model, voice, or style.
• Build larger games iteratively: core loop first, then enemies, UI, audio, polish, and menus.
• If the agent gets stuck, ask it to reread the current file and make a smaller targeted edit.

Troubleshooting

WizardGenie says no project is open

Open or create a Sorceress project first, then retry your request. Most project-editing actions require an active project folder.

A scene file is locked

Scene layout files are protected because they are managed by the visual Scene Editor. Ask WizardGenie to put gameplay logic in script files instead. If you intentionally want the agent to edit the scene layout, unlock the scene file from the Explorer context menu.

WizardGenie cannot find text to edit

The file may have changed since WizardGenie last read it, or the edit target did not match the file exactly. Ask it to reread the relevant lines and retry with a smaller edit.

A command was blocked

WizardGenie blocks dangerous commands and common long-running preview/server commands. Use the built-in preview for game testing. If you truly need a server command, explain why and keep the command one-shot where possible.

The model stops after planning

Ask it to proceed with implementation in the same task. If it repeatedly plans without editing, switch to a stronger tool-capable coding model.

Local model output is unreliable

Local and self-hosted models vary widely in tool-use quality. If a model emits raw tool instructions, stalls, rambles, or fails to edit files, try a different local model or switch to a hosted tool-capable coding model.

Semantic search misses a file

Use exact search with a known file name, symbol, or phrase. You can also ask WizardGenie to refresh its codebase map or search the project directly.

Preview testing does not reflect a change

Ask WizardGenie to reload or reopen the preview, then take a screenshot. If the game has multiple entry points, tell it which page or file should be previewed.

Asset generation is unavailable

Asset tools depend on your configured Sorceress or Pixel Lab access. Ask WizardGenie to list available asset tools. If none are available, configure the relevant integration first.

FAQ

Can WizardGenie build an entire game from scratch?

Yes. It can create project files, add gameplay code, generate or connect assets when configured, and test the result in the preview. Larger games work best when built in stages.

Can it edit any file in my project?

It can create and modify normal project files inside the project sandbox. Scene layout files managed by the visual editor are protected by default unless you unlock them.

Can it use the internet?

Yes. WizardGenie can read web pages and use an agent browser to navigate, search, click, type, scroll, and extract page text.

Can it see the game while testing?

Yes. It can open the project preview, interact with the game, and inspect screenshots.

Does it remember previous sessions?

Yes. WizardGenie can store and recall long-term project memories such as decisions, discoveries, conventions, and preferences. It also keeps working knowledge during a session.

Can it generate art and audio?

Yes, when the relevant integrations are configured. Current workflows include image generation, sound effects, speech, music, and Pixel Lab asset workflows.

Should I ask it to run a dev server?

Usually no. Sorceress already provides the built-in preview. Ask WizardGenie to use the preview unless you have a specific reason for a separate server process.

Can it run tests or builds?

Yes. It can run one-time project commands for tests, builds, installs, and checks, subject to safety restrictions and command time limits.