用户迁移至GPT-6 Astra模型
correction: the switching costs weren't enough to stop my desire to try out gpt-6 astra i ported ov...
Jerry Liu实测迁移GPT-6 Astra，谈AI工具切换成本和上下文管理痛点。
Jerry Liu将所有技能和对话上下文迁移至Codex，计划作为日常驱动使用。他认为早期采用者在新模型发布时的迁移成本可能为零。Liu指出，现有应用间的切换成本主要来自技能、系统指令和项目设置。记忆功能可缓解重复输入上下文的痛点。
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 ⚡
