This is a stability release for /reload and for strict OpenAI-compatible providers. Some gateways used to reject the interactive_shell tool definition, sometimes on one request and not the next. They now accept it. You can also run /reload while a hands-free or dispatch session is still working: Pi stays up, and that session's updates and final result show up in the reloaded session. Nothing to configure or migrate.
Highlights
- Use
interactive_shellwith strict OpenAI-compatible gateways that used to reject its tool definition. - Run
/reloadwhile a hands-free or dispatch session is still going without crashing Pi. - Keep getting updates and results from those sessions in the reloaded session.
Highlights
- Use
interactive_shellwith strict OpenAI-compatible gateways that used to reject its tool definition. - Run
/reloadwhile a hands-free or dispatch session is still going without crashing Pi. - Keep getting updates and results from those sessions in the reloaded session.
Fixed
- Strict OpenAI-compatible gateways no longer reject the
interactive_shelltool with aninvalid_toolserror. Input validation is unchanged. Thanks to @Phoenix0531-sudo for #83. - Pi no longer crashes when a hands-free or dispatch session that kept running through
/reloadlater sends an update, finishes, or hands back its output. Thanks to @masonc15 for #82. - Updates that a running session sends while
/reloadis still in progress now reach the reloaded session, instead of stopping the extension from loading or crashing Pi (#85). - Closing a
/spawn --worktreeoverlay after a/reloadno longer shows a stale-context error (#85).