Yes — you can usually keep working while Codex is running with Roblox Studio, but expect some slowdown if it is actively reading docs, scanning your place, or making changes. Recent Roblox community reports mention that Codex can lag Studio or bloat usage when it searches a lot, and some creators say keeping Studio open in the background is normal for the connection to work.

How it behaves

Codex and Roblox Studio can run side by side, but they are sharing your computer’s CPU, memory, and sometimes disk activity. That means simple tasks like typing, moving around the editor, or tweaking UI usually stay fine, while heavier AI actions can make Studio feel sluggish for a bit.

Practical workflow

A good setup is to keep working on planning, reading output, or editing unrelated files while Codex does its thing. If Codex is making large changes, generating lots of code, or searching documentation, it is smarter to pause and let it finish before testing in Studio, because the lag can make debugging harder.

Best habits

  • Keep Roblox Studio open if you’re using the MCP-style connection, since guides say the Studio instance needs to stay running.
  • Work on design, assets, notes, or other non-heavy tasks while Codex processes.
  • Let it finish before you run playtests or judge performance, since AI-driven searches can distort how responsive Studio feels.
  • If it gets slow, reduce how much Codex is searching or reading at once, because docs access was specifically called out as a source of bloat.

Simple rule of thumb

If Codex is just waiting or doing a small edit, keep working. If it is actively churning through a big task, treat that moment like a background render: you can still work, but the smoothest results usually come from letting it finish first.

TL;DR: Yes, you can work while it runs, but for big tasks it is often faster and less annoying to let it finish first.