告诉HN：不要使用Claude Design，取消订阅后我失去了对我的项目的访问权限。
我在订阅了五个月的Claude Code Max后，想尝试一下Codex。然后我回到之前的Claude Design项目，才意识到我已经无法再访问它们了。
这是第一次。我从未因为在任何大型语言模型应用中取消订阅而失去过对我过去会话的访问权限。
其实我之前也想尝试Codex，但在使用我的积分时遇到了类似的问题。他们给了我额外的积分，相当于我的月度订阅费用，但有时间限制，因为那个时候Claude有很多问题。计划结束后，我失去了对这些积分的访问权限。即使在重新订阅后，我仍然无法访问这些积分。
我对工程师们表示同情，尤其是那些在X上公开自己的人。但只有当某个拥有大量粉丝的人遇到问题时，他们才会得到解决。
我曾在一家计费公司工作，能理解复杂的合同对销售和增长团队来说听起来不错，但对实际执行这些合同的工程师来说却是噩梦。他们复杂的速率限制现在已经成为常态，识别其他工具以计算额外使用量也可能很难实现，尤其是在处理非常复杂的边缘案例时。但所有“漏洞”都是用户受损的地方，这才是问题所在。
我只是想在这里发布这些内容，之前在X上多次标记他们以提醒其他用户。
查看原文
I wanted to try codex after 5 months of claude code max subscription. And then I went back to my previous projects on claude design only to realize I don't have access to them anymore.<p>This is a first. I never lost access to any of my past sessions because I unsubscribed in any of the LLM apps.<p>I actually wanted to try out codex previously, but had similar experience with my credits. They gave extra credits equivalent to my montly subscription price, with some time limit because claude has so many issues that month. And as soon as plan ended. I lost access to the credits. Even after resubscribing, I still don't have access to those credits.<p>I have sympathies towards the engineers, especially the ones that are putting themselves on X. But only when someone with large following has some issue, they sort it out.<p>Having worked at a billing company, I can see how complex contracts sound good for the growth/sales folks but are also horrible for engineers actually implementing those contracts. Their complex rate limiting which is now a norm, identifying other harnesses to count them against extra usage are all probably not easy to implement without very rough edge cases. But all the "bugs" are just where the user gets screwed is what is problematic.<p>I just wanted to post this here, after tagging them multiple times on X to alert other users.