Answers people should not have to dig for.

ClastX is a coding workspace with a public website around it. The website handles trust, pricing, docs, downloads, and support, while the desktop app handles the actual coding work.

Because local file access, command execution, update prompts, and project controls belong in the installed app instead of on the public website.

Yes. The website should handle account, billing, docs, support, and downloads even when the real coding workspace stays in the desktop product.

Each paid plan should come with a clear monthly allowance, visible usage limits, and a protected server-side billing check before paid AI work runs.

Go to Billing and use the dedicated cancel plan action. That opens the secure provider flow so you can stop renewal properly instead of hunting through settings.

The expected behavior is that renewal stops while access continues through the end of the current paid period unless the billing provider says otherwise.

No. Paid access should only come from real purchase and entitlement state, not from a default UI value or a fake local preview assignment.

ClastX should stop paid AI usage before surprise charges happen, then offer a clear upgrade or top-up path.

That is part of the intended product direction: users should see clearer activity states such as reading files, checking the app, or running commands instead of one vague loading message.

Use the Support page for account, billing, or product help, or email support@clastx.com with the page, expected behavior, actual behavior, and any visible error.