v0.131.0

What's new

OpenCode V2 setup is now available as an opt-in path for Action runs, while V1 remains the default. Provider API keys are kept in permission-restricted files and referenced from configuration, keeping them out of the restored session database; setup also installs and checks the required plugins, gates permissions and credentials, and waits for V1 history import to finish before prompting or saving. V2 execution itself is not yet supported, so runs selecting it stop after setup. #2012

Bundled Systematic skills can now read their own references and run their scripts under the Action’s external-directory restrictions. Access is limited to the installed version’s skills/ directory, with edits still denied; other external paths remain restricted. #2015

Full changelog

0.131.0 (2026-11-01)

Features

• action: set up and spawn OpenCode V2 with file-referenced provider keys (#2012) (3ea0402)

Build System

• deps: update Systematic to v3.28.1 (#2010) (e95013c)
• dev: update dependency tsdown to v0.23.3 (#2000) (dfbdb5e)

Bug Fixes

• action: let bundled skills read their own files under the external-directory deny (#2015) (e4f0d5b)
• deps: update dependency @aws-sdk/client-s3 to v3.1159.0 (#2013) (9e46d5d)

Code Refactoring

• runtime: share the OpenCode generation selector and add the V1 import status client (#2008) (9e469de)