Skip to content

Stop the claude wrapper printing build-settings' result - #18

Merged
ldayton merged 1 commit into
mainfrom
lily/quiet-claude-wrapper
Aug 23, 2026
Merged

ldayton merged 1 commit into
mainfrom
lily/quiet-claude-wrapper

Conversation

@ldayton

@ldayton ldayton commented Aug 23, 2026

Copy link
Copy Markdown
Owner

build-settings prints unchanged or updated on stdout as a result for install.sh and the ansible role to read. The claude shell wrapper called it without redirecting, so that word printed on every launch, landed in the capture whenever stdout was redirected (claude -p ... > out), and was wiped by the fullscreen TUI anyway.

Redirect its stdout to /dev/null in the wrapper; the exit status still gates the launch.

https://claude.ai/code/session_015pGjA5X5rx4U8QGavNcNeC

build-settings echoes `unchanged` or `updated` as a result for install.sh and the ansible role to read, not as a message. The wrapper called it bare, so that word printed on every session start, landed in the capture whenever stdout was redirected (`claude -p ... > out`), and was wiped by the fullscreen TUI a moment later regardless. Errors are unaffected: build-settings reports those on stderr and the wrapper still refuses to start on a non-zero exit.

Claude-Session: https://claude.ai/code/session_01ScFjFLyZCsRoxBz2Jt5CPy
@ldayton
ldayton merged commit 229197e into main Aug 23, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant