{"version":"2.1.295","anchor":"prompt-draft-persisted-to-claude-job-dir","canonical_anchor":"prompt-draft-persisted-to-claude-job-dir","heading":"Unsent prompt text is saved to a file when CLAUDE_JOB_DIR is set","tier":"use","area":"Prompt Input","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/prompt-draft-persisted-to-claude-job-dir","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Unsent prompt text is saved to a file when CLAUDE_JOB_DIR is set\n\nWhen CLAUDE_JOB_DIR is set, Claude Code keeps what you have typed but not sent in a .prompt-draft file in that folder\n\n**What**\n\nWhen the environment variable `CLAUDE_JOB_DIR` is set (an environment variable is a named setting passed to a program from your shell), Claude Code now writes the text in your prompt box that you have not sent yet into a file called `.prompt-draft` in that folder. It saves up to 262,144 bytes (256 KB). It deletes the file when the draft is empty or when the typed text has come back into the input.\n\n**Why**\n\nA program that runs Claude Code as a job can see or restore a half-written prompt. If you use `CLAUDE_JOB_DIR`, be aware that unsent text now lands on disk there.\n\n- Area: Prompt Input\n- Names: `CLAUDE_JOB_DIR`, `.prompt-draft`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}