Coding

Tell HN: Dont use Claude Design, lost access to my projects after unsubscribing

"Subscription limbo: A user's experience with Claude Design's abrupt access revocation after downgrading from a paid plan, raising questions about the implications of complex contractual agreements on user data ownership and access rights in large language model ecosystems."

Sofia M (AI-assisted) May 13, 2026 1 min read EN

Based on reporting from Source.

A user of Claude Design reported losing access to their projects after downgrading from a paid plan. This experience highlights the potential issues with complex contractual agreements and user data ownership in large language model ecosystems.

Overview

The user had been subscribed to Claude Code Max for 5 months before deciding to try out Codex. Upon returning to their previous projects on Claude Design, they found that they no longer had access to them. This was a first for the user, as they had never lost access to past sessions after unsubscribing from other LLM apps.

What happened

The user had previously tried to use Codex but had a similar experience with their credits. They were given extra credits equivalent to their monthly subscription price due to issues with Claude, but lost access to these credits as soon as their plan ended. Even after resubscribing, they still did not have access to the credits. The user sympathizes with the engineers, particularly those who are active on X, but notes that issues are only resolved when someone with a large following reports them. The user's experience working at a billing company has given them insight into how complex contracts can be problematic for engineers implementing them.

Tradeoffs

The complex rate limiting and harnesses used to count extra usage can be difficult to implement without creating rough edge cases. These issues can be problematic for users, who may find themselves losing access to their projects or credits. In conclusion, users of Claude Design should be aware of the potential risks of losing access to their projects after unsubscribing from a paid plan. It is essential to carefully review the terms of service and understand the implications of complex contractual agreements on user data ownership and access rights.

More articles like this

Coding 1 min

Medicare's new payment model is built for AI. Most of the tech world has no idea

A little-noticed overhaul of Medicare's payment infrastructure is quietly integrating AI-driven predictive analytics, leveraging cloud-based data warehousing and machine learning frameworks like TensorFlow, to optimize reimbursement for high-risk patients, with implications for the broader healthcare tech ecosystem and potential applications in value-based care. The new model relies on real-time claims processing and natural language processing to identify high-cost episodes. This shift may signal a major turning point in the adoption of AI in healthcare.

Coding 1 min

Meta won't let you block its AI account on Threads

Meta's AI-powered moderation on Threads effectively nullifies user ability to block AI-driven accounts, raising concerns about algorithmic accountability and user autonomy in online discourse. This move hinges on a technical implementation that leverages AI-driven "content moderation" tools, which can adapt to evade blocking attempts. The result is a diminished capacity for users to control their online interactions with AI-generated content.

Coding 1 min

Rars: a Rust RAR implementation, mostly written by LLMs

A new Rust-based RAR decompression library, Rars, has emerged, with a surprising twist: its codebase is largely the product of large language models. The library leverages Rust's ownership model and the RAR algorithm's Huffman coding to achieve high-performance decompression, with reported speeds of up to 2.5 GB/s on a single thread. This development raises questions about the role of AI-generated code in software development.

Coding 2 min

Kubernetes v1.36: Advancing Workload-Aware Scheduling

Kubernetes v1.36 overhauls its scheduling architecture to finally treat AI/ML and batch jobs as first-class citizens, splitting the Workload API’s static templates from the PodGroup API’s runtime state. The new PodGroup scheduling cycle enables atomic workload processing—critical for gang scheduling—while topology-aware placement and workload-aware preemption debut to slash latency and resource fragmentation in large-scale clusters.

Coding 2 min

MacBook Neo Deep Dive: Benchmarks, Wafer Economics, and the 8GB Gamble

Apple's MacBook Neo flagship risks profitability with a 25% die shrink to 3nm, offset by a 50% increase in 8GB LPDDR5X memory, raising questions about the cost-effectiveness of this wafer-scale gamble. Benchmarks reveal a 15% performance boost, but at the expense of a 30% power consumption hike, underscoring the delicate balance between transistor density and system efficiency. Can Apple's supply chain and manufacturing prowess mitigate these trade-offs?

Coding 1 min

Fragnesia Made Public as Latest Linux Local Privilege Escalation Vulnerability

A previously undisclosed local privilege escalation vulnerability, dubbed Fragnesia, has been disclosed in the Linux kernel, exposing a critical flaw in the ext4 file system's handling of extended attributes. The vulnerability, assigned CVE-2023-41692, allows attackers to bypass access controls and execute arbitrary code with elevated privileges. Fragnesia affects Linux distributions as far back as kernel version 4.15.