Cookie Jar

Scrapeman manages cookies using tough-cookie, a fully RFC 6265-compliant cookie library. Cookies are captured automatically from responses, injected automatically into matching requests, and survive app restarts.

Automatic Capture and Injection

• Set-Cookie response headers are automatically parsed and stored in the jar whenever a response is received.
• Cookie request headers are automatically assembled from the jar and injected into every outgoing request where the domain and path match.

No manual configuration is required. The jar behaves the same way a browser does for cookie matching, expiry, and the Secure / HttpOnly flags.

Restart Persistence

The cookie jar is written to disk on every change. When Scrapeman restarts, the jar is restored from disk. Session cookies (those without an explicit Expires or Max-Age) are cleared on restart, matching browser behaviour.

Scoping

Cookies are scoped per workspace and environment. Switching to a different environment gives you a separate jar, so production and staging cookies do not leak into each other.

Cookies Inspector

Open the Cookies panel in the sidebar to view, edit, import, and export the jar for the current workspace and environment.

Each row shows:

• Domain — the domain the cookie is scoped to
• Path — the path scope
• Name and Value
• Expiry — absolute expiration date, or "Session" for session cookies
• Flags — Secure, HttpOnly, SameSite

Filter

Type in the domain filter at the top to narrow the list. Clearing it restores all domains.

Add and edit manually

Click + Add to open an inline form: name, value, domain, path (default /), expires (ISO date or blank for session), httpOnly, Secure, SameSite. Saving inserts the cookie immediately. Click any existing row to open the same form pre-filled and edit it.

httpOnly masking

Cookies with httpOnly: true show •••••••• for the value by default. Click the eye icon to reveal the real value.

Export

• Export JSON — exports the visible cookies (respecting the domain filter) as a pretty-printed JSON array. Shape matches Scrapeman's CookieEntry type.
• Export Netscape — exports cookies in tab-separated cookies.txt format. Compatible with Playwright, Selenium, and curl (--cookie cookies.txt).

Import

Click Import and paste either:

• A document.cookie string: name1=val1; name2=val2. You also enter the domain these cookies belong to.
• A Netscape cookies.txt body. Domain is read from each line; the domain field is ignored.

The format is detected automatically from the presence of tabs.

Per-request cookie jar toggle

The Settings tab has a Use cookie jar checkbox. Disable it on a single request to bypass the workspace jar without touching it globally — no Cookie header on send and no Set-Cookie capture for that request.

Delete and clear

Delete individual cookies via the × button on hover, or clear the entire jar from the inspector.