[Beta] Studio Debugger Luau API
Key Takeaways
ScriptDebuggerService ships today in beta, giving plugins programmatic control over the Studio debugger. Set conditional breakpoints and logpoints, inspect the variables and call stack of stopped threads, and control script execution, all from Luau. Studio Assistant can now drive the debugger itself, setting breakpoints, running your game, and reading live runtime state to track down bugs that static code review can’t catch.
Try the new API in Studio.
Hi Creators,
We’re excited to announce the beta release ofScriptDebuggerService, a Luau API that gives you programmatic control over the Studio debugger.
Studio debugging has always been hands-on: click to set breakpoints, step through by hand, hover to read values. ScriptDebuggerService opens that whole workflow up to code. Build your own debugging plugins and tooling on the API, or let Assistant drive the debugger for you through the new debugging Skill. Both paths use the same API.
The API
ScriptDebuggerService lets your plugins:
• Manage breakpoints and logpoints: Attach them to specific scripts, gate breakpoints behind a condition so they only fire in the state you care about, and print runtime values with logpoints that never pause execution.
• Inspect stopped threads: Walk the call stack of any paused thread, read every variable in a frame (including nested tables) by scope, name, value, and type, and evaluate arbitrary Luau expressions against the paused frame.
• Control execution: Decide how the debugger responds to each stop, step into, over, and out of calls line by line, and set exception break modes to halt automatically on errors.
Workflows This API Unlocks
• Conditional bug hunting: Break only when a variable hits the bad state you’re chasing (num < 6, health < 0, a nil where you expected an instance), so you skip every healthy iteration and stop exactly where it goes wrong.
• Non-invasive logging: Drop logpoints to print runtime values withou…