diff --git a/docs/ci.md b/docs/ci.md
index 93cd75599cd..082440b2979 100644
--- a/docs/ci.md
+++ b/docs/ci.md
@@ -53,7 +53,7 @@ Local changed-lane logic lives in `scripts/changed-lanes.mjs` and is executed by
 
 On pushes, the `checks` matrix adds the push-only `compat-node22` lane. On pull requests, that lane is skipped and the matrix stays focused on the normal test/channel lanes.
 
-The slowest Node test families are split or balanced so each job stays small: channel contracts split registry and core coverage into eight weighted shards each, bundled plugin tests balance across six extension workers, auto-reply runs as three balanced workers instead of six tiny workers, and agentic gateway/plugin configs are spread across the existing source-only agentic Node jobs instead of waiting on built artifacts. `check-additional` keeps package-boundary compile/canary work together and separates it from runtime topology gateway/architecture work; the boundary guard shard runs its small independent guards concurrently inside one job, and the gateway watch regression uses the minimal `gatewayWatch` build profile instead of rebuilding the full CI artifact sidecar set.
+The slowest Node test families are split or balanced so each job stays small: channel contracts split registry and core coverage into eight weighted shards each, bundled plugin tests balance across six extension workers, auto-reply runs as three balanced workers instead of six tiny workers, and agentic gateway/plugin configs are spread across the existing source-only agentic Node jobs instead of waiting on built artifacts. The broad agents lane uses the shared Vitest file-parallel scheduler because it is import/scheduling dominated rather than owned by a single slow test file. `check-additional` keeps package-boundary compile/canary work together and separates it from runtime topology gateway/architecture work; the boundary guard shard runs its small independent guards concurrently inside one job, and the gateway watch regression uses the minimal `gatewayWatch` build profile instead of rebuilding the full CI artifact sidecar set.
 
 GitHub may mark superseded jobs as `cancelled` when a newer push lands on the same PR or `main` ref. Treat that as CI noise unless the newest run for the same ref is also failing. Aggregate shard checks use `!cancelled() && always()` so they still report normal shard failures but do not queue after the whole workflow has already been superseded.
 The CI concurrency key is versioned (`CI-v6-*`) so a GitHub-side zombie in an old queue group cannot indefinitely block newer main runs.
diff --git a/test/vitest-scoped-config.test.ts b/test/vitest-scoped-config.test.ts
index 707d1841201..08d126c3e9b 100644
--- a/test/vitest-scoped-config.test.ts
+++ b/test/vitest-scoped-config.test.ts
@@ -290,6 +290,10 @@ describe("scoped vitest configs", () => {
     expect(defaultAutoReplyReplyConfig.test?.include).toEqual(["reply/**/*.test.ts"]);
   });
 
+  it("keeps the broad agents lane on shared file parallelism", () => {
+    expect(defaultAgentsConfig.test?.fileParallelism).toBe(true);
+  });
+
   it("keeps selected plugin-sdk and commands light lanes off the openclaw runtime setup", () => {
     expect(normalizeConfigPaths(defaultPluginSdkLightConfig.test?.setupFiles)).toEqual([
       "test/setup.ts",
diff --git a/test/vitest/vitest.agents.config.ts b/test/vitest/vitest.agents.config.ts
index 01ca629913b..30a867c875e 100644
--- a/test/vitest/vitest.agents.config.ts
+++ b/test/vitest/vitest.agents.config.ts
@@ -4,7 +4,6 @@ export function createAgentsVitestConfig(env?: Record<string, string | undefined
   return createScopedVitestConfig(["src/agents/**/*.test.ts"], {
     dir: "src/agents",
     env,
-    fileParallelism: false,
     name: "agents",
   });
 }