Web Proxy Tools
Free Tools
Cookie Plugin
UA GeneratorWhat Is My Browser User Agent
MAC Address Generator
IP Generator
IP Address List
2FA Code Generator
World Clock
Anonymous Check
WebRTC Leak Test
UUID Generator
Free Web Proxy Site
Proxy Checker
FB Ad Checker
AI Web Scraping
Free SMM Tools
Twitter Shadowban Checker
Instagram Name CheckerRun DICloak Agent in Docker for headless and server-side workflows. Expose the Agent API on port 52100, forward CDP ports 45000-45099, persist runtime data under /dicloak/data, and connect Playwright or Puppeteer through the returned webSocketDebuggerUrl.
Pull dicloakinc/dicloak-agent-image:latest from Docker Hub. Browser kernels are downloaded on demand, so the first profile startup may take longer.
Use Docker Compose with TOKEN or USER_EMAIL and USER_PASSWD, AGENT_PORT=52100, DOCKER=1, and a persistent /dicloak/data volume.
Check http://127.0.0.1:52100/agent/status and /agent/user-info to confirm readiness, login state, running profile count, and kernel download progress.
Open a browser profile through your DICloak Local API workflow, read debug_port, request /json/version, and connect Playwright or Puppeteer with webSocketDebuggerUrl.
Docker gives server-side automation a repeatable runtime, persistent logged-in sessions, and predictable network boundaries.
Desktop installs are difficult to reproduce across CI, cloud servers, and long-running automation hosts.
Browser automation needs logged-in sessions and profile data that survive restarts without manual repair.
CDP ports and local API access can become risky when exposed without clear host bindings.
Running the wrong account type can interfere with active team sessions and make credential rotation messy.
Deploy the same dicloak-agent-image across development, staging, and production with Compose-managed settings.
Keep kernels, user-data, extensions, logs, and cache in a mounted /dicloak/data directory so sessions can be reused safely.
Publish the Agent API on 52100 and keep the CDP range bound to localhost by default unless your network design requires otherwise.
Run Docker with a dedicated internal member account so permissions, ownership, and credential rotation stay easy to manage.
A production-oriented DICloak Agent runtime for persistent logged-in browser sessions, profile isolation, and CDP automation.
The container exposes the HTTP Agent API on 52100 for status checks, account session inspection, and coordination with your Local API automation flow.
Browser debugging ports are forwarded through 45000-45099. Query /json/version on the returned debug_port before connecting your automation framework.
Mount /dicloak/data to keep downloaded browser kernels, profile user-data directories, extensions, logs, and runtime cache across container restarts.
Use a dedicated member account with the required Local API or Docker permission. Avoid exposing port 52100 publicly without firewall, VPN, or reverse-proxy protection.
The mapped CDP range supports up to 100 concurrent browser instances, with each active profile assigned its own debug port.
Use the Compose template for image updates, restart policy, resource limits, shared memory, host proxy reuse, and stable operational settings.
The current Agent image expects Compose-managed login variables, Agent API port 52100, CDP forwarding, and persistent /dicloak/data storage.
Choose TOKEN or USER_EMAIL plus USER_PASSWD. If both token and email login are present, Agent prefers email and password login.
Use a host bind mount for downloaded kernels, profile user-data, extensions, logs, and cache. Use separate host data directories for multiple instances.
Map 52100 for the Agent API and bind 45000-45099 to 127.0.0.1 by default. Protect 52100 if it is reachable from a public network.
Run docker compose up -d to start, docker compose pull to update, and docker compose logs -f dicloak-agent to inspect runtime behavior.
The Agent image is designed for server-side automation that needs stable browser identity, persistent sessions, and CDP connectivity.
Give AI agents persistent logged-in browser sessions that can be reopened and controlled through CDP in server-side workflows.
Run Playwright or Puppeteer against DICloak profiles on servers while keeping fingerprints, storage, and profile identity isolated.
Use repeatable containers for scheduled browser tasks, regression checks, or service-side workflows that need stable profile state.
Operate separate browser environments for multiple accounts while preserving user-data directories and reducing cross-session interference.
Open profiles through your Local API flow and inspect regional pages, ad placements, and authenticated experiences from controlled browser sessions.
Monitor regional pricing, inventory, promotions, and account-specific pages using persistent browser profiles and controlled CDP connections.
DICloak Agent Docker works with CDP-compatible frameworks and server-side automation stacks after your Local API flow opens a browser profile.
Docker Hub: dicloakinc/dicloak-agent-image
