知识库

Eye(FR) → Mill(skill) → Library(/app)

← 返回列表
Hacker News · 2026-05-13 · 已成文 · 来源 file

Tell HN: Dont use Claude Design, lost access to my projects after unsubscribing — 来自收藏队列的工程/Agent 相关条目,沉淀为可检索 claim 卡。

为什么重要

收藏条目进入 AI 处理集后必须补写,否则 star 与知识文断档;本卡把收藏接回可检索结论。

正文

Tell HN: Dont use Claude Design, lost access to my projects after unsubscribing — 来自收藏队列的工程/Agent 相关条目,沉淀为可检索 claim 卡。

Claim

Tell HN: Dont use Claude Design, lost access to my projects after unsubscribing — 来自收藏队列的工程/Agent 相关条目,沉淀为可检索 claim 卡。

Why it matters

收藏条目进入 AI 处理集后必须补写,否则 star 与知识文断档;本卡把收藏接回可检索结论。

Summary

收藏(FR favorite)无 ka 条目的 Mode B 补写。1:1 挂在同 URL Vault item。 正文四段给出可执行动作;证据含原文与 HN/讨论入口(若可得)。

Actions

  • (none)

Evidence

  • (none)

Caveats

  • (none)

Research queries

  • (none)

Body

正文

背景

FR 收藏但无 ka-v0,导致处理集与知识库断档。

机制

Mode B:同 item 写入围栏 ka-v0 + 正文四段;FR mark_read 对齐;不 bulk 清未读。

取舍

覆盖收藏缺口 vs 单篇深度;本批优先接通链路,深度可后续杂志化。

动作

核原文 → 合并同主题 → 纳入工作台检索。

结合的源文章

主源
Tell HN: Dont use Claude Design, lost access to my projects after unsubscribing
打开原文 ↗

原文快照

展开 / 收起快照

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.

This is a first. I never lost access to any of my past sessions because I unsubscribed in any of the LLM apps.

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.

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.

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.

I just wanted to post this here, after tagging them multiple times on X to alert other users.


Comments URL: https://news.ycombinator.com/item?id=48128003

Points: 247

# Comments: 70