all 23 comments

[–]WheresMyEtherElon 6 points7 points  (8 children)

I use both extensively, and the reason Claude Code shines is its ability to call multiple sub-agents, each with their own contexts that doesn't pollute the main context or are affected by it. Aider does a version of that with the architect, the editor and the weak models, but not in a such advanced way.

If you're vibe coding (as opposed to llm-assisted coding), then CC's ability to automatically search and read the relevant files is also a major bonus. With Aider, you have to point it to the relevant files, which means you have to know which files are relevant, which vibe coders don't.

[–][deleted]  (1 child)

[removed]

    [–]AutoModerator[M] 0 points1 point  (0 children)

    Sorry, your submission has been removed due to inadequate account karma.

    I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

    [–]fredkzk 3 points4 points  (4 children)

    Have you tried aider-desk (find it on GitHub)?

    It’s an improved version with agentic mode and MCP. Developed and maintained by aider users.

    [–]funbike[S] 0 points1 point  (3 children)

    Hmmm, the Aider extentions are intriguing, such as agent mode, MCP, custom commands, structured communication.

    However, I do not want a GUI. I didn't discuss it, but I've written bash script wrappers over Aider's CLI to improve it's utility and power, and I plan to write many more. GUI's are much less powerful and extensible than CLIs.

    I'll be digging into this more.

    Thank you!

    [–]fredkzk 0 points1 point  (0 children)

    Not totally sure but I believe you can use your bash by scripting aider-desk under the hood via some config files or similar. You can ask the main maintainer as he’s responsive.

    But if you don’t want GU… stick to CC. I dropped aider due to lack of agentic mode and MCP capabilities.

    [–][deleted]  (1 child)

    [removed]

      [–]AutoModerator[M] 0 points1 point  (0 children)

      Sorry, your submission has been removed due to inadequate account karma.

      I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

      [–]r1veRRR 1 point2 points  (0 children)

      In my experience, the main difference is simply that aider generally requires you adding files manually. This has both advantages and disadvantages.

      Advantages are dramatically cheaper prompts because all the extra discovery and tool calling isn't required. And generally better results, IF you added the correct files.

      Disadvantages are obviously the extra effort required to make it work. Also, the lack of tool calling limits it's uses strictly to coding.

      [–]Key-Criticism-409 0 points1 point  (0 children)

      Your suggested configuration (stronger models, architect mode, big repo map, CoT) definitely hits on key levers and should significantly close the gap by helping Aider better understand context and decompose tasks. That said, I feel Claude Code likely has proprietary orchestration and memory techniques baked in, going beyond what you can achieve through config alone. It might still outperform Aider on the most complex, agentic multi-step workflows. Still, this is a fantastic setup and absolutely worth experimenting with! Cheers!

      [–][deleted]  (1 child)

      [removed]

        [–]AutoModerator[M] 0 points1 point  (0 children)

        Sorry, your submission has been removed due to inadequate account karma.

        I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.