Understand the PlayWeld IDE system
See how the desktop Control Room, local service, project files, connectors, and website fit together.
On this page
PlayWeld combines a desktop frontend with a locally running platform service. The website is its documentation and marketplace hub, not the place where native game engines execute.
Know which component owns the state
| Component | Responsibility |
|---|---|
| Control Room | Theia-based editor and views for inspecting and operating the project |
| Platform service | Project registrations, tasks, settings, routing, discussions, integrations, and audit records |
| Project workspace | Design documents, agent instructions, source assets, and native game files |
| Engine and DCC tools | Their own native documents, editor sessions, processes, and artifacts |
| Plugins and MCP servers | Contributed tools under supported contracts and host access policy |
| PlayWeld.com | Knowledgebase, free package listings, creator tools, and product information |
Keeping these responsibilities distinct makes recovery and diagnosis easier. A closed view does not delete its persisted records, and an open desktop window does not establish a healthy external connector.
Follow an inspectable change
A user selects a project and submits a bounded request. The service records the request, chooses eligible models and skills, and manages tasks. Tool calls pass through validation and access decisions. Work can create artifacts or isolated Git changes, followed by an integration record and human review.
The visible task result should identify what happened. Gameplay acceptance belongs to the native engine checks, not to the mere existence of a completed agent message.
Local does not mean every endpoint is offline
Project files and operational records reside locally, while a configured model provider, asset provider, or connection can contact an external service. Review credentials, endpoints, context, access policy, and costs before sending work.
For exact service interfaces and schemas, use the upstream RPC reference. For extending the product, follow the developer and integration guides instead of writing a competing authoritative project database inside a plugin.