{"version":"2.1.281","anchor":"remote-runner-passes-system-prompts-by-file","canonical_anchor":"remote-runner-passes-system-prompts-by-file","heading":"Remote runner passes system prompts by file","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-runner-passes-system-prompts-by-file","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote runner passes system prompts by file\n\nThe remote session runner now hands system prompts to the processes it starts through files instead of on the command line\n\n**What**\n\nThe session runner starts child processes, which are separate copies of Claude Code doing the work. It now writes three kinds of instruction text to files instead of passing them as command-line text:\n\n- `system-prompt`\n\n- `append-system-prompt`\n\n- `append-subagent-system-prompt`\n\nThe files are named like `remote-system-prompt.txt` and use file permission mode 384, readable and writable only by their owner. The child receives a matching `--<key>-file` option. The subagent prompt still goes on the command line only when the child is not the runner's own program and every piece is under 131072 bytes.\n\n**Why**\n\nIn practice, instruction text for remote sessions travels in private files rather than in the command that starts each process."}