/health
See what's actually breaking in production
Check production error logs for a service in your stack and surface a grouped report.
What it does
Your app is live and something's failing, but the answer is buried in a logging dashboard you open twice a year. /health knows which log tool each service in your stack uses, pulls the recent errors, and groups them by root cause instead of dumping raw lines.
The report reads like a triage note: what's failing, how often, since when, and which group deserves attention first. It also remembers per-service overrides, so the second run on any service is faster than the first.
What it looks like
/health the API
142 errors in the last 24 hours, three groups. Group 1 (131 of them): checkout webhook rejecting a missing signature header. It started right after Tuesday's deploy, so this is the one to fix. Group 2 (9): timeouts calling the email service, external. Group 3 (2): one-off database blips, no pattern. Want the file and line for group 1?
Illustrative exchange. Output adapts to your actual project.
When to type /health
- Users report something broken and you don't know where to look
- You deployed yesterday and want to know if error rates moved
- You want a morning “is anything on fire?” check without opening dashboards
- A service went quiet and you're not sure if that's good
Pairs well with
Works in every major agent
/health installs as a plain file in your project and runs wherever your agent does.
Get /health and 21 more commands
Install it once. One license gets your agent the full Boost OS menu, seven always-on guards, and a memory of your project that survives between sessions. Lifetime updates.
From $99 · 7-day refund · license key emailed instantly