Context-Based Settings Profiles
Let project context select a saved terminal settings profile.
Availability
Partially implemented in stable. Read the limits below before relying on this workflow.
Reviewed against stable v0.5.1. Rust candidate additions are labeled separately. Release status.
The pain this solves
- Manually changing saved settings between configured contexts is repetitive.
- Profile copy should not confuse settings with shell-launch configuration.
What ships with it
- Saved profiles represent terminal settings presets.
- Rules can match directory, Git branch, SSH host, process, or environment context.
- A matching rule can switch the active settings profile.
- Stable source does not establish per-tab shell or environment launch profiles.
Questions this answers
- Can Chau7 switch saved settings by project context?
- What context can profile rules match?
- Do settings profiles launch a shell with per-tab environment variables?
How it works
Chau7's saved profiles are settings presets. The profile auto-switcher evaluates configured rules against context such as working directory, Git branch, SSH host, running processes, and environment variables.
When a rule matches, the switcher applies the target settings profile and can restore the previous profile when no rule remains matched. Behavior depends on enabled rules and available context.
This is not a per-tab shell-launch profile system. The audited stable source does not support claims that profiles launch a chosen shell with custom per-tab environment variables or act as tab-creation bookmarks.
Why it matters
Saved settings profiles can reduce repeated appearance and behavior changes when you move between configured contexts. These profiles change terminal settings, not the shell process environment for each tab.
Frequently asked questions
What context can a profile rule use?
The stable auto-switcher accepts directory, Git branch, SSH host, process, and environment context. Conditions depend on the configured rule.
Does a profile launch a specific shell or set per-tab environment variables?
The audited stable implementation is a settings-profile switcher. The source does not support those per-tab launch claims.
Is automatic switching always on?
It is controlled by the auto-switcher's enabled state and configured rules.