fix(copilot): context filtering

[Sg312]

Summary

Scope copilot context to workflows/kbs/chats from the workspace

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 GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
sim	Ready	Preview	Comment	Aug 28, 2025 6:02am

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Skipped			Aug 28, 2025 6:02am

[greptile-apps]

Greptile Summary

This PR implements workspace-based context filtering for the copilot feature by scoping the @ mention functionality to only show chats, workflows, and knowledge bases from the current workspace. The changes are made to the user-input.tsx component within the copilot panel.

The implementation adds workspace scoping through several key changes:

1. Workspace ID extraction: Uses Next.js useParams hook to extract workspaceId from the URL parameters
2. Chat filtering: Filters chats based on workspace workflows, requiring workflows to be loaded first since chats are associated with workflows rather than directly with workspaces
3. Workflow filtering: Directly filters workflows by workspaceId
4. Knowledge base filtering: Adds workspaceId as a query parameter to the knowledge base API calls

This change integrates well with the existing codebase architecture, as the workflows and knowledge APIs already support workspace-based filtering. The copilot component now follows the same patterns used throughout the application for workspace scoping, ensuring consistent behavior and proper data isolation between workspaces. The implementation maintains the existing user experience while preventing cross-workspace data leakage in the mention suggestions.

Confidence score: 4/5

• This PR addresses a clear security and UX concern with minimal risk of breaking existing functionality
• Score reflects solid implementation following established patterns, though the chat filtering dependency on workflows loading could potentially cause edge cases
• Pay close attention to the chat filtering logic which depends on workflows being loaded before chats can be properly filtered

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}