Set up with an AI coding assistant
Use the agent quickstart to connect your coding assistant, inspect existing monitoring, install the right integration, and verify a real run.
Connect your AI assistant, choose temporary access to one workspace, and copy the private setup prompt into your trusted coding assistant. It includes the temporary token so the assistant can start through the management API. MCP configuration is optional. The quickstart covers permissions, expiry, and the work your assistant can do.
Work on code without workspace access
Your assistant can still help edit your repository when you prefer to manage CronRadar in the console. Give it this prompt:
Connect this repository's scheduled jobs to CronRadar. Read
https://docs.cronradar.com/md/getting-started.md and identify the real scheduler
and deployment process. Choose the matching guide from
https://docs.cronradar.com/llms.txt and read its current availability notice.
Use only a published package's supported behavior, or the guide's manual HTTP
setup if SDK connections are unavailable. Do not invent installation methods.
Preserve schedules, time zones, retries, and job behavior. Read CRONRADAR_API_KEY
from the deployment secret store; use placeholders in code examples. Never ask
me to paste a key into chat, print it, or commit it. I will create the application
and key in the console's Setup tab. Keep deployment environments separate.
Run the relevant tests. Explain the deployment or restart needed, and follow
https://docs.cronradar.com/md/verify.md to verify a real run. Do not claim that
installation or a demo proves activation. Do not deploy or deliberately fail a
production job without my request. Report observed results and remaining steps.Use Setup in the selected application to create and save its ingestion key, then review the assistant's changes before deploying. Open Jobs to verify the real execution and Alerts to review recipients. Notification delivery remains unverified until the intended recipient confirms an alert or channel test.
Relevant references
- Agent quickstart: temporary workspace access, MCP, management API, and task recipes.
- Choose an integration: available SDK packages and manual HTTP alternatives.
- Connect your first automation: console setup and deployment steps.
- Verify the setup and troubleshooting.
The documentation itself grants no account access and contains no credentials.