shell Command

What It’s For

Enable arashi switch to change the current shell directory when the CLI is invoked through an installed shell wrapper.

Usage

arashi shell <subcommand>

Subcommands

• init <bash|zsh|fish> print shell wrapper code for manual setup.
• install detect the active shell and update the matching startup file.
• --json request a structured result when the selected shell action supports JSON mode.

Examples

# install for the active shell
arashi shell install

# print wrapper code for manual setup
arashi shell init bash
arashi shell init zsh
arashi shell init fish

# Check shell installation behavior from automation
arashi shell install --json

Notes

• The first release supports bash, zsh, and fish.
• Restart your shell or source the updated startup file after arashi shell install.
• If install cannot determine a writable startup file, Arashi tells you to use arashi shell init <shell> instead.
• Shell integration is what makes arashi switch --cd and defaults.switch.mode: "cd" | "auto" work in the parent shell.
• arashi shell init <shell> normally writes shell wrapper code to stdout, so JSON mode returns a structured unsupported-mode error instead of mixing shell code with JSON.

Agent Notes

• Do not install shell integration unless the user explicitly asks you to change their shell startup files.
• For inspection, prefer arashi shell init <shell> so the user can review the wrapper code before installing it.
• Expect JSON mode to be unsupported for shell-code output because stdout is reserved for the wrapper script.