{"version":"2.1.319","anchor":"cloud-runner-no-longer-uploads-the-child-debug-log-on-exit","canonical_anchor":"cloud-runner-no-longer-uploads-the-child-debug-log-on-exit","heading":"Cloud session runners no longer upload their debug log when they finish","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/cloud-runner-no-longer-uploads-the-child-debug-log-on-exit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Cloud session runners no longer upload their debug log when they finish\n\nThe cloud session runner stops sending its debug log to the server on exit; copy it yourself from `CLAUDE_RUNNER_DEBUG_LOG_PATH` if needed\n\n**What**\n\nThe runner that hosts cloud sessions used to send the end of its debug log (a detailed record of what happened) to the server when a session ended. It no longer does.\n\nWith `--remove-session-state`, the log is simply deleted. The status message now says the log is not uploaded and that you can copy it in your post-session hook (a script you set to run after a session ends) using `CLAUDE_RUNNER_DEBUG_LOG_PATH`.\n\n**Why**\n\nThe server's diagnostics for these sessions no longer include the debug log, so if you want it for troubleshooting you have to keep it yourself.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}