Experiment result
Aider /test passes arguments through
Written November 8, 2026
Two runs of aider 0.86.2 settle a confusing docs sentence: arguments you type after /test reach the command.
What was tested
Aider's docs say you can run tests with /test <test-command>, and in the next line that "Aider will run the test command without any arguments." Those two lines can be read two ways: either typed arguments are stripped, or the sentence is about aider running the configured test command on its own. We tested which reading matches what aider 0.86.2 actually does.
How
We installed aider-chat==0.86.2 in an isolated virtual environment and ran it in a throwaway repo holding a small script, show_args.py, that prints the arguments it receives. The configured test command was python3 show_args.py. Two runs, both with a dummy API key and no model call:
OPENAI_API_KEY=sk-dummy-no-real-key ../venv/bin/aider --model gpt-4o-mini --no-gitignore --analytics-disable --no-check-update --no-show-release-notes --test-cmd "python3 show_args.py" --message "/test python3 show_args.py ALPHA BETA" --exit < /dev/null
The second run was identical except that the message was "/test". Both runs exited with code 0.
What happened
With arguments, the script received them. Without arguments, it received none:
| Run | Command typed | What the script saw |
|---|---|---|
| 1 | /test python3 show_args.py ALPHA BETA | ALPHA and BETA |
| 2 | /test | Nothing added |
Decisive lines from the first run's transcript:
ARGV: ['show_args.py', 'ALPHA', 'BETA'] ARGS-SEEN: ALPHA BETA
Decisive lines from the second run's transcript:
ARGV: ['show_args.py'] ARGS-SEEN:
The installed source agrees: in aider/commands.py, cmd_test uses the full typed command when arguments are given, and falls back to the configured test_cmd only when none are given.
What it cost
No model call. A dummy key was used; aider started, ran the test command, and exited. No output from any model appears in either transcript.
What it means for the reader
You can pass arguments to /test and they reach the command — for example, /test python3 show_args.py ALPHA BETA runs exactly that. The docs sentence most plausibly describes aider's automatic case: when aider runs the configured test command itself (bare /test, or after edits), it runs it bare and adds nothing of its own. The two docs lines are consistent once read that way.
Limits
One version (0.86.2), one small script, and no model involved. The runs do not test aider running tests automatically after edits, and behaviour may differ in other versions. This settles the typed-arguments question only.
Related experiments
- Snorkel reward-code reproduction
- Stroq attack suite
- Fix a bug with an agent without breaking the test suite
- Should you still start a new project with Aider?
Sources
- Linting and testing — aider docs — the "/test <test-command>" line and the "without any arguments" sentence
- Fix a bug with an agent without breaking the test suite — our playbook on using aider's test flow
Back to: Fix a bug with an agent without breaking the test suite