Shell Integration
Supported shell hooks provide terminal context to Chau7.
Availability
Implemented in the stable source; configuration and compatibility limits are described below.
Reviewed against stable v0.5.1. Rust candidate additions are labeled separately. Release status.
The pain this solves
- Directory and command context can be lost without shell hooks.
- Remote and multiplexer behavior varies when hooks do not load or forward signals.
What ships with it
- Stable configurator creates Zsh, Bash, and Fish integration files.
- Terminal views consume supported OSC 133 events.
- Other shells and remote sessions are not guaranteed to expose identical context.
Questions this answers
- Which shells have generated integration scripts?
- Does Chau7 consume supported OSC 133 events?
- Is integration guaranteed through every remote shell or multiplexer?
How it works
The stable ShellLaunchConfigurator creates integration files for Zsh, Bash, and Fish. These hooks can report supported directory and command lifecycle data to the app.
Terminal views consume supported OSC 133 shell-integration events for prompt and command state. The feature depends on the configured shell and event behavior available in that session.
This is not universal shell support. Custom shells, remote environments, multiplexers, or sessions that do not load or forward the integration can provide less context.
Why it matters
Shell lifecycle signals let Chau7 associate directory and command state with a terminal tab. Listing supported shells is more useful than promising every shell setup is observed.
Frequently asked questions
Which shells are covered by generated integration?
The stable configurator has integration paths for Zsh, Bash, and Fish.
Does it work through every remote shell or multiplexer?
No universal compatibility claim is supported. Hooks must load and relevant signals must reach Chau7.