Log 'skipped, inputs unchanged' for toplevel tasks#14
Merged
Conversation
When a toplevel task detects no input changes (local cache hit), it previously exited silently. This adds an info log message so agents and users can distinguish a cache hit from an empty/broken run. The message only appears for toplevel tasks to avoid noise from subtasks. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
kozak
approved these changes
Mar 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Motivation
Currently when all tasks are skipped, not output is emitted.
This frequently confuses agents, they "think" something is wrong with the caching system.
Summary
skipped, inputs unchangedinstead of exiting silentlyisNothing m_hashToSaveso remote cache hits and prime-cache mode are unaffectedTest plan
toplevel-skip-messagetest: toplevel task logs the skip message on second runsubtask-skip-no-messagetest: subtask does NOT log the skip message🤖 Generated with Claude Code