A tiny traffic light for Claude Code, especially if you vibe code

If you vibe code with Claude Code, it is easy to miss when the session has gone bad. Claude can still look productive while it is actually stuck: rerunning the same failed command, filling context, burning tokens, or looping on tests. So I built a small status line tool for myself and my Claude code. It watches local Claude Code session metadata and shows: >Healthy / Careful / Stop And steer Claude code (for example, run/fix the test first) The most useful part is the stop. For example, if Bash fails multiple times while running tests, it prompts me to pause and inspect the command manually rather than letting Claude keep retrying. It does not upload prompts or tool output. It only stores derived metadata like counts, reason codes, token totals, costs, and hashed session IDs. For me, this is useful because vibe coding is fast, but it also makes it easier to trust the agent for too long when it is quietly stuck. Curious if others are using status lines or hooks to catch Claude Code loops earlier.