Skip to content

The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across disciplines: CAD, circuits, robots, games and music.

test: stop the hook specs racing vitest's own clock

0xken1565ff2635cc63
diff --git a/cli/src/hookNotify.spec.ts b/cli/src/hookNotify.spec.ts
index 259a470f2..01cf49500 100644
--- a/cli/src/hookNotify.spec.ts
+++ b/cli/src/hookNotify.spec.ts
@@ -5,7 +5,13 @@ import { chmodSync, mkdirSync, mkdtempSync, readFileSync, rmSync, statSync, syml
import { homedir, tmpdir } from 'os'
import { join } from 'path'
import { fileURLToPath } from 'url'
-import { afterEach, describe, expect, it } from 'vitest'
+import { afterEach, describe, expect, it, vi } from 'vitest'
+
+// Every case here spawns the real hook as a child process, and several spawn shell shims for tmux, ps
+// and sqlite3 on top of that. On a loaded machine — this file runs alongside 88 others — that chain
+// takes well over vitest's 5s default, and the failure looks like a product bug rather than what it is.
+// The hook's own budget still bounds it; this only stops the harness from calling time first.
+vi.setConfig({ testTimeout: 30_000, hookTimeout: 30_000 })
const HOOK = fileURLToPath(new URL('../hook/notify.mjs', import.meta.url))
const servers: ReturnType<typeof createServer>[] = []