EXZA REMOTE / PROMPT
Full prompt
EXZA Remote — detailed execution plan: Blender Python script code review OBJECTIVE Review bpy script for destructive operators, version mismatches, path writes and missing output validation before running. TARGET the currently paired, authorized macOS/Windows/Linux computer, subject to its actual supported EXZA tools. 1. PREFLIGHT AND ACCESS Confirm which device is actually paired, its OS, owner-approved scope and the real EXZA tool descriptions. For Blender tasks, check whether Blender and a compatible bpy/Python interface are installed. EXZA can inspect permitted files and propose scripts; do not claim it can directly manipulate Blender mesh vertices by itself. For scripted changes, show a version-compatible Blender background invocation and exact output paths, then require owner approval to run it. GUI keyboard automation is limited and may not be reliable for precision modeling. A model or render exists only if actual result files can be verified. 2. TARGETED DISCOVERY Ask me for required dimensions, versions, exact object names, file paths, file formats or recipients whenever they are needed. Inspect only the selected, authorized resources with bounded read-only tools. Check existing files, relevant documentation, file size limits and possible conflicts before taking action. 3. TASK-SPECIFIC PLAN Review bpy script for destructive operators, version mismatches, path writes and missing output validation before running. Propose concrete ordered steps, expected artifacts, meaningful filenames, measurable acceptance criteria and a small preview or test stage. Explain likely failure modes and how to preserve the original state. 4. APPROVAL BEFORE MODIFICATION Show the exact file edit, Blender Python script, terminal command, GUI text, or email recipient and message as applicable. Explain permissions, data exposure, possible side effects, target paths, estimated output size if relevant, and any non-reversible changes. Do not interpret this sample prompt as authorization. Ask for explicit approval through the AI client and local EXZA owner controls; never bypass denials or elevate privileges. 5. IMPLEMENTATION AND VALIDATION Only after approval, use a genuinely supported EXZA operation within the authorized workspace. Never overwrite original assets, delete files, mail recipients or trigger external actions implicitly. Confirm real tool output and independently verify results using read-only file metadata, project checks, rendered preview or test command where supported. If a step is unavailable, stop that step honestly. 6. REPORT Provide: preflight, evidence, proposed changes, approvals needed, executed actions, verified outputs, remaining limitations and precise next steps. State which operations were not performed. Mask credentials and unrelated personal data.