{"version":"2.1.239","anchor":"two-sdk-fields-drop-their-internal-only-caveats","canonical_anchor":"two-sdk-fields-drop-their-internal-only-caveats","heading":"Two SDK fields drop their internal-only caveats","tier":"notice","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/two-sdk-fields-drop-their-internal-only-caveats","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Two SDK fields drop their internal-only caveats\n\nTwo SDK fields dropped their internal-only caveats and now describe normal behaviour.\n\n**What**\n\nThe `source` field on UserPromptSubmit no longer says it is set only for Anthropic-internal sessions during a trial; it now says payloads may omit it while the field rolls out. The setModel `systemPrompt` replacement no longer claims only the subprocess stdin transport honors it.\n\n**Details**\n\n- setModel now states that transports which do not implement the replacement acknowledge success without applying it, so a success response is not proof the prompt changed.\n\n**Evidence**\n\n`Payloads may omit it while the field rolls out.`\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}