Agent Status Light

Docs

Activation and service rights

Accounts, activation codes, device binding, and official service rights stay separate from local basic status-light use.

文档

激活和服务权益

账号、激活码、设备绑定和官方服务权益与本地基础状态灯使用保持分离。

Sign in creates the account

Register with email and password, verify your email with a one-time code, or use GitHub OAuth. If GitHub provides a verified primary email, the service can bind it to an existing email account with the same verified email.

登录即创建账号

使用邮箱和密码注册，并用一次性验证码验证邮箱；也可以使用 GitHub OAuth。如果 GitHub 提供 verified primary email，服务可以把它绑定到已有的同邮箱账号。

Activation code redemption

Use the one-time activation code in the desktop app. Sign in, redeem the activation code in the desktop app, bind the connected device, then receive official service rights.

Media to prepare

Screenshot series · account activation and device binding Register, sign in, redeem, and bind with redacted test data

Use redacted test data only; hide email addresses, activation codes, tokens, and complete device fingerprints.

Use it for: Place through account and activation sections so users can follow the sequence without seeing real secrets.

suggested file: docs-activation-redacted-flow
  • Do not use a real activation code, real account email, session cookie, OAuth token, or complete device fingerprint.
激活码兑换

在桌面 app 中使用一次性激活码。先登录，在桌面 app 中兑换激活码，绑定当前连接的设备，然后获得官方服务权益。

待准备素材

截图组 · 账号激活和设备绑定 用脱敏测试数据展示注册、登录、兑换和绑定

只使用脱敏测试数据；遮挡邮箱地址、激活码、token 和完整设备指纹。

用途： 穿插在账号和激活章节，让用户能跟着流程操作，同时看不到真实 secret。

建议文件名： docs-activation-redacted-flow
  • 不要使用真实激活码、真实账号邮箱、session cookie、OAuth token 或完整设备指纹。
Official service rights

Official firmware updates, one-click flashing, and future remote services require an account, activation code, and device binding. Local basic status-light features do not require sign-in.

官方服务权益

官方固件更新、一键刷写和未来远程服务需要账号、激活码和设备绑定。本地基础状态灯功能不需要登录。

Privacy boundary

D1 stores activation code hash, prefix, and metadata, not plaintext. Public and desktop UI does not show the complete device fingerprint, session token, download token, OAuth token, or activation code after redemption.

隐私边界

D1 保存激活码 hash、prefix 和 metadata，不保存明文。公开页面和桌面 UI 不展示完整 device fingerprint、session token、download token、OAuth token 或兑换后的激活码。

Common questions

The current official support boundary is conservative until purchase, replacement, and support flows are fully productized.

  • If the activation code was already redeemed by another account or device, the service rejects reuse; the same account and same device can repeat idempotently.
  • Device replacement needs official support or a future replacement flow; do not assume self-service rebinding exists today.
  • If you use both email password and GitHub OAuth, verified email matching is the safe account-binding path.
  • If email does not arrive, use the newest email, check spam, and retry later; support flow is still being formalized.
  • If GitHub email is unavailable or unverified, continue with email password or email-link login instead of assuming automatic binding.
常见问题

在购买、换绑和支持流程完整产品化前，当前官方支持边界会保守表达。

  • 如果激活码已被其它账号或设备兑换，服务会拒绝复用；同账号同设备重复兑换会幂等成功。
  • 设备更换需要联系官方支持或等待后续换绑流程；不要假设当前已有自助换绑。
  • 如果同时使用邮箱密码和 GitHub OAuth，GitHub 提供 verified primary email 时才是安全绑定路径。
  • 如果收不到邮件，请使用最新邮件、检查垃圾箱并稍后重试；正式客服流程仍在完善。
  • 如果 GitHub 邮箱不可用或未验证，请继续使用邮箱密码或邮箱链接登录，不要假设会自动绑定。