-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy path.aider.conf.yml
55 lines (43 loc) · 1.64 KB
/
.aider.conf.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
architect: true
cache-prompts: true # This is false by default and I'm not sure why
## Set the color for user input (default: #00cc00)
user-input-color: "#98971a"
## Set the color for tool error messages (default: #FF2222)
tool-error-color: "#cc241d"
## Set the color for tool warning messages (default: #FFA500)
tool-warning-color: "#d65d0e"
## Set the color for assistant output (default: #0088ff)
assistant-output-color: "#d79921"
code-theme: gruvbox-dark
auto-commits: false
# Otherwise, Aider will make commits for you.
# You can always undo Aider's committed changes with `/undo`
watch-files: true # See explanation under Extras
# See Testing/Linting section below
#
# lint-cmd:
# test-cmd:
auto-test: true
# NB: Aider suggests adding `.aider*` to one's gitignore.
# (And can do it for you if it isn't there)
# I recommend adding it to your core.excludesfile
#
env-file: .aider.env # The default is `.env`
read: .aider.context.md
# Just a suggestion. The official docs suggest CONVENTIONS.md
# I think 'context' is more accurate, and there's no need to shout
#
# Equivalent to the /read-only command
#
# If you want this to work in subdirectories,
# add `AIDER_READ=.aider.context.md` to that directory's env-file
load: .aider.commands # A list of commands to run
# A great place to put `/web http://relevant-docs.example.com`
# Also a great place to configure lint and test commands (you can also put them in the env-file)
#
# Equivalent to the /load command
#
# If you want this to work in subdirectories,
# add `LOAD_FILE=.aider.commands` to that directory's env-file
# Don't ask to opt-in to analytics. See: the section in Extras for more info.
analytics: true