Account Setup Status
The account page is the source of the next safe product step. It combines hosted account sign-in, billing, entitlement, and support posture before VS Code runtime sign-in opens.
VS Code sign-in is ready only after the account launch packet says the paid-use path is ready. Until then, resolve the first account blocker shown by the packet.
Status Map
Section titled “Status Map”| Status | Meaning | Next step |
|---|---|---|
| Sign in required | Probes does not have a verified account session for this browser. | Use the website sign-in entry, then return to the account page. |
| Setup required | Account sign-in exists, but billing or entitlement is not ready. | Open the required billing or entitlement surface shown by the launch packet. |
| Payment pending | Checkout exists but the provider payment or fulfillment state is not complete. | Finish provider payment or refresh billing before continuing. |
| Blocked | Entitlement, quota, payment reconciliation, or safe ops posture blocks runtime setup. | Open the support-safe packet and share only the listed safe fields. |
| Ready | Billing, entitlement, and safe ops posture are ready. | Run Probes: Sign In with Browser from VS Code. |
Launch Packet Fields
Section titled “Launch Packet Fields”Every account surface shows the same launch packet when account context is available:
- the current readiness label
- the paid-use state
- the support-safe ops code
- the next surface to open
- the account steps that explain why that surface is next
- safe support fields when help is needed
The packet can route to Logto, billing, entitlement, support posture, or VS Code. /vscode-auth appears only when account setup is ready.
What Not To Do
Section titled “What Not To Do”Do not try to work around a blocked account state:
- do not use a website page as a VS Code runtime sign-in destination
- do not copy private account or payment details into support messages
- do not use separate desktop handoff tools for runtime access
- do not finish VS Code sign-in through visual code comparison
- do not paste credentials into workspace files, chat prompts, screenshots, or issue reports
The direct product path is VS Code-owned browser sign-in. The browser proves the account, Probes verifies account setup, and VS Code completes runtime access without showing secret material on the website.
Support Escalation
Section titled “Support Escalation”If the launch packet is blocked, share only the visible safe fields:
- readiness label
- visible order number or billing support code
- entitlement status
- support-safe ops code
- queue aggregate status when shown
Never send private account details, payment details, raw logs, source code, private paths, prompts, or hardware captures unless a Probes support engineer gives a separate secure upload path.