Jerry Liu suggests that labs should consider increasing switching costs for Claude models by improving context management, which could enhance user experience compared to other tools.
New model releases create inertia to switch between Claude apps due to existing skills and routines. Memory features help maintain context, but efficiently feeding the right context remains a challenge. Suggestion to build a self-improving context graph to enhance user experience.
i think there's a real opportunity for labs to bake in even higher switching costs between claude co...
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 💬 7 🔄 0 ❤️ 7 👀 878 📊 9 ⚡