Zsh Initialization Files and Non-Interactive SSH Execution

Question

A common requirement for production environments is the consistent application of environment variables and aliases across both interactive sessions and automated remote executions. In Zsh, the shell distinguishes between interactive and non-interactive modes, which dictates which initialization files are sourced.

When executing a command via SSH (e.g., ssh user@host 'command'), the shell typically operates in non-interactive mode. This behavior often results in the bypass of .zshrc, where many developers centralize their configuration, leading to a discrepancy between the local development experience and production behavior.

To ensure portability and reliability, it is necessary to determine the optimal placement of configuration logic within the Zsh startup sequence (.zshenv, .zprofile, .zshrc, and .zlogin) to support both shell types without introducing redundant overhead.

Which specific initialization file is guaranteed to be sourced during a non-interactive SSH command execution?
What are the architectural implications of moving environment variable definitions from .zshrc to .zshenv regarding performance and shell startup time?

Tasadduq Burney · Answer

AnswerThe initialization file that is guaranteed to be sourced for a non‑interactive SSH command like ssh user@host 'command' is .zshenv.Why .zshenv?According to Zsh startup rules, .zshenv is read for every invocation of the shell, regardless of whether it is interactive, login, or non‑interactive. The other files (.zshrc, .zprofile, .zlogin) are only sourced for interactive or login shells, so they are skipped when SSH runs a command non‑interactively.Moving environment variables to .zshenvPlacing variable definitions (e.g., PATH, EDITOR) in .zshenv makes them available to the SSH command, but the file is parsed on every zsh startup, including scripts and non‑interactive invocations. This adds a small, constant parse overhead; the impact is noticeable only if the file becomes large or contains costly operations.Recommended stepsKeep .zshenv minimal: only variable assignments and export statements; no echo, print, or other output.Leave aliases, prompts, completions, and any interactive‑only logic in .zshrc.After moving definitions, verify that the remote login shell is indeed zsh; if it is another shell, .zshenv will not be read.To confirm the remote shell, run on the host: getent passwd $(whoami) | cut -d: -f7 and ensure the path ends with zsh.

Zsh Initialization Files and Non-Interactive SSH Execution

1 answer

Answer

Why .zshenv?

Moving environment variables to .zshenv

Recommended steps

Your perspective belongs here.

0 question comments