improvement(copilot): tool dependency errors show as skipped

[Sg312]

Summary

Tool dependency errors now show as skipped instead of errored

Type of Change

• Other: ui update

Testing

Manual testing

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 4, 2025 10:19pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
docs	⬜️ Skipped (Inspect)			Aug 4, 2025 10:19pm

[greptile-apps]

Greptile Summary

This PR improves the user experience in the copilot tool execution system by changing how dependency-related failures are handled. Previously, when tools failed due to missing dependencies (like API keys or required connections), they would display as "errored" which implied a system failure. Now, when a tool fails with the exact error message "skipped", it's treated as a "rejected" state instead of "errored".

The changes are implemented consistently across three key components:

1. RunWorkflowTool (run-workflow.ts): Modified to check if the error message equals "skipped" and set the target state to "rejected" instead of "errored"
2. Copilot Store (store.ts): Enhanced the handleToolFailure function and SSE handler to distinguish between skipped and errored states, with added debugging logs
3. Inline Tool Call (inline-tool-call.tsx): Updated client-side tool execution to apply the same skipped vs errored logic

This change leverages existing infrastructure - the tool metadata already defines a "rejected" state with display name "Skipped workflow execution" and a skip icon. The modification ensures that dependency-related skips are visually distinguished from actual errors, providing clearer feedback to users about why a tool didn't execute and whether action is needed on their part.

Confidence score: 4/5

• This PR is safe to merge with minimal risk as it only changes UI state representation without affecting core functionality
• Score reflects well-contained changes that improve user experience without introducing breaking changes or complex logic
• Pay close attention to the store.ts file due to its central role in state management and the addition of debugging logs

_{3 files reviewed, 3 comments}

_{Edit Code Review Bot Settings | Greptile}