Comment by toniantunovi

This is a useful forcing function for distinguishing two architectural categories of Claude Code adjacent tooling. Tools that route your API traffic through a third-party harness are definitionally dependent on Anthropic's policy toward that harness. Tools that run locally and integrate via MCP, without touching the API subscription path at all, are outside this restriction entirely because they are just another tool in your local environment. The local-first architecture was always the right one for teams with compliance or privacy requirements. This week is a good illustration of why it is also the right one for teams that just want to avoid dependency on a vendor-intermediary relationship they cannot control.