Table of Contents

• Table of Contents
• 🚀 About
• 📸 Screenshots
• ✨ What's New
  • Version 3.8 (Latest)
• 📝 Installation
  • From Releases
  • From the Creator Store
  • From Source
• 🤝 Feedback and Contributions
• 🙏 Credits
• 📃 License

🚀 About

To use a Luau package in Roblox Studio, the usual path is four tools deep. You install Wally or pesde, set up Rokit, set up Rojo, wire it into your project, and only then can you actually require the thing. Great for an existing workflow. Slow if you just want one package.

Studio Discover skips the setup. Browse Wally and pesde packages from inside Studio, hit install, and the package shows up in your place: dependencies, types, and all.

📸 Screenshots

Click to expand

Expanded sidebar

Collapsed sidebar

✨ What's New

Version 3.8 (Latest)

✨ New

• Update count in widget title: the dock widget title flags pending updates with a · N update(s) suffix.
• Reset to Defaults: Settings now has a row that restores every setting (display name overrides included) after a confirm.
• Changelog screen: the sidebar's bottom slot opens a new Changelog screen that renders the bundled CHANGELOG.md, replacing the previous About page.

✏️ Improvements

• Themed toolbar icon: the toolbar button ships dedicated colorful-light, colorful-dark, and mono variants and swaps automatically with the Studio theme.
• Tokenizer-driven type rewrites: Wally's processPackageTypes parser is now a hand-written tokenizer with full test coverage, so type re-export generation handles nested generics, string literals, and comments correctly.
• SharedToolbar 0.3.x: bootstrap now drives Interposer and Leader directly instead of going through the old register wrapper.

🛠 Fixes

• Large module installs: installing a package with a file over Roblox's 200,000-char ModuleScript.Source limit no longer crashes the install. Every script source write is now routed through ScriptEditorService:UpdateSourceAsync.
• Stuck "busy" state: install/uninstall/updateAll no longer leave the plugin locked in a busy state when an operation throws — the lock now releases and the installer transitions to an error status on uncaught failures.
• Shared toolbar visibility: the plugin's toolbar button now advertises itself as shared so peer plugins running SharedToolbar can see it and dock alongside it.

See 📋 CHANGELOG.md for full details.

📝 Installation

From Releases

The fastest way to get the plugin without building it yourself.

1. Download the latest StudioDiscover.rbxm from GitHub Releases.
2. Drag the file into Roblox Studio.
3. Right-click the Discover folder in the Explorer and pick Save / Export > Save as Local Plugin.

A Discover button will appear in your toolbar.

From the Creator Store

Warning

Roblox moderation is currently preventing the plugin from being distributed via the Creator Store. Pending appeal (see issue #24).

Hopefully this'll be resolved soon. In the meantime, install via Releases or from source.

From Source

For contributors and anyone who wants to run a local build.

You'll need Rokit installed.

# Open a terminal (Command Prompt or PowerShell for Windows, Terminal for macOS or Linux)

# Clone the repository
git clone https://github.com/morgann1/studio-discover.git

# Navigate to the project directory
cd studio-discover

# Install the toolchain
rokit install

# Set up the project
lute run setup

# Run codegen (optional)
lute run codegen

# Install the packages
lute run install

# Build the plugin
lute run build

Then drag the generated StudioDiscover.rbxm into Roblox Studio, right-click the Discover folder in the Explorer, and pick Save / Export > Save as Local Plugin.

To test changes alongside the Creator Store version without collisions, run lute run build --dev. This produces StudioDiscover-Dev.rbxm with its own toolbar slot, widget, and plugin settings namespace.

🤝 Feedback and Contributions

Issues and pull requests are welcome.

• Bugs and feature requests: open an issue at GitHub Issues.
• Pull requests: before opening one, please file an issue describing the change so we can agree on direction. Run lute run ci locally before pushing. It mirrors what CI checks.
• Scope: contributions that fit the project's goals (see About) are the easiest to land. Studio Discover is a solo project, so response times vary.

🙏 Credits

Studio Discover is built on top of work from a lot of other people. Thank you to:

• cxmeel: the Luau, Creator Store, GitHub Releases, and GitHub Repository badges are from their Markdown Buttons gist.
• maneetoo: the Changelog and My Profile badges are from their Roblox OSS Badges collection.
• Roblox: the Foundation UI library the plugin is built with and the Contributions Welcome badge in this README is from Roblox's own assets.
• UpliftGames and daimond113: for the Wally and pesde registries the plugin queries.
• jsdotlua: the React port for Roblox.
• littensy: Charm and ReactCharm for reactivity.
• Corecii: GreenTea for runtime type checking.
• evaera: the Promise implementation.
• rojo-rbx: Rojo and Rokit for project sync and toolchain management.
• The Luau team and the Lute project: for the language and the standalone runtime that powers the build/CI scripts.
• grilme99: the .lute build/CI scripts started as a port of their .lune scripts from studio-activity, reworked to be cross-platform and adapted for this project.
• flipbook-labs: the roblox-packages crate pulls Foundation (Roblox's modern Studio UI components) into the build; without it the plugin would likely be sitting on StudioComponents or a hand-rolled UI instead.
• Elttob (Daniel P H Fox): the toolbar button uses Vanilla icons, and the cross-plugin toolbar slot is built on SharedToolbar, Interposer, Leader, and DoCleanup from LibStudioElttob (the morgann1/* wally forks are minor adaptations of these).

📃 License

Studio Discover's own source is intended to be freely redistributable: read it, fork it, modify it, and ship it. There's no LICENSE file in the repo yet, but the intent is permissive (MIT or similar).

The one thing to watch out for is Foundation, Roblox's UI library. The built StudioDiscover.rbxm bundles it at build time, and Foundation is not open source, so redistributing the built artifact is subject to Roblox's terms for Foundation, not this repo's license. A proper LICENSE will be added once Foundation is either swapped out or its redistribution terms are confirmed.

For now: do whatever you want with the source in this repo, but check Foundation's terms before redistributing the build.

Back to top