pi-subagents Files

Highlights

• Security fix: workflow scripts can no longer reach the Pi process outside their sandbox. Upgrade if you use workflow scripts.
• A locked-down background agent that fails because one of your extensions' providers did not load in it now says which provider and how to load it.
• Old background runs are now actually deleted from disk.

Security

• Workflow scripts could reach the Pi process outside their sandbox. Upgrade to this version; see GHSA-6v8j-6w28-2w8r for affected versions and a workaround. Workflow scripts can no longer set Error.prepareStackTrace, and a script that calls import(), which always failed inside a workflow, is now rejected before it runs.

Fixed

• Old background runs are now deleted from disk. Background runs are meant to be removed 30 days after they finish, but a run was kept forever while its Pi session file still existed, and session files are never deleted, so almost no run was ever removed. A run whose session still exists is now kept for 90 days, so you can still resume it for that long, and is then removed like any other finished run. Thanks to @LCorleone for the report and fix, and @isjiajia01 for reproducing it. (#3098)
• A background agent that loads no ambient extensions (for example one with extensions: []) now says so when it fails on a model whose provider one of your extensions registers or overrides. That extension never loaded in the child, so the child sent its requests through the built-in provider of the same name and failed with an unrelated provider error. The failure now names the provider and how to load its extension for that agent. Thanks to @Yivas for the report. (#3100)