dsh-roblox-studio

When you bridge multiple Roblox Studio instances through DeepSeek Harness MCP, a pure command-line workflow makes it hard to tell which instances are live, which one the Agent should target, and whether the bridge itself is healthy. dsh-roblox-studio closes that gap by adding a dedicated Roblox Studio section to the Settings panel, where you can see connected instances, bridge status, and stale-connection flags at a glance, and activate or deactivate a target with a single click.

Activation is more than a label. The plugin injects the chosen studio_id into the Agent runtime context so every mcp__roblox__* tool call is scoped to that instance, and the Agent is warned if the selection has gone stale. The choice persists across restarts in your local settings file, so the next session picks up right where you left off.

A second pillar of the plugin wraps around Roblox Studio's native Script Sync feature. The settings page queries InstanceFileSyncService in real time to surface sync roots, error trees, and failure reasons for the active instance, with a 45-second cache and scheduled refreshes. If you set a local sync directory in the config, the Agent is steered to edit Rojo-style local script files (*.server/.client/.local/.legacy.luau and folder init files) directly within that sync scope, letting the official sync push changes back into Studio. This is faster and less conflict-prone than issuing every write through MCP.

If you develop in Roblox Studio driven by MCP inside DeepSeek Harness, juggling two or three Studio windows while relying on the built-in Script Sync to keep code in sync, this plugin removes a layer of cognitive overhead around instance switching, status verification, and script collaboration.