Cursor changed the category
Cursor made AI-assisted editing feel practical for more developers. It gave many users their first serious AI editor.
That work mattered. It pushed the whole category forward, even for developers who later moved to other tools.
Why it left Onyx Pro
Onyx Pro supports local AI IDE cleanup. Cursor ended free trials, so Cursor no longer matched the product.
Keeping it would add surface area without a clear user benefit.
The evaluation path changed
When free evaluation ended, the decision became simpler: pay for Cursor directly or choose a different tool.
What stays in Onyx Pro
Onyx Pro stays focused on supported IDEs with clear local behavior.
- Windsurf
- Kiro
- Trae
- Warp
- Antigravity
- Codex
Cursor support is removed so the product stays narrow and predictable.
Why removal was better than a confusing promise
Keeping a page for an unsupported or no-longer-relevant integration would create the wrong expectation. Users would arrive looking for a cleanup path that no longer matched the product, and support would spend time explaining a mismatch that the website could have prevented.
Removing Cursor support also keeps the route map cleaner. Old Cursor URLs redirect to this explanation, while the current product pages point users toward tools that still fit Onyx Pro's local cleanup model.
How we decide what belongs
A supported tool needs a clear local behavior that Onyx Pro can explain, test, and support. If the value depends mostly on vendor-side account changes, remote eligibility, or paid plan logic, it does not fit the cleanup model.
- There must be supported local state to clean up on the user's computer
- The expected side effects must be explainable before install
- The vendor's accounts, credits, subscriptions, and terms must remain separate
- Support must be able to tell users what information helps troubleshoot the integration
What users should do instead
If you use Cursor today, follow Cursor's own account and plan flow. If you are evaluating a tool that Onyx Pro still supports, use the dedicated supported-tool page so you can see the scope, limits, and expected local cleanup behavior first.