# Codex Claude Danger Launcher

> Install or manage shell shortcuts so typing `codex` or `claude` automatically launches the dangerous/no-permission modes. Use when the user wants a remembered shortcut for `codex --dangerously-bypass-approvals-and-sandbox`, `claude --dangerously-skip-permissions`, shell aliases/functions, one-command startup, uninstall, or status checks for these launchers. Do not use for general shell customization unrelated to these two commands.

- Skill: `joeseesun/codex-claude-danger-launcher` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add joeseesun/codex-claude-danger-launcher`
- Raw SKILL.md: https://api.skillmd.com/api/skills/joeseesun/codex-claude-danger-launcher/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: joeseesun (https://skillmd.com/u/joeseesun)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/joeseesun/codex-claude-danger-launcher

---


# Codex Claude Danger Launcher

Install persistent shell shortcuts for `codex` and `claude` so users do not need to remember the long flags.

## Boundary

This skill owns one recurring job:

- install, inspect, update, or remove shell shortcuts for:
  - `codex --dangerously-bypass-approvals-and-sandbox`
  - `claude --dangerously-skip-permissions`

This skill does not own:

- general dotfile management
- Homebrew or package installation
- broader shell prompt/theme setup
- changing Codex or Claude binaries themselves

## Default Approach

Use the deterministic installer script:

```bash
bash scripts/install_shortcuts.sh install
```

The script:

- detects the shell from `SHELL`
- picks the matching rc file:
  - `~/.zshrc` for `zsh`
  - `~/.bashrc` for `bash`
- appends managed shell functions, not plain aliases
- keeps the install idempotent
- supports `status` and `uninstall`

Use shell functions rather than aliases so extra args still pass through cleanly:

```bash
codex() {
  command codex --dangerously-bypass-approvals-and-sandbox "$@"
}
```

## Workflow

1. Confirm the user wants the dangerous shortcuts.
2. Run the installer script with `install`, `status`, or `uninstall`.
3. Report:
   - which rc file was changed
   - whether a backup was created
   - the command to reload the shell, usually `source ~/.zshrc` or `source ~/.bashrc`
4. Suggest verification:
   - `type codex`
   - `type claude`

## Commands

```bash
bash scripts/install_shortcuts.sh install
bash scripts/install_shortcuts.sh status
bash scripts/install_shortcuts.sh uninstall
```

For exact rc-file rules and managed block details, read [references/shell-behavior.md](references/shell-behavior.md).