AssistantApiSupportedFeatures

Whether the client supports message summarization. Deprecated, use message_summary_support instead.

Information about what support this device has for fitness.

Whether the device supports masquerade mode (go/masquerade).

The client information for app control support. More details in: go/acaia.

Whether the client supports the Gearhead message notification source, in which case notification-related operations can access it.

Whether or not the client supports enabling parental controls. When a device to supports parental controls, it has the software necessary to store the relevant information required for parental controls to work. This information includes a boolean "enabled bit" as well as the obfuscated gaia ID of the kid account selected for use with parental controls. Devices supportings kids mode send this information to S3 via S3ClientInfo in every request. See go/aff-kidsproduct for details.

Information about how client handles media controls (play, pause, skip ...)

Whether the client supports the sunrise screen brightening feature before the alarm fires. This is used to indicate whether sunrise alarms can be set on the device. http://cs/symbol:assistant.api.core_types.governed.RingtoneTaskMetadata.GentleWakeInfo

Whether the client supports SmartHome lock screen logic (i.e. on Tangor).

Fluid Actions features supported by the client. If this field is not set in the incoming request, it could mean that the client does not support Fluid Actions. Alternatively, it could mean that the client supports Fluid Actions, but syncs state with server using the old protocol, namely ConversationStateParams. When b/140733618 is resolved, Surface Adaptation Layer will add this field for old clients that support Fluid Actions framework.

Whether or not Assistant should enforce the dismissal of communication notifications associated with messages.

Whether the client supports confirmation flow when a permission is missing. If set to true, the user will be prompted and on confirmation the original flow will continue.

Whether the client can monitor sleep. This allows us to show sleep CUJ related information: go/TwilightDesign Use for development only, see the same field in DeviceCapabilities.SoftwareCapabilities.SelinaCapabilities.

The ability of the client to detect media sessions on the device.

Whether account linking via Google Deep Integrations (GDI) is supported. go/opa-gdi-design

Whether the client supports joining a Zoom meeting.

Whether the client supports persistent display. The new feature allows Assistant devices with screen to display a continuously updating permanent display, such as ambient weather, without the need for a user to ask the Assistant. Design doc: go/assistant-persistent-display.

Whether the client supports AlarmTimerManager API (go/alarm-timer-manager-api).

Whether communications flows for the client can bypass the DI/DC check. The client will enforce some other equivalent permission as necessary concerning access to device contacts and apps.

Whether the client supports tts tapering for the read messages flow. If set to true the tapered tts variant would be used during the read messages flow.

Whether the surface client op performer supports Funtime alarms and timers. go/funtime-engdesign

Whether the supports opening a URL in a web browser. For example, we want to disable this for clients like Chirp.

Whether the client supports Assistant dialogs within Maps. This field will be set only when the Maps on the surface supports Assistant dialogs embedded within Maps. go/gsa-gmm.

When the entry source is search, whether the client supports rendering a similar response as OPA one does. Entry source is defined at http://cs/symbol:assistant.api.params.DeviceProperties.EntrySource

Whether paired-phone contact upload is needed for communications queries to work (e.g. on AAE).

Whether the client can render no input response or just ignore it. No input response is returned when client has a no speech input interaction, eg. user tapped mic but didn't say anything.

Whether the client supports smart space cross-device timers. (go/ss-x-device-timer)

Whether the client can batch client op results before sending them to the server.

If set, it indicates that the client can open a separate HTML browser/webviewer (full viewer) to display certain visual results. These visual results usually require more memory to render (e.g. high resolution photos). Compared to the regular viewer that display all other Assistant result, the full viewer does not have memory limit. The field is copied from the device model. See http://google3/assistant/devices_platform/proto/device_model_capabilities.proto?l=225&rcl=312576471 Also see go/webassistant-full-card-viewer.

Whether the client supports confirmation flow before announcement of multiple messages. If set to true the user will be prompted once and confirmation will be taken before all the messages are announced.

The client information for message summary. More details in: go/roadwayrecap-prd

In what way is assistant continued presence supported. (go/opa-acp-prd)

Whether the client supports viewing of reminder hub page or not. Default is supported. Set to true to disable returning reminder hub page url in reminder responses.

Whether the client supports Duo group calling.

Whether the client supports 1m providers (go/1m-partner-expansion).

Whether the client has a physical radio installed.

Whether the surface supports LiveCards. In cases where the user intent flow cannot be completed within the Assistant, LiveCards are used to take the user to an external app or website. These cards will be pushed to the Google Home app via the PushMessage ClientOp.

Which kind of sign in the client supports.

Whether the client supports the Lottie animation library for the broadcast feature.

Whether the Assistant Server should generate feedback suggestion chips.

Transactions features, supported by the client. Transactions feature may includes how Transactions team want to populate additional information from the device to the server.

Whether the client supports faster optimization for tap_to_read feature.

Whether the client has remote casting enabled. For ex: we want to disable this for clients like Auto.

Whether the client supports cross-device broadcast (i.e. on Torus).

Suggestion chips features, supported by the client.

The version of cross device broadcast (ie; broadcast on torus) which the client supports.

Whether the client can render conversational care responses. go/conversational-care

Whether Assistant for Kids (a.k.a. Designed for Family) features are supported.

Whether a Bluetooth-paired phone is a core component of communications flows on the client.

Whether the client supports csat visual overlay. (go/sd-od-csat)

The version of transactions which the client supports.

The features set which duo client on the device supports. This should be serialized from proto {@code duo_client_api.DuoClientApiFeatures}.

Whether the client supports the alternative message notification sources on AAE, in which case notification-related operations can access it.

Whether or not the client supports gesture detection via soli chips. The reason to prepend the name with soli is to distinguish it from computer vision based methods, e.g. Newman devices.

Whether the client has Google Lens (Assistant Eyes).

Whether the client supports the privacy-aware lockscreen protocol (go/assistant-lockscreen-spec).

Whether the client supports the assistant explore section. This field will be active only when the Explore section is available to the user. This means that the user is (a) signed-in, (b) a IOPA / AGSA user, and (c) in a locale where explore is available.

Whether the client supports joining a Google Meet meeting.

Which way of launching the keyboard the client supports.

Whether the client supports confirmation messages in Immersive Canvas actions. Deprecated: use the filed in immersive_canvas_support.

Whether the client supports the programmatic warm welcome tutorial. Design doc: go/opal-pww-design.

Whether the client supports account linking in-dialog (askForSignIn). This is used before this feature is moved to conversation protocol. To support this, the client needs to: - Integrate with Google Deep Integrations. - Have logic to send the result of account linking back to AS.

Whether the device supports the 3p GUI framework, which allows third parties to enter the conversation with the user, showing their logo next to their chat bubbles, etc. go/3p-phone