fix(copilot): fix state message sent on move to background

[Sg312]

Summary

Ensures the correct message is sent to the agent when a tool is moved to the background

Type of Change

• Bug fix

Testing

Manual

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sim	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 5, 2025 2:23am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
docs	⬜️ Skipped (Inspect)			Aug 5, 2025 2:23am

[greptile-apps]

Greptile Summary

This PR fixes a bug in the copilot system where tools moved to background execution were sending incorrect state messages to the agent. The changes span across multiple components in the copilot architecture to ensure proper state communication and message handling.

The core issue was in the tool confirmation component (tool-confirmation.tsx) where the "Move to background" action was incorrectly mapped to 'rejected' state instead of 'background' state. This caused the agent to receive the wrong message about tool execution status.

The fix includes several coordinated changes:

1. State mapping correction: Fixed the ternary operator logic to properly map 'background' action to 'background' state for both toolState and uiState variables

2. Enhanced notification system: Added executionStartTime parameter to notification functions (notification-utils.ts) to provide temporal context when tools are moved to background, improving the default message generation

3. Workflow execution tracking: Updated the RunWorkflowTool (run-workflow.ts) to capture and store execution timestamps in the context, enabling background notifications to include when execution started

4. Frontend integration: Modified the inline tool call component (inline-tool-call.tsx) to pass execution start time to the backend notification system

5. API payload simplification: Streamlined the notification API structure by consolidating multiple fields (toolName, toolState, stateMessage) into a single message field

The changes also include extensive debug logging in Redis operations (confirm/route.ts and methods/route.ts) to track message handling and identify potential issues with state persistence and retrieval.

This fix ensures that when users move long-running tools to background execution, the copilot agent receives accurate status messages with proper temporal context, improving the overall user experience for background task management.

Confidence score: 4/5

• This PR addresses a clear bug with a focused solution and minimal risk of introducing new issues
• Score reflects well-structured changes across multiple coordinated components with logical flow
• Pay close attention to the notification system changes and Redis logging additions for potential performance impact

_{6 files reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}