pub struct Launch {
pub args: Vec<String>,
pub env: Vec<EnvVar>,
pub remove_env: Vec<String>,
pub files: Vec<FileToWrite>,
pub fence_applied: bool,
pub read_only: bool,
pub fence_by_client: bool,
pub writes: Vec<String>,
pub shared: Option<SharedLaunch>,
pub trust: Vec<String>,
}Expand description
The description of a launch (engine/launch, terminal/launch): never its program, which the core found itself
(locate), and runs in its Job object, under WSL when need be.
Fields§
§args: Vec<String>§env: Vec<EnvVar>§remove_env: Vec<String>The variables of the app’s own environment it must not get (MSYSTEM for Cursor).
files: Vec<FileToWrite>§fence_applied: boolThe fence of LaunchParams::fence is in the launch (its arguments, variables or files).
read_only: boolThe harness is held read-only by this launch.
fence_by_client: boolThe fence of LaunchParams::fence is held by the plugin itself, on the reads and writes the harness makes
through it (ACP’s fs/read_text_file, fs/write_text_file and the permissions it asks), not by the launch:
the core then takes the launch without the paths in it (PLG-6).
writes: Vec<String>The first lines written on its input, once it started.
One process for several agents (opencode serve, 0,7 Go): the core runs it for those of the same program and
variables, and does not start it again for the next; the plugin speaks to it by a way of its own.
trust: Vec<String>For a terminal view: the trust bands its interface asks, shown before it opens.