Feat: Remove traditional code-review system in favor of deep-debugger and user prompt #202
Conversation
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
…at/code-review-simplification
- Updated bootstrap completion logic to only show messages for new chats, not reloaded ones - Enhanced message display to properly show "thinking" states with separate rendering logic - Improved websocket reconnection handling by clearing old messages to prevent duplicates - Reorganized message display order to group thinking states and regular messages separately - Removed unnecessary tool events and status messages for cleaner conversation
- Added error recovery for aborted inference calls by showing partial response transcript - Updated debug message bubble display logic to only show when there are tool calls - Fixed stop generation button to properly reset debugging state - Enhanced error handling in code debugger to capture partial responses from InferError - Added serializeCallChain utility to format partial response transcripts with last 5 messages - Modified inference
- Replaced fixed MAX_TOOL_CALLING_DEPTH with configurable depth limit based on agent action type - Added getMaxToolCallingDepth function to allow higher recursion depth (100) for deepDebugger agent - Updated error handling to use AbortError with more descriptive messages for depth limit exceeded - Enhanced logging to include agent action key in tool calling depth messages - Changed default tool calling depth constant name to MAX_TOOL_CALLING_
- Added deep debug session state tracking and restoration to preserve debugging context across page reloads - Improved deep debugger prompts to enforce single call per conversation turn limit - Added UI feedback for active debug sessions with placeholder message and status indicators - Fixed potential race conditions in debug session cleanup by properly tracking conversationId - Updated websocket types to include deep debug session state in conversation
- Added git tool with commands for commit, log, show, revert, and checkout operations - Updated FileManager to support staging files without immediate commit - Enhanced code debugger prompt with git usage guidelines and best practices - Added logging for partial response transcripts in error handling - Modified system prompt to emphasize Cloudflare Workers and extremely high reasoning capability - Added automatic file staging after regener
Feat: improve code-deep-debug tooling, behavior + git reset
feat: improve chat message handling and reconnection flow
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.
This should fix the common UX pain point of code review cycles taking too long and being black-box, unintuitive.
Code deep debugger is an agent which shall fix the app akin to agentic code assistants like windsurf/cline.