aykutseker

6 ms·

1. 31.▲
   by aykutseker 6mo ago

   running an ai product on top of anthropic's api. from this side: customer demand is real, recurring revenue is real. but margin lives or dies on whether anthropic keeps cutting token prices. real revenue, fragile pricing. that's t
2. 32.▲
   by aykutseker 6mo ago

   in short tasks they look identical and most people can't tell. opus shows its edge in long agent loops and 50k+ context, when sonnet starts dropping tool calls or rerunning steps. sonnet's fine for short stuff and the price is bet
3. 33.▲
   by aykutseker 6mo ago

   yeah and the reconciliation pattern only really works when you can actually read current state. half of what agents do is side effects you can't observe. slack messages, payments, emails. agent times out, retries,customer gets billed t
4. 34.▲
   by aykutseker 6mo ago

   thanks, will try both. if you've actually migrated an existing claude code setup to one of them, curious how the portability story worked. that's the part i'd been worried about.
5. 35.▲
   by aykutseker 6mo ago

   been building on claude code for a while. the post's framing is right. mcp gives you open standards on the tool layer but the harness (claude code, cursor) is still proprietary. your product is one anthropic decision away from breaki