GPT-6 Astra User Experience
correction: the switching costs weren't enough to stop my desire to try out gpt-6 astra i ported ov...
GPT-6 Astra users may face zero switching costs when moving between AI coding assistants, affecting workflow continuity.
Jerry Liu ported all his skills and conversational context to Codex over the weekend. He plans to use GPT-6 Astra as his daily driver if the model performs sufficiently well. Liu notes that switching costs for early adopters might remain zero with each new model release. The biggest pain point for these tools is efficiently feeding the right context each time.
correction: the switching costs weren't enough to stop my desire to try out gpt-6 astra i ported ov...
correction: the switching costs weren't enough to stop my desire to try out gpt-6 astra i ported over all my skills and conversational context to codex this weekend. planning to use it as my daily driver for now if the new model is sufficiently good enough, the switching costs for early adopters might continue to be 0 😅 Jerry Liu @jerryjliu0 i think there's a real opportunity for labs to bake in even higher switching costs between claude code/codex/grok bot etc. whenever a new model release comes out, i already feel an inertia to switch between apps because of my existing skills, routines, system instructions, project setup, and more. i do maintain an externally generated wiki / artifacts for each project, so technically i could point any app at the same wiki and get similar results, but this loses the nuances of conversation history. if memory is turned on, then these apps index and remember your context for subsequent sessions, alleviating the need to retype massive amounts of context for new sessions the biggest pain point for any of these tools is figuring out how to efficiently feed it the right context every time. maybe the answer really is around building a good, self-improving context graph 🔗 View Quoted Tweet 💬 1 🔄 0 ❤️ 0 👀 757 📊 1 ⚡
