Opt-in public profile and personal usage rank on top of anonymous telemetry #8372

Area

Multiple areas

What are you trying to accomplish?

As an opencodex user who already shares anonymous daily usage telemetry, I want to choose to join a public usage leaderboard: see where my own token and request usage ranks over the last day, week and month on the dashboard Home and at https://opencodex.me/dashboard, the way tokscale (https://github.com/junhoyeo/tokscale) lets its users submit usage and see a public rank.

What prevents this today?

Telemetry is anonymous by design. Each report carries only a per-day install hash, and the public dashboard shows only project-wide aggregates. There is no way to opt in to a profile, and no personal rank or leaderboard.

What should OpenCodex do?

• While anonymous telemetry is on, the dashboard Home shows a "Public profile & rank" card. Nothing is connected by default.
• A person explicitly connects a public profile with a chosen handle, display name and avatar colour. A human dashboard session or an interactive terminal is required; agents are refused. No e-mail is asked for or shown.
• The collector issues a secret. Once a day the proxy sends only that day's totals for the profile: requests, token buckets and model-family totals. It never sends prompts, outputs, keys, account ids, provider names, URLs or paths, and never sends the anonymous install id or install-day hash.
• The card and opencodex.me/dashboard show rank, tokens, requests and model families for day/week/month. A public leaderboard lists only opted-in profiles with minimal fields.
• Disconnecting, from the card or with ocx telemetry profile disconnect, deletes the profile and all its rows on the collector. Turning anonymous telemetry off pauses profile submissions without changing the profile, and connecting a profile never changes the telemetry decision.

Example usage or interface

ocx telemetry profile connect --handle jun --name "Jun" --avatar blue
ocx telemetry profile status --json
ocx telemetry profile disconnect

Public endpoints (collector): GET /v1/leaderboard?period=week&metric=tokens, GET /v1/profiles/by-handle/jun.

Alternatives or workarounds

Use a separate tool such as tokscale, which reads local session logs and uploads broader metadata (devices, session timing, MCP server names). GitHub device-flow login was considered for identity; it needs a maintainer-created OAuth app, so it is a follow-up.

Additional context

Builds on the telemetry stack #8300, #8348, #8303, #8304, #8305 and #8308. Design notes: devlog/_plan/261109_telemetry_personal_rank/. The collector deploy remains a maintainer step.

Checks

• I searched existing issues and documentation.
• This request describes a concrete OpenCodex workflow rather than merely naming a desired technology.
• I removed secrets and personal data.