Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question regarding folder constraints in Vault QA mode #823

Open
AW2307 opened this issue Nov 16, 2024 · 4 comments
Open

Question regarding folder constraints in Vault QA mode #823

AW2307 opened this issue Nov 16, 2024 · 4 comments
Labels
question Further information is requested

Comments

@AW2307
Copy link

AW2307 commented Nov 16, 2024

Hi,

I'm attempting to use folder constraints in vault qa mode. However, the response always contains notes from across the vault.

In chat mode, the folder constraints work as intended.

Could you please take a look?

@logancyang logancyang added the question Further information is requested label Nov 16, 2024
@logancyang
Copy link
Owner

What do you mean by folder constraint?

  • Is it {folder} in custom prompt? If yes, this is by design. {folder} is just a way to pass the things in that folder to the input, the output is still from vault search.
  • Is it "exclusion" or "inclusion" filter? If yes, you have to clear your copilot index first because any "refresh index" does not remove previously indexed files.

@AW2307
Copy link
Author

AW2307 commented Nov 16, 2024

Is it {folder} in custom prompt? If yes, this is by design. {folder} is just a way to pass the things in that folder to the input, the output is still from vault search.

Yes, that's it.

May I ask why by design the folder constraint is not available in vault qa mode? Since it seems to be working in chat mode.

Basically I would like to accomplish two things:

  • use only notes from specific folder/s as context
  • see the specific notes that were used to generate a response to my prompt

Is there any way to accomplish this?

Thx by the way for a really useful plugin.

@logancyang
Copy link
Owner

logancyang commented Nov 16, 2024

@AW2307 I see. Vault QA (basic) is a mode that searches the entire indexed context - the whole vault by default. {folder} is just a template that passes whatever notes into your input, so Vault QA mode uses your extremely long input to search the entire vault.

To achieve your goal, you have 2 options

  1. Use a long-context model in chat mode
  2. Use the inclusion filter in Vault QA mode, and only index those folders you want as context. Keep in mind that you have to run Copilot command "Clear vector store" first, set the inclusion filter correctly, and trigger a new round of indexing. Any of your previous index will be overwritten, so beware.

There's a "Project-based context" FR in the open issues and that will avoid the need to reindex and overwrite the whole index.

@AW2307
Copy link
Author

AW2307 commented Nov 16, 2024

Thanks for explaining.

The context in most of the folders I'd like to use is too large to use it in chat mode, so this leaves only the reindexing option.

Project-based context would be super useful! I strongly support that feature request

@AW2307 AW2307 changed the title Folder constraint is ignored in Vault QA mode question regarding folder constraints in Vault QA mode Nov 16, 2024
@AW2307 AW2307 changed the title question regarding folder constraints in Vault QA mode Question regarding folder constraints in Vault QA mode Nov 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants