Tested scope: The downloadable preflight passed in an Ubuntu 24.04.4 LTS ARM64 container on September 8. Installer download and shell syntax passed and the entry point reported
v260904. The full product, console login, development host and restore procedure were not installed or accepted in that test.
1. Allocate an isolated evaluation host
The project README lists a console minimum of 2 cores, 4 GB RAM and 40 GB storage; a development host is separately listed at 8 cores, 16 GB RAM and 100 GB. These are published starting figures, not a concurrency guarantee. The preflight container is not a replacement for both roles.
Use a disposable Ubuntu VM, retain console access and take a VM snapshot. Note its architecture, free storage and intended network routes. Install basic OS tools if absent, then run the read-only preflight:
sudo apt-get update
sudo apt-get install -y curl ca-certificates procps
curl -fL https://monkeycode.cc/examples/ubuntu-preflight.sh -o ubuntu-preflight.sh
less ubuntu-preflight.sh
bash ubuntu-preflight.shExpected output includes OS, architecture, CPU, memory, storage, “Installer syntax: passed” and a version label. See the actual preflight output. It does not create a MonkeyCode service.
2. Download and review the current installer
mkdir -p "$HOME/monkeycode-evaluation"
cd "$HOME/monkeycode-evaluation"
curl -fL https://monkeycode-ai.com/online/install -o install.sh
sh -n install.sh
sha256sum install.sh
less install.sh
sudo sh install.shRead the file before the last command. The installer requires root on Linux, chooses an AMD64/ARM64 package and invokes the package’s installer. The download URLs inside it expire, so obtain a fresh script instead of reusing an old signed package URL. The local checksum records what you reviewed; it is not a vendor signature. Save output privately if it contains credentials.
3. Follow the generated configuration
Use the addresses and service instructions emitted by your actual installation. This guide does not invent a console port, default password or systemd service name. Configure the console and development host, then connect a test repository and an available model route. Check that the environment can fetch dependencies and run its test command.
4. Accept a complete task before adding team code
Run the first task from clone through diff review. Reconnect after restarting the task environment and verify the files and recorded outcome. Save the installed version, runtime/image versions, configuration locations and backup/restore commands actually provided by that release.
Recovery
A root/OS/architecture rejection means the installer’s prerequisite is unmet. A package download failure may require a fresh entry-point script and a network check. If installation is partial, inspect its output and restore the disposable VM snapshot before trying again. Do not assume repeated execution is idempotent. Validate backup restoration in another isolated host before calling the deployment production-ready.