Codex threads run in a read-only sandbox; Solenta never passes --sandbox #170

Problem

codex exec is non-interactive and defaults to a READ-ONLY sandbox: it cannot edit files or run commands needing network access unless told otherwise (--sandbox workspace-write for edits, --sandbox danger-full-access for network) (codex exec docs).

Solenta's codex argv emits only exec --json --skip-git-repo-check [-m model] [-c model_reasoning_effort=...] <prompt> (electron/providers.js:199-228); the runner only adds MCP -c overrides (electron/runner.js:2274-2276). Grep for --sandbox/--full-auto in electron/: zero hits.

Impact

A codex thread in Solenta silently cannot edit files or reach the network unless the user's global ~/.codex/config.toml happens to override it: the one provider that looks broken compared to claude/kimi.

Fix direction

Map Solenta's permission modes to codex sandbox modes (plan -> read-only, default/acceptEdits -> workspace-write, bypassPermissions -> danger-full-access) and pass --sandbox explicitly so behavior does not depend on user config.