Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ldayton merged 1 commit into from
Aug 23, 2026
Merged

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion zsh/zshrc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,7 +100,11 @@ claude() {
mkdir -p ~/.claude
# settings.json is generated rather than linked, so the file Claude Code writes into is
# not one git tracks. build-settings carries `model` across the rebuild.
build-settings || return 1
#
# Its stdout is `unchanged` or `updated`, a result for install.sh and the ansible role to
# read -- not a message. Here it would print on every launch, land in the capture when
# stdout is redirected (`claude -p ... > out`), and be wiped by the fullscreen TUI anyway.
build-settings >/dev/null || return 1
# Build to a temp file and move it into place: `>` truncates before cat runs, so a
# missing or renamed base file used to leave a zero-byte CLAUDE.md. The mv also makes
# this safe when two shells start at once.
Expand Down
Loading