{"version":"2.1.292","anchor":"spawned-sessions-pass-autopickedbylevel-senduserfile-upload","canonical_anchor":"spawned-sessions-pass-autopickedbylevel-senduserfile-upload","heading":"File uploads from SendUserFile are checked once and report a suspected size limit","tier":"internal","area":"Attachments","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/spawned-sessions-pass-autopickedbylevel-senduserfile-upload","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### File uploads from SendUserFile are checked once and report a suspected size limit\n\nSendUserFile attachments are now checked once before upload, attachment data can note a suspected size limit, and child sessions get one more setting\n\n**What**\n\nSendUserFile is the tool Claude uses to send you a file. Its attachments are now checked once, and the result of that check is passed on to the upload instead of being worked out again. The message tool does the same. Attachment data can also carry `upload_suspected_limit_bytes`, a size limit Claude Code suspects the upload ran into.\n\nSeparately, when Claude Code starts a child session (another Claude Code process it launches), it now passes `autoPickedByLevel` along with the permission mode and proactivity level.\n\n**Why**\n\nWhen a file upload fails, Claude Code can report more detail, including a likely size limit.\n\n- Flag `tengu_send_user_file`: Not enough to say (read for one account on one subscription tier against v2.1.292; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Attachments\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}