Workspace files
The agent's workspace/ directory lives on the SPCS stage-backed volume and is mounted into the container at /home/node/.openclaw/workspace. It's intentionally not part of push or pull — workspace files can be large and agent-generated, so they get their own transfer commands.
All paths are relative to the workspace root.
ls
snowclaw ls
snowclaw ls reports/q4
List files in the workspace. Paths are workspace-relative. Use this to confirm where an agent put something before downloading.
upload
snowclaw upload ./input.csv
snowclaw upload ./input.csv --dest data/
snowclaw upload ./input.csv --dest data/ --force
Upload a local file into the workspace. The local filename is preserved.
| Flag | Meaning |
|---|---|
--dest <subdir> | Target workspace subdirectory. Defaults to the workspace root. |
--force | Skip the "destination already exists" prompt and overwrite silently. |
The underlying Snowflake PUT uses OVERWRITE=TRUE, so the CLI prompts on existing destinations unless --force is set. Uploads are live — the agent sees the new file immediately in /home/node/.openclaw/workspace.
download
snowclaw download report.pdf
snowclaw download reports/q4/summary.md --dest ./out/
Download a single file from the workspace to your local machine. The basename is preserved.
| Flag | Meaning |
|---|---|
--dest <local-dir> | Target local directory. Defaults to the current directory. |
In-container flow
For chat-driven transfers — where the agent itself suggests a file to download — the bundled snowclaw skill teaches the agent to generate a presigned URL. That flow works alongside these CLI commands; see the Security model page for more on how file permissions are scoped.