PRD: [Cody Ignore] Enterprise users cannot use ignored repos as context for Commands

[aramaraju]

Description:

When an enterprise admin has configured Cody to allow/ignore repos, Cody commands, both built-in and custom, must not be available to the user

As a user on an enterprise instance that has Cody allow/ignore repos configured...
P0: I cannot run any Cody commands, both built-in and custom, on any excluded code
P1: I am able to understand that I cannot use commands because the code has been excluded by my administrator
P2: I see guidance in the UX for how to request that my admin include an excluded repo

Objectives:

Cody does not send any code from excluded repos to the LLM when a user is using Cody's commands feature.

Acceptance Criteria:

• When the user selects content in an excluded file and attempts to perform a built-in command operation using the right-click menu, they should not be able to complete the operation
• When the user selects content in an excluded file and attempts to perform a built-in command using the in-line menu, they should not be able to complete the operation
• An appropriate notification is provided saying that these operations cannot be completed because the repo is excluded

Design Tasks:

Design Tasks

Beta Give feedback

1. Add a draft title or issue reference here

Engineering Tasks:

Engineering Tasks

Beta Give feedback

1. Add a draft title or issue reference here

Related Docs:

Cody Ignore and Cody Allow GA PRD
RFC 910: Cody Ignore GA Implementation

[aramaraju]

@taylorsperry Could use some help here as I am not completely clear on the different ways commands can be triggered on JBs?

Additionally, I think it should be an UX decision on whether the operation should be disabled or the operation should run and have an error saying it cannot be completed. I'm fine with either interaction personally (the latter is easier for me)

[dominiccooney]

@aramaraju let's break this up by Edit, Document, Generate Unit Test, Ask Cody to Fix, and Custom Commands because we need to track all of those in detail. (Note, no Custom Commands in JetBrains yet.)

I am not completely clear on the different ways commands can be triggered on JBs?

One of four ways:

Through a context menu:

Sidebar menu:

Keyboard shortcut

Or command palette:

Additionally, I think it should be an UX decision on whether the operation should be disabled or the operation should run and have an error saying it cannot be completed.

+1. Part of why I wanted this issue broken down in detail is so I can map @toolmantim 's design guidance against each item, then go work out what that will take to build.

[dominiccooney]

@aramaraju, @taylorsperry: We should polish this specific issue a bit.

• Is the "built-in" part of this is now handled by PRD: [Cody Ignore] Enterprise users cannot use ignored repos as context for Edit Command #1238, PRD: [Cody Ignore] Enterprise users cannot use ignored repos as context for Document Command #1239, PRD: [Cody Ignore] Enterprise users cannot use ignored repos as context for Generate Unit Test Command #1240, PRD: [Cody Ignore] Enterprise users cannot use ignored repos as context for Explain Command #1241, PRD: [Cody Ignore] Enterprise users cannot use ignored repos as context for Smell Command #1242?
• Do we have a roll-up tracking issue for all of the Cody Ignore work/PRD criteria?
• Do we need an issue for custom commands? This issue could be focused on custom commands specifically. (What are the plans/timing for adding custom commands to the JetBrains plug-in?)

[aramaraju]

@dominiccooney - Yes, I created those additional broken down items for the built-in commands as requested. I'll let @kalanchan chime in on an 'uber' issue for bucketing everything if that helps.

For custom commands, I agree that if there is a ticket for custom commands (my understanding is that it is not in GA scope based on the PRD), we should add the behavior for Cody Ignore under that.

[kalanchan]

closing this in favour of #1238 #1239 #1240 #1241 #1242