As a Roblox developer, it is currently too hard to use agentic coding tools
inside a Team Create place with Drafts Mode enabled.
Modern coding agents can implement features spanning multiple systems under one
prompt. For example:
Implement a quest system that features dialog, sounds, vfx, and ui animations
A task like this can create or modify dozens of related scripts:
Studio presents the result as a flat list of uncommitted drafts, resulting in the developer manually checking which drafts should be committed or discarded, and which scripts should be merged, and how.
Current workflow
My current workflow uses an external coding agent with Argon (a roblox → file system syncing application - similar to rojo) and a Studio
integration. The agent edits the filesystem project, while Argon synchronizes
those changes into Studio.
However, the agent cannot inspect the Drafts window or determine which scripts
have active or pending drafts. This has caused repeated confusion during real
development sessions.
In one session, after completing changes across several scripts, the agent
reported:
Agent: My edits are on disk but Studio shows the old versions, so Argon
isn’t syncing right now.
After further checks, it concluded:
Agent: Argon is running and Studio is connected, but the scripts in
Studio are stale.
I checked Studio manually and responded:
Developer: It does exist in Studio. I checked.
In another session, the agent eventually discovered another source of this
confusion:
Agent: In Edit mode, the committed
.Sourcelags the Argon-synced editor
buffer. Studio serializes the current buffers when play starts, so the game
runs the newer code.
The agent had to start a play session and inspect the running source before it
could confirm which version Studio was actually using.
This means the agent can modify code, inspect the filesystem, check whether
Argon is running, and communicate with Studio, but it still cannot answer basic
workflow questions such as:
- Which scripts currently have active or pending drafts?
- Does a draft differ from the filesystem version?
- Is
.Sourceolder than the current editor buffer? - Did every change from the current task reach Studio?
- Will the next synchronization conflict with an uncommitted draft?
- Have all drafts belonging to the completed task been handled?
This is extremely limiting for agentic development in Team Create places with
Drafts Mode enabled, because an agent can modify scripts but cannot discover
active drafts or submit selected drafts for commit or discard. Every task
therefore ends with the developer manually identifying, reviewing, and
finalizing each affected draft, which becomes unmanageable when a single prompt
changes many scripts. The agent cannot reliably verify that its work is complete
or participate in an end-to-end development workflow.
So isn’t it Argon’s fault?
Every application that syncs your filesystem to roblox will inevitably run into issues where code may not sync, that’s perfectly acceptable. However, it should be possible to identify when code isn’t syncing, and what other users in the team create may see.
Requested outcome
Development tools need a supported way to participate in Studio’s draft
workflow. One possible solution would be a supported Drafts or change-set API
that allows tools to:
- Enumerate active drafts and inspect their status
- Determine which scripts contain uncommitted changes
- Compare drafted, committed, and editor-buffer versions
- Commit or discard selected drafts
- Detect conflicts before additional changes are applied
Providing a supported draft workflow would bring the same reviewability to
external development tools and make agentic workflows practical inside Team
Create places that use Drafts Mode.
Related request
Make DraftsService PluginSecurity:
That older request concerns general plugin access to DraftsService. This request
focuses specifically on the task-scoped, multi-script review and completion
workflow required by modern agentic coding tools.