Runtime and Dependencies

Runtime configuration is defined in multimedia/manifest.json, and dependency bootstrap is centralized in multimedia/scripts/install.sh.

Manifest Contract

{
  "lite-sandbox": true,
  "container": "docker.io/assistos/ploinky-node:24-bookworm-tools",
  "profiles": {
    "default": {
      "install": "/code/scripts/install.sh"
    }
  }
}

The agent runs in the shared Ploinky Node 24 image and executes the default profile install script at startup.

Startup Install Behavior

  • in standard container runtime: the shared image already includes git and ffmpeg, so the script normally just validates them;
  • in host sandbox runtime (bwrap on Linux, seatbelt on macOS): it skips apt and validates tools on the host;
  • if git is missing on the host: startup fails;
  • if ffmpeg is missing on the host: a warning is emitted and multimedia capabilities may be limited.

Important: FFmpeg is a runtime dependency for processing audio/video/image attachments and for the video generation skill. That is why it is installed or validated during agent startup.

Operational Notes

For stability, treat missing ffmpeg as an environment issue, not a plugin bug. In host sandbox mode, the recommended fix is host installation:

sudo apt install -y ffmpeg
brew install ffmpeg