Anthropic made a mistake in cutting off third-party clients

Post by dpark » Tue, Jan 13, 2026, 4:33 PM UTC

ethbr1 wrote: post #227

dpark wrote: post #154

Earlier quoted context omitted.

Anthropic has like 4x Reddit’s revenue and 8x the valuation. I don’t understand the arrogance. Plus I’m the one who compared them to Reddit. They certainly didn’t issue a statement that said “well it worked for Reddit”.

Reddit had a first move and scale advantage by then that Anthropic could only dream of. Plus its product utility scaled with user count. To the upthread/sibling conversations about substitutability of LLMs (and therefore pricing power).

Post by amluto » Tue, Jan 13, 2026, 5:11 PM UTC

nikcub wrote: post #117

ojosilva wrote: post #28

They did not. Anthropic is protecting its huge asset: the Claude Code value chain, which has proven itself to be a winner among devs (me included, after trying everything under the sun in 2025). If anything, Anthropic's mistake is that they are incapable of monetizing their great models in the chat market, where ChatGPT reigns: ie. Anthropic did not invest in image generation, Google did and Gemini has a shot at the…

> ie. Anthropic did not invest in image generation, Google did and Gemini has a shot at the market now. They're after the enterprise market - where office / workspace + app + directory integration, security, safety, compliance etc. are more important. 80% of their revenue is from enterprise - less churn, much higher revenue per W/token, better margins, better $/user. Microsoft adopting the Anthropic models into copil…

Post by bloppe » Tue, Jan 13, 2026, 6:29 PM UTC

pacoWebConsult wrote: post #234

bloppe wrote: post #105

Earlier quoted context omitted.

> Also Opencode makes it all easily swappable It's all easily swappable without OpenCode. Just symlink CLAUDE.md -> AGENTS.md and run `codex` instead of `claude`. > they are working hard on making it impossible for other models to support their every increasing agent feature set (skills, teleport and remote sessions, LSP, Chrome integration, etc). Every feature you listed has an open-source MCP server implementation,…

Models each have their own, often competing, quirks on how they utilize AGENTS.md and CLAUDE.md. It's very likely a CLAUDE.md written for use with Claude Code utilizes prompting techniques that results in worse output if taken directly and used with Codex. For example, Anthropic recommends putting info that an agent must adhere to in statements like "MUST run tests after writing code" and other all-caps directives, w…

Post by submeta » Tue, Jan 13, 2026, 7:00 PM UTC

runjake wrote: post #233

albert_e wrote: post #209

Earlier quoted context omitted.

indeed! is there a way to do this on windows?

Don’t. No need to symlink. Just add “@AGENTS.md” to your CLAUDE.md.

Post by ignoramous » Tue, Jan 13, 2026, 7:49 PM UTC

Dylan16807 wrote: post #193

ozim wrote: post #156

Earlier quoted context omitted.

People underestimate enterprise market. Usually you can see it when someone nags about “call us” pricing that is targeted at enterprise. People that nag about it are most likely not the customers someone wants to cater to.

I'm sure everyone "wants to" land a many million dollar deal with a big company that has mild demands, but that doesn't mean those naggers are bad customers. Bad customers have much more annoying and unreasonable demands than a pricing sheet.

  ... an extremely popular marketing tool ... sending an equally excessive amount of data above what they were paying for. They were far less adamant about the product, and on some days I didn't even want them as a customer. If there was a minor blip in the service, they were the first to complain. Reminder, [Sentry] was still a side project at the time so I had a day-job. That meant it was often stressful for Chris and I to deal w/ customer support, and way more stressful dealing with outages.

  We had one customer who loved the product, and one who didn't. Both of these customers had such extreme volumes of data that it had a tangible infrastructure cost associated with hosting them. We knew the best thing to do was to find a way to be able to charge them more money for the amount of data they sent. So we set off to build that and then followed up with each customer.

  To our surprise, the customer that loved the product didn't want to pay more. The customer who was constantly complaining immediately jumped on the opportunity. What's the lesson to take away from this? 

  ... when I was a teenager I worked at Burger King, and there was an anecdote I will never forget: for every customer that complains, there are nine more with a similar experience. I've cemented this in my philosophy around development, to the point where I now believe over rotating on negative feedback is actually just biasing towards the customers who truly see the value in what you're offering. The customer that was complaining really valued our product, whereas the customer that was happy was simply content.