export.file
blender_export_fileExport Blender scenes to a target file path from a committed snapshot, requiring local user approval for safe, transaction-controlled output.
Instructions
PartMe Blender Harness command export.file. Risk: gated; maturity: L1. Requires local user approval in Blender: a client cannot approve its own request, and it retries the same request id after the user approves it. Requirements: Per-request argument checks and session policy still apply; Approved output root; export additionally requires a committed snapshot
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"path": "<path>",
"snapshotId": "<snapshotId>",
"_transactionId": "<_transactionId>"
},
"name": "blender_export_file"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| overwrite | No | ||
| sessionId | No | ||
| _requestId | No | Stable request id for replay safety | |
| parameters | No | Allowed keys depend on path extension | |
| snapshotId | Yes | ||
| _authorization | No | Action-bound Harness authorization claim | |
| _transactionId | Yes | Harness milestone transaction id | |
| _expectedSceneRevision | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||