[GH-ISSUE #1445] Chrome Browser Profile / Cookies not applying to SingleFile in v0.7.2?

kerem commented

2026-03-01 17:58:35 +03:00

Owner

Originally created by @JitteryDoodle on GitHub (Jun 3, 2024).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1445

Originally assigned to: @pirate on GitHub.

Hello,

I've been able to get cookies working for the Chrome > PDF, Screenshot, Headers, Chrome > HTML, and Readability views, but SingleFile is not signed in. This applies to multiple websites. What could the issue be and how can I troubleshoot this? I see nothing incorrect in the logs, even the logs related to singlepage display my user_data_dir path.

Here's my version info (confusingly on part, I named the chromium mount "chrome_profile", but this is actually the full chromium folder with the Default folder inside):

# archivebox --version
0.7.2
ArchiveBox v0.7.2 COMMIT_HASH=315c9f3 BUILD_TIME=2024-04-24 22:47:02 1713998822
IN_DOCKER=True IN_QEMU=False ARCH=x86_64 OS=Linux PLATFORM=Linux-6.1.74-Unraid-x86_64-with-glibc2.36 PYTHON=Cpython
FS_ATOMIC=True FS_REMOTE=True FS_USER=0:0 FS_PERMS=644
DEBUG=False IS_TTY=True TZ=UTC SEARCH_BACKEND=ripgrep LDAP=False

[i] Dependency versions:
 √  PYTHON_BINARY         v3.11.9         valid     /usr/local/bin/python3.11                                                   
 √  SQLITE_BINARY         v2.6.0          valid     /usr/local/lib/python3.11/sqlite3/dbapi2.py                                 
 √  DJANGO_BINARY         v3.1.14         valid     /usr/local/lib/python3.11/site-packages/django/__init__.py                  
 √  ARCHIVEBOX_BINARY     v0.7.2          valid     /usr/local/bin/archivebox                                                   

 √  CURL_BINARY           v8.5.0          valid     /usr/bin/curl                                                               
 √  WGET_BINARY           v1.21.3         valid     /usr/bin/wget                                                               
 √  NODE_BINARY           v20.12.2        valid     /usr/bin/node                                                               
 √  SINGLEFILE_BINARY     v1.1.46         valid     /app/node_modules/single-file-cli/single-file                               
 √  READABILITY_BINARY    v0.0.11         valid     /app/node_modules/readability-extractor/readability-extractor               
 √  MERCURY_BINARY        v1.0.0          valid     /app/node_modules/@postlight/parser/cli.js                                  
 √  GIT_BINARY            v2.39.2         valid     /usr/bin/git                                                                
 √  YOUTUBEDL_BINARY      v2023.12.30     valid     /usr/local/bin/yt-dlp                                                       
 √  CHROME_BINARY         v124.0.6367.29  valid     /usr/bin/chromium-browser                                                   
 √  RIPGREP_BINARY        v13.0.0         valid     /usr/bin/rg                                                                 

[i] Source-code locations:
 √  PACKAGE_DIR           24 files        valid     /app/archivebox                                                             
 √  TEMPLATES_DIR         3 files         valid     /app/archivebox/templates                                                   
 -  CUSTOM_TEMPLATES_DIR  -               disabled  None                                                                        

[i] Secrets locations:
 √  CHROME_USER_DATA_DIR  44 files        valid     /var/chrome_profile                                                         
 √  COOKIES_FILE          10.2 KB         valid     /var/chrome_profile/cookies.txt                                             

[i] Data locations:
 √  OUTPUT_DIR            7 files @       valid     /data                                                                       
 √  SOURCES_DIR           157 files       valid     ./sources                                                                   
 √  LOGS_DIR              1 files         valid     ./logs                                                                      
 √  ARCHIVE_DIR           293 files       valid     ./archive                                                                   
 √  CONFIG_FILE           81.0 Bytes      valid     ./ArchiveBox.conf                                                           
 √  SQL_INDEX             4.0 MB          valid     ./index.sqlite3

Willing to share more if needed.

Thanks!

Originally created by @JitteryDoodle on GitHub (Jun 3, 2024). Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1445 Originally assigned to: @pirate on GitHub. Hello, I've been able to get cookies working for the Chrome > PDF, Screenshot, Headers, Chrome > HTML, and Readability views, but SingleFile is not signed in. This applies to multiple websites. What could the issue be and how can I troubleshoot this? I see nothing incorrect in the logs, even the logs related to singlepage display my user_data_dir path. Here's my version info (confusingly on part, I named the chromium mount "chrome_profile", but this is actually the full chromium folder with the Default folder inside): ``` # archivebox --version 0.7.2 ArchiveBox v0.7.2 COMMIT_HASH=315c9f3 BUILD_TIME=2024-04-24 22:47:02 1713998822 IN_DOCKER=True IN_QEMU=False ARCH=x86_64 OS=Linux PLATFORM=Linux-6.1.74-Unraid-x86_64-with-glibc2.36 PYTHON=Cpython FS_ATOMIC=True FS_REMOTE=True FS_USER=0:0 FS_PERMS=644 DEBUG=False IS_TTY=True TZ=UTC SEARCH_BACKEND=ripgrep LDAP=False [i] Dependency versions: √ PYTHON_BINARY v3.11.9 valid /usr/local/bin/python3.11 √ SQLITE_BINARY v2.6.0 valid /usr/local/lib/python3.11/sqlite3/dbapi2.py √ DJANGO_BINARY v3.1.14 valid /usr/local/lib/python3.11/site-packages/django/__init__.py √ ARCHIVEBOX_BINARY v0.7.2 valid /usr/local/bin/archivebox √ CURL_BINARY v8.5.0 valid /usr/bin/curl √ WGET_BINARY v1.21.3 valid /usr/bin/wget √ NODE_BINARY v20.12.2 valid /usr/bin/node √ SINGLEFILE_BINARY v1.1.46 valid /app/node_modules/single-file-cli/single-file √ READABILITY_BINARY v0.0.11 valid /app/node_modules/readability-extractor/readability-extractor √ MERCURY_BINARY v1.0.0 valid /app/node_modules/@postlight/parser/cli.js √ GIT_BINARY v2.39.2 valid /usr/bin/git √ YOUTUBEDL_BINARY v2023.12.30 valid /usr/local/bin/yt-dlp √ CHROME_BINARY v124.0.6367.29 valid /usr/bin/chromium-browser √ RIPGREP_BINARY v13.0.0 valid /usr/bin/rg [i] Source-code locations: √ PACKAGE_DIR 24 files valid /app/archivebox √ TEMPLATES_DIR 3 files valid /app/archivebox/templates - CUSTOM_TEMPLATES_DIR - disabled None [i] Secrets locations: √ CHROME_USER_DATA_DIR 44 files valid /var/chrome_profile √ COOKIES_FILE 10.2 KB valid /var/chrome_profile/cookies.txt [i] Data locations: √ OUTPUT_DIR 7 files @ valid /data √ SOURCES_DIR 157 files valid ./sources √ LOGS_DIR 1 files valid ./logs √ ARCHIVE_DIR 293 files valid ./archive √ CONFIG_FILE 81.0 Bytes valid ./ArchiveBox.conf √ SQL_INDEX 4.0 MB valid ./index.sqlite3 ``` Willing to share more if needed. Thanks!

kerem

2026-03-01 17:58:35 +03:00

closed this issue
added the
expected: next release
label

kerem commented

2026-03-01 17:58:36 +03:00

Author

Owner

@pirate commented on GitHub (Jun 4, 2024):

So I just double checked, in 0.7.x chrome profile use with singlefile should work automatically... the code is there and it's working for me on some sites. Unfortunately many larger (big tech) sites detect headless browsers to block bots and log you out automatically.

Can you share some of the domains where you're getting logged out and I can try to investigate further to see if it's bot-blocking or a bug in ArchiveBox/singlefile?
Can you also try running single-file with your chrome profile manually outside Docker to remove ArchiveBox and environment issues as potential factors:

npm install single-file-cli@1.1.54 --legacy-peer-deps

single-file --browser-headless=false --browser-executable-path=/bin/outside/docker/chromium-browser --browser-args "[\"--user-data-dir=/Users/example/Desktop/chrome_profile\", \"--profile-directory=Default\"]" https://example.com singlefile.html

This will also open the browser window (instead of running it headless) ^ so you can see if there is any obvious reason you're getting logged out visually.

You can also try using cookies.txt (which it looks like you already have) and tweaking your CHROME_USER_AGENT to see if that helps:

To use cookies with singlefile on v0.7.x you'd do:

# to use cookies.txt:
archivebox config --set SINGLEFILE_ARGS=["--browser-cookies-file=/data/cookies.txt"]

On v0.8.0+ (coming soon) it'll work automatically without needing that ^ if you have COOKIES_FILE setup.

More info:

@pirate commented on GitHub (Jun 4, 2024): So I just double checked, in 0.7.x chrome profile use with singlefile should work automatically... the code is there and it's working for me on some sites. Unfortunately many larger (big tech) sites detect headless browsers to block bots and log you out automatically. - **Can you share some of the domains where you're getting logged out and I can try to investigate further to see if it's bot-blocking or a bug in ArchiveBox/singlefile?** - **Can you also try running single-file with your chrome profile manually outside Docker to remove ArchiveBox and environment issues as potential factors:** ```bash npm install single-file-cli@1.1.54 --legacy-peer-deps single-file --browser-headless=false --browser-executable-path=/bin/outside/docker/chromium-browser --browser-args "[\"--user-data-dir=/Users/example/Desktop/chrome_profile\", \"--profile-directory=Default\"]" https://example.com singlefile.html ``` This will also open the browser window (instead of running it headless) ^ so you can see if there is any obvious reason you're getting logged out visually. --- You can also try using cookies.txt (which it looks like you already have) and tweaking your `CHROME_USER_AGENT` to see if that helps: To use cookies with singlefile on v0.7.x you'd do: ```bash # to use cookies.txt: archivebox config --set SINGLEFILE_ARGS=["--browser-cookies-file=/data/cookies.txt"] ``` On [v0.8.0+](https://github.com/ArchiveBox/ArchiveBox/releases/tag/v0.8.0-rc) (coming soon) it'll work automatically without needing that ^ if you have [`COOKIES_FILE`](https://github.com/ArchiveBox/ArchiveBox/wiki/Configuration#cookies_file) setup. More info: - https://github.com/ArchiveBox/ArchiveBox/pull/1372 - https://github.com/ArchiveBox/ArchiveBox/pull/1021

kerem commented

2026-03-01 17:58:36 +03:00

Author

Owner

@iluvatyr commented on GitHub (Jun 5, 2024):

I tested with my docker archivebox and created the chrome profile within docker using the novnc container.
Whenever I start the chromium-browser and check the login into some page via novnc, it is actually working and Im logged into my profile. When I dont interactively do it and do the archive command for singlefile page, it is as if there was no chrome profile...
Environment variables are all set.

EDIT: So does anyone get how to get it to work?

@iluvatyr commented on GitHub (Jun 5, 2024): I tested with my docker archivebox and created the chrome profile within docker using the novnc container. Whenever I start the chromium-browser and check the login into some page via novnc, it is actually working and Im logged into my profile. When I dont interactively do it and do the archive command for singlefile page, it is as if there was no chrome profile... Environment variables are all set. EDIT: So does anyone get how to get it to work?

kerem commented

2026-03-01 17:58:36 +03:00

Author

Owner

@JitteryDoodle commented on GitHub (Jun 20, 2024):

My experience mirrors @iluvatyr - everything seems to be working, except for the archivebox singlefile.

@JitteryDoodle commented on GitHub (Jun 20, 2024): My experience mirrors @iluvatyr - everything seems to be working, except for the archivebox singlefile.

kerem commented

2026-03-01 17:58:36 +03:00

Author

Owner

@JitteryDoodle commented on GitHub (Jun 20, 2024):

I also just tried with the 8.0.0 dev version from March, and the same thing happens - SingleFile isn't signed in, but for everything else it appears to have my cookies.

@JitteryDoodle commented on GitHub (Jun 20, 2024): I also just tried with the 8.0.0 dev version from March, and the same thing happens - SingleFile isn't signed in, but for everything else it appears to have my cookies.

kerem commented

2026-03-01 17:58:36 +03:00

Author

Owner

@iluvatyr commented on GitHub (Jul 4, 2024):

so any fix upcoming?

@iluvatyr commented on GitHub (Jul 4, 2024): so any fix upcoming?

kerem commented

2026-03-01 17:58:36 +03:00

Author

Owner

@rumisle commented on GitHub (Jul 4, 2024):

This doesn't seem to be an ArchiveBox problem. From what I remember, Chromium just won't load profiles when it's launched headless. I can replicate this on my Mac, launching Chromium with a data directory, headless on/off. Not sure why it's designed this way or how to work around it.

@rumisle commented on GitHub (Jul 4, 2024): This doesn't seem to be an ArchiveBox problem. From what I remember, Chromium just won't load profiles when it's launched headless. I can replicate this on my Mac, launching Chromium with a data directory, headless on/off. Not sure why it's designed this way or how to work around it.

kerem commented

2026-03-01 17:58:36 +03:00

Author

Owner

@pirate commented on GitHub (Jul 7, 2024):

Chromium headless=new can load profiles, it just takes a specific combination of flags. I'll dig into this more post honeymoon!

@pirate commented on GitHub (Jul 7, 2024): Chromium headless=new can load profiles, it just takes a specific combination of flags. I'll dig into this more post honeymoon!

kerem commented

2026-03-01 17:58:36 +03:00

Author

Owner

@mstarodub commented on GitHub (Nov 13, 2024):

I'm experiencing the polar opposite of this (at least with the 0.8rc). Singlefile seems to be logged in, but everything else isn't.

I've verified that the profile is set up correctly by running with CHROME_HEADLESS=False - opened chromium with --user-data-dir=... prior to running archivebox add, and it opened the archived site in the same session.

However, when running archivebox with the chromium instance closed, it gets logged out. Even weirder is that a systemwide extension I manually disabled in the dedicated archivebox profile gets re-enabled?! So I have reason to believe it somehow resets the profile completely.

I've been debugging this for hours and at this point the only thing I haven't done yet is reading through chromium / archivebox source code. Would really appreciate some help as the archival matter at hand is quite urgent

@mstarodub commented on GitHub (Nov 13, 2024): I'm experiencing the polar opposite of this (at least with the 0.8rc). Singlefile seems to be logged in, but everything else isn't. I've verified that the profile is set up correctly by running with `CHROME_HEADLESS=False` - opened chromium with `--user-data-dir=...` prior to running `archivebox add`, and it opened the archived site in the same session. However, when running archivebox with the chromium instance closed, it gets logged out. Even weirder is that a systemwide extension I manually disabled in the dedicated archivebox profile gets re-enabled?! So I have reason to believe it somehow resets the profile completely. I've been debugging this for hours and at this point the only thing I haven't done yet is reading through chromium / archivebox source code. Would really appreciate some help as the archival matter at hand is quite urgent

kerem commented

2026-03-01 17:58:36 +03:00

Author

Owner

@lamons commented on GitHub (Dec 23, 2024):

I am having the similar issue here, in novnc everything seems working fine, but every archive method failed (stuck in the login page). I tried having CHROME_HEADLESS=False with novnc on and can actually see the chrome window pop up with successfully logged in page, but the archive still showing a login page. I tried also running sing-file (with --browser-headless=true) inside the container and it got the login page as well, if using --browser-headless=false the chrome windows poped up for a second and crashed for not sure what reason, but I can see in that second it's still the login page, so the profile probably failed to be loaded by single-file.

@lamons commented on GitHub (Dec 23, 2024): I am having the similar issue here, in novnc everything seems working fine, but every archive method failed (stuck in the login page). I tried having `CHROME_HEADLESS=False` with novnc on and can actually see the chrome window pop up with successfully logged in page, but the archive still showing a login page. I tried also running sing-file (with `--browser-headless=true`) inside the container and it got the login page as well, if using `--browser-headless=false` the chrome windows poped up for a second and crashed for not sure what reason, but I can see in that second it's still the login page, so the profile probably failed to be loaded by single-file.

kerem commented

2026-03-01 17:58:36 +03:00

Author

Owner

@TooManyStacks commented on GitHub (Jan 24, 2025):

I am seeing the same, `image: archivebox/archivebox:latest' I tried to put a cookies file, that didn't work. Checked with cat in the container,the data was there.

Then tried to pass my chromium profile with the cookies accepted on the site I am testing on (ad.nl a newspaper). I now see it finally gets the page title but still the cookie pop up blocks the whole page. Tried adding a cookie accept extension, no dice.

Also tried some other sites,all of them claim I never accepted cookies.

@TooManyStacks commented on GitHub (Jan 24, 2025): I am seeing the same, `image: archivebox/archivebox:latest' I tried to put a cookies file, that didn't work. Checked with cat in the container,the data was there. Then tried to pass my chromium profile with the cookies accepted on the site I am testing on (ad.nl a newspaper). I now see it finally gets the page title but still the cookie pop up blocks the whole page. Tried adding a cookie accept extension, no dice. Also tried some other sites,all of them claim I never accepted cookies.

kerem commented

2026-03-01 17:58:36 +03:00

Author

Owner

@yosofbadr commented on GitHub (Jun 8, 2025):

I am having the same issue, not sure if it is a misconfiguration on my part, if it is not supported, or if the website I am trying to archive is indeed logging me out.

Edit: Did some testing and it looks like the site detects chrome-driver and automatically logs out the account. A bit of a shame, are there any work arounds for this?

Edit2: I tested this in a small PoC, it was the site automatically logging me out, however I was able to get around this by injecting cookies after the site loaded then using SingleFile to download the page.

@yosofbadr commented on GitHub (Jun 8, 2025): I am having the same issue, not sure if it is a misconfiguration on my part, if it is not supported, or if the website I am trying to archive is indeed logging me out. Edit: Did some testing and it looks like the site detects chrome-driver and automatically logs out the account. A bit of a shame, are there any work arounds for this? Edit2: I tested this in a small PoC, it was the site automatically logging me out, however I was able to get around this by injecting cookies after the site loaded then using SingleFile to download the page.

kerem commented

2026-03-01 17:58:36 +03:00

Author

Owner

@TooManyStacks commented on GitHub (Jun 13, 2025):

What I notice in on projects, like playwright. Is that cookies do not easily transfer from system to system and headless and with head act differently with cookies.
Maybe the same is true for some sites here as well?

@TooManyStacks commented on GitHub (Jun 13, 2025): What I notice in on projects, like playwright. Is that cookies do not easily transfer from system to system and headless and with head act differently with cookies. Maybe the same is true for some sites here as well?

kerem commented

2026-03-01 17:58:37 +03:00

Author

Owner

@pirate commented on GitHub (Jun 26, 2025):

Yes that is unfortunately true @TooManyStacks, many sites tie the session to a browser fingerprint and will invalidate it if they detect a differnt browser trying to re-use cookies. Adding other headers like the USER_AGENT can help but it's not perfect, that's why it's better to use a full CHROME_USER_DATA_DIR with exactly the same browser binary used to set it up (instead of only cookies), and always run in headful mode.

@pirate commented on GitHub (Jun 26, 2025): Yes that is unfortunately true @TooManyStacks, many sites tie the session to a browser fingerprint and will invalidate it if they detect a differnt browser trying to re-use cookies. Adding other headers like the USER_AGENT can help but it's not perfect, that's why it's better to use a full `CHROME_USER_DATA_DIR` with exactly the same browser binary used to set it up (instead of only cookies), and always run in headful mode.

kerem commented

2026-03-01 17:58:37 +03:00

Author

Owner

@TooManyStacks commented on GitHub (Jun 26, 2025):

I tried with the chrome dir, but not headful mode. Will do that as a test later.

@TooManyStacks commented on GitHub (Jun 26, 2025): I tried with the chrome dir, but not headful mode. Will do that as a test later.

kerem commented

2026-03-01 17:58:37 +03:00

Author

Owner

@pirate commented on GitHub (Dec 29, 2025):

@claude can you fix this on dev, make sure singlefile uses the same SINGLEFILE_CHROME_ARGS (x-fallback: CHROME_ARGS) as the chrome plugin so that it gets the user data dir and other launch options.

@pirate commented on GitHub (Dec 29, 2025): @claude can you fix this on dev, make sure singlefile uses the same SINGLEFILE_CHROME_ARGS (x-fallback: CHROME_ARGS) as the chrome plugin so that it gets the user data dir and other launch options.

kerem commented

2026-03-01 17:58:37 +03:00

Author

Owner

@claude[bot] commented on GitHub (Dec 29, 2025):

Claude finished @pirate's task in 3m 45s —— View job • claude/issue-1445-20251229-2236 • Create PR ➔

Fixed SingleFile Chrome arguments ✓

Task: Make SingleFile use the same Chrome arguments (SINGLEFILE_CHROME_ARGS with fallback to CHROME_ARGS) as other Chrome-based plugins so that user data directory and cookies work correctly.

Changes Made

Added SINGLEFILE_CHROME_ARGS config option in archivebox/plugins/singlefile/config.json:
- New config field with fallback to CHROME_ARGS
- Allows passing Chrome command-line arguments like --user-data-dir
Updated SingleFile extractor in archivebox/plugins/singlefile/on_Snapshot__50_singlefile.py:
- Reads SINGLEFILE_CHROME_ARGS (with fallback to CHROME_ARGS)
- Passes Chrome arguments to SingleFile via --browser-args parameter
- Updated docstring to document the new environment variable

How It Works

When you set CHROME_USER_DATA_DIR or add Chrome arguments via CHROME_ARGS, SingleFile will now:

First check for SINGLEFILE_CHROME_ARGS environment variable
Fall back to CHROME_ARGS if not set
Pass these arguments to Chrome when launching via --browser-args

This ensures SingleFile respects the same Chrome configuration (user data directory, cookies, etc.) as other Chrome-based extractors like PDF and Screenshot.

Example Usage

# Set Chrome user data directory (will now work for SingleFile too)
archivebox config --set CHROME_USER_DATA_DIR=/path/to/chrome/profile

# Or set Chrome args that will apply to all Chrome-based extractors including SingleFile
archivebox config --set CHROME_ARGS='["--user-data-dir=/path/to/profile", "--profile-directory=Default"]'

# Or set SingleFile-specific Chrome args
archivebox config --set SINGLEFILE_CHROME_ARGS='["--user-data-dir=/path/to/profile"]'

--- | Branch: claude/issue-1445-20251229-2236

@claude[bot] commented on GitHub (Dec 29, 2025): **Claude finished @pirate's task in 3m 45s** —— [View job](https://github.com/ArchiveBox/ArchiveBox/actions/runs/20583908413) • [`claude/issue-1445-20251229-2236`](https://github.com/ArchiveBox/ArchiveBox/tree/claude/issue-1445-20251229-2236) • [Create PR ➔](https://github.com/ArchiveBox/ArchiveBox/compare/dev...claude/issue-1445-20251229-2236?quick_pull=1&title=Fix%3A%20Make%20SingleFile%20use%20SINGLEFILE_CHROME_ARGS%20with%20fallback%20to%20CHROME_ARGS&body=Fixes%20%231445%0A%0AThis%20PR%20resolves%20the%20issue%20where%20SingleFile%20was%20not%20respecting%20Chrome%20user%20data%20directory%20and%20other%20Chrome%20launch%20options%20that%20work%20for%20other%20Chrome-based%20extractors%20%28PDF%2C%20Screenshot%2C%20etc.%29.%0A%0A%23%23%20Changes%0A-%20Added%20%60SINGLEFILE_CHROME_ARGS%60%20config%20option%20with%20fallback%20to%20%60CHROME_ARGS%60%0A-%20Updated%20SingleFile%20extractor%20to%20pass%20Chrome%20arguments%20via%20%60--browser-args%60%0A-%20Updated%20documentation%0A%0AThis%20ensures%20SingleFile%20respects%20the%20same%20Chrome%20configuration%20as%20other%20Chrome-based%20extractors.%0A%0AGenerated%20with%20%5BClaude%20Code%5D%28https%3A%2F%2Fclaude.ai%2Fcode%29) --- ### Fixed SingleFile Chrome arguments ✓ **Task**: Make SingleFile use the same Chrome arguments (SINGLEFILE_CHROME_ARGS with fallback to CHROME_ARGS) as other Chrome-based plugins so that user data directory and cookies work correctly. #### Changes Made 1. **Added `SINGLEFILE_CHROME_ARGS` config option** in `archivebox/plugins/singlefile/config.json`: - New config field with fallback to `CHROME_ARGS` - Allows passing Chrome command-line arguments like `--user-data-dir` 2. **Updated SingleFile extractor** in `archivebox/plugins/singlefile/on_Snapshot__50_singlefile.py`: - Reads `SINGLEFILE_CHROME_ARGS` (with fallback to `CHROME_ARGS`) - Passes Chrome arguments to SingleFile via `--browser-args` parameter - Updated docstring to document the new environment variable #### How It Works When you set `CHROME_USER_DATA_DIR` or add Chrome arguments via `CHROME_ARGS`, SingleFile will now: 1. First check for `SINGLEFILE_CHROME_ARGS` environment variable 2. Fall back to `CHROME_ARGS` if not set 3. Pass these arguments to Chrome when launching via `--browser-args` This ensures SingleFile respects the same Chrome configuration (user data directory, cookies, etc.) as other Chrome-based extractors like PDF and Screenshot. #### Example Usage ```bash # Set Chrome user data directory (will now work for SingleFile too) archivebox config --set CHROME_USER_DATA_DIR=/path/to/chrome/profile # Or set Chrome args that will apply to all Chrome-based extractors including SingleFile archivebox config --set CHROME_ARGS='["--user-data-dir=/path/to/profile", "--profile-directory=Default"]' # Or set SingleFile-specific Chrome args archivebox config --set SINGLEFILE_CHROME_ARGS='["--user-data-dir=/path/to/profile"]' ``` --- | [Branch: claude/issue-1445-20251229-2236](https://github.com/ArchiveBox/ArchiveBox/tree/claude/issue-1445-20251229-2236)

Rows
Columns

[GH-ISSUE #1445] Chrome Browser Profile / Cookies not applying to SingleFile in v0.7.2? #2373

Fixed SingleFile Chrome arguments ✓

Changes Made

How It Works

Example Usage