Help / safe diagnostics

Support

Prelaunch draft

Last updated July 28, 2026. Written for the current prelaunch product.

Public email is available during prelaunch. Choose the narrowest address below so the request can be handled correctly, and never include credentials or customer workload content.

Contact directory

Start with a safe reference

API responses include an X-Request-Id. A create operation whose upstream outcome is uncertain also includes a safe operation ID. Share those identifiers, the approximate time, the Wildflower API version, the selected provider, and the normalized error code.

Never send secrets or workload content

  • Wildflower API keys or provider credentials.
  • Google ID tokens, session cookies, or CSRF tokens.
  • Commands, environment variables, file paths, or file contents.
  • Sandbox stdout, stderr, or provider-native sandbox identifiers.

If a credential may have been exposed, revoke it with Wildflower or the provider before requesting support.

Useful local checks

  1. Confirm the API health endpoint responds.
  2. Confirm the project API key is active and not expired.
  3. Check provider capability discovery for the requested option.
  4. Retry only when the normalized error says doing so is safe.
  5. Do not automatically retry an uncertain sandbox create outcome.

The status page keeps API and derived analytics state separate. Until the external watchdog is deployed, its feed fails closed as unknown rather than presenting a dated check as live availability.

Product and account help

The console can create and revoke project API keys, sign out browser sessions, and delete an account after its active sandboxes are removed. The documentation covers the shared lifecycle, credentials, provider behavior, and errors.

Security reports

Email support@wildflower.computer with “Security report” in the subject and include only the minimum safe reproduction facts. Do not test against accounts, sandboxes, or infrastructure you do not own or control.