Shell history

Shell history supplies commands recalled with the shell's arrow keys and autosuggestions. It is separate from visible scrollback and from the saved-command library.

Isolated history #

In a terminal's Edit window, Isolated shell history is enabled by default. Each profile uses its own native command history instead of mixing commands with other profiles. For example, API's shell suggestions do not need to include Web's recent commands.

Bash and Zsh use a profile-specific history file in Terminalis's configuration directory. Fish uses a separate terminalis_<profile-id> history session in its Fish data directory. Unsupported shells receive best-effort setup and may retain their normal shared-history behavior.

Shared history #

Clear Isolated shell history, save, and reinitialize when ready to apply the change. The next shell returns to the history behavior configured by your shell and dotfiles, which can share commands with terminals outside Terminalis.

Changing the preference does not merge the private file into the shared one or copy old shared history into the private file. Re-enabling isolation selects the profile's private history again. Shell plugins that change history settings can affect the result.

Reinitialization #

History files survive ordinary profile edits, app restarts, and shell reinitialization. Zsh's isolated history appends entered commands promptly and disables cross-profile sharing. Bash and Fish retain their own history-writing semantics; abrupt replacement can lose entries not yet flushed. Permanent profile deletion removes its private history.

Terminalis also records a separate per-terminal recent-command store, populated by supported integration and managed runs. That store is independent of native history flushing and isolation. It does not turn the current Cmd+R saved-command selector into a shell-history search: use your shell's history keys or shell-native history search for previously typed commands.