This is not accurate. We made this change like six months ago (back in November) due to enterprise customer demand for it. These pricing plans have been published on our site for months.
@bcherny
-
Enterprise Pricing Change Implemented Six Months Earlier
By
–
Not accurate. We made this change like six months ago (back in November) due to enterprise customer demand for it. Pricing plans are on our website.
-
Enterprise Pricing Changes Announced Six Months Ago
By
–
This is not accurate. We made this change like six months ago (back in November) due to enterprise customer demand for it. These pricing plans have been published on our site for months.
-
Claude reading node_modules dependencies source code permissions
By
–
You can ask Claude to add a permission rule so it can’t read node_modules, but in practice it is actually often helpful to have Claude read your dependencies’ source
-
1h Prompt Cache: Cost Analysis and Usage Patterns
By
–
1h prompt cache is nuanced actually. It costs more for cache writes, and less for cache reads. Whether you benefit from cheaper cache reads depends on your usage pattern — context window size, whether the query is the main agent or subagent, etc. We have been testing a
-
Prompt Cache Pricing: Read vs Write Cost Trade-offs
By
–
1h prompt cache is nuanced actually. It costs more for cache writes, and less for cache reads. Whether you benefit from cheaper cache reads depends on your usage pattern — context window size, whether the query is the main agent or subagent, etc. We have been testing a
-
Claude Code Token Usage Default: Transparency and User Choice
By
–
This is false. We defaulted to medium as a result of user feedback about Claude using too many tokens. When we made the change, we (1) included it in the changelog and (2) showed a dialog when you opened Claude Code so you could choose to opt out. Literally nothing sneaky about
-
TypeScript Performance: Simplifying Build Without Native Dependencies
By
–
TS felt simpler if we could make it fast — no napi, no native builds, no per platform vendoring
-
Performance optimization strategies for file search systems
By
–
The wins came from three places: 1. Pre-computing upfront in a clever way that doesn't block the main thread
2. Avoiding NAPI overhead for small result sets
3. Iteratively asking Claude to find perf improvements for faster file search