Answers for every step.

EXZA Remote connects your own computer to AI assistants using an agent that runs visibly in a terminal. During the open beta, authorized users can request file, shell and application actions from supported AI assistants. Device pairing, OAuth scopes and explicit on-computer approval protect sensitive operations.

Registration is open to everyone. Create an account with a strong password (at least 12 characters) and verify your email with the six-digit code. No invitation is required.

Obtain the official agent package from the official EXZA Remote download source. Extract the entire archive, check its source, and run the correct launcher for your operating system. Do not execute unknown scripts.

Sign in to your customer portal, request device pairing and explicitly approve it in the local terminal. Then authorize the EXZA Remote MCP connection in AI assistants with OAuth. Official AI assistants app review and wider availability are still pending; the cloud tool only reports device status.

Yes. The computer must remain powered on, connected to the internet and running the agent terminal. Closing the terminal, losing the connection or entering sleep mode makes remote commands unavailable. The service cannot turn on a powered-off computer.

Use a compatible version of macOS, Node.js 22 or later and an internet connection. Open Terminal and run node --version to verify the Node.js installation. The Mac agent has been tested locally.

Open Terminal in the extracted agent folder and run ./Start-EXZA-Remote.command. If the executable bit is missing on a verified package, run chmod u+x Start-EXZA-Remote.command. Keep Terminal open while connected.

Verify the package source and make sure the full archive was extracted. Open the launch script using Terminal in the package folder. Do not disable Gatekeeper or macOS security globally.

Run node --version in the same Terminal. Install Node.js from its official website if missing, reopen Terminal, and ensure the active shell loads any Node version manager configuration.

Local development supports explicitly approved workflows, but supported local workflows can use Blender, Mail, shell commands and files after OAuth authorization and required approval on the paired computer. Premium never bypasses consent.

Windows 10 or 11, Node.js 22+, Command Prompt and internet access. Windows launchers are included, but independent native end-to-end testing is still outstanding.

Extract the complete official agent package. Open Command Prompt in the agent folder and run Start-EXZA-Remote.cmd. Check node --version first.

Check your folder using cd and dir. Confirm the CMD launcher exists and Node.js is installed and available in PATH. Restart Command Prompt after installing Node.js. Review antivirus warnings before proceeding.

Normally no. Run the agent with ordinary user permissions. Do not elevate to Administrator merely to bypass a permissions error.

The Linux launcher is a beta target. Distribution-specific validation is not yet complete. A current Linux distribution with Node.js 22+, a shell and internet access is recommended.

In the extracted official agent directory run node --version and then ./Start-EXZA-Remote.sh. If necessary, inspect and mark the trusted launcher executable with chmod u+x Start-EXZA-Remote.sh.

Check file permissions with ls -l Start-EXZA-Remote.sh, check your current directory and any noexec mount flags. Do not run as root to bypass checks.

Pairing persists until revoked, but paired does not mean online. Restart the agent and refresh the device screen. You can revoke the old device pairing in the portal.

Check spam and the entered email address. Verification messages use the configured EXZA Remote sender at mail.exza.de. Request a new code and note that codes expire after ten minutes. Contact info@exza.de if delivery still fails.

Codes are short-lived and tied to a specific running agent terminal. Request a new code and approve the correct account in the local terminal. Never publish pairing codes.

Check power, internet, terminal process and firewall or VPN restrictions on outbound connections. Restart the agent if necessary. No inbound router port forwarding is required.

Check that the computer is online, select the correct paired device, grant the required OAuth scope and approve the request in the local terminal. Sensitive commands are rejected without authorization or approval.

Verify your EXZA account email, pair the intended device, and restart the AI assistants OAuth authorization if your code has expired. Use the same account as the paired device.

Rate limits protect sign-in and device pairing. Wait for the cooldown, avoid submitting the same code repeatedly and contact support if you cannot continue.

Pairing requires an authenticated account and an explicit confirmation in the local terminal. The remote agent does not silently grant desktop access.

Sign in to your customer portal, open Devices and select the revoke action for the relevant device. This also invalidates associated access tokens.

No. Sensitive authentication data must not be shown or stored in public dashboard views. Use strong account credentials and never share pairing or verification codes.

The agent disconnects and no new computer operations can proceed. Active local agent jobs are stopped by the tested terminal shutdown workflow.

The free plan includes up to 10,000 accepted MCP tool calls per UTC calendar month. Your portal shows the used count and the remaining allowance.

The verified EXZA Remote Stripe subscription price is currently €20.00 per month including VAT. Check the displayed Stripe-hosted checkout for the final terms before subscribing.

Only a correctly verified Stripe subscription event makes Premium active; simply returning to the portal from Stripe does not prove payment. Activation may take a short time while the event is processed.

Use the Stripe customer billing portal from your account when available. A separate cancellation declaration form exists, but filing a request there requires operator processing and does not automatically stop Stripe billing.