AI Issues

When the Roflow agent gets something wrong, seems stuck, or stops responding, you're never stuck with the result — this page walks through what to do in each case.

Which page do you need?

This page is about the AI agent itself misbehaving. Two nearby problems live elsewhere:

Roflow made a wrong or off-target change

Most of the time you'll catch this before it lands, because Roflow shows you every change first.

Catch it before it applies

When Roflow proposes an edit, it shows the change as a diff and waits. Read it, then:

• Click Reject to discard it, and say what was wrong in your next message. A quick "reject + reason" is one of the fastest ways to steer Roflow — it revises and proposes again with your feedback in mind.
• Click Apply (or Save) only once the change is what you meant.

Commands prompt Run Command / Reject, and other actions prompt Approve / Reject, so you always see what's about to happen before it happens.

Undo a change that already applied

If a change is already in and you don't like it, roll it back:

• Restore a checkpoint. Roflow snapshots your workspace after each step. Open an earlier point in the conversation, click Compare to see exactly what changed, then Restore — choosing to roll back just the code, just the conversation, or both.
• Edit an earlier message and resubmit. Click one of your own earlier messages, edit it, and resend. Restore Chat rolls the conversation back but leaves your files as they are; Restore All rolls back the conversation and your workspace files, so you can try a different direction from a clean start.

Checkpoints work alongside Studio's own undo, too — edits Roflow makes to your place are grouped, so Edit > Undo in Studio reverses them like your own changes.

Then say what was wrong

The fix is usually a clearer follow-up. Tell Roflow specifically what's off — "the shop opens on the wrong side," "you changed the save format and shouldn't have," "keep the coins server-authoritative." Naming the file, folder, or system (or attaching it with @) keeps the next attempt from wandering. See Getting Great Results.

The change is incomplete or stopped short

If Roflow did part of the job and stopped, you don't have to start over.

• Just tell it to keep going. Reply with what's missing — "you built the dropper but not the collector pad," "the HUD isn't wired to the coins yet." Roflow keeps your task's context, so it picks up where it left off.
• Watch the live checklist. On bigger tasks Roflow keeps a running to-do list in the task header (for example, 3/8) with the current step highlighted. If it stalled mid-list, that shows you exactly what's left — and you can open and edit that checklist to add, remove, or reorder steps.
• Break a big ask into stages. A request that's too large in one go is the most common reason work comes out half-finished. A good rule of thumb: a request is the right size if you could playtest it and say whether it worked. Build the core loop, get it playable, then layer on the next system. See Building in Stages.

Roflow seems stuck or won't respond

A few things can pause the agent — and most resolve with a single click.

• It's still working. While Roflow runs, a Cancel button is available and the activity timeline narrates what it's doing ("Read file", "Ran command", "Studio: action"), settling a "Thinking…" indicator into "Thought for Ns." If you want to take over, press Cancel.
• It paused to ask for guidance. Roflow stops and checks in when it hits its consecutive-mistake limit or its auto-approval action cap, so a task can't run away unattended. This is by design — just respond to steer it back on track. If it keeps hitting the same wall, restore a checkpoint and try a clearer request.
• An error appeared. On an error you may see Retry, Proceed Anyways, or Start New Task. Try Retry first; use Start New Task to begin fresh if the current task is tangled.
• "Rate limit exceeded. Please try again later." The AI service is briefly throttled. Wait a moment and use Retry.
• The conversation got very long. Roflow summarizes long tasks automatically so it can keep going without forgetting earlier decisions, and it can hand a task off to a fresh session (with your approval) carrying the important context forward. You can also run /smol to condense the conversation yourself, or /newtask to start clean.
• The Dashboard shows "Roflow could not reach its agent service." This usually appears right after launch while Roflow is still starting up, and clears on its own once it finishes. Give it a moment, then retry or refresh.

The output is unclear or you don't follow it

If you don't understand what Roflow did or why, ask — it can explain in plain language.

• Ask it directly. "Why did you change that file?" or "Explain what this script does." Roflow keeps the task's context, so it can walk you through its own work.
• Explain a piece of code. Select code in the editor and right-click Explain with Roflow Agent to have it break down what an error or a confusing block means before you decide what to do.
• Answer its "Waiting on you" cards. When Roflow needs a decision it shows a "Waiting on you" card with clickable options; you can pick one, type your own answer, or skip. Picking the right option early keeps it from guessing.
• Open the task details. The expandable task header shows your original request and how much of the context window the task is using, which can explain why a long task started summarizing or slowing down.

The request was the real problem — clarify and re-ask

Often the agent did exactly what was asked; the ask just wasn't what you meant. Re-asking clearly beats another round of trial and error.

• Be specific about what, where, and how it behaves. "Add a shop UI in the top-right that sells three speed upgrades for coins" gives Roflow far more to work with than "add a shop." See Getting Great Results and Common Pitfalls.
• Give it the right context. Point Roflow at the real thing instead of describing it: type @ to attach a File, Folder, the current Problems, or a URL, and drag in or paste screenshots. See Talking to Roflow.
• Use Improve prompt. Not sure your wording is clear? Click the sparkle Improve prompt button; Roflow rewrites your draft into a stronger version and shows a before/after view. Nothing changes silently — you Accept the rewrite or Cancel to keep your original.
• Plan before building. For anything large or ambiguous, switch to Plan mode, where Roflow proposes an approach without changing anything; refine it in plain language, then switch to Act mode (Cmd+Shift+A) to build. For a feature that would normally need a design doc, /deep-planning has Roflow investigate, ask targeted questions, and produce a reviewable plan first. See Planning Your Game.

You've run out of AI usage

Every plan includes a monthly AI allowance, and heavier AI tasks draw down more of it. When it's used up, the chat shows a limit banner — something like "Free tier limit reached (you've used your AI quota for this month)" — with a button to upgrade or buy more and a Retry Request button.

What to do:

• Wait for the reset. Your allowance refreshes each billing cycle. The rest of the IDE keeps working in the meantime — only the AI features pause.
• Upgrade for more right away. A higher plan raises your allowance immediately (and unlocks more capable models). The banner's upgrade button takes you to roflow.co/pricing.
• Check where you stand first. Your Settings > Plan & usage shows your current tier, how much of the monthly budget you've used as a percentage, and when it resets. See Usage and Plans & Pricing.

Other things that can stop the agent

A couple of blockers aren't really the AI misbehaving — they're guardrails:

• "Sign in to Roflow IDE to use the agent." The composer is disabled until you sign in with your Roblox account (free, no credit card). Sign in and the input re-enables. See First Launch.
• A blocked file path. If Roflow tries to touch a path excluded by your project's .roflowignore file, it tells you: "Roflow Agent tried to access <path> which is blocked by the .roflowignore file." Sensitive paths like .env, *.key, node_modules, .git, and Packages are ignored by default. If the agent genuinely needs that file, unignore it; otherwise this is Roflow protecting it.

Where to go next

• Fixing Issues — when the problem is a bug in your game, not the agent.
• Getting Great Results and Common Pitfalls — how to ask so you get what you meant the first time.
• Talking to Roflow — making requests, giving context, approvals, and checkpoints.
• Planning Your Game — Plan mode and deep planning for bigger asks.
• Usage and Plans & Pricing — your AI allowance and how to raise it.
• Connection Problems — when Studio won't connect or sync.