{"version":"2.1.292","anchor":"cloud-session-artifacts-restored-from-session-metadata-back","canonical_anchor":"cloud-session-artifacts-restored-from-session-metadata-back","heading":"Cloud artifacts are restored, and background tasks show their parent","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/cloud-session-artifacts-restored-from-session-metadata-back","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Cloud artifacts are restored, and background tasks show their parent\n\nArtifacts saved with a cloud session are now restored, and the SDK's background task list adds run_id and parent_task_id\n\n**What**\n\nArtifacts recorded in a cloud session's saved details are now added back to the session's artifact list and marked as coming from the cloud session.\n\nThe SDK's list of live background tasks gains two optional fields. The SDK lets programs run Claude Code.\n\n- `run_id`\n\n- `parent_task_id`\n\nBefore, the list had only `task_id`, `task_type`, `description` and `ambient`. It is now also sent again when a task's `parent_task_id` changes.\n\n**Why**\n\nPrograms using the SDK can see which background task started which, and artifacts from a cloud session are not lost.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}