Per-model reasoning memory is still missing across clients #7566
NikitaMGrimm
started this conversation in
Ideas
Replies: 1 comment
|
One related behavioral question w/ #6508: My expectation is that existing threads keep their own model/reasoning state unchanged. Example (last used settings):
So #6508 affects initialization of new threads, while per-model memory handles model-switching within a thread. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
#2324 is closed as completed, but current main does not implement the requested behavior on web/desktop or mobile.
Web / Desktop
Web/desktop keeps one sticky
ModelSelectionper provider, so options carry across models instead of being remembered per model.Mobile
Mobile rebuilds non-current models from their defaults.
Expected behavior
Mobile stores only the current
ModelSelection, so switching loses the previous model's options.I can also implement this across web/desktop and mobile with regression tests if needed.
Also a question that should be considered:
Should per-model memory apply only to reasoning effort, or to the full
ProviderOptionSelection[].I feel like it should not do the second thing, since "fast" should probably be a global toggle. Though, I can see the benefit of having it coupled to the model. (Having Luna always on fast for example)
All reactions