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 and manage all stored cookies.

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

You can delete individual cookies or clear the entire jar from the inspector.