The Problem
Every Claude Code session starts the same way. You open a terminal, type claude, then remember you need the flag. So you type the whole thing:
claude --dangerously-skip-permissions35 characters. Every single time. No autocomplete. Easy to mistype. And if you forget it, you're stuck approving every file edit and shell command manually.
I got tired of it. So I set up a two-letter shortcut: cc. Here's how.
macOS / Linux (Zsh or Bash)
Most Mac users are on Zsh. Linux users are typically on Bash. Either way, it's one line.
For Zsh (macOS default):
echo "alias cc='claude --dangerously-skip-permissions'" >> ~/.zshrcFor Bash (Linux default, some macOS setups):
echo "alias cc='claude --dangerously-skip-permissions'" >> ~/.bashrcThen reload your shell:
source ~/.zshrcOr just open a new terminal. That's it. Type cc and Claude Code launches with full autonomy.
You can also pass arguments through. cc "refactor the auth module" works exactly like claude --dangerously-skip-permissions "refactor the auth module".
Windows (PowerShell)
If you're running Claude Code in VS Code on Windows, you're almost certainly in PowerShell. PowerShell doesn't use aliases the same way — you need a function.
Open PowerShell and run:
notepad $PROFILEIf it asks to create the file, say yes. Then add this line:
function cc { claude --dangerously-skip-permissions @args }Save, close notepad, and restart your terminal. cc now works in every new PowerShell session.
If PowerShell blocks it with a security error about execution policies, run this once:
Set-ExecutionPolicy RemoteSigned -Scope CurrentUserThat allows local scripts (like your profile) to run while still blocking unsigned remote scripts.
Windows (Git Bash)
Some developers use Git Bash on Windows instead of PowerShell. If that's you, the setup is identical to Linux:
echo "alias cc='claude --dangerously-skip-permissions'" >> ~/.bashrcOpen a new Git Bash window and you're set.
Why This Matters More Than You'd Think
Two letters vs thirty-five characters sounds trivial. It's not.
It changes when you reach for Claude Code. When the startup cost is zero friction, you use it for smaller tasks — quick refactors, file renames, test runs. The kind of stuff you'd normally do manually because "it's not worth opening Claude for." With cc, it's always worth it.
It eliminates the permission approval loop. Without the flag, Claude asks before every file write, every shell command, every git operation. That's sensible for exploration. It's painful for execution. When you know what you want built, cc gets out of your way.
It compounds. If you open Claude Code 10 times a day, that's 350 characters of typing saved daily. More importantly, it's 10 moments where friction didn't slow you down.
The Quick Version
Copy the one that matches your setup:
- macOS (Zsh):
echo "alias cc='claude --dangerously-skip-permissions'" >> ~/.zshrc - Linux (Bash):
echo "alias cc='claude --dangerously-skip-permissions'" >> ~/.bashrc - Windows (PowerShell): Add
function cc { claude --dangerously-skip-permissions @args }to$PROFILE - Windows (Git Bash):
echo "alias cc='claude --dangerously-skip-permissions'" >> ~/.bashrc
Or just paste this into Claude Code and let it handle the whole thing:
Make a shell alias so typing cc runs claude --dangerously-skip-permissions.
Set it up for whatever shell I'm using.Try It Now
Open your terminal, run the one-liner for your OS, and type cc. That's your new workflow.