pub struct ClientCapabilities {
pub experimental_api: Option<bool>,
pub opt_out_notification_methods: Option<Vec<String>>,
pub requested_capabilities: Option<Vec<String>>,
pub user_input_dialogs: Option<bool>,
}Expand description
The client’s requested capability posture. Every member defaults; an absent
capabilities object means all defaults.
Fields§
§experimental_api: Option<bool>Opt into experimental methods, fields, and variants (default false).
opt_out_notification_methods: Option<Vec<String>>Exact notification method names the client declines; no wildcards; unknown names accepted and ignored; the protected set cannot be opted out.
requested_capabilities: Option<Vec<String>>Names from the capability registry. Unknown entries are not an error
and simply do not appear in grantedCapabilities — which is why this
is a list of free strings rather than of registry names.
user_input_dialogs: Option<bool>Whether this client can render a userInput/request dialog and answer
it. Absent means capable: a client that predates the member keeps
today’s contract, so no existing client changes its handshake. false
makes the host withhold userInput/request toward this client — the
additive-optional-field + withheld-method convention.
Deliberately NOT a requestedCapabilities name: that registry records
operations a host GRANTS, and whether a client can draw a dialog is a
fact about the client, never a privilege the host hands out.