Restore the app-server fs default onto Environment::default(), bring back a sync local Environment default for that path, and rename the process RPC adapter to match the filesystem handler style.
Co-authored-by: Codex <noreply@openai.com>
Match the filesystem structure from #15232 for exec process: expose the trait on Environment, keep LocalProcess as the real implementation, use RemoteProcess as the network proxy, and make ProcessHandler a thin RPC adapter over LocalProcess.
Co-authored-by: Codex <noreply@openai.com>
Apply the pending formatting reorderings and switch the server-side
filesystem default to LocalFileSystem so the current PR compiles again.
Co-authored-by: Codex <noreply@openai.com>
Remove the temporary Environment::local_filesystem() helper and export
LocalFileSystem so fs-only defaults can construct the local filesystem
directly without going through Environment.
Co-authored-by: Codex <noreply@openai.com>
Drop the stale remote_exec_server_client() accessor now that Environment
exposes the process capability directly, and rename the capability getter
to get_executor() on the environment trait and concrete type.
Co-authored-by: Codex <noreply@openai.com>
Remove sync Default from Environment, construct the local process client
with connect_in_process() in create(None), and switch the fs-only app
server default to a local filesystem constructor.
Co-authored-by: Codex <noreply@openai.com>
Remove the duplicate direct-handler local process implementation and make
the local ExecProcess path delegate to the existing in-process
ExecServerClient. Keep lazy initialization only to support sync
Environment::default().
Co-authored-by: Codex <noreply@openai.com>
Replace the in-process client wrapper with a local ExecProcess that owns
ExecServerHandler directly and forwards process notifications to the
trait event stream. This keeps the default Environment process path
entirely local instead of routing through ExecServerClient.
Co-authored-by: Codex <noreply@openai.com>
Give Environment a real local ExecProcess implementation by default and
keep remote mode selecting the websocket-backed client when configured.
The local implementation lazily initializes an in-process exec-server
client on first use.
Co-authored-by: Codex <noreply@openai.com>
Fall back to an in-process exec-server client when no remote URL is
configured, so constructed Environment values have a real process
capability in both local and remote modes.
Co-authored-by: Codex <noreply@openai.com>
Add a narrow ExecProcess trait for process lifecycle RPCs and expose it
from Environment behind an ExecutorEnvironment trait. Keep the first cut
behavior-preserving by delegating remote mode to the existing
ExecServerClient and returning an unavailable process stub for default
local Environment values.
Co-authored-by: Codex <noreply@openai.com>
The idea is that codex-exec exposes an Environment struct with services
on it. Each of those is a trait.
Depending on construction parameters passed to Environment they are
either backed by local or remote server but core doesn't see these
differences.