[Study / Discussion] Applying #1479 BYO computer host to Edge / local devices (Raspberry Pi scenario) #1893

Confirmation

• This is not a security vulnerability report

Description

Hi,
I’m studying the project and especially interested in #1479 (BYO computer host).
We are from Mulberry Lab and are exploring a use case where lightweight local devices (for example Raspberry Pi or similar edge machines) act as bot computers in a self-hosted Rakazo setup. This is for a small regional pilot involving Edge AI, where the device should be able to register itself outbound and execute limited commands/files under clear approval rules.
I’d like to understand how the proposed pairing + outbound connection model in #1479 could apply in this setting, and whether there are any parts of the current sandbox / host-computer design that would make this difficult.
A few questions to start:

Would the existing host-computer-protocol approach still be the right base for a low-resource device?
Are there any constraints around graphical tools or desktop sessions that we should be aware of when the host is not a full desktop machine?
If we were to contribute later, which of the suggested small PRs in #1479 would be a reasonable first entry point?

We are currently in a study phase and would like to participate gradually. Any pointers or thoughts from maintainers or others working on this area would be very helpful.
Thank you.

Steps to reproduce

Read the discussion in #1479 regarding BYO computer host.
Review the current sandbox provider design in docs/computer-runtime.md and related host-computer protocol.
Consider the scenario of registering a lightweight edge device (e.g. Raspberry Pi) as a bot computer via outbound connection.
Evaluate whether the proposed pairing and approval model can be applied with minimal changes.

Expected behavior

We expect the proposed BYO computer host model in #1479 to be adaptable to lightweight edge devices (such as Raspberry Pi) with outbound registration and clear approval boundaries, without requiring a full desktop environment

Actual behavior

Currently, registering an external or edge device as a bot computer is not supported. The existing SANDBOX_PROVIDER=desktop option runs on the same host as the API/worker and does not provide a clear outbound pairing model for remote lightweight devices.

Rakazo version or commit

v.0..10

Operating system

Linux

SANDBOX_PROVIDER

docker

AGENT_RUNTIME

pi

Logs or screenshots