More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Warm Browser: Keep Headless Chrome Alive in LXC

    1

    Stop headless Chrome and Puppeteer dying by themselves inside a Proxmox LXC. Your agent finds whether AppArmor or D-Bus is killing the browser, fixes it, and adds the monitoring that tells you when it dies.

    $7

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Warm Browser: Keep Headless Chrome Alive in LXC

    Warm Browser: Keep Headless Chrome Alive in LXC

    Example session with this skill installed

    Our app renders invoices with a long-lived Puppeteer browser and falls back to pdfkit when Chrome is gone. We just discovered customers have been getting the ugly fallback for days and nobody noticed. There's no record of Chrome dying. What should we add so this can't happen quietly? A separate cron process sends our morning report.

    • Read your context and instructions
    • Compiled the warm browser

    Summary

    The core gap is that Chrome's death and the fallback are both unrecorded. Your cron is a separate process and can't see in-memory stats, so these events have to go to shared storage.

    What the answer covers

    • Capture every Chrome death and the reason for it.
    • Record every render by renderer, so no invoice can use pdfkit without leaving a record.
    • Make the morning report warn on fallbacks, on repeat deaths and on missing health data.
    • Send an immediate alert, because a morning report can be 24 hours late.
    • Prove it works by killing Chrome on purpose.
    • Then find the real cause, including the two LXC failures that kill a browser with no error.

    The skill gives your agent the code and the fixes.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A browser that stays open dies after a few idle minutes, while one-off renders look fine. Two separate faults cause that same symptom, and fixing one doesn't stop the other.

    Your agent will

    • Check for the AppArmor profile fault on Ubuntu 24.04 containers and disable it safely
    • Check for the D-Bus abort and set the right environment for the Chrome child only
    • Tell FATAL:dbus lines from the thousands of harmless ERROR:dbus lines, so you stop chasing noise
    • Add exit handlers, death counts and a record of every fallback render

    How it was tested

    These fixes come from a production service that renders PDFs with a long-lived browser. On five written scenarios, agents with the skill met every check. Agents without it met 77%. We wrote those checks ourselves, so read them as a guide.

    The AppArmor fault applies to Chrome at /opt/google/chrome/chrome. Puppeteer's bundled Chrome doesn't match that profile.
    Written for LXC. Docker has its own set of causes.
    We tested the fixes on Ubuntu 24.04 containers.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 8 days ago

    Requires

    Puppeteer or headless Chrome
    Shell access to the container

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    File Scopes

    /etc/apparmor.d/chrome

    Disabling the AppArmor profile applies only when Chrome runs with --no-sandbox and the host log shows the denial.

    Listed8 days ago
    Updated7 days ago

    What's inside

    Frequently Asked Questions

    The D-Bus and AppArmor faults apply to Chrome itself. The code samples use Puppeteer.

    The skill does it only where Chrome already runs with --no-sandbox, because that profile's sandbox permission goes unused.

    It's written for Proxmox LXC containers. Other LXC hosts should behave the same.

    New in Testing & Debugging