85 sources from practitioners, by month and sentiment.
Across public accounts the read is positive: model choice and explicit context control are the most praised capabilities. Practitioners split almost evenly on whether Aider's developer-driven control beats agentic tools that explore and run commands on their own, and the slower release pace is the newest concern.
Positive, mixed and negative sources
301712
The score counts them as 28 positive, 17 mixed and 12 negative votes, one per author. See How the numbers work.
Counted for All practitioners, from 85 sources. Change group
What practitioners praise
Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.
1Any Model, Any ProviderAll 15 sources on it praise itBringing your own key and switching among hosted and local models, including an architect model paired with an editor model.
Counted for All practitioners.
Positive
Anurag Singh, Technology journalist at XDA Developers
Moved routine work from Claude Code to Aider to pick a model per task, cheap DeepSeek or stronger Claude, Gemini or GPT; Claude Code stays ahead on autonomy.
Published May 22, 2026self-described: Personal coding work
Practitioner account, self-described; direct use; counts toward Operational control, Adoption and upkeep
Positive
Magneticdud, Aider user commenting on a GitHub issue
A user since before Claude Code still values Aider's terminal-first, git-native, model-agnostic design, and built a package to add agent skills since Aider has no plugins.
Published Feb 24, 2026self-described: Open source developer in test automation
Practitioner account, pseudonymous; direct use; counts toward Operational control, Adoption and upkeep
Switches to DeepSeek R1 as architect and Qwen3 Coder as editor in Aider when Gemini 2.5 Pro gets stuck; reasoning models plan well but write weaker code.
Published Aug 12, 2025self-described: DeepSeek R1 architect with a Qwen3 Coder editor
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Runs Aider on local Ollama models in architect mode, a reasoning architect plus a coder; local reasoning models do not always stick to the edit format.
Published Mar 10, 2025self-described: Local Ollama models in architect mode
Practitioner account, pseudonymous; direct use; counts toward Operational control
Says Aider works as a chat interface or from the editor by watching your files, and lets you tier models so a big model does the thinking while code reviews run on a smaller one. Last they looked, the maintainer had to focus elsewhere, and aider-ce is a fantastic fork.
Published Dec 9, 2025self-described: Watch mode from the editor
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Stays with Aider for its fit and model switching, but wishes a larger team maintained it, and is not comfortable letting agents loose on production code.
Published Sep 29, 2025
Practitioner account, pseudonymous; direct use; counts toward Operational control
Six Feet Up's CTO gave five assistants the same Django refactor. Aider offered fine-grained git control and a choice of models but needed more coaching to finish, while Claude Code made the most complete refactor.
"Aider offered fine-grained Git control and multi-model customization, but needed more coaching to complete tasks."
Excerpt, Calvin Hendryx-Parker
Published May 28, 2025Six Feet Up, a Python and AI consultancy; live IndyPy comparison of five assistants converting a Django project's GraphQL API to REST
Practitioner account, self-described; second-hand; not counted until substantiated
Rates Aider faster, more transparent and model-flexible than Claude Code, but by April 2025 used Claude Code for complex requests in larger codebases and Aider for smaller tasks.
Published Mar 20, 2025self-described: Command-line AI coding on a personal code base
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Operational control
2Explicit Context ControlAll 9 sources on it praise itChoosing exactly which files the model sees with /add and /read-only, backed by a map of the whole repository.
Chose Aider for a Go codebase of thousands of files, where agentic tools got overwhelmed. Adding files is manual, but the edits are accurate and never silent.
Published Dec 14, 2025self-described: Go codebase of thousands of files
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
On a Swift codebase with internal dependencies in other repos, Aider reads those files as read-only; Claude Code burned time and tokens searching for files.
Published Mar 11, 2025self-described: Swift codebase with dependencies in other repositories
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Recommends Aider as cheaper than Claude Code: pick models from its leaderboard, work incrementally on branches, cap context near 25k tokens and add only needed files.
Published Mar 9, 2025
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Gets more value from LLMs through Emacs and Aider, which leaves the user in control of the context and turns each chat change into a git commit that is easy to undo.
Published Jan 7, 2025self-described: Emacs
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Keeps Aider under 25k tokens of context at about 3 US cents a prompt on Gemini, but says it now lags Claude Code significantly; editor independence keeps BeetleB on it.
Published Jun 12, 2025self-described: Gemini for personal work; Copilot at work
Practitioner account, pseudonymous; direct use; counts toward Cost predictability and limits
Rates Aider faster, more transparent and model-flexible than Claude Code, but by April 2025 used Claude Code for complex requests in larger codebases and Aider for smaller tasks.
Published Mar 20, 2025self-described: Command-line AI coding on a personal code base
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Operational control
3Terminal Workflow9 of 11 sources on it praise itDay-to-day ergonomics: fast streamed replies, editor independence, and acting on AI comments written in any editor.
Says Aider works as a chat interface or from the editor by watching your files, and lets you tier models so a big model does the thinking while code reviews run on a smaller one. Last they looked, the maintainer had to focus elsewhere, and aider-ce is a fantastic fork.
Published Dec 9, 2025self-described: Watch mode from the editor
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Daily Aider user on Claude 3.5 who values seeing each query's cost and the session total; Claude Code struggled with basic patches to the same Go code.
Published Feb 24, 2025self-described: Daily use on a Go codebase
Practitioner account, pseudonymous; direct use; counts toward Cost predictability and limits
Rates Aider faster, more transparent and model-flexible than Claude Code, but by April 2025 used Claude Code for complex requests in larger codebases and Aider for smaller tasks.
Published Mar 20, 2025self-described: Command-line AI coding on a personal code base
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Operational control
Hones an idea into a spec with ChatGPT 4o or o3 and turns it into a prompt plan, then pastes each prompt into Aider, which runs the test suite and debugs. If a step doesn't work, works through it with Aider in Q&A before moving on.
Published Feb 16, 2025self-described: Greenfield and legacy side projects
Practitioner account, self-described; direct use; counts toward Delivered outcomes
With Gemini 2.5 Pro, Aider keeps editing other parts of the file with unrequested improvements, and its per-file, per-commit review makes partial acceptance hard.
Published May 13, 2025
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Values that Aider commits to git so each prompt can be undone, which Claude Code and Cursor don't do. Says the author could run parallel work by hand with a new git worktree and another copy of Aider, but finds ChatGPT Codex's way of doing it so smooth.
Published Jun 5, 2025self-described: Parallel Aider copies in git worktrees
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Six Feet Up's CTO gave five assistants the same Django refactor. Aider offered fine-grained git control and a choice of models but needed more coaching to finish, while Claude Code made the most complete refactor.
"Aider offered fine-grained Git control and multi-model customization, but needed more coaching to complete tasks."
Excerpt, Calvin Hendryx-Parker
Published May 28, 2025Six Feet Up, a Python and AI consultancy; live IndyPy comparison of five assistants converting a Django project's GraphQL API to REST
Practitioner account, self-described; second-hand; not counted until substantiated
Relies on Aider's default auto-commits to jump back when the model loses the thread, and does renames and large moves by hand because Aider handles them poorly.
Published Jan 26, 2025
Practitioner account, pseudonymous; direct use; counts toward Reliability
Gets more value from LLMs through Emacs and Aider, which leaves the user in control of the context and turns each chat change into a git commit that is easy to undo.
Published Jan 7, 2025self-described: Emacs
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
A user since before Claude Code still values Aider's terminal-first, git-native, model-agnostic design, and built a package to add agent skills since Aider has no plugins.
Published Feb 24, 2026self-described: Open source developer in test automation
Practitioner account, pseudonymous; direct use; counts toward Operational control, Adoption and upkeep
Recommends Aider as cheaper than Claude Code: pick models from its leaderboard, work incrementally on branches, cap context near 25k tokens and add only needed files.
Published Mar 9, 2025
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Keeps Aider under 25k tokens of context at about 3 US cents a prompt on Gemini, but says it now lags Claude Code significantly; editor independence keeps BeetleB on it.
Published Jun 12, 2025self-described: Gemini for personal work; Copilot at work
Practitioner account, pseudonymous; direct use; counts toward Cost predictability and limits
Mostly uses Aider and just tried Codex. Aider needs more guiding but costs an order of magnitude less, and Karrot_Kream iterates on a plan in Aider before it writes code, then reviews the result.
Published Jun 12, 2025self-described: Mostly Aider, compared with Codex
Practitioner account, pseudonymous; direct use; not counted, takes no position
On a Swift codebase with internal dependencies in other repos, Aider reads those files as read-only; Claude Code burned time and tokens searching for files.
Published Mar 11, 2025self-described: Swift codebase with dependencies in other repositories
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Recommends Aider as cheaper than Claude Code: pick models from its leaderboard, work incrementally on branches, cap context near 25k tokens and add only needed files.
Published Mar 9, 2025
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Reed migrated from Aider to Claude Code and has not looked back. Still likes Aider, which has a distinct use, but finds Claude Code a bit more useful for now and a hell of a lot more expensive.
"I have since migrated from Aider to Claude Code and not looked back. I still like Aider, and it has a distinct use, but Claude Code is a bit more useful atm."
Excerpt, Harper Reed
"Claude Code is powerful, and a hell of a lot more expensive."
Same speaker
Published May 8, 2025self-described: Spec-driven side projects; previously an Aider workflow
Practitioner account, self-described; direct use; not counted, takes no position
6Planning & ControlAll 6 sources on it praise itHow well Aider lets the engineer plan a change in architect or ask mode and keep control of what it edits.
Chose Aider for a Go codebase of thousands of files, where agentic tools got overwhelmed. Adding files is manual, but the edits are accurate and never silent.
Published Dec 14, 2025self-described: Go codebase of thousands of files
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Switches to DeepSeek R1 as architect and Qwen3 Coder as editor in Aider when Gemini 2.5 Pro gets stuck; reasoning models plan well but write weaker code.
Published Aug 12, 2025self-described: DeepSeek R1 architect with a Qwen3 Coder editor
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Mostly uses Aider and just tried Codex. Aider needs more guiding but costs an order of magnitude less, and Karrot_Kream iterates on a plan in Aider before it writes code, then reviews the result.
Published Jun 12, 2025self-described: Mostly Aider, compared with Codex
Practitioner account, pseudonymous; direct use; not counted, takes no position
Hones an idea into a spec with ChatGPT 4o or o3 and turns it into a prompt plan, then pastes each prompt into Aider, which runs the test suite and debugs. If a step doesn't work, works through it with Aider in Q&A before moving on.
Published Feb 16, 2025self-described: Greenfield and legacy side projects
Practitioner account, self-described; direct use; counts toward Delivered outcomes
Relies on Aider's default auto-commits to jump back when the model loses the thread, and does renames and large moves by hand because Aider handles them poorly.
Published Jan 26, 2025
Practitioner account, pseudonymous; direct use; counts toward Reliability
Every concern practitioners raise, most raised first.
1Slower Release Pace10 of 11 sources on it raise it as a concernFewer releases and dependence on a single maintainer, which leave practitioners unsure of the project's future while agentic tools move quickly.
Counted for All practitioners.
Raised as a concern, 10
Positive
Altchemist, Junior to intermediate software engineer
A junior to intermediate engineer who stayed away from AI because it affected their learning path calls Aider "such a paradigm shift in AI usage" and still relevant in 2026. Says its positive feedback to the human outweighs its performance against competitors, and the project needs to be forked or maintained.
Published Oct 8, 2026self-described: Recently adopted after avoiding AI tools
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Says Aider works as a chat interface or from the editor by watching your files, and lets you tier models so a big model does the thinking while code reviews run on a smaller one. Last they looked, the maintainer had to focus elsewhere, and aider-ce is a fantastic fork.
Published Dec 9, 2025self-described: Watch mode from the editor
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Says Aider is in a sad state because the maintainer has not been maintaining it, and that the community fork cannot match development in other CLI tools.
Published Nov 27, 2025
Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account
Mixed
adrianwebb, Aider user filing a GitHub issue, self-described
An Aider user wrote that the project's most urgent issue was clarifying the maintainer's status, since he had gone silent on X and Discord. The user named the aider-ce fork as the most active one.
"The most urgent issue currently for this project is clarifying Paul's status. He has gone dark on twitter (I've pinged him) and in the discord."
Excerpt, ErichBSchulz
"In the meantime, the most active fork of this project seems to be https://github.com/dwash96/aider-ce/ where Dustin is doing some great work."
Same speaker
Published Oct 30, 2025self-described: Daily Aider user following the project's community
Practitioner account, pseudonymous; opinion; not counted until substantiated
Mixed
Kreijstal, Aider user commenting on a GitHub issue, self-described
Used to frequently run pip install -U aider-chat before doing any work, as releases came out on a fairly consistent basis. On 0.86.1, asks why there has been no release since Aug 9.
Published Oct 13, 2025self-described: Upgraded Aider before every session
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Stays with Aider for its fit and model switching, but wishes a larger team maintained it, and is not comfortable letting agents loose on production code.
Published Sep 29, 2025
Practitioner account, pseudonymous; direct use; counts toward Operational control
Tried Claude Code and returned to Aider, and now values its conservative pace and lack of plugins as a way to master the core edit loop.
Published Jan 9, 2026
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.The latest GitHub release is v0.86.0 of August 9, 2025. PyPI has 0.86.2 of February 12, 2026, and the last commit to the main branch is dated May 22, 2026. Aider releases on GitHub
Runs Aider on local Ollama models in architect mode, a reasoning architect plus a coder; local reasoning models do not always stick to the edit format.
Published Mar 10, 2025self-described: Local Ollama models in architect mode
Practitioner account, pseudonymous; direct use; counts toward Operational control
Ran Aider in IntelliJ's terminal, where a local Llama 3.1 8B made incorrect changes and GPT-4o edited well. The commenter does not plan to pay OpenAI long term.
Published Jan 12, 2025self-described: IntelliJ terminal, local Llama 3.1 8B and GPT-4o
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
A year of Aider use: learn the chat and edit modes per model, build one feature at a time with limited context, and write preferences into convention files.
Published May 8, 2025
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
3Manual Context and Less Autonomy7 of 12 sources on it raise it as a concernAdding files by hand, and an assistant that does not search the repository or iterate on its own like agentic tools.
Saw little point in Aider after trying it, because it will not search the repository itself, refuses files not added to the chat, and runs on paretolaw's own API spend.
Published Aug 27, 2026
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
In a 15-year-old monorepo of about 100 services, Aider's repo map exceeded the token limit; Claude Code handles cross-codebase tasks without file picking.
Published Sep 9, 2025self-described: 15-year-old monorepo of about 100 services
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Keeps Aider under 25k tokens of context at about 3 US cents a prompt on Gemini, but says it now lags Claude Code significantly; editor independence keeps BeetleB on it.
Published Jun 12, 2025self-described: Gemini for personal work; Copilot at work
Practitioner account, pseudonymous; direct use; counts toward Cost predictability and limits
Six Feet Up's CTO gave five assistants the same Django refactor. Aider offered fine-grained git control and a choice of models but needed more coaching to finish, while Claude Code made the most complete refactor.
"Aider offered fine-grained Git control and multi-model customization, but needed more coaching to complete tasks."
Excerpt, Calvin Hendryx-Parker
Published May 28, 2025Six Feet Up, a Python and AI consultancy; live IndyPy comparison of five assistants converting a Django project's GraphQL API to REST
Practitioner account, self-described; second-hand; not counted until substantiated
Rates Aider faster, more transparent and model-flexible than Claude Code, but by April 2025 used Claude Code for complex requests in larger codebases and Aider for smaller tasks.
Published Mar 20, 2025self-described: Command-line AI coding on a personal code base
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Operational control
Discussed without concern, 5
Positive
Anurag Singh, Technology journalist at XDA Developers
Moved routine work from Claude Code to Aider to pick a model per task, cheap DeepSeek or stronger Claude, Gemini or GPT; Claude Code stays ahead on autonomy.
Published May 22, 2026self-described: Personal coding work
Practitioner account, self-described; direct use; counts toward Operational control, Adoption and upkeep
Moved from Aider on OpenRouter to a Claude Code subscription and hit its quota quickly; Claude Code is freer, but pure coding tasks work better in Aider.
Published Jan 23, 2026self-described: Anthropic models through OpenRouter, compared with a Claude Code subscription
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Chose Aider for a Go codebase of thousands of files, where agentic tools got overwhelmed. Adding files is manual, but the edits are accurate and never silent.
Published Dec 14, 2025self-described: Go codebase of thousands of files
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Mostly uses Aider and just tried Codex. Aider needs more guiding but costs an order of magnitude less, and Karrot_Kream iterates on a plan in Aider before it writes code, then reviews the result.
Published Jun 12, 2025self-described: Mostly Aider, compared with Codex
Practitioner account, pseudonymous; direct use; not counted, takes no position
Says the ML team the author works on has started using Aider daily. To make Aider more autonomous as part of wider AI adoption the company wants, the author forked it and added 5 commands that let it solve a Jira ticket from an issue id.
Published Apr 23, 2025self-described: Company ML team using Aider daily
Practitioner account, pseudonymous; ran the rollout; not counted, takes no position
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Aider sends a map of the whole repository with each request and recommends adding only the files that need to change. It can ask to add files it needs. Practitioners who want an agent that opens files and runs commands on its own report this as a limit. Tips
Seen repeatedly: when the model edits files and asks to add more files in the same response, Aider drops the edits while the model carries on as if they were applied.
"It took me a while to see this but now I've seen it repeatedly. When the LM makes changes and asks for file, the LM is (not unreasonably) assuming it's changes have been made, but they are not."
Excerpt, ErichBSchulz
Published Jul 5, 2025self-described: Personal Python project, plan file edited in diff mode
Practitioner account, pseudonymous; direct use; counts toward Reliability
In a 15-year-old monorepo of about 100 services, Aider's repo map exceeded the token limit; Claude Code handles cross-codebase tasks without file picking.
Published Sep 9, 2025self-described: 15-year-old monorepo of about 100 services
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
5Requires Close Review6 of 7 sources on it raise it as a concernEdits and answers that need correction before the output can be trusted, including unrequested changes and deleted code.
Aider's architect mode delivered 60-70% of a correct Go microservice scaffold from a spec. Authentication, Redis wiring, integration tests and docker-compose took 5-7 hours of manual fixes, for a time saving of about 0-2 hours, or 0-25%.
Published Apr 25, 2026self-described: Scaffolding a Go, gRPC, Postgres and Redis microservice from a specification
Asked Aider to add a Gemini-powered Research Mode to a Next.js app; it rewrote app/page.tsx and the entire UI disappeared. /undo reversed it, and a constrained prompt naming the files to create and saying not to remove existing fields got the change done.
Published Mar 12, 2026self-described: Next.js application, AgentPost
Practitioner account, self-described; direct use; counts toward Delivered outcomes
Mixed
Max Charas, Senior Staff Engineer, and Marc Bruggmann, Principal Engineer, at Spotify
Spotify first tried Aider and Goose for its background migration agent. Both got far on a prompt alone, but at the scale of its migrations they could not reliably produce mergeable pull requests.
"When we first got started, we experimented with open source agents such as Goose and Aider."
Excerpt, Max Charas and Marc Bruggmann
"But we quickly ran into issues when we tried to scale these agents to our migration use case. It was difficult to get them to reliably produce mergeable PRs."
Same speaker
Published Nov 24, 2025Spotify Fleet Management; automated code migrations across thousands of repositories
Practitioner account, self-described; direct use; counts toward Delivered outcomes
With Gemini 2.5 Pro, Aider keeps editing other parts of the file with unrequested improvements, and its per-file, per-commit review makes partial acceptance hard.
Published May 13, 2025
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Discussed without concern, 1
Mixed
Aaron Sumner, Software Engineering Manager at O'Reilly Media
Sumner's team maintains nearly fifty systems; this year Sumner used agents, first Aider and now Crush, to build long-lost context on old, undocumented systems. Bigger swings mean bigger diffs for teammates to review, so the author breaks work into chunks and stays the human in the loop.
"This year I’ve been using agents (first Aider; currently Crush) to build long-lost context to systems that are old enough to vote…"
Excerpt, Aaron Sumner
"I’ve felt emboldened to take bigger swings, which usually means bigger diffs for my fellow human team members and me to review."
Same speaker
Published Sep 7, 2025Team maintaining nearly fifty software systems and libraries, some with long-dead test suites and no documentation
Practitioner account, self-described; direct use; counts toward Delivered outcomes
Questions the sources split on, with the count on each side.
Evidence remains mixed
Is developer-driven control better than an agent that explores and runs on its own?
1112
Keep the developer in control, 11 sources
Some stay with Aider because it changes only what they ask for, in the files they choose, and keeps every change reviewable.
Move to an agentic tool, 12 sources
Others moved to Claude Code, Codex, or similar agents that find files and run commands, then iterate without step-by-step direction.
Evidence remains mixed
Is paying per token on your own key better value than a flat subscription?
43
Pay per token, 4 sources
Some find per-token spend with tight context cheaper than a subscription for the way they work.
Flat subscription, 3 sources
Others found API spend too high or unpredictable and moved to a flat plan such as Claude Pro or Max.
Evidence remains mixed
Do cheaper, open-weight, or local models do the job in Aider?
32
Cheaper models work, 3 sources
Some get useful results from local Qwen, DeepSeek, or gpt-oss models, often in architect mode.
Frontier models needed, 2 sources
Others found free and local models fall far short of Claude, GPT, or Gemini.
The evidence
Whose experience this is
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All practitioners. Leaders and teams have 3 accounts; GILD prints their sentiment from 20.
Engineering leaders and teams
10 sources. These accounts emphasize team settings, git and hook policy, headless automation, and whether a team standardizes on Aider or an agentic tool.
Individual builders
75 sources. These accounts emphasize model choice, control over context, git history, spend on personal keys, and how Aider compares with agentic tools in self-directed work.
All practitioners
85 sources. This counts every account: individual builders and the few team accounts together.
85 sources from practitioners, by the context they work in. Filled rows count for this group.
Individual practitionerSolo developers and independent builders75 sources, counted here
Emphasizes Model choice, context control, and how Aider compares with agentic tools
Very small team2 to 10 engineers, or a team of unstated size5 sources, counted here
Emphasizes Headless automation, git hooks, and packaging for colleagues
Professional team11 to 50 engineers, or a named company's team2 sources, counted here
Emphasizes Daily team use and extending Aider for team workflows
Technical leadershipLeaders and advisory boards assessing tools across teams2 sources, counted here
Emphasizes Two leaders' accounts, from O'Reilly Media and Six Feet Up, cover rebuilding context on old code and how much coaching Aider needs to finish a refactor; pilot it with one team and count merged changes
Organization-wideEnterprise or company-wide rollout1 sources, counted here
Emphasizes Spotify tried Aider for automated migrations across its repositories and moved on when it could not reliably produce mergeable pull requests
What changes with scale. Individual builders weigh model choice and explicit context against the convenience of agentic tools. Team accounts turn to settings that matter at scale, such as git hooks and exit codes in headless runs, and to packaging Aider for colleagues who will not install a Python CLI. At organization scale, Spotify's account shows the limit: it could not get reliably mergeable pull requests from Aider across automated migrations.
Where the sources come from
Where this group's sources were published.
Counted for All practitioners, from 85 sources. Change group
106 sources for this group, 21 of them documentation
Developer Communities74, 70% of 106 sources
Product Documentation21, 20% of 106 sources
Engineering Blogs & Reviews11, 10% of 106 sources
Older evidence is retained when it still applies. Sources that depend on a changed release, a fixed bug, or a replaced model stay in the history, marked Needs a recheck.
Nov 1, 2026: by the owner's decision, a record whose own words state no overall view of Aider now casts no vote; it still counts toward its topics and is listed, and 19 records that counted leave the vote this way. Leaders and teams stay unscored, individual builders move from +28 to +30 and all practitioners from +26 to +28.
Builds the first Aider evidence base from public sources only: every source links to the page it comes from and names its author and publication date.
Shows a finding on a page only when at least 5 sources from 3 different authors discuss it, and a disagreement only with at least 2 sources on each side.
Drops the Edit Quality praise theme, which splits 5 positive against 7 critical, and the Commit Noise concern, raised by only 3 sources.
Leaves token cost out of the concerns: 10 sources discuss it and 5 raise it, and the pay-per-token disagreement carries the debate.
Drops the Written Conventions and The Model Decides statements and the disagreement over net time saved, which do not reach the minimums.
Adds the release-pace concern from 10 sources between September 2025 and October 2026, checked against the PyPI and GitHub release records.
October 12, 2026 revision: removes 20 sources dated before 2025 and 5 from publishers outside the source standard. It drops the Commands and Config Trust concern and two statements with fewer than 5 sources from 3 authors, and ends the evidence window at the newest source, October 8, 2026.
October 12, 2026 scoring change: a GitHub issue that reports a bug counts as mixed unless its author rejects Aider. That moves three issues from negative to mixed: a rendering hang, a repository config that runs commands at startup, and a wrong exit code.
Oct 25, 2026: added Planning & Control from what existing accounts state: 6 praise planning a change in Aider and keeping control of its edits.
Oct 25, 2026: added 5 sources from outside Hacker News, among them Spotify's engineering blog on trying Aider for automated migrations. The others are AIMultiple's independent benchmark, Harper Reed's post on moving to Claude Code, and two GitHub issues on the maintainer's absence and dropped edits.
Method
A running review of what engineering teams report about Aider, from individual builders to company-wide rollouts. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Who counts
Engineering leaders and teams
Very small team, Professional team, Technical leadership, Organization-wide
Individual builders
Individual practitioner
All practitioners
Everyone in the leaders and teams and individual builders groups
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
How the numbers work
Overall signal. Positive votes minus negative ones, per 100 votes from the sources that take a side. Each author counts once, with their latest view, whoever they are and wherever they posted. The older weighted reading, where accounts GILD matched to a named person count three times when GILD lists the author among engineering leaders and twice otherwise, is shown beside it as a second view. Where an author wrote more than one source, the line beside the split gives the votes, one per author, so the score follows from it. When one author's sources from the same day disagree, that author counts as mixed, and a half point rounds away from zero. On the AI coding agent hubs, each account's overall stance comes from GILD's blind coding: two models from different families read the source's own words without seeing each other's codes, and a third settled where they differed. An account that states no overall view there, such as a bug report, casts no vote and still counts toward its topics. Other hubs count the stance stored on each record. Sources with no opinion are listed and not counted. Strong positive is +50 or higher, positive +20 to +49, mixed −19 to +19, negative −20 to −49, strong negative −50 or lower.
Weighted reading, second view. Counted the older way, where an account GILD matched to a named person counts two or three times, all practitioners read +27 positive (method sentiment/S1). GILD printed that number as "GILD score" until October 29, 2026; most of those matches rest on a name or a self-described role.
Method change, Oct 30, 2026. GILD changed how practitioner sentiment counts, to one vote per author. Weighted, it read +27 Positive; with one vote per author it read +26 Positive. No evidence changed.
Correction, Nov 1, 2026. GILD now takes each account's overall stance from its blind two-model coding, and accounts that state no overall view cast no vote. It read +26 Positive and now reads +28 Positive.
Unscored. A group gets a score only with 20 sources from 15 authors. Below that, one source moves the score about 5 points, so the read says "Unscored until 20 sources from 15 authors" and shows its counts.
Independence. A source whose author works for the vendor, for one of its partners or programs, or for a competitor, and a page the vendor published or ran, is listed with that tie and counts toward nothing. One author counts on at most two records per product. The line under the score says how many authors and how many separate discussions the counted sources come from: comments in one thread are one discussion.
Praise and concerns. How many of the sources that discuss a theme praise it or raise it.
Consensus. A statement joins when 20% of the group's sources support it and fewer contradict it. Contradicting sources are counted separately. Below that line a statement shows as building. At 40% or more it reads Strong agreement; below, Recurring point.
Disagreements. The count on each side. GILD names no winner and gives no share of all users.
Minimum evidence. A finding needs 5 sources from 3 authors; a disagreement also needs 2 on each side. Smaller counts stay in the table below, marked under the minimum.
Labels on a source
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
Documented
Stated in official documentation.
Reported
A practitioner's account of their own use.
Measured
Backed by the source's own measurements, such as a comparative test or tracked team metrics.
GILD analysis
GILD's check of a claim against official documentation.
Current
Describes the product as it is now.
Still applicable
Older, and the behavior or lesson still holds.
Needs a recheck
May depend on a plan, version or setting that changed since it was written. It keeps counting until GILD rechecks it, since the rest of the account usually holds, and its card says so.
Out of date
No longer accurate. Kept in the record; counts toward nothing current.
Flagged for a recheck, of the sources that take a side: leaders and teams 0 of 3, individual builders 0 of 56, all practitioners 0 of 59.
Limits
These figures describe reviewed sources; they do not represent all Aider users. GILD searched Hacker News through its API, issues on the Aider-AI/aider repository, named blogs and reviews, company engineering blogs, and independent benchmarks. Reddit is not in this record, and Medium blocked direct reads. 74 of the 85 sources are Hacker News comments and GitHub issues, because Aider's users write there more than on company blogs. A GitHub bug report counts as mixed unless its author rejects Aider. 10 sources speak for a team or an organization: Spotify's engineering blog is the one organization-wide account, and AIMultiple's benchmark is the one independent measurement. No finding among leaders has 5 sources from 3 authors.
Sources record the Aider version, provider, and model inconsistently; each source shows what it states. Accounts from early 2025 describe Claude 3.5 and 3.7 era models. A source that depends on behavior Aider has since changed, a fixed rendering hang, is marked Needs a recheck.
Every count, and the sources behind it
21 findings for 3 groups
Each row opens its sources for the group you are reading.
GILD's checks of claims against official documentation, kept apart from the source counts.
Manual Context and Less Autonomy. Aider sends a map of the whole repository with each request and recommends adding only the files that need to change. It can ask to add files it needs. Practitioners who want an agent that opens files and runs commands on its own report this as a limit. Tips, checked Oct 12, 2026
Slower Release Pace. The latest GitHub release is v0.86.0 of August 9, 2025. PyPI has 0.86.2 of February 12, 2026, and the last commit to the main branch is dated May 22, 2026. Aider releases on GitHub, checked Oct 12, 2026
Commands and Config Trust. Aider asks before running the shell commands it suggests unless --yes-always is set, loads .aider.conf.yml from the git repository root, and skips pre-commit hooks on its commits unless --git-commit-verify is set. Options reference, checked Oct 12, 2026