docs: document --message with --auto-test for headless runs - #5610
Open
aniruddhaadak80 wants to merge 1 commit into
Open
docs: document --message with --auto-test for headless runs#5610aniruddhaadak80 wants to merge 1 commit into
aniruddhaadak80 wants to merge 1 commit into
Conversation
|
|
A scripted --message run applies edits and exits without verifying them. Document how to combine --auto-test and --test-cmd with --message/--yes-always so headless (CI, benchmark) runs automatically fix compile/test failures before exiting. Fixes Aider-AI#4923
aniruddhaadak80
force-pushed
the
docs/headless-auto-test
branch
from
August 22, 2026 23:59
13b0bbd to
6bd5fee
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents how to combine
--auto-test/--test-cmdwith--messagefor headless (CI, scripting, benchmark) runs, as requested in #4923.The problem
The scripting docs show how to run aider one-shot with
--message, and the linting and testing docs explain--auto-test/--test-cmd- but only in an interactive context. Nothing tells headless users that a scripted--messagerun by default applies edits and exits without any compile/test verification, or that adding--yes-always --auto-test --test-cmd "..."gives them the same automatic fix-the-failing-tests loop in CI. As #4923 describes, this leads to benchmark/CI results full of unverified, broken edits.Changes
In
aider/website/docs/scripting.md:--auto-testand--test-cmdto the list of command-line options useful for scripting (help text copied verbatim fromaider --help)--message,--yes-always,--no-auto-commits,--auto-test, and--test-cmdmax_reflections = 3inbase_coder.py), and link to the linting/testing docs for per-language configurationDocs-only change; no code affected.
Fixes #4923