deep-debug

Status : Production Ready Last Updated : 2026-02-03 Dependencies : Chrome MCP tools (optional), debugger agent, code-reviewer agent Or invoke naturally: For browser-related bugs , use Chrome MCP tools: For backend bugs , gather: Launch these agents simultaneously with the gathered evidence: After agents complete, look for: After implementing the fix, re-gather the same evidence to confirm: Network tab showed 2 fetch requests for the same message. sendMessage useCallback had state.messages in dependency array. Every state update recreated the callback, causing duplicate calls during React re-renders. Use stateRef to access current state without including in dependencies: - Going in circles - You've tried multiple fixes but nothing works - Browser + API interaction bugs - Need to see Network tab, console logs - Symptoms don't match expectations - Something deeper is wrong - Complex state management bugs - React hooks, closures, race conditions - "I'm stuck on this bug, can you do a deep investigation?" - "This bug is resisting normal debugging" - "I need you to really dig into this" - Error logs and stack traces - Request/response payloads - Database query logs - Timing information - Network tab shows expected behavior - Console has no errors - State updates correctly - state in useCallback dependencies causing recreation - Missing dependencies causing stale closures - useEffect...