#1451·lux

Suggestion: SigCLI for automated cookie management

Author: brelianCreated May 11, 2026Updated May 15, 2026

Problem

For authenticated downloads (Bilibili premium, Douyin, etc.), users pass cookies via -c "cookie_string" or -c cookies.txt. This means manually opening DevTools, copying the cookie header, and re-doing it whenever the session expires.

Suggestion

SigCLI automates browser login and cookie extraction:

bash

# One-time setup
npm install -g @sigcli/cli && sig init
sig login bilibili  # Opens browser for QR scan

# Use with lux — pass cookie string directly
lux -c "$(sig get bilibili --no-redaction --format value)" "https://www.bilibili.com/video/BV..."

Benefits:

No manual DevTools cookie copying
Auto-refresh when cookies expire (sig watch)
Encrypted storage, multiple accounts
Works on remote/headless machines (sig sync)
Uses real Chrome/Edge — no bot detection

Verified provider config for Bilibili

yaml

bilibili:
    domains:
        - www.bilibili.com
    entryUrl: https://www.bilibili.com/
    strategy: browser
    ttl: 2h
    extract:
        - from: cookies
          as: cookie
          match: '*'
    apply:
        - in: header
          name: Cookie
          value: ${cookie}

Verified provider config for YouTube

yaml

youtube:
    domains:
        - www.youtube.com
        - youtube.com
    entryUrl: https://www.youtube.com/
    validateUrl: https://www.youtube.com/account
    strategy: browser
    ttl: 2h
    extract:
        - from: cookies
          as: cookie
          match: '*'
    apply:
        - in: header
          name: Cookie
          value: ${cookie}

This is just a user-workflow suggestion, not a code change request. Happy to contribute a docs section if helpful.

Links: https://github.com/sigcli/sigcli

Source: iawia002/lux

View original on GitHub View discussion on GitHub