Skip to content

Conversation

@jokemanfire
Copy link

Motivation and Context

I want to clear the history while the data is too much.
Like this:
image

How Has This Been Tested?

Yes

Breaking Changes

No

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

@cliffhall
Copy link
Member

cliffhall commented Jul 2, 2025

Hi @jokemanfire!

I'm not certain there's a good reason for this, given the scope of this tool.

@jokemanfire
Copy link
Author

Hi @jokemanfire!

I'm not certain there's a good reason for this, given the scope of this tool.

Hi, In my opinion , inspector as a testing tool, especially after multiple tests, there will be a lot of historical records. I prefer having a clear button for clearer testing.

@cliffhall
Copy link
Member

Hi @jokemanfire!
I'm not certain there's a good reason for this, given the scope of this tool.

Hi, In my opinion , inspector as a testing tool, especially after multiple tests, there will be a lot of historical records. I prefer having a clear button for clearer testing.

After every disconnect / connect sequence, the history is already being cleared. It is a stack with the most recent item on top, so prior items are not in the way of anything. And this button takes up an extra line at the top of that that box, which pushes the data further down. The server notifications stack to the right operates the same way.

I do not see the usefulness of this button.

@cliffhall cliffhall closed this Jul 3, 2025
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.

2 participants