My agent isn’t responding, or my quota runs down fast
A silent agent has three possible causes: it isn’t signed in to your AI account, the machine is short on memory, or it’s waiting its turn to drive Roblox Studio. A quota that runs down fast is a different issue: it depends on your AI provider, and a few habits can make it last much longer.
The agent isn’t signed in
Section titled “The agent isn’t signed in”Agents run on your AI account. Sign-in happens in each provider’s official tool, never on VibeStarter’s servers.
| Agent | What it asks for |
|---|---|
| Claude Code | Open the link, sign in, paste the code you get into Sign-in code, then Submit. |
| Codex (OpenAI) | First, turn on device code sign-in in ChatGPT’s security settings. You only need to do this once. |
| Grok Build (xAI) | Same principle as Codex: a device code to enter on the xAI page. |
| Antigravity (Google) | Open a Terminal tab and run the agy command. |
| OpenCode | Sign in from OpenCode, in front of its list of providers. |
If launch stops at the Connect your agents box, you can connect the agents from there, or click Launch anyway: the agent will then ask you to sign in from its terminal.
Codex then shows its own sign-in menu, in English: choose the second option, Sign in with Device Code. In VibeStarter, it is the only one that works. The first one, Sign in with ChatGPT, leads to a page your browser can’t reach.
When sign-in fails for no visible reason, click Show terminal: the official tool’s full message is readable there.
“Agent installation issue detected” means the installed tool no longer matches the expected official tool. Click Reset now: fresh copies are reinstalled from the official sources, and your projects, settings and conversations are kept. The status of each tool is shown in
Settings → Agents & tools, with the Update all button.
The agent pauses by itself
Section titled “The agent pauses by itself”These badges are normal: they come from automatic memory management, not from a failure.
- Paused — resumes automatically: the virtual machine ran short of room; the agent restarts as soon as there is some.
- Queued — starts automatically: the agent is waiting for memory before it starts.
The number of agents that can run in parallel depends on your RAM: 6 GB is the accepted minimum, between 8 and 15 GB several agents are cramped, and 16 GB or more is comfortable. To get some breathing room, close agents rather than leaving them all queued.
Three messages look alike, and none of them calls for the same action.
| Message | What it means |
|---|---|
| Compile fix in progress | The code doesn’t compile and a code agent is running in the project. An agent that is actively working fixes it on its own; if it is idle, ask it to fix the error. |
| The code doesn’t compile | The code doesn’t compile and no agent is running. Sync with Studio resumes as soon as it compiles: start an agent to fix the error, or fix the file yourself. |
| Out of memory (compiler) | The compiler used up the virtual machine’s memory. No agent will fix this: close agents, then reopen the project. |
The agent is waiting for Roblox Studio
Section titled “The agent is waiting for Roblox Studio”Only one agent drives a place at a time. The others aren’t blocked: they keep reading and writing code in the meantime. If nothing moves anymore, the problem is elsewhere — see The connection to Roblox Studio doesn’t work.
The agent says it can’t do something
Section titled “The agent says it can’t do something”There are two very different cases.
- Some refusals are deliberate, and the agent then receives a sentence explaining them: it doesn’t read or write code through Studio — it goes through the synced files — it doesn’t ask Roblox to generate a mesh or a material, and it doesn’t launch a Roblox sub-agent.
- An agent can also be wrong about its own abilities. If it says VibeStarter can’t do something you’ve seen documented, ask again explicitly, clear the current conversation, then restart the agent. Starting from a clean conversation often costs less than insisting.
What your agents can actually do is described in What your agents can do.
My quota runs down too fast
Section titled “My quota runs down too fast”The quota is that of your AI subscription, at your provider. VibeStarter doesn’t show your balance: check it on the provider’s website. Five habits make it last longer.
-
One task per agent. Two agents on the same task get in each other’s way and pay twice for the same work.
-
Clear the conversation between tasks. A conversation that keeps all the previous context sends it back with every message.
-
Avoid resuming a conversation that’s several days old. Resuming reloads the whole history and costs a lot; starting over is often cheaper.
-
Don’t switch models in the middle of a conversation, and match the effort level to the task. The maximum level doesn’t improve everything; it just uses more.
-
Use one AI account at a time per agent, and never resume a conversation opened with one account under another account.
The choice of model belongs to the agent’s tool: it’s made with the tool’s own command, not in VibeStarter’s interface. And what the terminal shows — modified files, execution log — costs nothing.
VibeStarter credits are used up
Section titled “VibeStarter credits are used up”VibeStarter credits are not your agent’s quota: they pay for asset generations made by the app’s tools. An agent that writes code uses none of them.
- “AI credits exhausted”: top up with a pack, or wait for the monthly renewal if you have a subscription.
- “You need X more credits”: the server charges image by image. The Top up and Launch N instead buttons avoid starting a batch that would stop partway through.
- “I saved my own key, and it still refuses”: saving the key isn’t enough. Open Settings → Keys & generation, section Who pays for generations, and switch the relevant line to your key: by default, it’s credits. These lines only exist if your account has a subscription or top-up credits you can use; without them, your key is used automatically. Each key covers only one type of generation: Gemini for images, Meshy for 3D models, ElevenLabs for audio. Two operations accept only credits: cutting a 3D model, and the visual AI Studio. Codex, Grok Build and Antigravity draw with their own image tool, so they use neither credits nor a key.
- When a generation fails, the app says so: no credits are charged.
- If you stop waiting for a 3D conversion, it carries on at the generation service and its credits stay committed; the model just won’t be brought back.
The details are in AI credits, in practice.
I closed the app and lost my session
Section titled “I closed the app and lost my session”The Pause button saves each agent’s conversation to your disk: you can resume it later, even after restarting the computer. The Stop button, on the other hand, can’t be undone.
When you come back, the Paused session found banner offers Resume session. While resuming, the app checks that each agent has found its conversation again. Known limit: an OpenCode agent may fail to find its conversation and start over from scratch; the rest picks up where it stopped.
Limits
Section titled “Limits”- VibeStarter doesn’t provide the agents’ intelligence and can’t see your quota balance: the subscription, its limits and its terms belong to your provider.
- There is no way to drive agents from a phone. This feature was removed in version 2.4.5, but it still appears in older videos.
- Game analytics tools are not open to customers’ agents: see Game analytics.
- Agents can’t use your Roblox Studio plugins.