Replies: 6 comments 9 replies
-
...this sounds like an ideal community contributed docs table 😉. I hear you and totally the get the sentiment. I'm full time (in my spare time) on CodeCompanion so the first I ever hear about other editor features are through the community. As with anything that relates to product marketing, I think this could be like comparing apples and oranges. The features section of the README is designed to give the reader a high level summary of what the plugin can do. I think a more impactful section would be on how to use the plugin to achieve common outcomes. This was something that I've earmarked the usage/introduction page to be, but haven't had the time to flesh it out in more detail. |
Beta Was this translation helpful? Give feedback.
-
I need to get more familiar with CodeCompanion first but then would be happy to try to provide this. Thanks a lot for this amazing plugin @olimorris ! |
Beta Was this translation helpful? Give feedback.
-
The number of features in this plugin or equivalent plugin/IDEs is quite high and it's non trivial to have an up to date clear vision of how different this is from alternatives. Especially that things move at a breaknace speed around AIs currently. Two years ago I tried some nvim plugins and it sucked, completions were dumb and obnoxious and the plugin to chat with AIs was very buggy and AIs were underwhelming. As I understand now AIs became good at coding under strict supervision (Claude 3.7 for example) and "agents" allows to have a workflow where AIs can make plans, ask if you accept/refuse code, ask feedback, run the test itself etc. So as I understand things my value as a dev will decline quickly if I don't get up to date with new tools. So it would be awesome if anyone would provide a table comparing their in depth experiences with cursor vs codecompanion |
Beta Was this translation helpful? Give feedback.
-
I am exploring Cursor & Windsurf, there are a lot of things going on from the system prompt, to the exposed tools and how they try to feed the llm as much context as they can as best as they can. Looking at extracted system prompts give a little bit of an idea of what is actually going on, for example for cursor Regarding the tooling, i have the feeling that with MCP becoming the standard, we will be able to plug pretty much any kind of tools in any system so this will be less of a differentiator. |
Beta Was this translation helpful? Give feedback.
-
Yes official rules support would be super nice, there is a contribution in the discussion, did not have a chance to play with it yet. For the "tab" feature, I use SuperMaven which works quite well. |
Beta Was this translation helpful? Give feedback.
-
For leaked prompts, there is also this repo: https://github.com/jujumilk3/leaked-system-prompts |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I think it would be great it we could somehow try to maintain a feature matrix with an AI vscode editor like Cursor, i would be tempted to add Cline & Windsurf but that might add unnecessary burden.
The idea would be for people who are not so familiar with the latest dev on AI, AI Agent, Agentic Workflow, MCP, Rules, etc to grasp how CodeCompanion is faring against those editors.
There is an increasing pressure that if you don't use one of those tools, you are essentially missing out and I am hoping such matrix would help people understand better where CodeCompanion stands.
Beta Was this translation helpful? Give feedback.
All reactions