Files
orca/src
Brennan Benson b91795ac33 fix(native-chat): store a chat's permission mode on its own, so a model pick can't reset it (#28268)
* fix(native-chat): picking a Codex model or effort keeps the chat's permission mode

A model or effort pick on a running chat replaced the record's options with
the provider's answer, which names only the provider's own options. The
saved permission mode was dropped, and the next start read it as Ask.

The pick now keeps the record's permission mode beside the provider's
answer; everything the provider reset still resets.

* chore: re-run CI against current main

* chore: re-run CI against current main

* test(native-chat): keep one permission-mode-survives-pick test

* refactor(native-chat): store a chat's permission mode as its own record field

A model or effort pick replaces the record's options with the provider's
answer, which dropped the permission mode saved among them. The mode now
lives beside the options, so no provider answer can touch it. Clients
still pick it with setOption and read it from the same published fields.

* fix(native-chat): keep a permission mode an earlier dev build saved among options

Hourly builds before the separate field saved the mode in options.permissionMode.
The startup pass now moves it into the field instead of re-deriving it from the
agent's arguments. Temporary; removed after 1.4.226 ships.

* chore: re-run CI against current main
2026-10-13 21:51:30 -07:00
..