The Ecosystem

From one Mac app to a family of Amiga tools

Amiga Imager started in December 2025 as a way to build PiStorm images on a Mac. Along the way it grew shared building blocks, an emulator for iPad and iPhone, tools that run on the Amiga itself, and tools that let an AI agent work on real Amiga hardware.

On the Mac, iPad and iPhone

The apps you install.

macOS

Amiga Imager

Builds bootable Amiga systems for PiStorm/Emu68, Classic A500 to A4000, Vampire V4, MiSTer, UAE and Amiberry. Reads and writes floppies through Greaseweazle and DrawBridge, and keeps an eye on every Amiga on your network with the Amiga Fleet console.

Amiga Imager →
iPad · iPhone · Mac

Amigo

A native port of WinUAE for iPad, iPhone and Apple Silicon Macs. Free, without ads or accounts, and GPL-2 like WinUAE itself. It boots the free AROS ROM on first launch, so there is nothing to set up.

Amigo on the App Store →
iPadOS prototype

Amiga Imager Pad

A proof of concept that answered one question: does the Amiga Imager engine run on an iPad? It does. The prototype builds a bootable Amiga disk image on the device, writes files into it and browses it, with no Mac involved.

Prototype, not released

Shared building blocks

Native Swift modules inside Amiga Imager. They replaced the external tools and the shell scripts the app started with.

Disk engine

AmigaDiskKit

Reads and writes Amiga disk images without external tools: RDB and MBR layouts, FFS/OFS, PFS3 and FAT32 partitions, ADF floppies including raw flux from Greaseweazle, and LHA archives. It replaced hst-imager in June 2026.

AmigaDiskKit on GitHub →
Build engine

AmigaBuildKit

The native build engine that installs AmigaOS, drivers, RTG and networking into an image. It replaced about 28,000 lines of Bash scripts in 18 days in June 2026.

Software

AmigaPackageKit

Fetches and stages the optional software for a build, from WHDLoad and ScummVM to IBrowse, AmiSSL and MUI, with checksum-verified Aminet downloads.

Fleet

AmigaFleetKit

Powers the Amiga Fleet console: every Amiga on the network on one board, with a shell, file copy in both directions and the screen over VNC.

On the Amiga

Tools that run on AmigaOS 3.x, on real hardware and in emulators.

Package manager

amipkg

A package manager for AmigaOS 3.x: amipkg install downloads the software, checks it against a cryptographically signed catalog and resolves dependencies for your CPU. Runs from a stock A500 to a Vampire, as a CLI, a GadTools GUI and a MUI GUI.

amipkg guide →
Catalog

amiga-pkg

The package repository behind amipkg. It collects package submissions, validates them and publishes the single signed index that amipkg and Amiga Imager-built systems trust.

amiga-pkg on GitHub →
Remote control

amiagent

A small daemon on the Amiga that runs AmigaDOS commands, copies files, takes screenshots, sends mouse and keyboard input and drives GUI programs through its ARexx port. TLS is used when AmiSSL is installed.

amiagent on GitHub →
MUI

amifleet68

The Amiga Fleet console, native on the Amiga as a MUI application. It talks to every amiagent on the network directly, with no Mac in the loop.

amifleet68 on GitHub →

For the AI agent

The tools that let Claude work on real Amiga hardware instead of guessing how an Amiga behaves.

MCP server

amimcp

An MCP server on the Mac that gives Claude hands on a real Amiga through amiagent. You describe the problem, and Claude tries it on the actual hardware.

amimcp on GitHub →
Know-how

AllAmigaTooling

A Claude Code plugin with one skill per project. It tells the agent which tool already exists for disk images, 68k builds, packages, icons and real hardware, so it uses them instead of rebuilding them.

Toolchain

amiga-sdk

One build-and-run layer over the m68k cross compilers: pick a CPU profile and get the right compiler, flags and link order, plus a way to run the result on a matching Amiga. Four fixes found along the way went upstream to GCC and libnix and were merged.

How it grew

December 2025

The first idea was to run the Windows Emu68 Imager on the Mac through PowerShell. The scripts were not the problem, the Windows user interface was. So the first Amiga Imager was a Swift interface around Bash scripts and hst-imager.

June 2026

AmigaDiskKit replaced hst-imager first. Then the native Swift build engine replaced the Bash scripts, 28,000 lines of them, in 18 days.

July to September 2026

Amigo, amipkg, amiga-pkg, amiagent and amimcp, AllAmigaTooling, amiga-sdk and amifleet68 followed, each one filling a gap the previous one had made visible.


What the ecosystem made possible

In September 2026 the tools came together for a project nobody had planned: a port of OpenRCT2, the open-source RollerCoaster Tycoon 2 engine, to 68k AmigaOS. It was started from an iPhone by the pool on Maui, during my honeymoon: the iPhone drove Claude, Claude drove the Mac at home, and the Mac ran Amigo with amiagent inside. The first build started in Amigo on the first day. After eight days there were 118 commits and 26 test builds, and the simulation matches the Mac bit for bit.

OpenRCT2 for Amiga on GitHub →

The idea for amiagent came from Jan Stermann, who said that if I ever had the time and the tokens, I could give it a try. Years of client platform engineering meant I knew how agents work. Jan has since used the ecosystem to build ami2ha, a native Home Assistant client for AmigaOS with a MUI dashboard, live updates over WebSocket and an ARexx port.

ami2ha on Aminet →  ·  ami2ha on GitHub →