Short: Remote desktop and AI agent for Amigas Author: Andreas Wendorf (Akustikrausch) Uploader: akustikrausch gmail com (Andreas Wendorf) Type: comm/net Version: 1.3.0 Replaces: comm/net/amigent-1.1.1.lha Requires: a TCP/IP stack with bsdsocket.library, such as Roadshow Architecture: m68k-amigaos >= 2.0.4 Distribution: Aminet A REMOTE DESKTOP FOR YOUR REAL AMIGA, LIKE TEAMVIEWER OR VNC Sit at your PC or Mac and use your Amiga as if it were in front of you: its screen live in a window, your own mouse and keyboard on it, Amiga keys and shortcuts on a side panel, files in either direction (drop them on the window to send them) and one shared clipboard. No VNC server and no extra software on the Amiga beyond this archive, and it stays quick even on a 7 MHz 68000 behind a plipbox. And if you like, an AI agent (Claude, Codex or any other MCP client) takes over the same way: it runs commands, copies files, installs software and clicks through programs, while you watch every click in that window and can take over at any moment. This archive is the Amiga half: amigentd, the small service that does the work on the Amiga, amigent-status, a window that shows who is connected, amigent-monitor, a window that shows what the agent is doing, and Amigent-Update for updating an earlier installation. The PC or Mac half is a Python package: pipx install amigent or just tell your AI agent: "Install Amigent from https://github.com/akustikrausch/amigent for me." It then finds the Amiga on the network and sets everything up from the PC. NEW IN THIS VERSION - Scripts on the Amiga can bring a window to the front and type into it through the ARexx port: ACTIVATEWINDOW, TYPE and KEY. - A drive that isn't there makes a command fail at once instead of opening an "insert volume" requester that waits for someone at the Amiga. - Games and programs on 256-colour graphics card screens come through in their real colours in the remote desktop and in screenshots. - After a lost connection the AI agent learns whether the Amiga started again and which guru code it kept. - An open menu or a popup left open on the desktop, which holds back every new window, is noticed; the AI agent closes the popup before it starts a program. - The AI agent reads the text on the screen instead of taking a picture where text is enough, and waits on the Amiga for a window or a text. - Data travel packed when the Amiga packs faster than its network carries, such as a PiStorm behind a plipbox: several times as fast. - amigent-monitor, a window on the Amiga, shows line by line what the AI agent does, with the traffic of the link; it fits an A500 screen too and can be sized. - The AI agent moves and sizes windows by mouse movement, as a hand would, so drag bars, size gadgets and programs that follow the mouse react. - Other AI agent bridges on the same Amiga, such as amimcp, are noticed and reported before the first click; nothing of theirs is touched. - Installations can be taken back; Aminet archives install from the PC, disk images (.adf, .adz) included. - kprintf and Enforcer output reach the AI agent (start amigentd with NOTEXT or NODEBUG to leave the recording out). TUNED FOR SLOW AMIGAS AND SLOW NETWORKS Chipset screens go out as the bitplanes the Amiga keeps anyway, graphics card screens as tiles with their own small palette, and only what changed. Mouse and keys are carried out at once, even while a picture is still on its way. 68000 at 7 MHz, 640x256: whole screen 0.6-1.0 s, unchanged 80 ms, under 10% of the CPU while the PC watches 68020 at 14 MHz: whole screen 0.1 s, 2-3% of the CPU 1920x1080 RTG on a plipbox (about 50 KB/s): whole screen about 3 s INSTALLATION 1. Unpack the archive, e.g. LhA x amigent.lha RAM: 2. Double-click amigentd (amigentd.000 on a plain 68000), or in a Shell: RAM:Amigent/amigentd SETUP 3. On the PC or Mac: pipx install amigent, then amigent-setup. It copies amigentd to C:, adds it to S:User-Startup and gives it a key. 4. For the remote desktop alone, no AI agent needed: amigent-viewer --install puts Amigent into the Start menu (Windows) or Applications (macOS). A Vampire's 68080 runs the plain amigentd. Tool types and Shell arguments: SETUP, KEY=, PORT=, QUIET, TLSONLY. amigentd answers ARexx on the port AMIGENT (STATUS, CLIENTS, VERSION, PAUSE, RESUME, ACTIVATEWINDOW, TYPE, KEY, BUSY, HELP, QUIT). UPDATING FROM AN EARLIER AMIGENT Amigent has two halves, amigentd on the Amiga and the program on the PC or Mac. Update both. Easiest: paste this into your AI agent: Update Amigent for me, both halves: run "pipx upgrade amigent" on this computer, then "amigent-setup --update" for the amigentd on my Amiga. Then tell me to restart you, so you get the new tools. By hand, from the PC or Mac, both at once: pipx upgrade amigent, then amigent-setup --update. Or on the Amiga: unpack the archive, double-click Amigent-Update in its drawer, then run pipx upgrade amigent on the PC. Afterwards restart the AI app and the remote desktop. Key, certificate and the start line in S:User-Startup stay. Should the new amigentd not start, the old one starts again. One side alone keeps working as before; the new features need both. From 1.3.0 on the PC tells you when the Amiga is ahead. REQUIREMENTS AmigaOS 2.04 or newer, any CPU from the 68000 on, a network connection (a plipbox on the parallel port is enough). Encrypted connections need OS 3.0 and AmiSSL 5.1 or newer. Updating on the Amiga needs ARexx (RexxMast). On the PC: Windows, macOS or Linux with Python 3.10 or newer. SECURITY amigentd asks every connection for a key that amigent-setup creates, and with AmiSSL it encrypts the connection with TLS, pinned to the certificate made for this Amiga. Keep it in your home network; do not open its port to the internet. Source, documentation and the wire protocol: https://github.com/akustikrausch/amigent Licence: MIT.