Automated monitoring
Recurring checks that run on a schedule without you thinking about it.
Set it and forget it
Running security audits and performance checks manually works until you forget. And you will forget. Something ships on a Friday, the security check doesn't happen, and three weeks later you discover a permissions gap that's been exposed to production traffic the whole time.
Inside Claude Code, type /monitor. It sets up recurring scheduled tasks for the checks you care about. Security audits, performance sweeps, dependency checks, error monitoring. Each one runs on its own interval, and you get notified when something needs attention.
How to set it up
Run the command and it configures scheduled tasks on your machine. You choose which checks to enable and how often they run. Security checks default to every few days. Dependency audits default to weekly. You can adjust the intervals to fit your deployment rhythm.
Each scheduled run writes a report. When findings are severe enough, you get an email notification so you don't have to remember to check.
What gets monitored
The same checks you can run manually: security scans, performance audits, dependency and dead code analysis, production error tracking. The difference is that they happen automatically on a schedule. Your codebase gets checked whether you remember to check it or not.
Why this matters
The first month after launch, you're paying attention to everything. Three months in, you're focused on growth and features. Six months in, a dependency you forgot about has three critical vulnerabilities. Automated monitoring catches the things you stop thinking about.