Running Kiro CLI from a Raspberry Pi 400

Source: Dev.to

Getting Started with a Raspberry Pi 400

I received a Raspberry Pi 400 a few years ago and set it aside. After working with Kiro for a couple of months, I decided to try running the Kiro CLI on the Pi.

Preparing the SD Card and OS

1. Flash the microSD

   • Use Raspberry Pi Imager and select the default Raspberry Pi OS (Debian‑based).
   • Complete the initial configuration, insert the card, and power up the Pi.

2. SSH into the device (if it’s on your local network):

   ssh user@

Installing Required Tools

# Update the system
sudo apt update && sudo apt upgrade -y

# Install Node.js (v20) and Git
curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -
sudo apt install -y nodejs git

Verify Architecture

uname -m          # should output: aarch64
ldd --version     # e.g., ldd (Debian GLIBC 2.41-12+rpt1) 2.41

The Pi 400 runs on ARM64 (aarch64).

Installing Kiro CLI (Standard Build)

Follow the official “Linux ARM (aarch64)” instructions:

# Download and unzip
curl --proto '=https' --tlsv1.2 -sSf \
  'https://desktop-release.q.us-east-1.amazonaws.com/latest/kirocli-aarch64-linux.zip' \
  -o kirocli.zip
unzip kirocli.zip

# Run the installer
bash ./kirocli/install.sh

Add the binary to your PATH:

echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc

First Run (fails)

kiro-cli
# → Illegal instruction (SIGILL)

The standard glibc build crashes with a SIGILL error on the Pi.

Switching to the Musl Build

The documentation also provides a musl variant, which is built against a different C library.

# Download the musl build
curl --proto '=https' --tlsv1.2 -sSf \
  'https://desktop-release.q.us-east-1.amazonaws.com/latest/kirocli-aarch64-linux-musl.zip' \
  -o kirocli.zip
unzip kirocli.zip

# Install
./kirocli/install.sh

Now the CLI runs correctly:

kiro-cli

Using Kiro CLI

The login flow works as expected, and both simple and complex tasks execute without issues. The entire setup—from flashing the SD card to a working Kiro CLI—took about an hour, most of which was spent troubleshooting the SIGILL crash.

Next Steps

With Kiro CLI operational on the Raspberry Pi 400, you can explore more advanced workflows, such as:

• Acting as a project manager: create and curate tickets, letting Kiro handle code implementation directly from the Pi.
• Automating repetitive development tasks on the edge device.

If you have a Raspberry Pi and want to try this yourself, feel free to share your experience in the comments!