Create the account layer
Sign in once and keep projects, billing, usage, and support under one identity instead of scattering them across tools.
Guide
Start quickly, then keep the product loop tight.
The shortest path from a new account to a useful coding session, without turning setup into its own side quest.
Core flow
The product should make the first useful session obvious.
Open the desktop workspace
Start a thread, explain the outcome, and let ClastX inspect the current context before it changes code or config.
Watch the work happen
Follow the files, commands, checks, and summaries while the task is moving instead of waiting for one final response.
Review and ship
Use the preview, summary, and checks to verify behavior before moving on or publishing anything.
Prompt shape
Clear requests speed the agent up without forcing perfect specs.
The best starting prompt is simple: say what changed, where it hurts, what ClastX can do next, and how you will judge the result.
01
What changed or what is broken
02
Where the problem lives in the product
03
What ClastX is allowed to do next
04
How you will judge the result
Better requests
Clarity makes the workspace faster.
You do not need a perfect specification. A clear result, useful context, and a visible success condition are enough to begin productively.
- Ask for one concrete outcome at a time.
- Include the route, page, file, or visible error that matters.
- Say what success should look like when the change is done.
- Let ClastX run checks before you accept the work.