Core Concepts
Permissions
Stud never takes action without your approval. Every file write, shell command, and Roblox operation goes through a transparent permission system.
How it works
When Stud wants to perform an action that modifies your system — writing a file, running a shell command, or editing a script in Roblox Studio — it shows you exactly what it plans to do and asks for your approval.
studPermission types
One-time approval
Approves the specific action being requested. Stud will ask again for similar actions in the future. This is the most conservative option.
Session-wide approval
Approves this type of action for the rest of the session. For example, allowing "Write" always means Stud can write files without asking again until you restart.
Deny the action
Blocks the action entirely. Stud will acknowledge the rejection and may suggest an alternative approach that doesn't require the denied permission.
What requires permission?
Not every action requires approval. Stud distinguishes between read-only and write/execute actions:
✓No approval needed
- → Reading files
- ✱ Searching files (Glob / Grep)
- ◆ Reading Roblox instances
- ◉ Spawning subagents
△Approval required
- ← Writing or editing files
- >_ Running shell commands
- ◆ Modifying Roblox instances
- ◆ Editing scripts in Studio
Best practices
Start conservative
Use "Allow once" until you're comfortable with how Stud operates. You can always switch to "Allow always" later.
Review diffs carefully
Stud shows you exactly what will change before writing. Take a moment to review the diff — it's your safety net.
Use git for backup
Commit your work before starting a Stud session. If anything goes wrong, you can always revert. Stud itself will suggest using git for safety.