Your first Codex task

How to use Codex with Roblox Studio

Start with a copy of your game and one player action you can repeat. Baseplate’s Guide takes you from choosing the project to connecting Codex and checking the change in Studio.

Baseplate 0.23.1 · Updated 28 October 2026

  1. 01Choose your game
  2. 02Describe one change
  3. 03Connect Codex & Studio
  4. 04Repeat the same test

Have Baseplate already? Open Guide in the left rail and choose Fix a bug. For this path you need Codex CLI installed and signed in on this computer, plus Roblox Studio. Your provider’s access and usage limits apply. Open Cloud is optional. You can start with a free local scan without AI.

01Choose your game

In Guide → Fix a bug, use Choose my game. Pick the way you already work:

  • My scripts are in a folder: select your source or Rojo project folder.
  • My game is in Roblox Studio: open a saved copy, stop Play and keep only that Studio game open. Follow Install / update Bridge and Check connection, confirm the game, then use Read scripts & add my game.

A Studio import is a script snapshot. Confirm changes in the open game and save in Studio; editing that local snapshot is not automatic Rojo sync.

02Give Codex one clear target

In What should change for the player?, describe a failure you can reproduce. Replace the brackets before starting:

Current behavior: [player action and what goes wrong]
Expected behavior: [what the player should see instead]
Test: [the same steps to repeat before and after]

Inspect the cause first. Keep the change limited to this issue.
Explain the changed files and what the test did not cover.

For example: touch checkpoint 3, return to checkpoint 1, then reset. If that sends the player backwards, the target is to preserve checkpoint 3 for this session. Use an action from your own game.

03Connect Codex and Studio

Expand Connect the tools for this change and select Codex under AI for building and playtesting.

  • AI missing or signed out? Open How do I connect AI?, follow the official Codex CLI setup, then use Check AI setup. After installing a CLI, fully restart Baseplate so it can find it.
  • Studio not ready? Open How do I connect Studio?. Follow the Bridge instructions, enable Studio MCP in Studio → Assistant → Manage MCP Servers and use Check setup. Approve the Bridge’s HTTP request when Studio asks.
  • Using Rojo? Start Rojo from Baseplate’s Studio section and connect Studio’s Rojo plugin to this project.

The Guide’s next action follows the setup it actually detects. A detected installation alone is not a successful connection or playtest.

04Build, then repeat your test

When Guide says Ready for one useful improvement, choose Build & test this change. This starts an agent that can edit the selected project and use connected Studio. Watch its requests, changes and test evidence.

Your result checklist: the right game was tested; you reviewed the changed files; you repeated the original player actions and observed the expected result. A runtime PASS covers its recorded checks. A clean console alone does not prove the gameplay bug is fixed.

Try the flow again yourself before publishing. Keep your normal project history, and use the RemoteEvent checklist for security checks.

If something gets stuck

Codex is not in the list
Install and sign in to Codex CLI in the operating system where Baseplate runs. An app or editor extension alone does not establish that the CLI is available. Restart Baseplate and run Check AI setup.
Sign-in or provider access fails
Finish the provider’s sign-in and check the displayed account or usage error. A Baseplate subscription does not include Codex access or remove provider limits.
The agent describes a test but no test runs
Open Studio setup and follow its next missing connection. Check the selected game, Bridge and live Play control. Describing a test is not evidence that it ran.
The local files changed but the game did not
For Rojo, check that its server and plugin use this project. For a Studio snapshot, check the actual edit in Studio and save the game there.

Want a first result without connecting AI?

In Guide, choose Find what to improve, add your project and use Open free local scan. Verify highlights risks and missing evidence. This local scan needs neither an AI account nor Open Cloud; its findings still need review and testing.

Advanced: manual Codex MCP configuration

Baseplate prepares its workspace connection for the session. For a separate manual CLI workflow, OpenAI documents user MCP configuration in ~/.codex/config.toml and trusted project configuration in .codex/config.toml. Use the official MCP configuration guide for current commands. A fixed localhost URL copied from another setup may point at a different port or project.

Bring one game. Start with one change.

The core one-agent workflow is included in Free. Use the Codex access you already have, or start with the local scan.

Download Baseplate free

Want help with your own project? Request a free hands-on session →