Onyx Pro runs locally
Onyx Pro is a desktop app. When you run cleanup, it works on your machine and targets supported IDE data stored on that machine.
It does not change vendor-side accounts, credits, or eligibility. Those stay with the IDE vendor.
What cleanup can change
The goal is simple: remove the local state that can block another evaluation or another account setup on the same computer.
- Trial and onboarding state stored by supported IDEs
- Local sign-in state for the selected tool
- Supported app-state folders and related local records
- The running IDE process if cleanup needs it closed first
What stays out of scope
Onyx Pro does not upload your code, prompts, repositories, or project files. It also does not add credits, change vendor accounts, or override third-party terms.
Why the scope stays narrow
A narrow scope keeps the app predictable. You can tell what it does from the first screen, and the same boundaries apply across the website, app, and legal pages.
That matters because the product is meant to help with supported local trial and onboarding state, not to turn into a broader account manager or hosted service.
Who this is for
Onyx Pro is for people testing supported AI IDEs on their own machine. It gives them a direct cleanup path when local state gets in the way of another run.
- Developers evaluating supported IDEs on one computer
- Users who want a desktop tool instead of manual file cleanup
- People who need a simple explanation before they install
How to prepare before cleanup
Before running cleanup, save work in the selected IDE and let Onyx Pro close the app if it asks. Some local state cannot be changed cleanly while the IDE is running because files, helper processes, or sign-in records can still be active.
After cleanup, expect the selected IDE to behave as if some local setup records were removed. That can mean signing in again, repeating onboarding, or seeing the vendor's normal account and eligibility checks.
What support needs if something fails
The fastest support reports include the operating system, processor architecture, selected IDE, and the result shown inside Onyx Pro. That context makes it easier to separate install problems, activation problems, and cleanup compatibility problems.
- Operating system, such as Windows 11 x64 or Linux DEB ARM64
- Selected IDE and whether it was open when cleanup started
- The exact Onyx Pro result or error message
- Whether the issue is download, activation, cleanup, or post-cleanup behavior
Why local wording matters
The word local is doing real work here. Onyx Pro is not promising to change remote services, grant credits, or alter vendor account decisions. It is promising a focused desktop cleanup path for supported state on the machine where the app runs.
That distinction keeps the product easier to evaluate before purchase and easier to support after install. A user should know the likely side effects before clicking cleanup: the IDE may close, local app state may reset, and vendor systems still decide account access.