{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicvd4uog3yuxayzdwdwcoyjr3evplrh52du447fpp5bybinzgrc4y",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mof2yr3ptnv2"
  },
  "path": "/t/a-codex-features-request-thread/1383829#post_5",
  "publishedAt": "2026-06-16T04:05:32.000Z",
  "site": "https://community.openai.com",
  "textContent": "Thanks for the feedback. Here is the core use case in plain form:\n\nI have multiple Codex chats inside the same project, each representing a different part of the workflow: planning, architecture, backend, frontend, testing, deployment, bugs, and support.\n\nThe problem is that the chat list appears to be organized mainly by recent activity, but real projects often have a logical order that is different from recency.\n\nFor example, I may want:\n\n  1. Project Index / Overview\n  2. Planning\n  3. Architecture\n  4. Backend\n  5. Frontend\n  6. Testing\n  7. Deployment\n  8. Bugs / Support\n\n\n\nEven if “Bugs / Support” was the most recently active chat, I may still want it to stay lower in the project structure.\n\nSuggested fix: allow manual drag-and-drop ordering of chats inside a project, ideally with an edit mode and optional sections.",
  "title": "A Codex Features Request Thread"
}