v1.3.0 — Persistent Browser Profiles
What's New
🔒 Persistent Browser Profiles
Each userId now gets a dedicated Firefox profile directory. All browser storage — cookies, localStorage, IndexedDB, Service Workers, and cache — persists automatically across sessions.
This means sites like Telegram (which uses IndexedDB for auth) and Facebook (cookies) stay logged in even after closing and reopening tabs.
Features
- Persistent browser profiles: Each
userIdgets a real Firefox profile directory that auto-persists ALL browser state - Per-user Firefox processes via
launchPersistentContext(userDataDir) - Context pool manager with LRU eviction and eviction callbacks
- New env var:
CAMOFOX_PROFILES_DIR(default:~/.camofox/profiles) - Health endpoint now reports pool stats (
poolSize,activeUserIds,profileDirsTotal)
Docker
docker run -d \
-p 9377:9377 \
-v ~/.camofox:/home/node/.camofox \
ghcr.io/redf0x1/camofox-browser:1.3.0Install
npm install camofox-browser@1.3.0Breaking / Behavior Changes
- Browser contexts now use persistent Firefox profile directories (instead of ephemeral/in-memory contexts)
- Singleton browser pattern removed in favor of per-user browser processes