mirror of
https://github.com/Aider-AI/aider.git
synced 2025-06-01 10:14:59 +00:00
57 lines
2.9 KiB
Markdown
57 lines
2.9 KiB
Markdown
# Aider
|
|
|
|
Aider is a command-line tool that allows you to chat with GPT-4 about your code.
|
|
It can make changes, improvements, and bug fixes to your code on your local.
|
|
Each change is automatically committed to git with a sensible commit message.
|
|
|
|
[](https://asciinema.org/a/eVfXYU9CwiKHeic1dKJ17w4DT)
|
|
|
|
## Features
|
|
|
|
* Chat with GPT about your code by specifying a set of source files to discuss.
|
|
* Request changes, improvements, and bug fixes to your code.
|
|
* Aider will apply the edits suggested by GPT.
|
|
* Aider will automatically commit each change to git with a sensible commit message to provide safety, change history and easy undo with normal git tools.
|
|
* Aider can make coordinated code changes across multiple source files at once.
|
|
* Aider will notice if you edit the files outside the chat:
|
|
* It will ask if you'd like to commit these out-of-band changes.
|
|
* It will make GPT aware of the updated file content.
|
|
* You can bounce back and forth between your aider chat and your editor, to fluidly collaborate with GPT.
|
|
* Live, colorized, human friendly output.
|
|
* Readline style chat input history, with autocompletion of tokens found in the source files being discussed (via `prompt_toolkit`)
|
|
|
|
## Installation
|
|
|
|
1. Install the package: `pip install git+https://github.com/paul-gauthier/aider.git`
|
|
2. Set up your OpenAI API key as an environment variable `OPENAI_API_KEY` or by including it in a `.env` file.
|
|
|
|
## Usage
|
|
|
|
Run the Aider tool by executing the following command:
|
|
|
|
```
|
|
aider <file1> <file2> ...
|
|
```
|
|
|
|
Replace `<file1>`, `<file2>`, etc., with the paths to the source code files you want to work on.
|
|
|
|
You can also use additional command-line options to customize the behavior of the tool. For more information, run `aider --help`. Many defaults can be set with `.env` or environment variables, see the help output.
|
|
|
|
## Input tips
|
|
|
|
* Use Control-C to safely interrupt GPT if it isn't providing a useful response.
|
|
* Provide a multiline chat message by entering `{` alone on the first line. End the multiline message with `}` alone on the last line.
|
|
* Aider will notice if you ask it to discuss files with uncommitted changes and offer to commit them before proceeding.
|
|
|
|
## Limitations
|
|
|
|
Aider basically requires GPT-4.
|
|
You can invoke it with `aider -3` to try using gpt-3.5-turbo, but it will almost certainly fail to function correctly.
|
|
GPT-3.5 is unable to follow directions and generate code changes in a stable, parsable format.
|
|
|
|
Aider also can only edit code that can fit in the context window.
|
|
For GPT-4 that is 8k tokens.
|
|
It helps to be selective about which of your source files you give to aider.
|
|
It can also help to refactor your code into more, smaller files.
|
|
Aider can help with such refactorings if you start them before the files hit the context window limit.
|
|
If you have access to gpt-4-32k, I would be curious to hear you experiences using it with aider.
|