Option to associate conversations with specific projects

[TiagoTiago]

Would be nice to be able to filter conversations by which project (based on the root folder currently open?) the conversation took place in; so if you work on multiple things, you can later open something and get the conversations that are relevant to it in the history more easily.

[bdougie]

This is interesting. @TiagoTiago do you have examples of other products that have this user experience so we can better research this?

[TiagoTiago]

I didn't had any specific other product in mind when this idea came to mind. It's just the general concept that a chat might be not be relevant if it happened in a different context, and when switching from one project to another if you wanna go back to where you were you have the search thru logs to load the relevant conversation. I don't have much experience with the paid AI services besides stuff I see people showcasing and talking about on videos and stuff, but perhaps it could be to some extent compared to a sorta inside-out version of Claude Artifacts, where instead of files the AI create being bound to a chat, you have chats that are associated to a project folder.

Maybe by saving the chat logs on the folder itself (thought that might not be ideal, as you would need to keep adding new conversation to .gitignore to not waste space), or just have some sort of "tag" file in the folder and on conversations that happened with that folder open in the same window or something like that, and a toggle on the Continue interface to filter the history to just the relevant conversations, and maybe also a toggle in the settings to reload whatever conversations where open when reopening a project later, and this could be handled with another little file in the root folder?

ps: My experience is mainly with using Continue in VSCodium, dunno how different things are in other editors and whether it makes sense in other contexts.

[ShellOliver]

I think it should be the default behaviour, vscode copilot is in this way.

[caioribeiro-dev]

The file-per-project approach mentioned here actually maps nicely to how a few other tools handle this: keeping a context file at the project root (like .cursorrules, CLAUDE.md, or similar) that scopes what the model should know about this project specifically.

The conversation history association is a UX layer on top of that — but the underlying problem is the same: how do you prevent context from one project from bleeding into another?

My current workaround in Continue is having a project-specific config.yaml with different system prompts per workspace, but that's manual overhead. A native "project scope" toggle in the history panel would be a clean solution.