Roblox Forum

Quick Summary

• As of 2026-05-06, Yeet v0.3.1 syncs code both ways between Roblox Studio and Visual Studio Code or Antigravity.
• You can now fix edit clashes with a 3-pane merge view right inside Studio (disk, Studio, merged result).
• This is still early-stage on 2026-05-06, so expect quick updates and some bugs while it grows.

What's New

1. True two-way sync: edit `.lua` or `.luau` on either side and see the change on the other side.
2. Reverse Bootstrap: pull an existing Roblox Studio place into on-disk files from the plugin UI.
3. Rojo-friendly layout: folder structure matches Rojo-style projects, so setup feels familiar.
4. Conflict tools: 3-pane merge in Studio helps you choose the final script safely.
5. 3-part system: local Rust daemon + Luau Studio plugin + TypeScript editor extension.
6. Current protocol info (2026-05-06): JSON wire format is live now, MessagePack is planned later for less overhead.

Before vs. After
[table]
[tr]
[td]Before Yeet[/td]
[td]After Yeet v0.3.1 (2026-05-06)[/td]
[/tr]
[tr]
[td]Manual exports/imports between Studio and editor[/td]
[td]Live sync in both directions</td]
[/tr]
[tr]
[td]Hard to jump back into old projects fast</td]
[td]Reverse Bootstrap can generate on-disk files from current DataModel</td]
[/tr]
[tr]
[td]Conflicts can get messy and scary</td]
[td]3-pane merge shows both versions and a final merged file</td]
[/tr]
[tr]
[td]Extra setup friction when using external editors</td]
[td]Daemon + plugin + extension flow is direct and repeatable</td]
[/tr]
[/table]
Developer Context
The creator shared Yeet in a DevForum introduction post and said it was built with fast AI-assisted iteration. On 2026-05-06, the message is clear: "works in real projects, still early, report bugs fast."
Why make it? To remove boring setup steps and let devs code where they feel fastest. That is extra useful if you switch between multiple games a lot.
Why You Should Care
If you are a player who wants to start creating, this update makes "first real dev workflow" way easier.
If you already build games, you save time every session:

• Less copy-paste, more building gameplay.
• Cleaner teamwork when files conflict.
• Easier path from Studio-only project to version-controlled files.

Quick tip: test Yeet first on a small side project, then move your main game after you trust your sync flow.
FAQ

• Q: Do I need Rojo to use Yeet?
  A: No. Yeet is separate, but its folder style is Rojo-friendly.
• Q: Can I start from an old Roblox Studio place?
  A: Yes. Use Reverse Bootstrap to create the disk files from your existing place.
• Q: What happens if Studio and VS Code edits clash?
  A: Yeet opens a 3-pane merge so you can pick and combine changes safely.
• Q: Is Yeet stable for huge production games yet?
  A: On 2026-05-06 it is labeled early-stage (v0.3.1), so treat it like active beta and keep backups.
• Q: Can I use Antigravity instead of Visual Studio Code?
  A: Yes, Antigravity is listed as supported in the shared update.

Sources

• Roblox DevForum post: "Yeet - Bidirectional sync between Roblox Studio and VS Code / Antigravity"