{"version":"2.1.319","anchor":"session-ingress-log-fetch-drops-its-fourth-parameter","canonical_anchor":"session-ingress-log-fetch-drops-its-fourth-parameter","heading":"Fetching a remote session's log no longer takes an extra option","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/session-ingress-log-fetch-drops-its-fourth-parameter","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Fetching a remote session's log no longer takes an extra option\n\nThe step that fetches a remote session's log from the server has dropped an optional setting it used to pass on\n\n**What**\n\nWhen Claude Code fetches the log of a remote session from the server, the step that does this no longer accepts an extra on or off option, and no longer passes it on.\n\n**Why**\n\nThis is probably the removal of an option used when resuming remote sessions.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}