How the pieces of PlayWeld fit together
See how the desktop workspace, local service, game files, connected tools, and website work together.
On this page
PlayWeld has a few parts that work together. The desktop Control Room is where you work; a local service keeps project activity; your game stays in its native files; and this website has guides, downloads, and community tools.
Know which component owns the state
| Part of PlayWeld | What it does |
|---|---|
| Control Room | The desktop workspace where you open your game and reach project tools |
| Local service | Keeps track of your projects, settings, conversations, tasks, and changes |
| Your game project | Holds design notes, source assets, and the files your engine uses |
| Game and art tools | Open and work with their own project files, editors, processes, and outputs |
| Community tools | Add features or guidance to PlayWeld under the permissions each package requests |
| PlayWeld.com | Offers guides, downloads, community packages, and ways to contribute |
Your game stays in its engine's project files. PlayWeld keeps notes and activity that help you understand and continue the work. If a tool or connection has a problem, check its own status rather than assuming the whole project is unavailable.
Follow an inspectable change
Choose a project and give an AI task a clear goal. PlayWeld tracks its questions, tool use, and file changes, then leaves the result for you to review.
A finished task is not the same as a tested game. Open the result in your engine and try it to see whether it behaves as you expected.
Know where your information goes
Your project files and PlayWeld records stay on your computer. A model or asset provider you connect may be a separate online service and may receive information needed for a request. Check the provider and the context you are sharing before you send work.
PlayWeld is open source. If you want to change the system itself or understand its internals, start with the source code and technical guides on GitHub.