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

Inconsistent passing of local file context #5166

Open
garrmark opened this issue Feb 14, 2025 · 6 comments
Open

Inconsistent passing of local file context #5166

garrmark opened this issue Feb 14, 2025 · 6 comments
Assignees
Milestone

Comments

@garrmark
Copy link

I filed this in the tech preview feedback for copilot extensions, but it was suggested that it might be better addressed here.

copilot-extensions/user-feedback#24

Thanks.

@vs-code-engineering vs-code-engineering bot added the triage-needed Issues needing to be assigned to the prospective feature owner label Feb 14, 2025
@isidorn isidorn assigned isidorn and unassigned ulugbekna Feb 14, 2025
@isidorn isidorn removed the triage-needed Issues needing to be assigned to the prospective feature owner label Feb 14, 2025
@isidorn isidorn added this to the Backlog milestone Feb 14, 2025
@garrmark
Copy link
Author

garrmark commented Feb 18, 2025

let me know if you need more info @isidorn , thanks.

also, any tips on getting me unstuck, are there cache files I can clear somewhere etc.?

@isidorn
Copy link

isidorn commented Feb 18, 2025

@roblourens might be able to help

But I am curious if you tried extending Copilot via a VS Code extension locally? With that flow I will be able to help more.

@garrmark
Copy link
Author

I haven't tried that route, but I can explore that more if necessary. Thanks.

@roblourens
Copy link
Member

Sounds like this is with attaching context to a remote copilot extension

@garrmark
Copy link
Author

Correct

@garrmark
Copy link
Author

I've put my work on hold and have switched over to using https://github.com/modelcontextprotocol/servers instead to achieve my goals, I hope I can pursue this further when it's fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants