feat(runtime): support installable sandbox provider plugins

Aperta
#348 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go

Direzione di ricerca

Start by reading the existing runtime implementations and eval configuration for the none, Docker, and OpenSandbox providers; the issue names no files or tests. Then trace how evaluations produce judge results and downloaded artifacts, and identify the existing cleanup and contract test entry points. Done means a documented, version-pinned plugin workflow, one additional provider completing a real evaluation, contract tests, and the specified English documentation.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Goal

Allow users to install and configure additional sandbox providers without maintaining a fork of skill-up. Provider plugins should extend execution environments while preserving the evaluation and artifact contracts.

Scope

  • Define a versioned provider contract covering provisioning/readiness, command execution, file transfer, cancellation, and resource cleanup.
  • Provide an explicit installation and discovery flow with pinned plugin versions and inspectable provider metadata. CLI syntax and packaging are design decisions for implementation.
  • Allow eval configuration to select a provider and supply validated provider-specific settings; keep credentials out of persisted configuration snapshots, logs, and reports.
  • Declare capabilities such as guest OS/shell, network policy, and isolation. Reject unsupported requirements explicitly.
  • Record the resolved provider/plugin version and non-sensitive environment configuration in run artifacts.
  • Preserve existing none, Docker, and OpenSandbox configurations and behavior.

The initial implementation should establish one supported plugin mechanism and demonstrate one additional provider through it. It need not support every provider or language.

Acceptance criteria

  • A documented install/list/remove workflow supports a pinned provider plugin and reports missing or incompatible versions clearly.
  • An eval selects the installed provider through validated configuration.
  • At least one additional provider completes a real evaluation with agent output, judge results, and downloaded artifacts.
  • Timeout, cancellation, provisioning failure, and partial initialization trigger defined cleanup behavior.
  • Capability checks prevent unsupported isolation/network settings from silently falling back.
  • Contract tests cover execution, file transfer, compatibility, error propagation, and cleanup; the real-provider canary is documented separately.
  • English documentation includes a provider-author guide and a runnable user example.

Related work

  • #32: built-in Docker runtime support.
  • #45: Windows guest support for OpenSandbox.
  • #308: isolated multi-judge execution in Docker and OpenSandbox.

This issue concerns sandbox provider extensibility, rather than Agent host plugin packaging or installing plugins into the agent under test.

Lingua principale
Go
Stelle
1.5k
Fork
134
Merge medio
1g 22h
PR unite (30g)
61

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di alibaba/skill-up

Tutte le issue di alibaba/skill-up

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.