Prevent tool usage in Claude Code SDK environments #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
When
claude-auto-commitruns in environments where the Claude Code SDK has tool access (e.g., Claude Code itself), commit message generation can fail because Claude tries to use tools to analyze the repo instead of producing a message from the supplied diff.This led to:
Root Cause
ClaudeCodeSDK.query()interprets prompts as allowing tool usage in tool-enabled contexts. Claude then attempts to rungit diff(and similar) rather than relying solely on the diff already provided in the prompt.Solution
The prompt was modified to explicitly instruct Claude to:
git diffChanges
buildPrompt()insrc/claude-auto-commit.js