Skip to content

chore(ui): remove debug console.log from core components, fix 2 log levels#7882

Closed
jeffa-block wants to merge 2 commits intoblock:mainfrom
jeffa-block:jeffa/cleanup-debug-logs-core
Closed

chore(ui): remove debug console.log from core components, fix 2 log levels#7882
jeffa-block wants to merge 2 commits intoblock:mainfrom
jeffa-block:jeffa/cleanup-debug-logs-core

Conversation

@jeffa-block
Copy link
Copy Markdown
Contributor

Why

Core UI components contain debug console.log statements that trace internal state to DevTools. Two of these are misclassified — errors logged as console.log instead of console.error/console.warn.

What

Changes across 7 files:

File Change Detail
ConfigContext.tsx console.logconsole.error Extension list fetch error was silently logged at info level
AnnouncementModal.tsx console.logconsole.warn Expected announcement load failure was logged at info level
ModelAndProviderContext.tsx Remove Fallback provider check trace
ChatInput.tsx Remove 'No model or provider found' trace
useCostTracking.ts Remove Model change tracking trace (7 lines)
McpAppRenderer.tsx Remove MCP app notification forwarding trace (4 lines)
recipe/index.ts Remove Deeplink decode trace

How to review

7 files, 4 insertions (log level fixes), 16 deletions. The two log level corrections improve signal quality — actual errors now surface at the correct severity.

Testing

  • npm run build in ui/desktop — no compile errors
  • Manual: verify chat, recipes, MCP apps, and model switching still work

Remove debug logging from 7 core UI files:

- ConfigContext.tsx: upgrade misclassified console.log to console.error
  for extension list fetch errors
- AnnouncementModal.tsx: upgrade console.log to console.warn for
  expected announcement load failures
- ModelAndProviderContext.tsx: remove fallback check trace
- ChatInput.tsx: remove 'No model or provider found' trace
- useCostTracking.ts: remove model change tracking trace
- McpAppRenderer.tsx: remove MCP app notification forwarding trace
- recipe/index.ts: remove deeplink decode trace

Two log level corrections (log→error, log→warn) improve signal quality.
All other console.error/warn calls preserved.
@DOsinga
Copy link
Copy Markdown
Collaborator

DOsinga commented Mar 26, 2026

Squashed into #8142

@DOsinga DOsinga closed this Mar 26, 2026
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