Stop Grepping. Start Knowing. Meet HazelJS Inspector.

One line of code. Zero instrumentation. Your entire app—routes, cron jobs, agents, flows, circuit breakers—visible in seconds. You've Been There It's 2 PM. A new dev joins your team. "Where does POST /orders go?" You open three files, trace five imports, and 20 minutes later you're still not sure. The OpenAPI spec? Last updated six months ago. The README? "See code." Or it's 11 PM. Production is acting weird. "Is that cron job even running?" You dig through service files, grep for @Cron , wonder if the expression is right. No way to know without logs—and logs won't tell you what's registered . Or you're refactoring. "What breaks if I move this module?" You map dependencies in your head. Or in a doc. Or you just... hope. Sound familiar? The Moment It Clicks Imagine this instead: You add one import to your app. You run it. You open http://localhost:3000/__hazel . Suddenly you see: Every route, method, path, controller—live Every cron job, expression, next run time Every agent, AI functio