Open the source and read safety notes before installing.
Citation facts
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
- Canonical URL
- https://heyclau.de/entry/tools/aider
- Source URLs
- https://aider.chat/docs, https://github.com/Aider-AI/aider, https://aider.chat
- Brand
- Aider
- Brand domain
- aider.chat
- Brand asset source
- brandfetch
- Privacy notes
- Aider sends your prompts and the contents of selected repository files to your configured model provider (Anthropic for Claude); a provider API key is required.
- Author
- Aider
- Claim status
- unclaimed
- Last verified
- 2026-04-27
Privacy notes
- Aider sends your prompts and the contents of selected repository files to your configured model provider (Anthropic for Claude); a provider API key is required.
Schema details
- Install type
- copy
- Troubleshooting
- No
- Scope
- Source repo
- Website
- https://aider.chat
- Pricing
- open-source
- Disclosure
- editorial
- Application category
- DeveloperApplication
- Operating system
- macOS, Windows, Linux
Full copyable content
## Editorial notes
Aider is an open-source command-line coding assistant that edits files directly in your Git repository through a chat loop. You point it at a repo, describe a change, and it proposes edits, applies them, and commits each change with a descriptive message — so every AI edit lands as a reviewable diff in your Git history.
It is model-agnostic and works well with Claude models: provide an Anthropic API key (or route through a proxy) and Aider uses Claude for the editing loop. Because it lives in the terminal rather than an editor, it fits existing workflows — tmux, CI shells, or remote machines — and it builds a repo map so it can make coherent edits across multiple files.
Reach for Aider when you want tight, Git-native AI editing without adopting a new IDE, and when you value every change landing as an inspectable commit. If you would rather have inline, editor-integrated suggestions, an editor-based tool like Cursor may fit better.
## Disclosure
Editorial listing. No paid placement or affiliate link is used.About this resource
Editorial notes
Aider is an open-source command-line coding assistant that edits files directly in your Git repository through a chat loop. You point it at a repo, describe a change, and it proposes edits, applies them, and commits each change with a descriptive message — so every AI edit lands as a reviewable diff in your Git history.
It is model-agnostic and works well with Claude models: provide an Anthropic API key (or route through a proxy) and Aider uses Claude for the editing loop. Because it lives in the terminal rather than an editor, it fits existing workflows — tmux, CI shells, or remote machines — and it builds a repo map so it can make coherent edits across multiple files.
Reach for Aider when you want tight, Git-native AI editing without adopting a new IDE, and when you value every change landing as an inspectable commit. If you would rather have inline, editor-integrated suggestions, an editor-based tool like Cursor may fit better.
Disclosure
Editorial listing. No paid placement or affiliate link is used.
Source citations
Add this badge to your README
Show that Aider is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/tools/aider)How it compares
Aider side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Open-source terminal coding assistant that edits files in Git repositories using chat-driven development loops. Open dossier | Terminal-first AI coding agent for local development workflows, codebase edits, and model-flexible automation. Open dossier | Terminal-based agentic AI coding assistant from Charm that works with many LLM providers, uses LSP and MCP for context, manages per-project sessions, and asks permission before running tools by default. Open dossier | Google's open-source terminal AI agent for Gemini-powered coding and automation, with code understanding, file edits, shell commands, web fetching, Google Search grounding, MCP server integrations, checkpointing, GEMINI.md context files, and GitHub workflow automation. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety · Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | |||
| Category | tools | tools | tools | tools |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | Aider | SST | Charm | |
| Added | 2026-04-27 | 2026-04-27 | 2026-06-05 | 2026-06-18 |
| Platforms | AiderCLI | CLI | CLI | GeminiCLI |
| Source repo | — | — | — | — |
| Safety notes | — missing | ✓OpenCode is an agent that reads, edits, and can run code in your local repository; review proposed changes and run it in version-controlled projects. | ✓Crush executes tools and commands; by default it asks for permission before each tool call. The --yolo flag skips all permission prompts; the project warns to be very careful with it, so avoid it on untrusted work. The crush.json config is trusted code — any $(...) in it runs at load time with your shell's privileges, so review config files before use. LSP and MCP servers can read your codebase and influence agent behavior; only connect servers you trust. | ✓Gemini CLI can read and edit local files, run shell commands, fetch web content, use Google Search grounding, and call configured MCP servers; keep it inside version-controlled workspaces and review high-impact actions. MCP integrations can expose databases, SaaS accounts, browsers, cloud resources, files, or internal APIs to the agent; apply least privilege and approval gates per server. Preview and nightly release channels may contain regressions or unvetted changes; use stable releases for shared or production workflows unless testing intentionally. Non-interactive scripting can run without the same operator attention as an interactive session; constrain prompts, output parsing, credentials, and command permissions. GitHub workflow automation through Gemini CLI should be reviewed like any other code-review or issue-triage automation before granting repository permissions. |
| Privacy notes | ✓Aider sends your prompts and the contents of selected repository files to your configured model provider (Anthropic for Claude); a provider API key is required. | ✓OpenCode sends your code, prompts, and file context to the configured LLM provider to plan and apply edits; choose providers deliberately and keep secrets out of shared context. | ✓Your code context and prompts are transmitted to the LLM provider you configure. API keys are read from environment variables or config files and sent to the configured provider; store them as secrets. Crush records pseudonymous usage metrics tied to a device-specific hash; prompts and responses are never collected. Opt out with CRUSH_DISABLE_METRICS=1 or DO_NOT_TRACK=1. | ✓Prompts, selected source files, GEMINI.md context, shell output, web fetches, MCP tool arguments, MCP tool results, checkpoints, and command output may be sent through the configured Gemini or Vertex AI route. Keep API keys, Google Cloud project IDs, service credentials, private paths, customer data, and internal code out of prompts, logs, shared terminal output, and public issues. Google account, Gemini API, Vertex AI, retention, quota, telemetry, and billing behavior depend on the selected authentication mode and organizational settings. MCP server logs, Gemini CLI logs, terminal history, GitHub workflow logs, and generated artifacts can retain sensitive code or operational context. |
| Prerequisites | — none listed | — none listed |
|
|
| Install | — | — | — | |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Related resources
OpenCode
Terminal-first AI coding agent for local development.
Crush
Terminal-based AI coding agent from Charm with multi-model support, LSP and MCP context, and permission prompts before running tools.
Related guides
Source-backed guides for putting this to work.
Featured in
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.