Coding Agent GUIs Need Better Support for Multi-Chat Workflows

this is what my codex chat history looks like. we absolutely need a new UX for coding agent guis a few thoughts: 1. my usual workflow is i have one main chat where im doing all my work for the day and then separate windows for each individual issue / feature. once those are in good shape and reviewed, i send them to my main chat to qa on staging and deploy 2. the "main chat" paradigm is nice because i want one place to have a good idea of "here's everything i need to accomplish today, what's been done, and what hasn't"—but right now it's at the same level of prominence in the UX / priority as every other chat which isn't great. 3. the main chat "orchestrator" should also be able to easily know what's going on in other threads. i need to be able to reference other chats easily and also have each sub thread have some idea of what the others are doing by default (should be able to isolate if i want though) 4. it's pretty wild to be doing your n-th codex run of the day, type what you want, and then have the model be like "okay, let's see what's going on here, ahhh there's a repo, and it has X features..." as if it has no idea what i've been doing that day. seems like a huge waste of time and tokens, we need something better by default.