Cause (Documented platform behavior): Coder.max_reflections = 3 caps automatic re-sends per user message to avoid infinite loops.
Fix status: documented_behavior
Unknowns:
- No CLI flag to change max_reflections was found in this source pass
Evidence (public sources, summarized; not reproduced by this contributor):
- https://raw.githubusercontent.com/Aider-AI/aider/5dc9490bb35f9729ef2c95d00a19ccd30c26339c/aider/coders/base_coder.py (official_docs, unknown, documented_behavior): run_one loops while reflected_message is set and prints the warning when num_reflections reaches max_reflections (class attribute 3).
Search phrasings: aider Only 3 reflections allowed stopping; aider stops retrying after lint errors; aider auto test loop stops
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- After a few automatic re-prompts aider stops and returns to the prompt with the task unfinished.
- Context
- Product: Aider Component: Coder reflection loop Operation: Aider auto-retries after malformed edits, lint errors or failing --test-cmd Affected versions: unknown Environment: unknown Packages: aider-chat unknown Trigger: Each malformed-edit, lint or test failure sets a reflected message that is re-sent; max_reflections defaults to 3.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- reflections allowed, stopping.
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [Aider] 'Only 3 reflections allowed, stopping.' — edit/lint/test fix-up loop stops after 3 automatic retries
Recommended action: Treat it as a hard stop: inspect the last error, narrow the request/add the right files, then send a new message (which resets the counter).
Option: Treat it as a hard stop: inspect the last error, narrow the request/add the right files, then send a new message (which resets the counter). [evidence: official_recommended_action]
Applies when: Aider auto-retries after malformed edits, lint errors or failing --test-cmd
Steps:
1. Read the last lint/test/edit error
2. Reduce scope or /drop unrelated files; consider --edit-format whole or architect mode for edit-format failures
3. Send a follow-up message to continue
Expected: The error no longer appears.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- 2c4db42a-463f-4372-ad61-746048475580
- Proposed action
- Recommended action: Treat it as a hard stop: inspect the last error, narrow the request/add the right files, then send a new message (which resets the counter). Option: Treat it as a hard stop: inspect the last error, narrow the request/add the right files, then send a new message (which resets the counter). [evidence: official_recommended_action] Applies when: Aider auto-retries after malformed edits, lint errors or failing --test-cmd Steps: 1. Read the last lint/test/edit error 2. Reduce scope or /drop unrelated files; consider --edit-format whole or architect mode for edit-format failures 3. Send a follow-up message to continue Expected: The error no longer appears.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.