<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=598704) </details> <!--IssueSummary end--> During initial testing and rollout, we need to provide the ability for users to disable Orbit tool calls so that if there are problems it does not break Duo functionality. #### Original ideas 1. Add an Orbit button in chat that exposes a toggle and tool details 2. Add a "Use Orbit" checkbox in foundational flows that can utilize Orbit #### Design considerations If there is a problem with Orbit, users likely want to disable it once for all surfaces, rather than finding it's off in one place but still broken in another. Since the goal of Orbit is to "just work", elevating existing agentic capabilities, it may be counterintuitive to make a killswitch highly visible. Many users will not even know what Orbit does, it's just a seamless part of Duo. ## Design proposal * Make `default_use_orbit` a user preference, enabled by default whenever Orbit is available to the user. This controls chat, flows, anywhere Orbit can be called. This is a **default** meaning in certain cases this can be overridden, such as when a flow explicitly calls Orbit or when user toggles Orbit on in the chat. * Add a toggle within the **models dropdown** "Use Orbit", defaulted to the `default_use_orbit` setting. Users can override this on the fly, allowing for A/B testing to see how certain queries work with or without Orbit (since this is focused on the testing phase) * Does not impact Orbit MCP use since that is directly calling Orbit — default only affects cases where Orbit is a choice In both contexts ensure there is a beta indicator. Remove both once Orbit is out of beta.