Connected devices and data transfer

Amazi Desktop availability

Amazi Desktop is available for Windows x64, Linux amd64 (Debian/Ubuntu), and macOS 13 or later on Apple Silicon. Download the installer from the project's Devices tab. On macOS, open the DMG and move Amazi to Applications. macOS updates require downloading and installing the newer DMG.

Ask Amazi for a clickable link to Devices in your current project. Its format is https://app.amazi.pro/project/{projectId}?chat={chatId}&rightTab=devices, with your actual project and chat IDs and your current Amazi application origin. Keep the existing chat value when available; otherwise omit it. See Direct links to project tabs for the full format. This opens the download tab; a link to this guide opens installation instructions.

Install and open Amazi Desktop, sign in through your browser, and save the project's access settings in Desktop. Then select the device in Devices and click Save. Downloads are available to everyone; using connected devices depends on your plan.

If your account already has connected devices, you can select or deselect one for the project even while it is offline. Change the device switch, then click Save at the top right of Devices. Changes apply only after saving; choosing another device replaces the previous selection. Status refreshes preserve your unsaved changes, and a failed save leaves them available for retry. The header shows the saved selection's connection status: Connected, Offline, or Not connected. Connect new devices and choose the project's access level and allowed folders in Amazi Desktop. The agent works only within those permissions while the device is online. Selecting a device does not grant access by itself. If no devices are connected, the tab shows an empty-state placeholder.

Background work and startup

Closing the Desktop window keeps Amazi running in the system tray on Windows and Linux, or the menu bar on macOS. Device tasks and browser access continue with the project's saved permissions. Use the Amazi icon to reopen the window or choose Quit to stop the application and disconnect the device. Launching Amazi again also reopens its window. Some Linux desktop environments require tray support to show the icon.

Open the account menu and enable Start at login to launch Amazi in the background when you sign in to your computer. This is off by default and applies only to this installation, not your other devices. You can turn it off in the same menu. On macOS, approve the Login Items request in System Settings if prompted. Install the application first; startup is unavailable in portable or development builds.

Device access

Each device card shows Network Access / Network Blocked and Browser Access / Browser Blocked for the project's saved permissions. The network tag follows the command access mode: Full access allows networking, Restricted uses its saved network setting, and Off blocks it. This tag does not test the device's Internet connection or limit Chrome. Full access includes the browser automatically; Restricted has a separate browser toggle, and Off blocks the browser. Expand Device details to see Chrome's connection status: Connected, Connecting, Disconnected, Not configured, or Connection error. Status refreshes automatically; an offline device or an expired connection check is no longer shown as connected. Change browser permission in Amazi Desktop; the agent connects when needed for a task.

Ask Amazi to list the project owner's devices to see their connection and access settings, including devices not currently selected. Only the selected device can execute commands; listing devices does not connect them to the project or change their permissions.

When an authorized task works in another project you own, device commands use that target project's selected device and saved permissions. Access from the original project does not grant access to the other project's device.

Amazi can check a selected device's details even when access is Off or its permissions have not been saved. It explains whether access needs to be enabled, settings need to be saved, or the device needs to reconnect. A connected device can still have access turned off for this project.

In Desktop, the web-selection reminder appears at the top of the project's settings. Off blocks all project access to the device, including commands, files and the browser. Restricted runs commands in the sandbox with your folder and network limits. The agent can also request an ordinary-terminal command without these limits: a saved rule authorizes it, otherwise only the device owner can approve it in chat. Full access runs commands with your operating-system account's file, program and network permissions, without those folder/network limits. Save the permissions in Desktop and save the device selection separately in the web project's Devices tab.

Each device shows its access mode beside its online status and in its details: Off, Restricted or Full access. Restricted also shows folder and network permissions. Each folder's Read only or Read and write permission appears as a gray tag; the two permissions use different shades. Restricted also shows saved terminal command rules. Selecting a device does not change its saved folder and network settings. Deselecting it in Web revokes its command rules and pending approvals for the project.

The account owner or an administrator can expand Device details and choose Disconnect device at the bottom right. Confirm the action, then click Save to unlink the device from its owner's account and every project and sign out its Desktop session. Before saving, Undo removal cancels the pending disconnection. Connecting it again requires signing in and selecting it for the relevant projects. Invited participants, including those with full project access, cannot unlink the device from its owner's account.

In Amazi Desktop, open the account menu and choose Sign out and remove device. After confirmation, the device is removed from your account and all projects, and you are signed out of Desktop. If removal fails, you stay signed in and can retry.

Device actions are available only through Amazi chat. In Restricted, an ordinary-terminal request without a matching rule shows a confirmation before execution. Failed sandbox commands also request a new execution in the ordinary terminal, using a saved rule or owner approval. The error may have another cause; retrying may repeat partial changes. The command appears in a separate code block with its first 100 characters followed by an ellipsis when longer. Choices show only their labels, with the program prefix highlighted. This only shortens the display; approval runs the full original command with full access. The device owner can Deny, Allow only this time, Allow this command in future, or Allow all program * commands in future. The last option stays visible but disabled when Amazi cannot identify a literal program. Only the two future-permission choices save a rule. An exact rule matches the whole command, including its arguments and any literal * characters. A prefix rule allows the program with additional literal arguments from any working folder for this project and device; it does not automatically allow shell chains, substitutions or redirects. Amazi sees remembered permissions on its next device check. Choose Deny or stop the task to cancel the action. After approval, Amazi continues the saved command automatically; no additional message or agent request is needed. Cancellation, lost connection and revoked access never request retries. Ordinary-terminal errors do not start another approval request. A successful sandbox command can still miss host processes or services; Amazi can explicitly request a terminal check when needed. Switching modes cancels pending and one-time approvals and stops active commands. Saved command rules and Restricted folder/network settings are retained separately, including after restarting Desktop. Full access includes files, programs and the network with your operating system account’s permissions.

In Amazi Desktop, Network access sits above the settings tabs and controls sandbox networking. Restricted has two tabs: Sandbox folders for folder permissions and Terminal allow list for commands permitted outside sandbox limits, including permissions granted in chat. Click Add command, enter a command and choose exact or prefix; enter prefixes such as git or git status without adding *. Use the delete button to revoke a rule. Existing entries cannot be edited: delete and add a replacement. Command-list changes apply immediately while connected, separately from Save for project. Web Devices shows the list read-only. Saved rules authorize terminal execution in Restricted and remain available when you return to that mode. A program prefix permits any literal arguments, including destructive operations or code passed to an interpreter.

Only the project owner can approve a device command or save a permission rule. Other participants see this restriction inside the question card. Anyone with permission to chat can choose Skip: the command will not run and no permission will be saved. The chat input remains visible while the question awaits an answer.

When you first save a device's permissions for a project, Approved commands starts with a small set of exact diagnostic commands for its operating system, covering the current folder, file listing, user, computer name and running processes. These rules authorize terminal execution in Restricted and can be deleted like any other saved rule. They do not allow extra arguments. Existing project/device settings are not changed. Saving again, switching modes or reconnecting does not restore deleted rules.

In Amazi Desktop, Full access includes browser access automatically. In Restricted, enable Allow browser access; this toggle starts disabled and changes apply immediately. Either permission lets the agent connect to your personal Google Chrome for that project's tasks without a separate chat confirmation. You do not need to keep a browser session connected in advance or paste a token into Desktop.

Install the official Playwright extension in Chrome. When a task needs your browser, the agent starts a connection. The extension may ask you to select the intended tab in Chrome. Existing saved browser credentials remain local. The agent receives only the connection status and the exposed tabs.

Enabling access, restarting Desktop and background checks do not open connection tabs. Closing the last tab in the Playwright group ends the session; your project permission remains saved. If the connection is lost, Desktop updates its status and sends a system notification, including while minimized. The agent can request a new connection for a task, but failed connection attempts and interrupted website actions are not retried automatically.

The browser session is shared across permitted projects. Access includes signed-in pages and is independent of folder limits and sandbox networking. Off blocks all browser access, hides the toggle and stops that project's current browser work, even if its browser permission was saved earlier. The device must be selected for the project and online. In Restricted, turn off Allow browser access to block further actions and stop that project's current browser work. Other project permissions stay saved.

A failed page action does not by itself mean browser access was revoked. Amazi reports the action's error and can continue using an available session. In Full access, synchronizing a previously saved Restricted browser setting does not interrupt browser work.

Amazi Desktop lets you work with a connected device's files from your project, with separate access permissions for every project. Sign-in uses the browser and the available Amazi login methods. Theme and language follow your account settings.

Device file transfers require Restricted with suitable folder permissions or Full access; terminal rules do not authorize transfers or exceptions to their folder settings.

In Desktop, Restricted lets you choose folder permissions and network access. On Windows, All folders is always enabled with Read only access and cannot be turned off or changed to write access. Commands can read outside the selected folders, except protected Amazi data, subject to Windows permissions. Add individual folders with Read and write access to allow changes. You can save without individual folders when only reading is needed. Linux and macOS restrict user-file reads to the selected folders, with the system resources needed to run commands still available.

On Linux/macOS, add at least one folder or enable All folders before saving. On these systems, this switch covers your home folder, not every drive; its read/write selector becomes available when enabled. On every system, Selected folders remains editable alongside general access: you can add, remove and change individual folder permissions. Saving preserves these permissions together. Changing or turning off general access on Linux/macOS keeps the individual folders and their permissions. The home-folder path and access explanation stay above the access modes. Errors and successful saves appear inside Desktop. In the background, Desktop also requests system notifications. In Web, expand folders and approved commands to inspect their lists; their settings are changed in Desktop. You can correct your settings without losing the draft.

If Desktop shows Update Amazi Desktop, select Check for updates or download the latest installer from Devices. The notice shows your installed version and the minimum supported version. Device access pauses while the versions are incompatible; signing in again does not fix this. If the notice asks for a server update, update the local server or contact its administrator.

Updating Desktop

Starting with version 0.25.0, installed Windows and Linux apps check for updates at startup and periodically while running. You can also select Check for updates in the account menu or on the sign-in screen. Select Download update, wait for the download, then select Update and restart and confirm. Before restarting, Amazi stops active commands and file transfers. Save any unsaved settings first. Your sign-in, device and saved access settings are retained. Linux may ask for your system password. You can postpone an update; closing the app does not install it automatically.

Version 0.24.0 needs one manual installation of a newer version to gain this feature. Close Amazi and run the newer installer under the same operating-system account without deleting Amazi's settings. On Debian/Ubuntu, open the new DEB in the package installer or run sudo apt install ./<downloaded-file>.deb. Portable builds are updated manually. If a check or download fails, keep using the installed version and try again when your connection is available.

Import and export project database data

File transfers preserve contents without parsing or conversion. For database imports, first copy the file into the project, then ask Amazi to write and run a task-specific parser in the project runtime. For exports, prepare and verify the file in the project runtime first, then copy it to your device. Files already in the project can be processed without Desktop; see Database and storage.

Specify the table or query, project file path and import behavior. Appending, updating matching rows, replacing rows and restoring a database have different effects. Development and production share the database; confirm consequential changes after their scope is clear. See Database and storage.

Wait for the completed result before using the destination. Starting a transfer is not proof of completion. Cancellation or an error can interrupt work; ask Amazi to inspect an uncertain result before retrying. Transfers involving files on your device require a connected device with access to the relevant folders.