Multiple Studio Window Title Differentiation

Please follow the format in How to post a Feature Request

Be as specific as possible, give your post a clear and descriptive title, and focus on problems and use cases, rather than proposed solutions.

As a Roblox developer, it is currently too hard to …

Recently Roblox added studio_id to the MCP ecosystem and this has made running multiple studio sessions with multiple Claude Code agents at the same time workable in a safe way (with some custom automation). But now the human is the biggest problem - I simply am not reliable at differentiating which Studio session I’m currently looking at. So I have to ask Claude to tell me what marker to look for in Explorer to confirm that I’m in the right studio instance before launching a playtest or saving the rbxl to disk. It’s too hard to quickly remember which Studio session is which.

I propose that being able to annotate the Studio top bar with both a name and a color would allow for quick and easy distinction. I’m exploring ways to do this with plugins instead, but it seems like it’s a feature that probably warrants first class support at some point soon.

If Roblox is able to address this issue, it would improve my development experience because …
I will make fewer mistakes working in the wrong Studio instance and I will not have to spend expensive human time looking for markers created by a specific Claude and replicated into a specific studio from that Claude’s clone of the git repo through that Claude’s rojo instance.

3 Likes

Hey, thank you for this feedback! I work on the MCP server, and it’s great to hear the studio_id solution is working for you in a safe way.

We haven’t considered this painpoint before, and will take a look.

As an aside, I would like to hear from you about the shortcomings and what custom automation you’re using.