Short: Remote desktop and AI agent for Amigas Author: Andreas Wendorf (Akustikrausch) Uploader: akustikrausch gmail com (Andreas Wendorf) Type: comm/net Version: 1.4.0 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. AN AI AGENT THAT WORKS ON YOUR AMIGA, THROUGH MCP 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. It reads the screen as text where a picture isn't needed, can take an installation back, explains a guru, sees which drivers really run, and helps you develop: it builds C programs on the Amiga, reads their debug output and sets tracepoints in them. 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, Amigent-Update for updating an earlier installation, and Amigent.guide, the help for all of it. 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 - After a crash the AI agent puts the guru in words and knows what it did and what ran just before the Amiga went away. - It sees what really runs: libraries, devices and drivers in memory with their versions, programs with their hunks, resident modules, every task with priority and stack. It changes a priority or sends Ctrl-C to a task. - It reads memory (RAM and Kickstart ROM only, never the custom chips) as hex, text or 68k code with library function names, and names any address: program and hunk, library function, ROM module. Enforcer and MuForce hits get those names too. - Tracepoints: when a program you test gets to an address, its registers and the top of its stack are kept, and it runs on without stopping. Writing memory works only when amigentd runs with ALLOWPOKE. - Several background jobs at once, with numbers and return codes; their output can be read while they run. - Before and after a program: memory, open libraries, tasks and ports compared, so leaks show. Screens compared with a saved picture. - New C programs set up and built on the Amiga with vbcc. - A hang or a stutter: what a task waits for with the calls on its stack, who holds the layer locks, the CPU load per task measured on the Amiga, and how closely a dragged window follows the mouse, in milliseconds. - A "Software Failure" requester is read, explained and answered with Suspend, never Reboot. - From the PC, an Amiga in WinUAE 6.1 can be debugged from outside through the emulator's GDB server, saved whole before an installation, and its custom chips read (Paula, copper, sprites). - ZZ9000: the screen is read through the card's own encoder, not over the Zorro bus. A look at a screen where little changed takes 55 ms instead of 0.7 s on a 68060 (firmware 2.9.0, zz9k.library 2). - amigentd gives its screen memory back when nobody is watching (767 KB on an A1200), amigent-monitor draws without flicker, and packing no longer slows down a fast line. - Restart from the remote desktop also on Kickstart 2.x; updating a busy amigentd no longer fails; amigentd builds with GCC as well as vbcc. - Thanks to kaffeine1, midwan, reinauer and AmanitaHouse for their pull requests. 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, ALLOWPOKE. 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.