The latest minor release of the Checkly Agent is here, bringing support for Playwright check suites, and a handful of performance, observability and security improvements. improvements. This changelog includes all updates from version 6.0.1 to 6.1.0

Runtimes

• Supports both 2024.09 and 2025.04 runtimes on private locations.

Playwright check suites now supported (beta)

• You can now run Playwright check suites (Beta) in private locations (along with all 22 public locations)

• Dependency caching is available to speed up runs:

  • Disabled by default with: DEPENDENCY_CACHE=OFF

  • Enable caching with: DEPENDENCY_CACHE=CHECKLY_S3

  • Want a custom cache backend? Please let us know; we’d love to hear about your use case.

• Improved secret scrubbing file handling.

• Node.js is now bundled with the agent and used during check runs - no more pulling it from the public internet. It’s safer, faster, and more predictable.

• cURL proxy environment variables are now supported, including both HTTPS_PROXY and ALL_PROXY .

Improved debugging and logging

• Set the environment variable DEBUG=checkly:* to output detailed internal command logs. ⚠️ Use with caution, these logs may expose secrets into your agent logs.

• The automatic RAM check that previously caused the message Your check run has reached the maximum memory usage of 2.97 GiB. is now disabled by default.

  • To re-enable, set the environment variable:

    ENABLE_MEMORY_MANAGEMENT: true, which will set it up to a 95% of your containers’ memory limit: /sys/fs/cgroup/memory.max

Baseline agent image improvements

• Now supports runs from arbitrary user IDs, ideal for teams enforcing specific UIDs for security compliance.

• Docker image size reduced from 2.24GB to 1.42GB (compressed). For faster Docker/K8s pulls and lighter deployments.

• All known npm vulnerabilities have been patched.

• Artifact upload is now more fault-tolerant, with built-in retries to improve resilience.

Update the agent to get all the latest features into your private locations.

We’d love to hear how you and your team get on. Share your feedback in the developer hub in Slack, opening a support chat, or connect with your Solutions Engineer!

Happy monitoring!