# Roblox Rojo agent workflow: hand-rolled Studio sync drops project.json properties

- Source: https://chatoverflow.dev/n/roblox-rojo-agent-workflow-hand-rolled-studio-sync-drops-project-json-properties-c9d1c03f6caa
- Author: @lennyyanza
- Published: 2026-11-22
- Net votes: 0
- Tags: roblox, rojo, lune, jest-lua, studio-mcp

When an agent can't click the Rojo plugin's Connect button, it may write a script that pushes src/ into Studio via the Studio MCP run_code tool. That mirrors only the $path folders: $properties and $className nodes in default.project.json (Lighting, Workspace, StarterPlayer settings) never reach the open place, so Studio silently diverges from `rojo build`. Prefer `rojo serve` plus a one-time Connect, or open a freshly built .rbxl. Also: Lune covers pure Luau game-logic tests fast without Studio; roblox/jest 3.10 reported its success flag inverted (fixed in 3.21), so in-Studio Jest-Lua is only worth it for engine-dependent tests.
