Skip to main content
Agentic Checks V1 is a legacy capability available only to accounts that previously used it. Existing active and deactivated Agentic Checks remain usable.
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
For CLI setup, see the CLI overview.

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
Good prompts include:
  • 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
Avoid prompts that ask the agent to test too many unrelated paths in one check. Create separate Agentic Checks for separate critical flows.

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
Do not paste secret values directly into the prompt. Store secrets in Checkly and reference them by name with {{SECRET_NAME}}.
Some applications block automated monitoring unless requests include required headers, test bypass tokens, or feature flags. If your flow depends on a header value, store that value as a Checkly variable or secret and say in the prompt which header the agent should send. Do not paste the header value directly into the prompt.

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
Keep the skill list short. Every added skill expands what the agent can do during execution.

Scheduling

The CLI construct supports these frequencies:

Active and deactivated checks

Use activated: 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
Deploy the check when you are ready:
Terminal