feat: add toggleable tool source diagnostics#1825
Draft
DuyPrX wants to merge 2 commits into
Draft
Conversation
bloodf
pushed a commit
to bloodf/9router
that referenced
this pull request
Jun 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
[TOOLS]diagnostic line can be enabled only when needed.Why
Tool-heavy agent clients can send many built-in, hosted, and MCP tools. A compact source summary is useful when diagnosing routing/model behavior, but always-on tool logs make normal request logs harder to read. This keeps the diagnostic available while leaving it off by default.
Testing
node --check src/sse/handlers/chat.jsnode --check src/lib/db/repos/settingsRepo.jspnpm exec next build --webpackOpened as draft so maintainers can decide whether this belongs in profile settings or another diagnostics area.