{"id":94087,"plugin_id":"plugin_asdk_app_6ae5ff48500481919bc74f9e26ab3aa6","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-13T00:10:24.458Z","digest":"2a47b263cc5d81e326974656658e3847b26c628c2f42781529adc2f8e2a856fe","against":null,"payload":{"description":"Connect an EXZA Remote computer safely and check its live status in ChatGPT.","included_files":[],"name":"get-started","skill_md_contents":"---\nname: get-started\ndescription: Connect an EXZA Remote computer safely and check its live status in ChatGPT.\n---\n# EXZA Remote — first connection\n\nEXZA Remote connects a ChatGPT user only to the computer they own or are explicitly authorized to administer.\n\n1. Open https://remote.exza.de and sign in. Open registration requires email confirmation; no invitation code. Never ask for or collect user passwords, invitation codes, device secrets or email verification codes in chat.\n2. Start the EXZA Remote Connection client on macOS, Windows or Linux using the system's terminal starter. Keep the EXZA terminal window open.\n3. Enter the six-digit pairing code into the website and review the account email shown in the computer terminal; press **Y** once to approve or **N** once to deny (no Enter required in an interactive terminal). Enter alone never approves pairing. If the account is unfamiliar, deny pairing.\n4. Complete the EXZA OAuth authorization and choose the correct computer.\n5. Use EXZA Remote tools only for the authenticated device explicitly selected by its owner. Read and write capabilities require OAuth scopes; ChatGPT presents its native approval dialog according to the connected app permission settings; the terminal logs actions. A confirmation dialog cannot be forced by the MCP server. Never bypass consent or reveal private pairing secrets.\n6. A listed capability is not proof that a specific device or account is authorized. If a tool is unavailable, disabled or needs new scopes, explain that rather than claiming a completed action. Never claim access to file operations, shell commands, application control, email send or payment checkout while they are locked. Do not suggest bypassing ChatGPT host confirmation or elevated OAuth. Do not ask a user to disable security controls.\n7. If the device is offline, tell the user to start EXZA Remote Connection on that computer. Stopping or closing the EXZA terminal ends its connection.\n\nFor help: https://remote.exza.de/support.html or info@exza.de.\n\nUsers may remove computers from My Devices or permanently delete their EXZA account in Account settings. Account deletion requires the exact word DELETE, current password and browser confirmation, revokes device and OAuth access and ends EXZA Premium billing. Legally required invoices and third-party processor records may remain. Never bypass owner consent.\n\nPermission policy: Initial OAuth grants computer:read only. External directory listings and write/device tools require separate computer:write OAuth consent. The plugin uses the native ChatGPT tool approval flow and the account-specific ChatGPT App permissions (Always ask, low-risk actions, etc.). ChatGPT alone controls whether an approval is shown and whether an Always allow option is eligible. EXZA must not fabricate confirmation, claim an unseen click or provide a fake native-looking window. OAuth scopes, selected device account, file sandbox, deny mode, local full-computer scope for commands, and system privacy rules remain independent barriers. The terminal shows redacted request and result logs, never an extra approval for authorized cloud tool calls. Do not call shell or mail tools without the user's specific request.\n\n## Disconnect and reconnect\n- Clicking **Disconnect** in My Devices completely closes the foreground EXZA Remote computer connection and local agent. It does **not** delete the saved device pairing.\n- There is no automatic web Resume. To reconnect, the user must manually start EXZA Remote on that computer through the normal terminal installer/launcher; no new pairing PIN is required unless the device was permanently removed.\n- **Remove** revokes the saved device pairing, and starting again requires a confirmed new pairing.\n\n## External directory listings (RC36)\nFor an explicit request to list Downloads, Desktop, Documents or another directory\noutside the EXZA workspace, call exza_list_external_folder directly with its exact\npath. The server deliberately rejects such paths through exza_list_files, so a\nread-scope-only tool can never silently elevate into computer:write. ChatGPT\ncontrols the native approval prompt according to app settings. The additional\nOAuth scope computer:write is required regardless of ChatGPT app setting.\nThe server returns at most 200 visible names/types in that single directory,\nwithout contents or permanent home permission. User home root itself is blocked;\nprivate and hidden paths are blocked, including symlink escapes.\nIf ChatGPT declines or blocks the action, no tool execution reaches EXZA.\nThe operating system may still require a one-time privacy permission.\n\n## Safe Downloads folder creation (RC38)\nIf the user explicitly asks to create a new folder directly inside their Mac Downloads,\ncall **exza_create_downloads_folder** with only the desired folder name. Do not use\n**exza_run_command** for that operation or ask for full-computer scope.\nThe tool requires computer:write OAuth and ChatGPT native app permission according\nto user settings. Its action is limited to a single NEW visible folder directly\ninside Downloads; existing folders, symlinks, absolute/relative paths, and hidden\nnames are rejected. Any macOS privacy permission still applies.\n\n## Managed everyday operations (RC39)\nFor named Downloads/Desktop/Documents/Pictures/Music directories use exza_home_list, exza_home_mkdir,\nexza_home_read_text, exza_home_write_text and exza_home_move instead of exza_run_command.\nFor an existing text file read first and provide the exact expectedSha256 to update it.\nOpen installed macOS applications with exza_desktop_launch and visible unsent email drafts with exza_email_draft.\nShell commands, long-running jobs and email sending remain powerful operations and require the active owner-approved terminal session, computer:write OAuth, and applicable ChatGPT permissions. ChatGPT's own permission UI is host-controlled.\nNever assume its confirmation will always appear; explain scopes honestly.\n\n## Everyday desktop toolkit (RC40)\nUse dedicated exza_home_info, exza_home_copy, exza_home_search, exza_system_info, exza_process_list,\nexza_browser_open, exza_clipboard_read and exza_clipboard_write.\nDo not use exza_run_command as a shortcut for these ordinary tasks. Never assume the ChatGPT\nnative permission sheet will always appear; access is controlled by host app settings and OAuth.\nClipboard contents can be sensitive: read only when explicitly requested.\nBrowser opening is a side effect. For arbitrary shell access and email sending, retain\nan active owner-approved terminal session. Linux requires appropriate desktop commands\n(xdg-open, wl-clipboard/xclip, gio); Windows PowerShell and Explorer must be installed.\n\n## Recoverable deletion (RC41)\nFor deleting files/folders under a managed Downloads, Desktop, Documents, Pictures or Music\npath, call exza_home_trash with the exact area and relative path. NEVER use exza_run_command\nfor a simple deletion, and do not ask the user to enable full-computer scope for it.\nexza_home_trash moves one existing item to a private EXZA recycle bin and returns recycleId.\nUse exza_home_trash_list to inspect records and exza_home_restore with recycleId to restore.\nPermanent deletion is intentionally not exposed. Users may have to approve each tool in\nChatGPT, depending on their ChatGPT permission setting; an app cannot force host popups.\n\n## Owner-confirmed computer access (RC48)\nThe user physically presses Y once in the visible EXZA Terminal to approve the verified account/device and computer control for this terminal session, or N to deny. The first pairing also requires the six-digit PIN in My Devices. Previously paired computers keep their saved pairing identity but need a new physical Y/N each time the client is started. No second Y, scope computer, or confirm computer step is valid. The grant ends when the terminal closes or the user disconnects; scope workspace revokes computer control immediately. OAuth, ChatGPT tool permissions, and OS privacy settings still apply.\n\n## RC43 interactive jobs / multiple text reads\nUse exza_process_start to create an interactive job ONLY after owner-enabled local computer scope.\nUse exza_process_output (offset optional) to read live output and exza_process_input to send\ntext into that exact process session. Use exza_process_sessions and exza_process_stop to\ninspect/stop EXZA-owned sessions. Never use these tools to avoid the owner permission gate.\nUse exza_home_read_multiple_text for 1-8 text files in the same managed home area.\nThe native ChatGPT Allow Once / Always Allow UI is controlled by ChatGPT, not the plugin.\nMac Mail sending remains subject to its existing local authorization requirement.\n\n## RC48 email permissions\nMac email sending via exza_email_send requires the active owner-approved computer session, computer:write OAuth, applicable ChatGPT tool authorization, and macOS Mail automation permissions. Only send a message when the user explicitly requests the exact recipient and contents. Email preview never sends. Do not promise delivery.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}