Skip to content

fix(kimi-web): align health probe with executor domain - #11521

Merged
diegosouzapw merged 1 commit into
diegosouzapw:release/v3.8.51from
pacocartones:fix/11515-kimi-web-health-domain
Aug 25, 2026
Merged

diegosouzapw merged 1 commit into
diegosouzapw:release/v3.8.51from
pacocartones:fix/11515-kimi-web-health-domain

Conversation

@pacocartones

@pacocartones pacocartones commented Aug 25, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • validate kimi-web sessions against www.kimi.ai, matching the executor
  • align Origin/Referer and re-login guidance with the international domain
  • add focused regression coverage for endpoint, headers, and auth errors

Fixes #11515

Verification

  • focused validation tests: 37/37 pass
  • core typecheck: pass
  • live unauthenticated probe confirms https://www.kimi.ai/api/user exists and returns the expected 401 boundary

Note

The touched source file has two pre-existing unused-variable lint findings (addModelsSuffix, parseError); this patch introduces none.

@diegosouzapw
diegosouzapw merged commit 987b674 into diegosouzapw:release/v3.8.51 Aug 25, 2026
7 of 16 checks passed
muhamadgalihsaputra pushed a commit to niyatna/NiyatnaRoute that referenced this pull request Sep 27, 2026
…11521)

Validated in a combined 10-PR batch worktree off release/v3.8.51 tip. Fixes diegosouzapw#11515.
- Focused test: tests/unit/kimi-web-validation-11515.test.ts — 37/37 pass; live unauthenticated probe confirms www.kimi.ai/api/user returns the expected 401 boundary
- typecheck:core, file-size, changelog-integrity, complexity, cognitive-complexity gates — all OK
- Full-repo lint: 503 pre-existing problems confirmed identical on the pure release/v3.8.51 tip — unrelated to this diff

⚠️ base-red inherited: diegosouzapw#11449

Thanks for aligning the health probe with the executor's actual domain plus the live verification.
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.

[bug] kimi-web health check validates against kimi.com while executor uses kimi.ai — false-negative gates connection

2 participants