AgentScope v0.7.6

AgentScope now generates filesystem profiles that match the selected Codex runtime, fixing native Windows sandbox startup failures reporting elevated Windows sandbox requires effective ':root' read access.

Changes

• Add agentscope.codexFilesystemMode with Auto, Strict and Windows-compatible choices.
• Auto uses Windows compatibility for Windows runtime paths and Strict permissions for WSL2, Linux and macOS, including Windows-host/WSL setups and custom runtime mappings.
• Preserve selected write grants and disclose the effective read boundary in the panel, generated profile and Apply confirmation.
• Let older presets inherit the new setting, refresh pending drafts when runtime settings change, and reject stale Apply operations after configuration changes.
• Remove redundant Windows read entries and reject unsupported read-only carveouts with writable descendants without widening write access.

Windows read access

Windows compatibility permits OS-level reads outside selected paths, including disabled projects. Read selections remain agent instructions; write grants stay limited to selected paths and runtime temporary storage. For OS-enforced read isolation, use WSL2 or Strict with a compatible native sandbox such as MXC. Legacy Windows backends still have platform-specific limitations; this release does not bypass the sandbox.

Install and upgrade

Download agentscope-0.7.6.vsix below and run Extensions: Install from VSIX... in VS Code. Reload the window, open AgentScope, select Preview → Apply, and start a new Codex session. Repeat Preview and Apply after switching between native and WSL runtimes; one generated profile targets one runtime at a time.

Validation

• All 341 automated tests passed.
• Built and installed the VSIX locally.
• The generated Windows-compatible profile successfully started the installed elevated Windows sandbox with Codex CLI 0.162.0-alpha.17.2.