# Get help > Public channel — documentation of app 3.6.3. Follow the availability notices of each service. Source: [Get help](/en/aide/) Three different parties run your game: VibeStarter, Roblox Studio and the provider of your AI agent. Each has its own support, and none of them handles incidents from the other two. This page helps you find the right contact, then write to them once with the right details. ## Find an answer quickly The [search of the documentation](/en/aide/recherche/) accepts words from your problem, such as “Studio won’t connect,” “agent” or “backup.” In the 3.6.0 app, the **Documentation** button stays available in the top bar. The Studio connection, agent connection and Cloud backup screens also offer a link to their guide. You can ask your agent to read the official documentation. It has tools to search for and read the published pages, with no setup on your part. Ask it for the link to its source, and check that the instructions match your version of the app. The documentation describes how things are meant to work; on its own, it does not prove the cause of a problem on your computer. If it is unavailable or does not answer your question, support is still available. ### Have an outside assistant read the pages You can give your assistant [the index of the official website](https://vibestarter.pro/llms.txt) or [the index of this documentation](/en/llms.txt). They point to Markdown versions that can be read without menus or scripts: overview, pricing, system requirements, support and legal texts for the website; guides for the app and the services for the documentation. For example, [the website home page](https://vibestarter.pro/en/index.md), [the pricing](https://vibestarter.pro/en/pricing.md) and [the full Terms of Service](https://vibestarter.pro/en/terms.md) are available in Markdown. The pricing page includes the Solo and Duo variants when they are offered on the website. In the documentation, add `index.md` to the URL of an article ending with `/`, like [this help page](/en/aide/index.md). Each file points back to its reference page. These texts are derived from the public pages. The website is re-read on request, with a cache that can last five minutes; the documentation is regenerated with each publication. Ask your assistant to read the relevant pages and to cite its sources: it does not necessarily find them on its own. The labels **Coming soon**, **Pilot** or **Beta**, the dates of the legal texts and the app version still need to be checked. Your account pages, your payments, the reserved training and administration are not exported. Videos and interactive demonstrations are not transcribed. For a problem happening right now, check [the status of the services](https://vibestarter.pro/en/status): the Markdown text of this page does not contain live measurements. ## Where does the problem come from? Decision tree: depending on the symptom you see, the problem comes from VibeStarter, from Roblox Studio or from your agent's AI provider. — Something is not working — VibeStarter — The app does not open, stays — blank, the cloud backup gets — stuck or the credits are stuck — Roblox Studio — Studio lags or closes, a — place refuses to link, the — publish is rejected — Your AI provider — The agent does not connect, — reports a quota reached or — stops writing — The troubleshooting pages — below, then VibeStarter — support — The Roblox documentation — and Roblox support — The website of your agent’s — provider: Anthropic, — OpenAI, xAI, Google… The symptom you see points to the party involved. VibeStarter can do nothing about a Roblox incident or about the quota of your AI account. Three landmarks help you decide quickly. - Agents run on **your** AI account, never on VibeStarter’s servers. A refused connection, an exhausted quota or an empty reply comes from your provider. - The `VibeStarter Sync` plugin is placed by the app at each start. If it is missing in Studio, restarting Roblox Studio loads it, with no setting to turn on. - The status page only covers VibeStarter services. An outage at Roblox or at an AI provider will never appear there: see [Check the status of the services](/en/aide/etat-des-services/). ## Who do I talk to? Routing: a bug goes to the members-only Discord, an account or purchase question goes by e-mail, a how-to question is answered in the documentation. — My request is about… — A reproducible bug, — with steps — My account, a purchase, — an invoice, an access — How to do something — in the app — Discord member — signaler-un-bug channel, — private ticket — support@vibestarter.pro — with the e-mail used — at purchase — This documentation — then peer help on the — Discord Two channels, depending on the kind of request. The third is peer help, with no individual answer guaranteed. | Your request | The channel | | --- | --- | | A bug in the app | signaler-un-bug channel on the members-only Discord | | Account, sign-in, devices | [support@vibestarter.pro](mailto:support@vibestarter.pro) | | Declined payment, cancellation, refund within 14 days | Your account area, Purchases and payments tab | | Invoice, access not unlocked, other purchase question | [support@vibestarter.pro](mailto:support@vibestarter.pro) | | Usage question, peer help | This documentation, then the Discord | | Exercising your rights over your data | [support@vibestarter.pro](mailto:support@vibestarter.pro) | | Reporting content | The form at `vibestarter.pro/signaler-un-contenu` | The page [vibestarter.pro/support](https://vibestarter.pro/en/support) brings these channels together, with the buttons that lead to them. The response time we announce is **five business days**, in French or in English. The Discord, for its part, is run by the community: no individual answer is guaranteed there. The members-only Discord opens when you link your Discord account from your account area on the website: the bot lets you in, there is no invitation to request. The public Discord is open to everyone. Both are described in [The VibeStarter Discord community](/en/communaute/discord/). “Contact support from Settings” When a message in the app sends you to support, use the channels above. ## The report kit Five items are requested with every report. Gathering them before you write avoids a back-and-forth that can take several days. 1. The app version. 2. Your system and the amount of RAM in the machine. 3. The result of the virtualization test. 4. The exact steps that reproduce the problem. 5. The error message, copied word for word. If the app opens, the **Hardware** step of the first-time setup contains the Copy diagnostics button, which puts the complete state of the machine on the clipboard. For the files to attach, see [Find your logs and report a bug](/en/aide/journaux/). ## Open a bug ticket 1. In the members-only Discord, open the signaler-un-bug channel. No one writes in this channel: it only contains a panel with a button. 2. Click Report a bug. A private triage screen asks two questions, then offers Yes, it’s a bug or No, it’s a question. The second answer does not create a ticket and points you to the question channels. 3. Fill in the form: title, exact steps (60 characters minimum), what you expected and what you got, the app version, and the error message. 4. A private thread opens, visible only to you and the team. This is where you add your screenshots and your logs, never in the channel. 5. Only one ticket can be open at a time. Close yours with Close ticket when it is resolved. ## What support does not cover - The BIOS, UEFI, drivers and firmware, and the system instability that follows from them. - Third-party AI providers and their terms: you remain responsible for following their rules and their limits. - Roblox: your Roblox account, the moderation of your games and the platform’s rules. ## The troubleshooting pages [Frequently asked questions](/en/aide/faq/)The thirty questions customers ask most, with the short answer and the page that details it. [The app does not start](/en/aide/demarrage/)Blank screen on Windows, virtualization, environment that refuses to start. [I can't sign in](/en/aide/connexion/)The sign-in link, the two-device limit, network errors. [The connection to Roblox Studio does not work](/en/aide/studio/)The plugin that does not attach, the place not recognized, sync stopped. [My agent does not respond, or my quota is draining](/en/aide/agents/)Agent connection, full memory, provider quota and VibeStarter credits. [Find your logs and report a bug](/en/aide/journaux/)The exact path for each system, what the files contain, what to attach. [Check the status of the services](/en/aide/etat-des-services/)The status page, what it monitors and when to check it. ## Go further - [Close your account and understand the remaining payments](/en/aide/fermer-son-compte/): review, erasure and follow-up without an account. - [Invoices and refunds](/en/offres/factures-et-remboursement/): your payments and refunds are tracked in your account; ask support for an invoice. - [Pay a declined payment and get your access back](/en/aide/paiement-refuse/): the payment button is in your e-mails and in your account. - [Your account and your data](/en/offres/compte-et-donnees/): export, deletion, rights. - [Ten misconceptions about VibeStarter](/en/decouvrir/idees-recues/): half of the reported “bugs” are misunderstandings about what the app does.