Talking to Roflow

You build with Roflow by chatting with the Roflow Agent — describing what you want, giving it the right context, reviewing the changes it proposes, and steering it until the result is exactly what you had in mind.

Where you talk to Roflow

The Roflow Agent lives in a side panel inside the app. At the top of the panel is a three-tab bar:

• Chat — where you talk to the agent and watch it work.
• History — your past tasks, so you can revisit earlier work.
• Settings — preferences for the agent, including auto-approve.

You type in the composer at the bottom of the Chat tab. To jump straight to it from anywhere in the editor, press Cmd/Ctrl+L.

Making a request

1. Click in the composer (the box reads "Type your task here..." for a new task, or "Type a message..." once a task is running).
2. Describe what you want in plain language — for example, "build a tycoon with a conveyor and purchase pads" or "add a shop where players spend coins on speed upgrades."
3. Press Enter — or click the paper-plane Send button — to send it. Use Shift+Enter to add a line break without sending.

That's the whole loop: you ask, Roflow proposes, you review, and you iterate. Everything below is about doing each of those steps well.

Starter tasks for a blank chat

On an empty chat you'll see one-click starter pills: Build a Tycoon Game, Build a Simulator Game, Build an RNG Collector, and Build an Obby Escape. Picking one gets you a full playable game to build on rather than an empty project — Tycoon, for instance, then lets you choose a theme before it starts. They're the fastest way to see Roflow in action if you're not sure where to begin.

Giving Roflow the right context

Roflow builds best when it can see what you're talking about. The composer gives you several ways to point it at the right things — the hint underneath it sums them up: "Type @ for context, / for slash commands & workflows, hold shift to drag in files/images."

Reference things with @

Click the @ Add Context button or type @ in the composer to open a menu that lets you attach:

• a File or Folder from your project,
• the current Problems (the errors and warnings Roflow has flagged),
• the Terminal contents,
• a Git commit, or
• a URL for Roflow to fetch and read.

Referencing a specific file or folder is the best way to tell Roflow where to work, so it changes the right thing instead of guessing.

Attach files and images

Click the + Add Files & Images button to open a file picker, or:

• Paste an image (PNG, JPEG, or WebP) straight into the composer, or
• Drag and drop files and images in — hold Shift while dragging to drop them onto the composer.

Attachments show up as small thumbnails you can remove before sending. There's a limit on how many you can attach to a single message, so add the ones that matter most.

Pull in code from the editor

If you're looking at something in the code editor:

• Select the code and press Cmd/Ctrl+' (or right-click and choose Add to Roflow Agent) to drop that selection into the chat as context. Terminal output can be added the same way.
• Inside a chat message, select some text and choose Quote to pin a quoted preview above the composer, so your next message refers to exactly that line.

Speeding things up

Slash commands and saved workflows

Type / in the composer to open a command menu. Built-in commands turn common jobs into structured tasks — for example:

• /init — inspect an existing game so Roflow learns your setup before adding to it.
• /deep-planning — investigate your project and produce a full, reviewable plan before writing code.
• /new-service and /remote-event — scaffold common Roblox building blocks like services and validated client-server events.
• /playtest — prep and run a playtest.
• /smol — condense a long conversation so Roflow can keep going without losing the thread.

Any reusable workflows you save show up here as slash commands too. See Commands for the full list.

Improve your prompt

Not sure your wording is clear? Click the sparkle Improve prompt button and Roflow rewrites your draft into a stronger version, showing you a before/after view that streams in. Nothing changes silently — you explicitly Accept the rewrite or Cancel to keep your original.

Choose how much power to spend

A model button in the composer shows the current model and opens a picker with three tiers: Fast (quick edits, low usage), Balanced (the all-round default that can also read images), and Max (most capable, for complex reasoning and debugging). Higher tiers produce stronger results on hard tasks but draw down more of your monthly usage — see Usage for how that works.

Plan first, or build right away

Roflow has two modes, and you choose which one a task starts in:

• Plan mode — Roflow reads your project and proposes an approach without changing anything. You settle the plan first, which is the safest way to start a big feature.
• Act mode — Roflow actually does the work.

Switch from Plan to Act with the Act Mode control shown in the agent's message, or press Cmd+Shift+A. You can bounce back to Plan whenever something unexpected comes up. For the full picture, see Planning Your Game.

Reviewing and approving changes

By default, Roflow asks before it acts. Whenever it wants to do something that touches your project, it pauses and shows action buttons just above the composer, then waits for your choice.

• File edits. When Roflow wants to create or change a file, it shows the change first — you review it and click the green Apply button to accept it, or Reject to discard it. New files work the same way.
• Terminal commands. A command shows what it will run, with Apply to run it and Reject to decline. For a long-running command, a Proceed While Running button lets the task continue while the command keeps streaming output.
• Browser and other tools. Fetching a web page or using a connected tool prompts Apply / Reject the same way.

Because you see each change before it happens, you always know exactly what Roflow is about to do.

Following along while it works

You don't have to guess what Roflow is doing. As it works, its actions are summarized in plain language — "Read <file>," "Edited <file> (3 edits)," "Created <file>," "Ran <command>" — with a rolled-up header like "Edited 2 files · Read 3 · Ran 1 command." A "Thinking…" indicator settles into "Thought for Ns" when it's done reasoning.

For bigger jobs, a task plan appears under the task with the phases and steps ticking off — checkmarks and spinners, a "Phase X of Y" counter, and an overall progress bar — plus a live checklist in the header (like 3/8) you can open and edit to add, remove, or reorder steps. An expandable task header shows your original request along with running usage totals.

While a request is in progress you can press Cancel at any time to stop it.

Answering follow-up questions

Sometimes Roflow needs a decision from you. It shows a "Waiting on you" card with clickable option buttons. You can pick an option, type your own answer in the composer instead, or skip the question. If it asks several things at once, you page through them and press Submit.

Letting Roflow act on its own

Once you trust it on a given task, you can loosen the reins so it doesn't stop for every step. In the agent's Settings, the Auto-approve area lets you pre-authorize categories of actions:

• Read project files
• Edit project files
• Execute safe commands
• Use the browser
• Use MCP servers

Each has an optional wider scope, and you set a Max Requests number — how many actions Roflow may take before it checks back in with you. A master toggle turns the whole thing on or off.

Iterating toward what you want

Getting the result right is usually a conversation, not a single message. A few ways to steer:

• Just keep talking. After a change lands, reply with the next adjustment — "make the shop UI bigger," "the coins aren't saving, please fix it." Roflow keeps the context of your game across the task.
• Edit an earlier message. If a request didn't land the way you wanted, click one of your own earlier messages, edit it, and resend. Choose Restore Chat to roll the conversation back to that point while keeping your files as they are, or Restore All to roll back both the conversation and your workspace files — so you can try a completely different direction from a clean starting point.
• Undo with checkpoints. Roflow snapshots your workspace as it goes, so you can compare what changed and restore to an earlier point at any time. This is your safety net for experimenting.

When Roflow can't continue

A few things will pause the conversation:

• You've used up your AI allowance — the chat shows a limit banner with a retry option and a link to upgrade. See Usage and Plans & Pricing.
• You're signed out — the composer is disabled until you sign in with Roblox.
• Studio isn't connected — Roflow can still edit files and run commands, but it can't playtest or verify visuals, and it will flag that rather than pretend it checked. See Connection Problems.

For more on getting unstuck, see AI Issues and Fixing Issues.

Where to go next

• How Roflow Works — the plan-build-test-improve loop behind every task.
• Planning Your Game — Plan mode, deep planning, and mapping out a build.
• Getting Great Results and Common Pitfalls — how to phrase requests for the best output.
• Existing Projects — bringing Roflow into a game you already have.
• Keyboard Shortcuts and Commands — the full reference.