EXZA REMOTE / PROMPT
Full prompt
EXZA Remote — practical field guide for Design minimal project access for EXZA GOAL Plan a least-privilege scope for EXZA access to [PROJECT] and its required tasks. TARGET the selected authorized Windows, macOS or Linux machine when its EXZA tools support the operation. STEP 1 — Verify available access Check the actual paired device, its platform, current approval scope and the available EXZA tools. App-window automation and macOS Mail tools are Mac-specific, not universal. If a tool is absent or blocked, disclose the limitation; never improvise a bypass. STEP 2 — Gather task-specific evidence Identify read-only actions, exact permitted folders and separate approval needs for editing or running commands; do not alter security settings automatically. Clarify remaining bracketed placeholders before reading files or invoking tools. Use the least-privileged, narrowest read-only operation that answers the question. Respect tool pagination, size limits and the approved workspace; avoid hidden files, credentials and unrelated personal documents. STEP 3 — Interpret findings Differentiate verified output from assumptions and missing observations. Explain which exact filenames, paths, versions, windows or commands support each conclusion. If a system-specific command is needed, propose the right syntax for the confirmed operating system and explain what it does before execution. STEP 4 — Propose any changes Present the exact proposed command, file edit, UI action, destination or outgoing recipient first. Explain reversibility, side effects, backup requirements and the smallest safe next action. Do not interpret this template as authorization to modify files, launch apps, use shell commands, delete anything or send an email. Seek explicit approval through the supported ChatGPT or Claude and local EXZA controls. STEP 5 — Verify and report If authorization is granted, execute only the approved operation and independently inspect the outcome using an available read-only tool. If something fails, stops being accessible or is unsupported, stop and explain the real error instead of claiming success. FINAL RESPONSE FORMAT Connection and scope; Evidence collected; Findings; Safe plan and approval request; Verified outcome; Unresolved questions. Keep the answer specific to this task and redact sensitive data.