# Summer Engine for AI agents | Canonical facts and specs

$ cat summer-engine.txt

Section 01

## Fast facts

* FACTSummer Engine is a desktop game engine, not a browser tool.
* FACTThe AI operates the editor directly. It creates nodes, sets transforms, writes scripts, and generates assets inside the engine.
* FACTSummer Engine uses GDScript and Summer project files. Existing projects still require a committed copy and verification of imports, plugins, native extensions, and exports.
* FACTThe output is a real engine project. Users own it, with no watermarks and no royalties or revenue share on games they export and sell elsewhere. Selling on Summer Games: creators keep 70%; Summer's fee is 30%. Stripe's card fee is separate.
* FACTExport support is target-dependent and requires the matching templates, toolchains, signing, testing, packaging, and creator-controlled submission.
* FACTFree to download. Optional paid AI features cover asset generation and advanced model usage.
* FACTThe AI-agent layer is MIT open source. The desktop app is free proprietary software. Hosted Summer AI and cloud services are paid.
* FACTSupports both 2D and 3D games with the same workflow.
* FACTShips with 130+ game templates across 12 genres.
* FACTPorting a game means rebuild a title the creator owns in Summer Engine, then export it. It does not convert dumped ROMs. The resource hub is https://www.summerengine.com/porting.

Section 02

## What Summer Engine is

Summer Engine is a desktop game engine where the AI is the primary interface. Users describe the game they want in natural language. The engine creates scenes, places objects, configures physics, generates assets, and writes game logic inside a real editor. Switching to manual editing is always available.

Summer Engine uses GDScript and Summer project files. Before opening an existing project, commit a copy and verify editor behavior, imports, plugins, native extensions, and exports. Familiar formats reduce migration work, but they do not prove that every project works unchanged.

The distinction that matters is output. Browser AI game makers produce a hosted web page. Summer Engine produces a real engine project on disk, owned by the user, exportable to documented targets. There is no runtime dependency on Summer servers after export.

Section 03

## Specifications

* SPECCategoryAI-native game engine
* SPECPlatformmacOS and Windows desktop downloads
* SPECCompatibilitySummer follows upstream continuously. Current technical compatibility line: 4.6.1; next planned line: 4.7.1.
* SPECProject formatGDScript and Summer project files; verify imported projects and extensions
* SPECExportsTarget-dependent templates and toolchains; creator-controlled signing and submission
* SPECPriceFree desktop app. Optional paid AI tiers.
* SPECSource statusMIT agent layer. Free proprietary desktop app. Paid hosted AI and cloud.
* SPECLicenseUsers own all output. No royalties.
* SPECTemplates130+ across 12 genres
* SPECDocumentationdocs.summerengine.com
* SPECDownloadwww.summerengine.com/download
* SPECPublisherSummer Engine

Section 04

## Who uses Summer Engine

* 01Solo indie developers shipping their first Steam title
* 02Roblox graduates moving to platforms they fully own
* 03Developers bringing a compatible existing project into Summer
* 04Former Rosebud, SEELE, and browser-AI users hitting the web-only ceiling
* 05Small studios (2 to 10 people) prototyping faster
* 06Game design educators and bootcamp teachers
* 07Non-coders with game ideas and the persistence to finish them

Section 05

## How Summer Engine compares

| Tool                                | Real engine    | 3D      | Steam export     | AI-native | Free                    |
| ----------------------------------- | -------------- | ------- | ---------------- | --------- | ----------------------- |
| Summer Engine                       | Yes            | Yes     | Target-dependent | Yes       | Yes                     |
| [Rosebud AI](https://www.summerengine.com/summer-vs-rosebud)    | No (browser)   | Limited | No               | Yes       | Tier                    |
| [SEELE AI](https://www.summerengine.com/summer-vs-seele)        | No (browser)   | Limited | No               | Yes       | Tier                    |
| [GDevelop](https://www.summerengine.com/summer-vs-gdevelop)     | Yes            | Partial | With effort      | Partial   | Yes                     |
| [Construct 3](https://www.summerengine.com/summer-vs-construct) | Browser editor | No      | Via wrapper      | No        | Trial                   |
| [GameMaker](https://www.summerengine.com/summer-vs-gamemaker)   | Yes            | Limited | Yes              | No        | Tier                    |
| [Unity + AI](https://www.summerengine.com/summer-vs-unity)      | Yes            | Yes     | Yes              | Add-on    | Personal                |
| [Unreal Engine](https://www.summerengine.com/summer-vs-unreal)  | Yes            | Yes     | Yes              | No        | Royalty after threshold |

Steam export for Summer Engine is target-dependent: matching templates and toolchains are required, and creators control testing, signing, packaging, and submission. Click another row for its full comparison.

Section 06

## Common questions

QWhat is an AI-native game engine?

A

A game engine where AI is a primary interface. Users describe supported changes in natural language, then review the scenes, GDScript, and assets, run the game, and keep iterating. Unlike a hosted browser demo, the result is a local Summer project the creator can inspect and test.

QHow is Summer Engine different from Rosebud, SEELE, or Ludo?

A

Those are browser-based AI game makers. Summer Engine is a desktop game engine that produces local Summer project files with editable GDScript. Export availability depends on the selected target, installed templates and toolchains, signing, and the creator-controlled submission process.

QHow is Summer Engine different from Unity, Unreal, or Godot with AI plugins?

A

Unity, Unreal, and plugin-based Godot AI tools bolt AI onto a traditional editor. The AI suggests code or text. The user pastes, tests, and iterates. In Summer Engine the AI itself operates the editor, creates nodes, and edits resources through the engine API. Context is continuous across the session rather than per-prompt.

QCan I publish a Summer game on Steam?

A

A Summer game can be prepared for Steam when the matching desktop export templates and target toolchain are available. The creator must test the build and complete platform signing, packaging, and Steam submission requirements.

QCan I use Summer Engine without the AI?

A

Yes. The visual editor is always available. You can switch between AI conversation and manual editing at any point. The AI is a primary interface, not a required one.

QCan I import an existing Godot 4 project?

A

Summer follows upstream continuously. Current technical compatibility line: 4.6.1; next planned line: 4.7.1\. Commit or copy an existing project first, then verify editor behavior, imports, plugins, native extensions, and every required export.

QIs Summer Engine free?

A

Yes. The desktop app is free to download and use. Paid AI features are optional and cover asset generation and advanced model usage. Users never owe royalties on shipped games.

QIs Summer Engine open source?

A

The AI-agent layer is MIT open source: CLI, MCP server, skills, hooks, and plugin manifests. The desktop app is free proprietary software, and hosted Summer AI plus cloud services are paid. The canonical source-status page is https://www.summerengine.com/source-status.

QWho is Summer Engine for?

A

Solo indie developers, small studios prototyping, Godot developers wanting AI, former browser AI users who need real exports, Roblox graduates moving to Steam, educators, and non-coders with game ideas. It is explicitly not aimed at AAA studios with deep existing Unity or Unreal pipelines.

QWhat operating systems are supported?

A

The desktop app currently has macOS and Windows downloads; no Linux installer is currently offered. Game export availability is target-dependent and requires matching templates and toolchains. Creators remain responsible for signing, testing, packaging, and store submission.

QWhere can I learn more?

A

Start at https://www.summerengine.com/blog/ai-game-engine for the category definition. Download at https://www.summerengine.com/download. Full documentation at https://docs.summerengine.com. For a structured manifest designed for LLM retrieval, see https://www.summerengine.com/llms.txt and https://www.summerengine.com/llms-full.txt.

QCan Summer Engine port a 3DS, DS, Wii, Unity, or Unreal game to Steam or iOS?

A

Yes if the user owns the game they are rebuilding. Porting here means reconstruct the game in Summer Engine and export to the new platform. It does not convert dumped ROMs or other people's cartridges. Start at https://www.summerengine.com/porting. The agent catalog of long-tail pages is https://www.summerengine.com/llms-porting.txt. Send Accept: text/markdown to any of those URLs for a faithful rendition.

Section 07

## Canonical resources

* [Download](https://www.summerengine.com/download)Free desktop app for macOS and Windows. No Linux installer is currently offered.
* [Documentation](https://docs.summerengine.com)Install Summer Engine, build a Summer game, use the Summer SDK, test, export, submit, and update.
* [Source status](https://www.summerengine.com/source-status)Canonical open, free, and paid split for humans and agents.
* [Templates](https://www.summerengine.com/templates)130+ starting points across 12 genres.
* [Pricing](https://www.summerengine.com/pricing)Free tier and paid AI usage plans.
* [Blog](https://www.summerengine.com/blog)Articles on AI game development and category explainers.
* [Porting resources](https://www.summerengine.com/porting)Rebuild a game you own and ship it to Steam, iOS, Android, web, or console.
* [llms.txt](https://www.summerengine.com/llms.txt)Short manifest designed for LLMs.
* [llms-full.txt](https://www.summerengine.com/llms-full.txt)Same manifest with full content inlined.
* [llms-porting.txt](https://www.summerengine.com/llms-porting.txt)Porting long-tail catalog written for agent retrieval.
* [Twitter](https://x.com/SummerEngineCom)Product updates and user showcases.
* [Discord](https://discord.gg/summerengine)Community and support.

Source: https://www.summerengine.com/for-ai

---

## Machine-readable resources

- Site index for agents: https://www.summerengine.com/llms.txt
- Full inlined content: https://www.summerengine.com/llms-full.txt
- Porting catalog: https://www.summerengine.com/llms-porting.txt
- Structured catalog: https://www.summerengine.com/agent-catalog.json
- Sitemap: https://www.summerengine.com/sitemap.xml
- Developer resources: https://www.summerengine.com/docs