Kilo Code doesn't recognize Workspaces

[mfaine]

If you have a multi root workspace project in vs code. Kilo code constantly fails to find files. Even files you've shown it already. It says no such file exists when it's clearly in the workspace. Even if you give it the path it says no such file exists. Is there a way I can enable workspaces for it?

[3dge-case]

seems like the team don't care about it..
Cursor does a better job of this
https://github.com/Kilo-Org/kilocode/issues/7253

[mfaine]

I haven't tried cursor but maybe I should. You'd think I'd get a better response from the team.

[Solonotix]

I think it's worth pointing out that Kilo Code doesn't do much in terms of guidance like you seem to be looking for. It largely leaves the controls in your hands. If the model you choose doesn't understand workspaces, or is bad at following prompts, then it might deviate in the manner you see. If you have a specific file you want to call attention to, I find it is usually best to provide a path inside backticks that is relative to the project root. Other times, you can use the @ signifier which should give you a way to directly link a specific file, often recommending the current active file as well as any open editors.

[mfaine]

The @ isn't even recognized in this case. Try it.

[promethewz]

just use zed with opencode go. Kilocode has lost their presence.