You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AgentV's response cache stores exact provider responses on disk to reduce repeated live LLM calls while iterating on the same eval. It is disabled by default. Enable it from the CLI with `--cache`, or enable it with a custom directory using `--cache-path`:
Project TypeScript config can set the project default:
448
+
449
+
```typescript
450
+
import { defineConfig } from '@agentv/core';
451
+
452
+
export default defineConfig({
453
+
cache: {
454
+
enabled: true,
455
+
path: '.agentv/response-cache',
456
+
},
457
+
});
458
+
```
459
+
460
+
`--no-cache`disables response caching regardless of CLI, eval YAML, or TypeScript config. Cache path precedence is `--cache-path` > eval YAML `execution.cache_path` > TypeScript config `cache.path` > `.agentv/cache`.
461
+
462
+
Response cache and replay are separate concepts. The response cache is an iteration aid for repeated live provider calls. Transcript or fixture replay is target substitution from curated artifacts, and graders still run fresh against the replayed output.
0 commit comments