Only print a dot every 30 seconds instead of every 1 second when using our progress spinner in a non-TTY #327
+4
−2
Conversation
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
…g our progress spinner in a non-TTY
kylekthompson
approved these changes
Feb 6, 2026
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.
Currently we print a dot every second when using our
spincomponent in a non-interactive terminal. These dots accumulate into Claude tokens, meaning that if you wait 5 minutes onrwx results --wait, you're burning 300 tokens processing dots. If you wait 15 minutes, that's 900 tokens.Plus, because they become input tokens on subsequent messages in the same conversation, the token usage compounds.
This PR changes that progress dot to print every 30 seconds, though I could also see an argument for not printing anything (it just might seem somewhat opaque whether it's progressing).