Aider in Late 2026: Five Months of Silence, 531 Open PRs — What Happened to the Terminal Pair Programmer and Where Its Users Went
TL;DR: Aider has had no commit since May 22, 2026, no feature release since v0.86.0 (August 9, 2025), and 531 pull requests waiting with nobody merging them. The installed tool still runs fine — but its model aliases and edit-format settings are frozen in May 2026 and it won’t install at all on Python 3.13+. The community fork cecli ships weekly and keeps the whole Aider workflow.
| Aider v0.86.2 (today) | cecli v1.9.0 (fork) | Cline CLI v3.0.73 | |
|---|---|---|---|
| Best for | Scripted git-first edits with models from early 2026 or older | Keeping Aider’s workflow with MCP, agent mode, and current models | Full agentic loop, biggest ecosystem, VS Code + CLI + desktop |
| Price | $0 + API tokens (Apache 2.0) | $0 + API tokens (fork of Aider) | $0 + API tokens (Apache 2.0) |
| The catch | Dormant: stale model aliases, degraded edit mode on new models, no Python 3.13 support | 415 stars — small community, one primary maintainer | Different mental model: autonomous agent, not diff-based pair programmer |
Honest take: If you liked Aider enough to miss it, move to cecli — it is the same tool with a pulse. If you were only on Aider because it was the best free terminal agent in 2024, that crown passed to OpenCode and Cline a long time ago; migrate and don’t look back.
Aider was the original git-native AI pair programmer — the tool that made /add file.py, auto-commits, and diff-based edits the standard grammar that Claude Code, OpenCode, and a dozen others later absorbed. As of October 20, 2026, its repository shows 49.6k stars, 13,138 commits — and the most recent of those commits is dated May 22, 2026. This piece documents exactly what state the project is in, what still works, what quietly breaks, and where its users have gone. Everything below was checked against the GitHub repo and PyPI on October 20, 2026.
Is Aider abandoned in 2026?
Dormant is the accurate word: nothing in the repo says “abandoned,” but no human has merged, released, or committed anything in five months. The verifiable timeline, from the Aider-AI/aider releases page and PyPI:
| Event | Date | Gap to today (Oct 20, 2026) |
|---|---|---|
| Last feature release (v0.86.0) | Aug 9, 2025 | ~14.5 months |
| Last PyPI release at all (v0.86.2 patch) | Feb 12, 2026 | ~8 months |
Last commit to main (merge of PR #5173, adding newer Anthropic model names) | May 22, 2026 | ~5 months |
The 2026 commit activity was already maintenance-only: April 24–25 added GPT-5.5 model settings, May 15–16 added bash tree-sitter tags for the repo map, May 22 expanded the Anthropic model list. Then nothing. Meanwhile the backlog kept growing: 1.4k open issues and 531 open pull requests as of today, with contributor PRs from the summer sitting unreviewed. There is no archive banner, no maintenance-mode notice in the README, and no public statement from the maintainers that we could find — which is itself the problem. An archived repo tells you to leave; a silent one strands you.
For context on what the tool was at its peak, our Aider review from earlier this year still describes the feature set accurately — because the feature set hasn’t changed since.
Does Aider still work in October 2026?
Yes — if you run it on Python 3.10–3.12 and either stick to pre-May-2026 models or override settings for newer ones. We installed v0.86.2 fresh in a clean Python 3.11 virtualenv on October 20, 2026 and it installs and launches normally. The two real breakages are below, and both are worth understanding before you decide to stay.
Breakage 1: Aider will not install on Python 3.13 or 3.14
Every modern Aider release pins python >=3.10, <3.13 (visible on PyPI). On a Python 3.13 interpreter, pip skips every 2024–2026 release, falls back to ancient 2023-era versions that predate the pin, and then fails outright. Reproduced today with pip 24.0:
$ pip install --dry-run --python-version 3.13 --only-binary :all: aider-chat
ERROR: Cannot install aider-chat==0.13.0, aider-chat==0.14.0, aider-chat==0.14.1,
aider-chat==0.14.2, aider-chat==0.15.0 and aider-chat==0.16.0 because these
package versions have conflicting dependencies.
ERROR: ResolutionImpossible
Python 3.13 became the default python3 on Ubuntu 25.04, Fedora 41+, and current Homebrew in 2025–2026, so a growing share of “Aider is broken” reports are really this packaging pin. The fix if you stay: install with a pinned interpreter rather than your system Python — uv tool install --python 3.12 aider-chat or pipx install --python python3.12 aider-chat. Nobody is going to lift the pin upstream until someone merges those 531 PRs.
Breakage 2: aider’s tuned model settings end in May 2026, so late-2026 models run in degraded mode
This one is subtler than “it doesn’t know new models.” Aider learns model names and prices from LiteLLM’s metadata, which it refreshes independently of releases — so our fresh v0.86.2 install happily lists claude-sonnet-5-5 and claude-haiku-5-5 in --list-models. What froze on May 22, 2026 is aider’s own curated per-model settings: which edit format each model gets, which weak model pairs with it, and what the convenience aliases point to. Tested today on v0.86.2:
$ aider --model sonnet --exit
Main model: claude-sonnet-4-5 with diff edit format, infinite output
Weak model: claude-haiku-4-5
$ aider --model anthropic/claude-sonnet-5-5 --exit
Model: anthropic/claude-sonnet-5-5 with whole edit format
Two problems in eight lines. The sonnet alias silently resolves to claude-sonnet-4-5 — a model from September 2025 — because nobody is updating the alias table. And any model newer than the freeze falls back to the whole edit format, where the model rewrites entire files instead of emitting diffs: the slowest, most token-expensive mode aider has, and the one most likely to mangle long files. The same fallback hits claude-haiku-5-5, Mistral Large 4, and everything else shipped after May. The workaround is forcing edit_format: diff per model in .aider.model.settings.yml — our Aider “model not found” fix guide covers the mechanics, which are unchanged because the tool is unchanged. If you’ve hit search/replace block failed to match errors after overriding, that guide applies too.
One thing that keeps working untouched: local models. Aider + Ollama (our setup guide) doesn’t care about the frozen cost table, since there are no token costs to report and you supply the context-window metadata yourself anyway. Dormant software plus a local backend is arguably the most stable AI coding setup that exists — nothing can change under you. If that appeals to you, the hardware side is covered in runaihome.com’s GPU buying guide for local AI.
What is cecli, and does the fork actually keep up?
cecli is a community fork of Aider by dwash96 that kept the git-first workflow and bolted on what 2026 agents are expected to have: agent mode, MCP server support, skills, subagents, persistent memory, hooks, custom commands, and Agent Client Protocol support. Unlike upstream, it is visibly alive — commits every day this past week and three releases this month (dwash96/cecli, checked October 20, 2026):
| cecli release | Date |
|---|---|
| v1.9.0 | Oct 17, 2026 |
| v1.8.0 | Oct 12, 2026 |
| v1.7.0 | Oct 3, 2026 |
The honest caveats: 415 stars and 52 forks means a community two orders of magnitude smaller than Aider’s, and the bus factor is roughly one. The flip side of a small fork is responsiveness — 11 open issues and 8 open PRs against upstream’s 1.4k and 531. If your muscle memory, scripts, and .aider.conf.yml are shaped around Aider, cecli is the only successor where the migration cost is near zero: same command grammar, same auto-commit behavior, current model support. It’s packaged on the AUR and installs the same way Aider does.
Where did the rest of the FOSS coding agent field land?
Aider is not the only 2026 casualty — Continue.dev’s repo went read-only this year after the Anysphere acquisition (we covered that in the Continue.dev acquisition analysis), and Roo Code shut down in the spring. Here is the actual state of the major open-source options, all checked October 20, 2026:
| Tool | Stars | License | Latest release | Status |
|---|---|---|---|---|
| OpenCode | 217.9k | MIT | v1.19.3 — Oct 16, 2026 | Very active (3 releases in the 2 days before that) |
| Cline | 70.6k | Apache 2.0 | CLI v3.0.73, Desktop v0.0.48, SDK v0.0.95 — all Oct 17, 2026 | Very active, now CLI + desktop + SDK, not just VS Code |
| Aider | 49.6k | Apache 2.0 | v0.86.2 — Feb 12, 2026 (last commit May 22) | Dormant |
| Continue | 36.3k | Apache 2.0 | v2.0.0 (marked final) | Read-only; README says no longer actively maintained |
| cecli | 415 | Apache 2.0 | v1.9.0 — Oct 17, 2026 | Active fork of Aider |
Two patterns worth naming. First, terminal-native users consolidated on OpenCode — it does what Aider did (terminal, BYOK, any provider) plus the agentic loop, and its 217.9k stars make it the largest FOSS coding tool by an enormous margin; our OpenCode review has the full picture, and if you run it, patch past the two RCE CVEs from October. Second, VS Code users consolidated on Cline, which spent 2026 expanding from an extension into a CLI, desktop app, and SDK (Cline review). Both are genuinely free software with BYOK, both work against local backends, and both merged more code last week than Aider has all year.
For a deeper head-to-head of the three classic FOSS agents as they stood when all were alive, the sister site’s Continue.dev vs Cline vs Aider comparison is the most-cited page in this site network for a reason — just read it knowing that two of its three contestants have since stopped moving.
Should you stay on Aider or migrate — and to what?
Migrate unless you fit the narrow “stable scriptable tool” profile. The decision, by situation:
| Your situation | Do this | Cost | Where |
|---|---|---|---|
| You love Aider’s git-first diff workflow and just want current models | Switch to cecli | $0 + your API tokens | github.com/dwash96/cecli |
| You want the strongest maintained terminal agent, workflow change accepted | Switch to OpenCode (≥ v1.19.3) | $0 + your API tokens | github.com/sst/opencode |
| You live in VS Code or want agent + CLI + SDK from one project | Switch to Cline | $0 + your API tokens | github.com/cline/cline |
| Aider in CI/scripts, pinned models, Python ≤ 3.12 | Staying is defensible — pin aider-chat==0.86.2 and your Python version | $0 | PyPI |
| Fully local, Ollama backend, nothing changes under you | Aider or cecli both fine; cecli if you want MCP | $0 after hardware | Aider + Ollama guide |
What you should not do is keep an un-pinned Aider in a team onboarding doc or CI image. The Python 3.13 pin means new machines increasingly fail at pip install, and the frozen settings mean new teammates typing --model sonnet silently get a year-old model, or a current one in degraded whole-file edit mode. Dormant tools are fine for individuals who understand the freeze; they are a slow leak for teams.
FAQ
Is Aider officially dead? No official statement exists either way as of October 20, 2026. The observable facts: last commit May 22, 2026, last release February 12, 2026, 531 open PRs, no maintainer activity for five months. Treat it as dormant until the repo says otherwise.
Is it safe to keep using Aider? Reasonably. It’s Apache 2.0, runs locally, and has no daemon or cloud service that can be shut off. The risks are unpatched dependency CVEs accumulating over time and the model/packaging drift described above — not the tool disappearing.
Does Aider support Claude Sonnet 5.5 or other late-2026 models? It can call them — LiteLLM’s metadata keeps the names and prices current — but aider’s own tuned settings stop in May 2026, so these models default to the inefficient whole edit format. Override edit_format: diff in .aider.model.settings.yml and they work acceptably.
Is cecli a drop-in replacement? Closest thing to it — it forked Aider’s command grammar and git behavior, then added MCP, agent mode, and current model support. Expect some config differences; it’s a 415-star project with one primary maintainer, so weigh that against upstream’s total silence.
Why did Aider stall? Unknown. There’s no public explanation from the maintainer, no acquisition announcement (unlike Continue.dev), and no archive notice. The commit history simply stops on May 22, 2026.
Sources
- Aider releases — GitHub (v0.86.0 Aug 9, 2025; checked Oct 20, 2026)
- aider-chat — PyPI (v0.86.2, Feb 12, 2026; requires Python >=3.10, <3.13)
- Aider commit history on main — GitHub (last commit May 22, 2026)
- cecli — GitHub (v1.9.0 Oct 17, 2026; commits daily through Oct 17)
- cecli — Arch User Repository
- Cline releases — GitHub (CLI v3.0.73, Desktop v0.0.48, SDK v0.0.95 — Oct 17, 2026)
- OpenCode releases — GitHub (v1.19.3, Oct 16, 2026)
- Continue repository README — GitHub (read-only notice, final v2.0.0)
Last updated October 20, 2026. Repo activity, stars, and release versions were checked on that date and change constantly; verify against the linked pages before making a migration decision. Install and model-settings tests in this article were run October 20, 2026 with pip 24.0 on Linux: aider v0.86.2 (litellm 1.81.10 pinned) in a Python 3.11 venv for the working install and the edit-format checks, and a --python-version 3.13 dry-run for the failure case.
Was this article helpful?
Thanks for the feedback — it helps improve future articles.
Need hands-on help?
I offer 1-on-1 technical consulting for local AI setup, GPU selection, and AI coding tool configuration — same topics covered on this site.
Book a session — $49 / hour →Know which coding tool is worth paying for
Hands-on comparisons of AI coding assistants and what each one costs to run — including the local-model path. Sent only when something changes. Unsubscribe anytime.