Agentic Checks V1 is a legacy capability available only to accounts that previously used it. Existing active and deactivated Agentic Checks remain usable.
Prerequisites
Prerequisites
Before creating Agentic Checks, ensure you have:
- Access to Agentic Checks on your Checkly account
- An initialized Checkly CLI project if you want to manage the check as code
- Any required test credentials saved as Checkly variables or secrets
Define the check goal
Write the prompt as a monitoring objective, not as implementation instructions. Include the target URL, the user journey, and the observable success criteria. For broader guidance, see Prompt best practices.Prompt
- The exact page or flow to start from
- The expected end state
- Important assertions
- Known constraints, such as test account behavior
- What should count as a failure
Reference variables and secrets
Agentic Checks do not automatically expose all account variables or secrets to the agent. To expose one to an Agentic Check, reference it directly in the prompt with double curly brackets, such as{{TEST_USER_EMAIL}}.
checkout.agentic.check.ts
Add skills
Agentic Checks include a default browser automation skill. You can add extra skills when the agent needs domain-specific capabilities.agentic-runtime.check.ts
Scheduling
The CLI construct supports these frequencies:Active and deactivated checks
Useactivated: false to keep an existing Agentic Check deactivated while preserving its configuration and history:
draft.agentic.check.ts
Test and deploy
Test your project before deploying:Terminal
Terminal