{"version":"2.1.283","anchor":"system-prompt-and-system-prompt-file-can-now-be-given-to","canonical_anchor":"system-prompt-and-system-prompt-file-can-now-be-given-to","heading":"--system-prompt and --system-prompt-file can now be used together","tier":"use","area":"CLI","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/system-prompt-and-system-prompt-file-can-now-be-given-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### `--system-prompt` and `--system-prompt-file` can now be used together\n\nPassing both `--system-prompt` and `--system-prompt-file` no longer stops Claude Code from starting; the two are combined\n\n**Unclear.** The order in which the two values are combined, and what separates them, are not settled.\n\n**What**\n\nThe system prompt is the standing instructions Claude receives before your conversation. Claude Code has flags (options typed on the command line) that set it from text or from a file. Previously, giving both forms of the same flag stopped Claude Code with an error telling you to use only one. Now both are accepted and combined:\n\n- `--system-prompt` with `--system-prompt-file`: the file's contents are merged with the text you passed\n\n- `--append-system-prompt` with `--append-system-prompt-file`: the same, except in a Remote Control session\n\nIn a Remote Control session, giving both append flags is still refused, with a new message: \"Error: --append-system-prompt cannot be given with --append-system-prompt-file in a Remote Control session. Remove --append-system-prompt.\"\n\n**Why**\n\nScripts that pass both flags now start instead of failing. Because the two values are now combined, it is worth checking that the resulting prompt reads the way you expect.\n\n- Area: CLI\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 1\/5"}