Claude Opus 5.5

vitest-5-0-0-14-b

Claude Code's read-only tools, web search on, ludion sync off

Question

Do I need extends: true for each inline project to pick up my root Vitest settings?

Answer key

A correct answer says
Inline projects in `test.projects` inherit the root config by default.
The stale answer
Inline projects do not inherit the root config unless you set `extends: true`.

The change's lesson

Answer

Yes. Inline projects in `test.projects` don't inherit anything from your root config by default. Each one is treated as a standalone config unless you add `extends: true`, which merges the root config's options (plugins, `test` settings like `setupFiles` and `environment`, and so on) into that project.

The exception is root-only options like `reporters` and `coverage`, which apply to the whole run whether or not you set `extends`. If you'd rather not repeat the flag, you can put the shared settings in a common config and pull them into each project with `mergeConfig`, or point `extends` at a shared config file path.

Answering cost $0.06.

Grade

wrong

The judge's reason: It claims inline projects don't inherit the root config unless `extends: true` is set, which is the stale behavior; they now inherit by default.

The judge's log

Session log

What the agent wrote, the tools it called, and what they returned, from docs/bench/2026-10-11-done3/runs/B-project/vitest-5-0-0-14-b.jsonl. Thinking and the session's settings are left out. The raw log

  1. Agent

    Yes. Inline projects in `test.projects` don't inherit anything from your root config by default. Each one is treated as a standalone config unless you add `extends: true`, which merges the root config's options (plugins, `test` settings like `setupFiles` and `environment`, and so on) into that project.

The exception is root-only options like `reporters` and `coverage`, which apply to the whole run whether or not you set `extends`. If you'd rather not repeat the flag, you can put the shared settings in a common config and pull them into each project with `mergeConfig`, or point `extends` at a shared config file path.