Scope Codex chats to VS Code projects/workspaces

[majid4466]

What feature would you like to see?

Summary

Currently, Codex chats in the VS Code extension are global. The Recent Tasks list shows chats created in other projects/workspaces, which makes it hard to keep Codex sessions organized.

Proposed behavior

Scope Codex chats to the active VS Code project/workspace. Ideally:

• Each project has its own Recent Tasks history.
• Optionally, provide a way to switch between “global history” and “per-project history.”

Use case

Example: I worked in project TradeAssist yesterday and had two Codex chats there. Today, when I switched to a different project M1, those same TradeAssist chats still appeared in Recent Tasks. This makes it difficult to separate Codex sessions by project.

Benefits

• Clear separation of Codex sessions per project.
• Reduced confusion when working across multiple repositories.
• Easier context management when returning to a project after time away.

Environment

• VS Code version: 1.103.2
• Codex extension version: 0.4.6
• OS: Xubuntu 20.04

Are you interested in implementing this feature?

No response

Additional information

No response

[pbarker]

It's insane this isn't the default behavior, when you have a lot of projects, finding your place again on editor restart is very challenging

[pherkan]

I think I'm slightly tripping... this was the case for me; for every project I had separate history of chats in Codex. Until literally yesterday where suddenly every chat appears on every project of mine and I learned (learn?) that it's default behaviour?

[thomasf1]

Is there any movement on this? There is little to no benefit to having conversations unrelated to the current project showing up and sorting though them (while not being able to name conversations) is quite annoying.

[Nesquik]

Is there any movement on this? There is little to no benefit to having conversations unrelated to the current project showing up and sorting though them (while not being able to name conversations) is quite annoying.

While you can't name conversations, my make-do solution has has been prepending to the the first prompt message the uppercase repo name and ending it with a dot so that you can easily filter through the list, either at a quick glance from the last shown or via the search feature through "View all"/"Task History".

It shouldn't really be a hindrance to the quality of the response, I reckon, and that plus enough thread archiving makes it bearable for me.

[pherkan]

@Nesquik ah that's a good workaround for now yep. Thanks

[iarc13]

Yeah I also felt the need for this. BTW, I would usually try to write something like "This chat is about backend", thinking it would make the chat name "Backend Chats" or something like it happens in chatgpt ui. It's just pretext I guess like @Nesquik uses. That helped! Good workaround.

[thomasf1]

Is there any movement on this? There is little to no benefit to having conversations unrelated to the current project showing up and sorting though them (while not being able to name conversations) is quite annoying.

While you can't name conversations, my make-do solution has has been prepending to the the first prompt message the uppercase repo name and ending it with a dot so that you can easily filter through the list, either at a quick glance from the last shown or via the search feature through "View all"/"Task History".

It shouldn't really be a hindrance to the quality of the response, I reckon, and that plus enough thread archiving makes it bearable for me.

Thanks, I´ve started doing the same, it helps.

Noticed that in the latest version, the Chat window is blocked if you´re in the wrong project (which kind of baffles me to put that effort in but still just show all chats)