Account and VS Code Sign-In

Probes uses a browser account session for account proof and a VS Code-owned browser sign-in flow for runtime access.

The important boundary is simple: the website prepares account, billing, entitlement, and support state; the VS Code extension finishes runtime access inside VS Code.

Account Path

1. Start from the Probes website or run Probes: Sign In in VS Code.
2. Complete the browser account session.
3. Let the account center confirm billing, entitlement, and support readiness.
4. Return to VS Code and start the extension browser sign-in flow.
5. Continue only after VS Code shows the signed-in state.

Why VS Code Finishes Sign-In

Runtime access belongs to the developer tool. It should not be shown on a website page, copied through chat, pasted into settings, or handled by a separate desktop handoff.

The extension-owned browser sign-in flow gives users the normal hosted account experience while keeping runtime access inside VS Code.

Browser completion pages are status pages only. They do not display private account details, runtime access material, or extra codes for users to compare.

Website Responsibility

The website helps you reach a ready account state:

• account session confirmation
• billing and order continuity
• entitlement and quota visibility
• support-safe status when setup is blocked
• a clear next action when VS Code sign-in is ready

If the account center does not show a ready state, resolve that account step first. VS Code sign-in is the final runtime setup step, not a replacement for billing, entitlement, or support readiness.

Credential Handling

Keep account and runtime access material out of public places:

• do not share them in issue reports
• do not include them in screenshots
• do not paste them into chat prompts
• do not store them in workspace files

Use the extension sign-in and sign-out commands to manage local runtime access.