MoonshotAI / MoonshotAI/kimi-cli

SearXNG MCP Logs Dumped into TUI on each request

Open
#1,624 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
11.4k
Forks
1.3k
Avg merge
9h 47m
Merged PRs (30d)
2

Description

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?
  1. Install Searxng MCP
  2. Open kimi
  3. [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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue by installing SearXNG MCP, opening Kimi, and triggering a web search, then trace where MCP server logs are forwarded into the TUI. Done means those internal log lines are no longer shown in the main TUI, or are routed to a separate view.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.