{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifvr45lfrpusd3r2rfi3fqvyzfrlvlmdu2sb7lkkve2eaycw453oy",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3ml5ccssiylk2"
  },
  "path": "/t/contextual-iterative-messages/1380341#post_5",
  "publishedAt": "2026-05-05T21:30:49.000Z",
  "site": "https://community.openai.com",
  "textContent": "I didn’t know about that. I tried it and it misses a few points. It copies the entire original chat into the new one, it is added to the side bar as a separate unit (except for its label), it is a branch of the entire chat up to the last response.\n\nMy request is the “branch” to start from a section of a response. In this sense, the word “fork” ends up being illustrative, because I don’t need the entire chat again, only the relevant section.\nExample\n\n\n\nHere I am learning about quadratic functions. You can see there is 2 separate sections in the screenshot. I might want to ask follow ups to the lower section (“Caso A”), and only require that for context. Not needing the WHOLE conversation again (like a branch). See, I don’t want or need infinite branches for my follow ups (cluttering my side bar). I am just making precise questions to clarify the received information. UI-wise this could have a lateral flow so I could review all my follow ups quickly inside the conversation’s context. It would feel like a notebook with annotations.\n\nI believe branches are a separate use case. 1) I might be exploring ideas and have 2+ possible directions → I branch. Chat direction is FINE, I just need specific follow ups without losing the main thread ( I prefer the received information to be organized) → I ask a folllow-up from the relevant section and I can go back to main thread when done",
  "title": "Contextual Iterative Messages"
}