What version of Kimi Code CLI is running?
1.27.0
Which open platform/subscription were you using?
/setup
Which model were you using?
any
What platform is your computer?
MacOS
What issue are you seeing?
Each time kimi calls SearxNg MCP there is 4-5 lines of MCP internal logs dumped into TUI
[03/28/26 08:29:23] INFO Server log: meta=None level='info' logger=None data={'message': 'MCP SearXNG Server v0.10.0 connected via STDIO logging.py:40
'}
INFO Server log: meta=None level='info' logger=None data={'message': 'Log level: info'} logging.py:40
INFO Server log: meta=None level='info' logger=None data={'message': 'Environment: development'} logging.py:40
INFO Server log: meta=None level='info' logger=None data={'message': 'SearXNG URL: http://.....'} logging.py:40
What steps can reproduce the bug?
- Install Searxng MCP
- Open kimi
- [optional] trigger some web-searches (to see more of that)
What is the expected behavior?
No MCP logs are visible inside TUI, or there is a separate view for that
Additional information
No response
What version of Kimi Code CLI is running?
1.27.0
Which open platform/subscription were you using?
/setup
Which model were you using?
any
What platform is your computer?
MacOS
What issue are you seeing?
Each time kimi calls SearxNg MCP there is 4-5 lines of MCP internal logs dumped into TUI
What steps can reproduce the bug?
What is the expected behavior?
No MCP logs are visible inside TUI, or there is a separate view for that
Additional information
No response