Of the 3 Storage methods, browser sessions serve 3, phone sessions 0 and computer sessions 3. A method marked not served answers StrategyUnavailable on that kind of session; check the handshake’s capabilities before relying on one.

Storage.getCookies

Browser: served Phone: not served Computer: served The session’s cookies, or those that would be sent to urls. Partitioned cookies carry partitionKey, so setCookies round-trips them.
{"id": 1, "method": "Storage.getCookies", "params": {}}
ParamTypeRequiredDescription
urlsstring[]NoOnly cookies that would be sent to these URLs. Omitted means all.
Result
FieldTypeDescription
cookiesCookie[]

Storage.setCookies

Browser: served Phone: not served Computer: served Set cookies, for example to carry a login from another session.
{"id": 1, "method": "Storage.setCookies", "params": {"cookies": [{"name": "sid", "value": "abc", "domain": "example.com", "path": "/"}]}}
ParamTypeRequiredDescription
cookiesCookie[]Yes
idempotencyKeystringNoMakes a re-send after a reconnect safe: a repeated key returns the recorded response without acting again. See Idempotency keys.
Result: an empty object {}.

Storage.clearCookies

Browser: served Phone: not served Computer: served Delete every cookie in the session.
{"id": 1, "method": "Storage.clearCookies", "params": {}}
ParamTypeRequiredDescription
idempotencyKeystringNoMakes a re-send after a reconnect safe: a repeated key returns the recorded response without acting again. See Idempotency keys.
Result: an empty object {}.