Fresh install test — clean Orange Pi 5 Plus

[jaylfc]

Test the full flow on clean hardware:

1. Wipe Orange Pi to stock Armbian
2. Run install script or flash pre-built image
3. First-boot wizard detects hardware (RK3588 NPU)
4. Browse Store, install agent framework
5. Download model
6. Deploy agent via wizard (LXC container)
7. Embed content, test memory search via qmd serve
8. Verify backend health monitoring
9. Test app store install (Docker service)
10. Test from mobile browser (PWA)

[redkjuegos]

Tried to install it using the automated install script on my OrangePi5B 16GB.
Used Armbian v26.2.1 for Orange Pi 5 running Armbian Linux 6.1.115-vendor-rk35xx
Fresh Install

apt update
sudo apt install build-essential
curl -fsSL https://raw.githubusercontent.com/jaylfc/tinyagentos/master/scripts/install-server.sh | sudo bash

The script got stuck here for hours...

[server-install] installing controller python deps into .venv (pip install -e .)
[server-install] installing yt-dlp for YouTube/X content ingestion
[server-install] verifying controller import
[server-install] controller import ok
[server-install] installing qmd service
[server-install] qmd not found on PATH — installing via npm
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@tobilu/qmd@2.0.1',
npm WARN EBADENGINE   required: { node: '>=22.0.0' },
npm WARN EBADENGINE   current: { node: 'v18.19.1', npm: '9.2.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'better-sqlite3@12.9.0',
npm WARN EBADENGINE   required: { node: '20.x || 22.x || 23.x || 24.x || 25.x' },
npm WARN EBADENGINE   current: { node: 'v18.19.1', npm: '9.2.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'node-llama-cpp@3.18.1',
npm WARN EBADENGINE   required: { node: '>=20.0.0' },
npm WARN EBADENGINE   current: { node: 'v18.19.1', npm: '9.2.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'cmake-js@8.0.0',
npm WARN EBADENGINE   required: { node: '^20.17.0 || >=22.9.0' },
npm WARN EBADENGINE   current: { node: 'v18.19.1', npm: '9.2.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'ora@9.3.0',
npm WARN EBADENGINE   required: { node: '>=20' },
npm WARN EBADENGINE   current: { node: 'v18.19.1', npm: '9.2.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'slice-ansi@8.0.0',
npm WARN EBADENGINE   required: { node: '>=20' },
npm WARN EBADENGINE   current: { node: 'v18.19.1', npm: '9.2.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'validate-npm-package-name@7.0.2',
npm WARN EBADENGINE   required: { node: '^20.17.0 || >=22.9.0' },
npm WARN EBADENGINE   current: { node: 'v18.19.1', npm: '9.2.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'which@6.0.1',
npm WARN EBADENGINE   required: { node: '^20.17.0 || >=22.9.0' },
npm WARN EBADENGINE   current: { node: 'v18.19.1', npm: '9.2.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'which@6.0.1',
npm WARN EBADENGINE   required: { node: '^20.17.0 || >=22.9.0' },
npm WARN EBADENGINE   current: { node: 'v18.19.1', npm: '9.2.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'cli-spinners@3.4.0',
npm WARN EBADENGINE   required: { node: '>=18.20' },
npm WARN EBADENGINE   current: { node: 'v18.19.1', npm: '9.2.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'string-width@8.2.0',
npm WARN EBADENGINE   required: { node: '>=20' },
npm WARN EBADENGINE   current: { node: 'v18.19.1', npm: '9.2.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'isexe@4.0.0',
npm WARN EBADENGINE   required: { node: '>=20' },
npm WARN EBADENGINE   current: { node: 'v18.19.1', npm: '9.2.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'isexe@4.0.0',
npm WARN EBADENGINE   required: { node: '>=20' },
npm WARN EBADENGINE   current: { node: 'v18.19.1', npm: '9.2.0' }
npm WARN EBADENGINE }
(################⠂⠂) ⠧ reify:typescript: http fetch GET 200 https://registry.npmjs.org/typescript/-/typescript-5.9.3.tgz 3388ms (cache miss)    ```

[jaylfc]

Ah I've been testing/building on the edge kernel, leave it with me, I either need to add vendor kernel compatibility or advise what image to use. I am hoping for a proper working release next week! Preconfigure orange pi images are on my todo list.

[jaylfc]

Thanks for the detailed report — this is a Node.js version issue, not a kernel one.

Armbian vendor-kernel images ship Node 18 from apt, but qmd requires Node >=22. On Node 18, node-llama-cpp has no prebuilt ARM64 binary and falls back to compiling from source via cmake — which can hang for hours on an SBC.

Fix is now in master. The install script now detects the Node version after installing system deps. If it's below 22, it automatically installs Node 22 LTS via NodeSource (which provides ARM64 binaries and works with any kernel — no reflash needed).

You can re-run the install script as-is:

curl -fsSL https://raw.githubusercontent.com/jaylfc/tinyagentos/master/scripts/install-server.sh | sudo bash

If you want to verify Node 22 is present first before re-running:

curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -
sudo apt-get install -y nodejs
node --version  # should show v22.x.x

[jaylfc]

Give it another try now — the Node version issue is fixed so the install should complete cleanly this time.

Just a heads up though: the core system functions (agent management, worker connections, model routing etc.) aren't wired up to the GUI yet. I'm spending the next few days connecting everything end-to-end, so expect some things to not work as expected for now. Will update the issue once it's ready for a proper test.

[jaylfc]

Leaving this open until you can confirm the install completes cleanly — let us know how it goes!

[redkjuegos]

Ah I've been testing/building on the edge kernel, leave it with me, I either need to add vendor kernel compatibility or advise what image to use. I am hoping for a proper working release next week! Preconfigure orange pi images are on my todo list.

I dropped edge kernel because it had tons of WiFi issues, it didn't work with the onboard wifi of the Orange Pi 5B and some other apps were having trouble working.

Thanks for the detailed report — this is a Node.js version issue, not a kernel one.

Armbian vendor-kernel images ship Node 18 from apt, but qmd requires Node >=22. On Node 18, node-llama-cpp has no prebuilt ARM64 binary and falls back to compiling from source via cmake — which can hang for hours on an SBC.

Fix is now in master. The install script now detects the Node version after installing system deps. If it's below 22, it automatically installs Node 22 LTS via NodeSource (which provides ARM64 binaries and works with any kernel — no reflash needed).

You can re-run the install script as-is:

curl -fsSL https://raw.githubusercontent.com/jaylfc/tinyagentos/master/scripts/install-server.sh | sudo bash

If you want to verify Node 22 is present first before re-running:

curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -
sudo apt-get install -y nodejs
node --version # should show v22.x.x

Tried a fresh install:

root@orangepi5:~# curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -
sudo apt-get install -y nodejs
node --version  # should show v22.x.x
2026-04-15 15:22:28 - Installing pre-requisites
Hit:2 https://github.armbian.com/configng stable InRelease
Hit:1 http://armbian.chi.auroradev.org/apt noble InRelease
Hit:3 http://ports.ubuntu.com noble InRelease
Hit:4 http://ports.ubuntu.com noble-security InRelease
Hit:5 http://ports.ubuntu.com noble-updates InRelease
Hit:6 http://ports.ubuntu.com noble-backports InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
58 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
ca-certificates is already the newest version (20240203).
gnupg is already the newest version (2.4.4-2ubuntu17.4).
gnupg set to manually installed.
The following additional packages will be installed:
  libcurl4t64
The following NEW packages will be installed:
  apt-transport-https
The following packages will be upgraded:
  curl libcurl4t64
2 upgraded, 1 newly installed, 0 to remove and 56 not upgraded.
Need to get 560 kB of archives.
After this operation, 36.9 kB of additional disk space will be used.
Get:1 http://ports.ubuntu.com noble-updates/universe arm64 apt-transport-https all 2.8.3 [3,970 B]
Get:2 http://ports.ubuntu.com noble-security/main arm64 curl arm64 8.5.0-2ubuntu10.8 [222 kB]
Get:3 http://ports.ubuntu.com noble-security/main arm64 libcurl4t64 arm64 8.5.0-2ubuntu10.8 [334 kB]
Fetched 560 kB in 2s (361 kB/s)
Selecting previously unselected package apt-transport-https.
(Reading database ... 27685 files and directories currently installed.)
Preparing to unpack .../apt-transport-https_2.8.3_all.deb ...
Unpacking apt-transport-https (2.8.3) ...
Preparing to unpack .../curl_8.5.0-2ubuntu10.8_arm64.deb ...
Unpacking curl (8.5.0-2ubuntu10.8) over (8.5.0-2ubuntu10.6) ...
Preparing to unpack .../libcurl4t64_8.5.0-2ubuntu10.8_arm64.deb ...
Unpacking libcurl4t64:arm64 (8.5.0-2ubuntu10.8) over (8.5.0-2ubuntu10.6) ...
Setting up apt-transport-https (2.8.3) ...
Setting up libcurl4t64:arm64 (8.5.0-2ubuntu10.8) ...
Setting up curl (8.5.0-2ubuntu10.8) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.7) ...
Get:2 https://deb.nodesource.com/node_22.x nodistro InRelease [12.1 kB]
Hit:3 https://github.armbian.com/configng stable InRelease
Hit:4 http://ports.ubuntu.com noble InRelease
Get:5 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages [9,580 B]
Hit:6 http://ports.ubuntu.com noble-security InRelease
Hit:1 http://mirror.vinehost.net/armbian/apt noble InRelease
Hit:7 http://ports.ubuntu.com noble-updates InRelease
Hit:8 http://ports.ubuntu.com noble-backports InRelease
Fetched 21.7 kB in 1s (18.0 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
56 packages can be upgraded. Run 'apt list --upgradable' to see them.
2026-04-15 15:22:56 - Repository configured successfully.
2026-04-15 15:22:56 - To install Node.js, run: apt install nodejs -y
2026-04-15 15:22:56 - You can use N|solid Runtime as a node.js alternative
2026-04-15 15:22:56 - To install N|solid Runtime, run: apt install nsolid -y

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  nodejs
0 upgraded, 1 newly installed, 0 to remove and 56 not upgraded.
Need to get 37.0 MB of archives.
After this operation, 233 MB of additional disk space will be used.
Get:1 https://deb.nodesource.com/node_22.x nodistro/main arm64 nodejs arm64 22.22.2-1nodesource1 [37.0 MB]
Fetched 37.0 MB in 6s (6,243 kB/s)
Selecting previously unselected package nodejs.
(Reading database ... 27689 files and directories currently installed.)
Preparing to unpack .../nodejs_22.22.2-1nodesource1_arm64.deb ...
Unpacking nodejs (22.22.2-1nodesource1) ...
Setting up nodejs (22.22.2-1nodesource1) ...
Processing triggers for man-db (2.12.0-4build2) ...
v22.22.2
root@orangepi5:~# curl -fsSL https://raw.githubusercontent.com/jaylfc/tinyagentos/master/scripts/install-server.sh | sudo bash
[server-install] os=Linux arch=aarch64
[server-install] install_dir=/root/tinyagentos branch=master port=6969 qmd_port=7832
[server-install] installing apt deps (python3, venv, git, curl, libtorrent, nodejs, sqlite3)
E: Unable to correct problems, you have held broken packages.
root@orangepi5:~#

[jaylfc]

Thanks for testing so thoroughly and posting that full log — it made the root cause obvious.

What happened: The install script's apt step included nodejs npm in the package list. On Ubuntu/Armbian systems where NodeSource's nodejs is already installed (which bundles its own npm), apt sees a conflict between the bundled npm and the Ubuntu-repo npm package and throws the "held broken packages" error.

Fix is now in master. nodejs and npm are removed from the apt install list entirely — ensure_node22() already handles node installation via NodeSource right after, so they were redundant there anyway. This means the apt step will never conflict with an existing NodeSource install.

Re-run the install script:

curl -fsSL https://raw.githubusercontent.com/jaylfc/tinyagentos/master/scripts/install-server.sh | sudo bash

This should go through cleanly now.

[redkjuegos]

Processing triggers for man-db (2.12.0-4build2) ...
[server-install] node now at v22.22.2
**[server-install] Rockchip NPU detected but rkllama is not installed**
[server-install]   controller will run without NPU acceleration until you install rkllama
[server-install]   run: sudo bash scripts/install-rknpu.sh    (or set TAOS_RKNPU_SETUP=1 before re-running this installer to opt in automatically)
[server-install]   see: https://github.com/notpunchnox/rkllama
[server-install] cloning https://github.com/jaylfc/tinyagentos into /root/tinyagentos
Cloning into '/root/tinyagentos'...
remote: Enumerating objects: 1335, done.
remote: Counting objects: 100% (1335/1335), done.
remote: Compressing objects: 100% (977/977), done.
remote: Total 1335 (delta 149), reused 1125 (delta 137), pack-reused 0 (from 0)
Receiving objects: 100% (1335/1335), 32.87 MiB | 9.91 MiB/s, done.
Resolving deltas: 100% (149/149), done.
[server-install] creating venv
[server-install] installing controller python deps into .venv (pip install -e .)
[server-install] installing yt-dlp for YouTube/X content ingestion
[server-install] verifying controller import
[server-install] controller import ok
[server-install] installing qmd service
[server-install] qmd not found on PATH — installing via npm
npm warn deprecated prebuild-install@7.1.3: No longer maintained. Please contact the author of the relevant native addon; alternatives are available.
npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, open '/usr/lib/node_modules/@tobilu/qmd/node_modules/node-llama-cpp/dist/config.js'
npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, lstat '/usr/lib/node_modules/@tobilu/qmd/node_modules/@modelcontextprotocol/sdk/dist/esm/server'
npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, lstat '/usr/lib/node_modules/@tobilu/qmd/node_modules/node-llama-cpp/dist'
npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, lstat '/usr/lib/node_modules/@tobilu/qmd/node_modules/@modelcontextprotocol/sdk/dist'
npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, lstat '/usr/lib/node_modules/@tobilu/qmd/node_modules/node-llama-cpp/dist'
npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, lstat '/usr/lib/node_modules/@tobilu/qmd/node_modules/@modelcontextprotocol/sdk/dist'
npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, lstat '/usr/lib/node_modules/@tobilu/qmd/node_modules/node-llama-cpp/dist'
npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, lstat '/usr/lib/node_modules/@tobilu/qmd/node_modules/node-llama-cpp/dist'
npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, lstat '/usr/lib/node_modules/@tobilu/qmd/node_modules/@modelcontextprotocol/sdk/dist'
npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, lstat '/usr/lib/node_modules/@tobilu/qmd/node_modules/node-llama-cpp/dist'
npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, lstat '/usr/lib/node_modules/@tobilu/qmd/node_modules/@modelcontextprotocol/sdk/dist'
npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, lstat '/usr/lib/node_modules/@tobilu/qmd/node_modules/node-llama-cpp/dist'
npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, lstat '/usr/lib/node_modules/@tobilu/qmd/node_modules/@modelcontextprotocol/sdk/dist'

It continued for a while doing that and then:

npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, lstat '/usr/lib/node_modules/@tobilu/qmd/node_modules/node-llama-cpp/bins'
npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, lstat '/usr/lib/node_modules/@tobilu/qmd/node_modules/node-llama-cpp/bins'
npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, lstat '/usr/lib/node_modules/@tobilu/qmd/node_modules/node-llama-cpp/bins'
npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, lstat '/usr/lib/node_modules/@tobilu/qmd/node_modules/node-llama-cpp/llama'
npm error code ENOENT
npm error syscall spawn sh
npm error path /usr/lib/node_modules/@tobilu/qmd/node_modules/better-sqlite3
npm error errno -2
npm error enoent spawn sh ENOENT
npm error enoent This is related to npm not being able to find a file.
npm error enoent
npm notice
npm notice New major version of npm available! 10.9.7 -> 11.12.1
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.12.1
npm notice To update run: npm install -g npm@11.12.1
npm notice
npm error A complete log of this run can be found in: /root/.npm/_logs/2026-04-15T20_12_15_418Z-debug-0.log
[server-install] npm install of qmd failed — cannot continue (qmd.service would never start)
root@orangepi5:~#

[jaylfc]

Sorry about all the back and forth on this — I should mention I'm building and testing on a different kernel and board setup, so ironing out the vendor kernel path has taken longer than expected. Fingers crossed we'll get there!

The error this time is a leftover from the first failed install — the partial @tobilu/qmd files in /usr/lib/node_modules/ are conflicting with the reinstall. Try clearing that first:

sudo npm uninstall -g @tobilu/qmd 2>/dev/null || true
curl -fsSL https://raw.githubusercontent.com/jaylfc/tinyagentos/master/scripts/install-server.sh | sudo bash

Fair warning though — even once it installs cleanly, the OS is pretty limited right now. The GUI is there but the agent creation and management flow isn't wired up yet. We're working on that next, specifically the agent deployment flow so you can actually spin up and configure agents through the UI.

Out of curiosity — what kind of agent would you most want to see working first? Happy to make sure it's ready for you to test when that lands.

[redkjuegos]

Sorry about all the back and forth on this — I should mention I'm building and testing on a different kernel and board setup, so ironing out the vendor kernel path has taken longer than expected. Fingers crossed we'll get there!

don't worry, Im having fun.

The error this time is a leftover from the first failed install — the partial @tobilu/qmd files in /usr/lib/node_modules/ are conflicting with the reinstall. Try clearing that first:

sudo npm uninstall -g @tobilu/qmd 2>/dev/null || true
curl -fsSL https://raw.githubusercontent.com/jaylfc/tinyagentos/master/scripts/install-server.sh | sudo bash

I did it on a brand new fresh install so it shouldn't have had anything from the previous attempt.

Fair warning though — even once it installs cleanly, the OS is pretty limited right now. The GUI is there but the agent creation and management flow isn't wired up yet. We're working on that next, specifically the agent deployment flow so you can actually spin up and configure agents through the UI.

Out of curiosity — what kind of agent would you most want to see working first? Happy to make sure it's ready for you to test when that lands.

I honestly have no idea what i would do with it.... i just wanted to play with a new toy and this seemed like a great project!
I've been thinking for a couple of weeks now what i would use an agent for and i honestly have yet to come up with a good idea. So far I was testing the OPI as a coding assistant for my AI.duino and VSCode & Continue