Support that tells the truth

Find the fastest support path for Optima Forge without pretending unavailable auth, chat, download, or runtime dependencies are live.

Start with docs

Use setup, API, ForgeBot, and account guides for self-service fixes before opening a support thread.

Open support path

Check runtime status

Review known service, provider, deployment, and telemetry gaps before troubleshooting locally.

Open support path

Review trust and security

Find security, privacy, legal, and compliance context without exposing private account data.

Open support path

Contact support

Open a prefilled email path for account, billing, device, or runtime help.

Open support path

Common honest states

Sign-in unavailable: Clerk keys are not configured for this runtime or the OAuth provider requires owner action.

Download disabled: ForgeOS installers remain locked until real release artifacts are published.

Chat unavailable: provider or Forge API connectivity is blocked, and the UI should show the failure instead of fake success.

Console redirect: protected workspace routes require a signed-in Forge account before device or account state is shown.

Need a human?

Email [email protected] with your account email, affected route, expected outcome, actual outcome, browser, and whether you were using public, signed-in console, chat, download, or device surfaces. Do not include API keys, OAuth tokens, recovery codes, or private device data.

Email support Security disclosure