Why can a sandbox task read but not change an attachment?

Selected sandbox attachments are mounted read-only so the tool can use them as input without editing the original through that mount. Save transformed content in the writable workspace.

Before you begin

A workspace determines where a teammate executes work and saves files. The environment is captured with a task, so changing a teammate later does not rewrite an earlier task. Local execution and Docker isolation have different permissions; read the selected mode before submitting real project data.

Steps

1. Keep the original attachment selected as a source.
2. Name a new output file under the workspace.
3. Ask for a change report alongside the transformed copy.

Example

Read the attached inventory.csv and write /workspace/outputs/inventory-clean.csv plus rejected-rows.csv. Preserve the original file.

Check the result

Compare the new file with the source and confirm that excluded records are accounted for.

Limits and troubleshooting

Read-only input mounts do not make generated results accurate. They protect that mounted input path from writes.