itch.io

For your interviews, I'd ask someone to walk through their last bug or art handoff: where did the request start, which file changed, and where did the reason for the change end up? A board can tell you who owns a task while still leaving that trail scattered across chat.

I'm building PlayWeld, a free open-source workspace for project files, notes and searchable project knowledge, so I'm interested in that gap too. It's still a testing prerelease, rather than evidence of a proven team workflow. Are you finding the bigger problem is assigning work, or recovering why a decision was made?

Hey everyone! I’m sharing PlayWeld, an open-source desktop IDE built on Eclipse Theia for AI-assisted game development.

PlayWeld brings your project files, plans, conversations, knowledge search, and connected tools into one workspace. The goal is to keep your game’s context close while you work, with supervised AI workflows and reviewable changes.

What’s inside:

• Project files and development notes in one place
• Knowledge search with source references
• Connections to game engines and asset tools
• AI-assisted workflows with approval controls for tool actions

It’s still in active development, and integration support varies by tool and provider. Start with a test project and keep backups. The IDE is free under Apache-2.0; connected AI and asset services may have their own costs.

I’d love feedback from other developers: what feels useful, what’s confusing, and what would you want to see next?

Check out PlayWeld on itch.io: https://scarecr0w12.itch.io/playweld

Website: https://playweld.com Source code and bug reports: https://github.com/scarecr0w12/PlayWeld