Cookies

1. Export the cookies from the browser where the session lives — with that browser’s own tools or an extension — as JSON or as a Netscape cookie file.
2. In Liminal, add them as a saved account: paste the text or choose the file.
3. Attach the account to a profile and open the profile.

There is no separate “import cookies into this profile” command: a saved account is the way in.

Three formats are read, from pasted text or from a file:

[
  {
    "name": "session",
    "value": "<value>",
    "domain": ".example.com",
    "path": "/",
    "secure": true,
    "httpOnly": true,
    "sameSite": "lax",
    "expirationDate": 1798761600
  }
]

# Netscape HTTP Cookie File
.example.com	TRUE	/	TRUE	1798761600	session	<value>
#HttpOnly_.example.com	TRUE	/	TRUE	1798761600	token	<value>

Set-Cookie: session=<value>; Domain=.example.com; Path=/; Secure; HttpOnly

JSON

A list of cookies, or an object that holds one under cookies. A cookie needs a name and a domain; value, path, secure, httpOnly, sameSite and the expiry — expirationDate or expires — are read when present.

Netscape

The tab-separated cookie file many tools write. A line that starts with #HttpOnly_ is read as an HttpOnly cookie.

Set-Cookie

Header lines as a server sends them. Each line has to carry Domain=: without it the app cannot tell which site the cookie belongs to.

The sheet says what it recognised — the platform and the number of cookies — before you add anything.

An account’s menu has Cookie Import History…: a list, for the profile the account is attached to, of what earlier imports brought in — each cookie by name, domain and path, never its value — where a cookie can be removed from the import and from the profile’s storage at once.

Cookies run out. The Session column on the Accounts page shows Cookies expired when the stored ones have passed their date; the profile then opens signed out. Sign in on the site by hand, or import a fresh set into the account.