Tool Call Repair: Invalid input for tool "grep" - The tool call failed because the patterns are missing.

Summary

Seeing a few tool call fails with DeepSeek v4 Pro:

✻ Thought for 1 second
  The user wants the search to also find scheduling requests for people who are associated with a company (i.e., people who work at a company),
  not just direct company/people matches. So if I search for a company name, I should also find scheduling requests where that company's people
  are listed as participants.

  Let me look at the relationship between people and companies - there's probably a `people`.`current_company` field or a `relationships` table
  that links people to companies.

⠶ Let me check how people are associated with companies.

 SEARCH  ["undefined" in files]
 │ Invalid input for tool "grep". Please correct and retry:
 └   • pattern: Invalid input: expected string, received undefined

 SEARCH  ["undefined" in files]
 │ Invalid input for tool "grep". Please correct and retry:
 └   • pattern: Invalid input: expected string, received undefined

✻ Thought for 1 second
  The tool call failed because the patterns are missing. Let me check the schema and how people relate to companies.

Expected Behavior

Not to fail.

Actual Behavior

See above

Steps to reproduce the issue

Not sure.

Command Code Version

0.40.8

Operating System

macOS

Terminal/IDE

ghostty

Shell

zsh

Additional context

No response

No source files, tests, or entry points are named. Start by reproducing the DeepSeek v4 Pro transcript on macOS with version 0.40.8, then trace the grep tool-call path when the pattern is undefined. Done means the agent does not issue an invalid grep call and handles the missing pattern without failing.