Repository navigation
Conversation
|
This PR doesn't fully meet our contributing guidelines and PR template. What needs to be fixed:
Please edit this PR description to address the above within 2 hours, or it will be automatically closed. If you believe this was flagged incorrectly, please let a maintainer know. |
|
Thanks for your contribution! This PR doesn't have a linked issue. All PRs must reference an existing issue. Please:
See CONTRIBUTING.md for details. |
|
The following comment was made by an LLM, it may be inaccurate: Based on my search, I found one potentially related PR: #26419 - This PR addresses the bash tool description parameter, while PR #49400 requires descriptions to be nonblank and trimmed. These are related changes to the same tool schema, though #26419 made descriptions optional while #49400 enforces them as required. All other results are either the current PR itself (#49400) or unrelated PRs about different features (workflows, storage, authentication, etc.). |
|
This pull request has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window. Feel free to open a new pull request that follows our guidelines. |
Require a trimmed, nonblank description field for read and shell tool calls in the legacy and Core V2 schemas. The description is propagated to normal and external-directory permission requests. Missing or blank values fail validation before execution or permission prompting.
Changes
Verification