Frequent UI or config changes in ChatActivity (e.g., model/backend switch, orientation change) are tightly coupled with the lifecycle of AI services, causing unintended pauses, resumes, or restarts. This issue proposes decoupling ChatActivity from service management to improve stability and modularity by introducing a dedicated component to handle AI services independently from activity lifecycle events.
Frequent UI or config changes in ChatActivity (e.g., model/backend switch, orientation change) are tightly coupled with the lifecycle of AI services, causing unintended pauses, resumes, or restarts. This issue proposes decoupling ChatActivity from service management to improve stability and modularity by introducing a dedicated component to handle AI services independently from activity lifecycle events.