benthecarman 521afd9f33 Find Kimi usage for logins to kimi.ai ...

The Kimi CLI keeps one credential slot per deployment. A login to the
global (kimi.ai) deployment writes its token to
credentials/kimi-code-env-<hash>.json and talks to api.kimi.ai, but the
usage source only read credentials/kimi-code.json and only called
api.kimi.com. Users signed in through kimi.ai saw no Kimi usage, or a
"Login expired. Sign in again." message when an old kimi-code.json from
an earlier login was still on disk.

Discovery now checks the slots of both official deployments and picks
the one with the latest expiry, which is the slot the CLI keeps
refreshing. The usage request goes to the API of that deployment.

Kimi access tokens last 15 minutes, so a CLI token is often expired
while the user is still signed in. Report those with refreshedBy so the
Usage page says to run kimi instead of asking for a new sign-in.

2026-11-01 01:03:14 -06:00

..

server

Find Kimi usage for logins to kimi.ai

2026-11-01 01:03:14 -06:00

shared

Find Kimi usage for logins to kimi.ai

2026-11-01 01:03:14 -06:00

icon.svg

feat(usage): usage sources as built-in plugins, following the session's account (#5465)

2026-09-28 16:36:34 +01:00

index.server.ts

feat(usage): show each agent's own plan usage in its context window details (#5975)

2026-10-03 23:12:57 +01:00

paseo-plugin.json

feat(usage): usage sources as built-in plugins, following the session's account (#5465)

2026-09-28 16:36:34 +01:00