Bring your own agent to ilert
Access ilert fully through the command line.
Point whatever agent you already use at the CLI and put it to work. All agents are welcome.
Your agent can do anything you can do
Any AI agent, Claude Code, Codex, Cursor, and others, can use the CLI.
Talk to ilert where you already work
> Pull everything from last night's checkout outage: alerts, who was paged, when they acked, how long each escalation took, and draft the postmortem timeline.
> We just hired three SREs. Add them to the payments-platform team and into the follow-the-sun rotation without breaking existing coverage. show me the schedule before you apply it.
> Group last week's alerts from checkout-api by summary and tell me which one is noisiest — then draft an ICL condition that suppresses it outside business hours.
Anything you can do in ilert, your agent can do too.
Use the agent you already use everyday; Claude Code, Codex, Cursor. It doesn't need a wrapper someone keeps up to date; the command tree is generated from ilert's spec, so the agent discovers the platform while it works.
Learn more in the docs →Safe to hand over
Giving an agent the keys to your on-call setup is a big deal. So here's exactly what it can and can't do.
Destructive commands don't run unattended
--dry-run shows the whole plan
Output is machine-readable
Credentials stay out of the conversation
Switching to ilert in a heartbeat
Switching providers stalls on the same thing every time: someone has to rebuild every team, schedule and escalation policy by hand. Your agent can read your current setup on Opsgenie, PagerDuty or others, and rebuild it in ilert.
1 · It reads your current setup
A read-only token from your old provider, kept in an environment variable the agent never resolves.
2 · You approve a plan, not payloads
Every change is staged with --dry-run first, in dependency order: users and teams, then schedules, escalation policies, alert sources and status pages.
3 · You verify, then cut over
ilert on-call now and a smoke-test event confirm routing. Then you point your monitoring at the new keys and revoke the old ones.
Get started with ilert CLI
Install
Docker images and build-from-source instructions are in the repository.
curl -sL https://raw.githubusercontent.com/iLert/ilert-cli/master/install.sh | bash -
Authenticate
Opens your browser and completes an OAuth flow. In CI, set ILERT_API_KEY instead and every command picks it up with no login step.
ilert auth login
Use
ilert --help lists every resource and action, and ilert api /any/path calls an endpoint directly.
ilert alerts list # list open alerts ilert alerts ack 42 # accept alert #42 ilert incidents create --set summary=... # create an incident ilert event send -k <INTEGRATION_KEY> -s "msg" # fire an event at an alert source ilert dashboard # live TUI
