{"version":"2.1.292","anchor":"remote-session-adopts-cloud-artifacts-and-tools-usage-limit","canonical_anchor":"remote-session-adopts-cloud-artifacts-and-tools-usage-limit","heading":"Remote sessions and workflow agents track artifacts, tools and quota refusals","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/remote-session-adopts-cloud-artifacts-and-tools-usage-limit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Remote sessions and workflow agents track artifacts, tools and quota refusals\n\nRemote sessions record adopted cloud artifacts and pass along their tools, and workflow agents record quota refusals\n\n**Unclear.** It is not clear whether any of these changes alter what a user sees.\n\n**What**\n\nSeveral changes affect sessions that run on another machine and agents that run as part of a workflow:\n\n- Remote sessions now record when they take over artifacts, items attached to the session, either given at the start or sent while it runs.\n\n- The first message a remote session receives when it starts now also passes along its tools.\n\n- Workflow agents now record a refusal when a request is rejected for hitting a rate limit that comes with quota details.\n\n- Remote workflow agents now go through an extra registration step when they start.\n\n**Why**\n\nThese changes keep the state of remote sessions and workflows in step between the machines involved.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}