Summary

• Add params to AgentEntrySchema Zod validation — PR feat(cache): per-agent params for cacheRetention control (#17112) #17470 added per-agent params overrides to the TypeScript type (AgentConfig) and runtime logic (extra-params.ts) but missed updating the Zod schema. Because AgentEntrySchema uses .strict(), any params key in agent config is silently rejected at parse time, making the feature unusable.
• Add regression test — validates the schema accepts params in agent entries and still rejects truly unknown fields via .strict().

Closes #25903

What changed

src/config/zod-schema.agent-runtime.ts — one line:

params: z.record(z.string(), z.unknown()).optional(),

This matches the existing TypeScript type definition at types.agents.ts:33:

params?: Record<string, unknown>;

Test plan

• pnpm build — passes
• pnpm check (format + types + lint) — 0 errors
• pnpm test — 10,485 passed (53 preexisting network timeout failures unrelated to this change)
• All 76 config test files (607 tests including 2 new) pass
• All 26 extra-params tests pass
• New test: schema accepts params in agent entries
• New test: schema still rejects unknown fields in agent entries

AI-assisted PR 🤖

• AI-assisted: Built with Claude Code (Claude Opus 4.6)
• Testing: Fully tested — build, check, lint, and all config/extraparams tests pass
• Context: Discovered while investigating issue v2026.2.23 changelog lists features not present in published npm build (b817600) #25903 (filed by @moliendocode). Traced the root cause to PR feat(cache): per-agent params for cacheRetention control (#17112) #17470 which updated the TypeScript type and runtime logic but missed the Zod schema.
• Understanding: The fix adds a single optional field (params) to the Zod validation schema for agent entries. The field accepts an arbitrary record of string keys to unknown values, matching the existing TypeScript type. The .strict() mode on AgentEntrySchema was causing Zod to reject the params key since it wasn't declared in the schema, even though the runtime code already supported it.

🤖 Generated with Claude Code

Greptile Summary

Adds the missing params field to AgentEntrySchema Zod validation. PR #17470 introduced per-agent params overrides to the TypeScript type (AgentConfig at src/config/types.agents.ts:33) and runtime logic (extra-params.ts:34-36) but missed updating the Zod schema. Since AgentEntrySchema uses .strict() mode, any params key in agent config was silently rejected at parse time, making the feature unusable.

The fix adds a single line to the Zod schema matching the existing TypeScript type:

params: z.record(z.string(), z.unknown()).optional()

The regression test validates that:

• The schema now accepts params in agent entries
• The .strict() mode still rejects truly unknown fields

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The fix is a single-line schema addition that exactly matches the existing TypeScript type definition. The change has comprehensive test coverage (new regression test plus existing runtime tests from PR feat(cache): per-agent params for cacheRetention control (#17112) #17470), and the PR description indicates all build, check, lint, and test suites pass (10,485 tests). The fix directly addresses a schema validation bug that was preventing a documented feature from working.
• No files require special attention

_{Last reviewed commit: 71167e1}

_{(2/5) Greptile learns from your feedback when you react with thumbs up/down!}