Raft 0.9.0
User-installed sandbox plugins
Register a trusted executable as a location without changing Raft or installing provider dependencies into its Python environment:
raft plugin add cloud -- node /absolute/path/to/plugin.mjs
raft plugin info cloud
raft new --location cloud --disposableExisting commands route by location. Plugins declare the commands they support
through a versioned handshake; unsupported commands fail before the action runs.
raft plugin remove cloud removes only the registration, not remote resources.
Registered Python virtualenv interpreters retain their dependencies.
The repository includes a runnable sandbox-sdk adapter for creating, inspecting and deleting sandboxes, executing commands, and transferring single files. A provider factory selects any compatible SDK provider. See user plugins for installation, the protocol and trust boundaries.
Cancellation and provider guarantees
Plugin actions get a bounded cleanup window on cancellation. Repeated signals,
launch-time cancellation and expired run alarms cannot bypass that cleanup.
Configured sizing defaults apply to plugin-backed run as well as new.
Plugins run with the controller user's privileges. They own their provider's expiry, persistence, networking and isolation guarantees; Incus guarantees do not transfer to other backends. The sandbox-sdk example requires disposable creation and documents provider-specific TTL limits. Explicitly destroy resources when done.
Upgrade
Update the CLI through your existing installation channel. Incus locations keep their behavior. Plugins are opt-in and have no effect until registered. Install plugin dependencies separately; updating Raft does not update plugins or live hosts.