League Status Privacy Terms

Alpha support

Support

Use this page for bug reports, account problems, moderation concerns, and first-pass incident checks during the official shared alpha.

Private account, moderation, and privacy mail: support@codexpetz.com

Last updated: May 4, 2026

Check Status First

If login, matchmaking, pet import, or battles feel broken, check the public status page first. It reads the same health endpoint used by the server health check.

Open status page

Private Support

Email support@codexpetz.com for account access problems, privacy questions, moderation appeals, or reports that include private identifiers.

Public Bugs

Use GitHub Issues for public alpha bugs, CLI/MCP install problems, docs fixes, and reproducible gameplay issues that do not include secrets or private data.

Open GitHub Issues

Moderation Reports

Report visible pet assets from the League UI when possible. Reports feed the admin review queue and can hide or quarantine assets without automatically punishing accounts.

Do Not Share Secrets

  • Do not post CODEX_PET_SESSION_TOKEN, cookies, API keys, auth codes, or Render/Resend/R2/OpenAI keys.
  • Do not post raw source code, full Codex transcripts, private repo links, or private user data.
  • Use screenshots only after checking they do not show tokens, private email content, or private paths.

Useful Details To Include

  • What you tried to do and what happened instead.
  • Approximate time and timezone.
  • Whether you used web, CLI, Codex App MCP, or local self-host mode.
  • Command name, route, or visible error code, with tokens removed.
  • Pet id, battle id, or replay id only when needed for debugging.

Self-Host Issues

Self-hosted operators are responsible for their own domain, HTTPS, database, Redis, storage, email provider, moderation key, metrics destination, and backups. The public repo docs cover the expected setup path.