Context provider "Active file" (ex Alt+Enter) doesn't work for unsaved files

[Astlaan]

Before submitting your bug report

• I believe this is a bug. I'll try to join the Continue Discord for questions
• I'm not able to find an open issue that reports the same bug
• I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: Windows
- Continue version: v0.8.55
- IDE version: VS Code 1.95.1

Description

ContextProvider for active file (ex. when submitting prompt about the file in Chat with Alt+Enter) doesn't work for unsaved files. This happens despite the UI saying that it has been passed as context, however it is seen as an Object content, not visible by the model.

This is the behaviour I get:

I haven't tested if this is also the case for the Quick Edits (Ctrl+I) since my Ctrl+I isn't working due to another bug (#2346 , #2346 (comment) ).

To reproduce

1. Open a new file, write some stuff, but don't save to disk
2. Open Chat, make a query about the file, add the active file as context with Alt+Enter

Log output

No response

[sestinj]

Thanks for bringing this up @Astlaan. My guess is that the solution to #1226 will be the same as for this, and it's something we plan to fix later this week

[RomneyDa]

Looks like it does check open text document case here

continue/extensions/vscode/src/VsCodeIde.ts

Lines 450 to 457 in 885e7c1

	private async _searchDir(query: string, dir: string): Promise<string> {
	const p = child_process.spawn(
	path.join(
	getExtensionUri().fsPath,
	"out",
	"node_modules",
	"@vscode",

Wondering if path issue, will debug

[RomneyDa]

just for clarity it does work for unsaved files that already exist, just not for brand new unsaved files like in @Astlaan's case

[RomneyDa]

Fixed by #2841

[Astlaan]

just for clarity it does work for unsaved files that already exist, just not for brand new unsaved files like in @Astlaan's case

Yes, sorry, could have been clearer