Skip to content
OpenAlerts logo

OpenAlerts

Watches agent runs locally and sends alerts to Slack, Discord or Telegram when sessions stall, LLM calls fail or spend spikes.

Maintained

At a glanceswept Oct 19, 2026

≈ 1visits/mo

Established · estimate, read Oct 20, 2026

For
Developers running AI agents who need alerts when sessions stall, error, or overspend.
Activity
Maintainedrelease 9 days ago · site updated 8 months ago
Runs as
Self-hosted
Used for
  • get Slack alerts when an agent session stalls
  • catch repeated LLM errors before the bill arrives
  • watch live agent sessions on a local dashboard
Worth knowingcomputed from what we read · each with its source
  • Publishes llms.txt, a file written for AI assistantsopenalerts.dev ↗
  • Launched on Product Hunt on Mar 3, 2026Product Hunt ↗
Alternatives in Agentsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare OpenAlerts with

Pick up to two.

All 10 alternatives to OpenAlerts →

All Agents tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use OpenAlerts for?

Sign in to leave a note
Questions this page answers
  • What is OpenAlerts?

    Watches agent runs locally and sends alerts to Slack, Discord or Telegram when sessions stall, LLM calls fail or spend spikes. It is listed in the Atlas under Agents.

  • Who is OpenAlerts for?

    Developers running AI agents who need alerts when sessions stall, error, or overspend.

  • Do people use OpenAlerts?

    Established: ≈ 1 visits/mo · estimate, 2026-10 · 113 installs/mo (npm).

  • Is OpenAlerts still maintained?

    Maintained: release 9 days ago · site updated 8 months ago.

  • What are alternatives to OpenAlerts?

    In Agents, by use: Future AGI, Seclai, Tessary, Navige, ClawHost.chat, Cerver.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk