Skip to content

feat(minimaxcode): add daily check-in - #575

Open
guyu233 wants to merge 1 commit into
caigee-cmd:mainfrom
guyu233:feat/minimaxcode-daily-checkin
Open

guyu233 wants to merge 1 commit into
caigee-cmd:mainfrom
guyu233:feat/minimaxcode-daily-checkin

Conversation

@guyu233

@guyu233 guyu233 commented Nov 21, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • MiniMax Code now advertises and implements daily check-in for both CN and global regions: account-card status, manual/bulk check-in, check-in history, scheduled auto check-in, and the system default check-in time.
  • Status and claim use the first-party signed /minimax-cloud/api/v1/signin gateway endpoints. Claimable/claimed/skipped states map onto the existing providers.AccountCheckiner contract, including streak and reward reporting.
  • When login has not persisted a MiniMax real user ID, check-in resolves it from /v1/api/user/info and records it as the account remote UID.
  • README (CN/EN) and an unreleased changelog fragment are updated.

Test plan

  • go test ./internal/providers/minimaxcode ./internal/providers ./internal/api ./internal/control ./internal/runtime -run 'Checkin|MiniMax|QwenWork' -count=1
  • go vet ./internal/providers/minimaxcode ./internal/providers
  • go build ./...
  • git diff --check
  • go test ./... (full suite still hits pre-existing Windows-only SQLite file-lock/path failures unrelated to this change)
  • Added changelog/unreleased/minimaxcode-daily-checkin.md
  • No tokens, auth blobs, raw captures, or host details in the diff

Verification scope

The request signature was probed against the live gateway: the signed status request returns 401 invalid access token, not 400 invalid signature, so the yy / x-timestamp / x-signature construction is accepted upstream. A real MiniMax Code account has not yet completed a claim, so live-account acceptance is still pending.

Release gate

Do not release this until the main repository author has merged this PR and confirmed daily check-in works with a live MiniMax Code account (status, claim, reward, and history). This PR is intentionally not release-ready on the strength of unit tests and a signature probe alone.

- registry: advertise check-in for the CN and global regions, with an Asia/Shanghai rollover.
- minimaxcode: implement status/claim against the signed /minimax-cloud/api/v1/signin endpoints, map already/skipped/error, and refresh the token once on 401.
- resolve realUserID from /v1/api/user/info when login did not persist it, so the panel is scoped to the right account.
- tests: status, claim, skip, identity, token refresh, URI encoding, adapter exposure, registry advertising.

Live-account claim acceptance is still pending.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant