MoonshotAI / MoonshotAI/kimi-cli
AuthlibDeprecationWarning from fastmcp dependency
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11.4k
- Forks
- 1.3k
- Avg merge
- 9h 47m
- Merged PRs (30d)
- 2
Description
AuthlibDeprecationWarning from fastmcp dependency
Environment
- Kimi CLI version: 1.37.0
- Python version: 3.13
- OS: Linux
- Installation method:
uv tool install kimi-cli
Problem
When running Kimi CLI, the following deprecation warning appears on every invocation:
/home/nenglab/.local/share/uv/tools/kimi-cli/lib/python3.13/site-packages/fastmcp/server/auth/providers/jwt.py:10: AuthlibDeprecationWarning: authlib.jose module is deprecated, please use joserfc instead.
It will be compatible before version 2.0.0.
from authlib.jose import JsonWebKey, JsonWebToken
Root Cause
The warning originates from fastmcp (a dependency of kimi-cli), which still imports from the deprecated authlib.jose module. This affects:
fastmcpversions tested: 2.12.5, 2.14.7, and 3.2.4 (latest)- All versions still use
from authlib.jose import JsonWebKey, JsonWebToken
Impact
- Cosmetic issue: warning clutters terminal output
- No functional breakage yet, but
authlibhas announced removal before v2.0.0
Possible Solutions
- Short-term: Suppress the warning in kimi-cli startup by setting
PYTHONWARNINGS=ignore::AuthlibDeprecationWarning - Medium-term: Pin or patch
fastmcpto migrate fromauthlib.josetojoserfc - Long-term: Wait for upstream
fastmcpto fix (issue should also be reported togithub.com/jlowin/fastmcp)
Steps to Reproduce
- Install kimi-cli via uv:
uv tool install kimi-cli - Run any kimi command:
kimi --versionor start an interactive session - Warning appears immediately during module import
Related
- authlib upgrade guide: https://docs.authlib.org/en/v1.7.0/upgrades/jose.html
- fastmcp repository: https://github.com/jlowin/fastmcp
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the warning with uv tool install kimi-cli and kimi --version, then inspect the dependency metadata and the fastmcp JWT provider mentioned in the traceback. Determine whether an upstream fix is available; done means the warning no longer appears during normal Kimi CLI invocation without hiding unrelated warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100