Policy question: may a third-party desktop app launch the user's own opencode serve under the user's own Zen/Go login and show its events? #49207

We are building Lift, a desktop application that runs on the customer's own machine. For the "other models" door we would like to do exactly what T3 Code does today: spawn the unmodified opencode binary the customer installed (opencode serve), under the customer's own login, and draw a chat from the local HTTP/SSE events. Lift never holds the credential, never proxies through its own servers, and never modifies the binary.

The Terms of Service (effective 15 Aug 2026) say the Services are for "your own internal use" and forbid processes "while you are not logged into the Services" and programmatic extraction of Output; they are silent on a third-party local client of opencode serve. Issue #49144 says the free tier can only be used in OpenCode itself.

Could you say in writing, for a paid Go or Zen login held by the end user:

1. Is a third-party desktop app on the user's machine allowed to launch that user's own opencode serve and display the resulting events, including when the desktop app itself is a paid product?
2. Does the same answer hold when the user has signed OpenCode into ChatGPT Plus/Pro, GitHub Copilot or xAI rather than Go/Zen?
3. Is the "programmatically extracts data or Output" clause meant to cover reading the documented local server's SSE stream?

A one-line yes/no with the clause you rely on is all we need; we will link this answer from our design record. Thank you.