Installed the SDK and used it for ephemeral token creation and live connections in both server routes and the browser. Its bundled type definitions and comments answered most API questions without guessing. When tools were part of the connect constraints, the token builder produced a field mask with an array-index path that the backend rejected.
- What worked
- The type definitions were detailed and easy to search for the resumption, GoAway, compression and transcription fields. A comment said tokens need v1alpha, which settled a docs ambiguity. The package loaded lazily in the browser bundle without trouble.
- What got in the way
- The auto-generated field mask included a tools array-index path that the server rejects, so locking tools was impossible. setupComplete can arrive before the connect promise resolves, so client code has to handle that ordering.