Lazygit UI flickers and operations occasionally drop when iTerm2 switches profiles on ssh invocations

[ryh]

I added &ssh in iTerm auto profile switching to another colors to monitor ssh being called.
I noticed lazygit startup with fetching making colors theme change.(that means ssh being used right?, call flashing bellow)

But when I check tags in lazygit , and add/delete local tags, also flashing , sometimes the new tag was not created, after flashing.... SO I am not sure if is lazygit did not properly maintain data in flashing, or iterm broke the lazygit.
Please help, thanks.

[stefanhaller]

I have no idea what you are talking about, can you explain this with more detail?

[ryh]

iTerm2 has a built-in feature called Automatic Profile Switching, which can dynamically changes the terminal profile (including the color theme) based on user set triggers,

I set up a trigger rule: whenever the ssh command is invoked in the terminal, iTerm automatically switches to my Nord dark profile.
I noticed that when lazygit starts up (e.g., during its initial fetch), it invokes ssh under the hood. I can see iTerm switch to the dark profile while ssh is running, then switch back to the default (light color) profile once ssh exits.
The problem: ssh gets called frequently during normal lazygit usage — like when viewing, adding or deleting local tags. This causes the UI to constantly flicker between dark and default themes, and can sometimes trigger a full UI redraw in lazygit. More critically, some operations in lazygit (such as creating a new tag) sometimes fail to save, or are silently dropped right after this profile switching occurs.
Given this behavior, I’m curious whether this is a bug in lazygit itself, or whether iTerm’s profile switching is interfering with lazygit’s internal state. Thanks.