Skip to content
BENIBIX Learn

--system-prompt vs --append-system-prompt

People think --system-prompt and --append-system-prompt both just add rules. Only one of them adds. --append-system-prompt puts your text after Claude Code's default prompt. So Claude keeps its guide to the tools, its safety rules and its coding habits. --system-prompt throws the default away and uses only your text. For a coding task with a few extra rules, append. Replace only when Claude should not act as a coding helper at all.

AI⌨️ Claude Code

--system-prompt Flag

It swaps the whole default prompt for yours.

--system-prompt replaces Claude Code's whole default system prompt with your own text. --system-prompt-file does the same with the text of a file. The default prompt holds the guide to the tools, the safety rules and the coding habits, so all of that goes too. Use it when Claude should not act as a coding helper at all.

Example
Emma's script uses Claude to sort support tickets, not to write code. She gives it --system-prompt-file with her own rules, so none of the coding advice gets in the way.
Why it matters
For a job that is not coding, a short prompt of your own is clearer than a long one built for code.
Full entry
AI⌨️ Claude Code

--append-system-prompt Flag

It adds your text to the end of the default system prompt.

--append-system-prompt adds your text to the end of Claude Code's default system prompt. --append-system-prompt-file adds the text of a file. Claude keeps its tool guide and safety rules, and also follows yours. If you pass both forms, the file's text goes first.

Example
Jack's CI asks Claude to review pull requests. He adds --append-system-prompt-file with his team's style rules, and Claude still knows how to use its tools.
Why it matters
You add just what is new, and keep all that Claude needs to work well.
Full entry

In one line

--system-prompt Flag
It swaps the whole default prompt for yours.
--append-system-prompt Flag
It adds your text to the end of the default system prompt.