5 ms·

I think this is an interesting pivot, but Cursor's project level rules and custom modes will probably quickly evolve to cover all the aspects listed on your hub

• talos_ 2y ago
  My main gripe with Cursor is that they put MCP usage behind a paywall and their support for the protocol is weaker than Continue's in meaningful ways[1]. Given the big community push on MCP development, I'm a bit annoyed that Cursor monetizes OSS work with a paywall... [1]https://modelcontextprotocol.io/clients https://modelcontextprotocol.io/clients
• sestinj 2y ago
  Agreed! If there's value here, they'll definitely follow behind and have already taken their own creative steps. One interesting note is that rather than a pivot, the hub was just a continuation of work we'd already been doing—we had a configuration file that tons of people were customizing, but it was just a bit too complicated to get started, so we decided to make that "1 click" easy with the hub In the long run, we feel that it's not the "features" in the IDE that will separate different AI coding tools (most are a matter of building out new UI), but that the ecosystem will be one of the biggest differentiators