A commit doesn't push. A hook fires but the output goes nowhere. A Convex note gets tagged wrong and never surfaces again. A project's backlog item has been "in progress" for three weeks and nobody noticed.
None of these send an alert. You find out weeks later when something downstream goes sideways. The problem isn't that things break. It's that nothing tells you they broke.
I needed a single place to look every morning and know: what's healthy, what's drifted, and what needs attention before I open a single project window.
Life at a Glance pulls data from Convex, git, the Claude Code hook layer, and the file system. It doesn't store state of its own. It reads the real state of everything already running and puts it in one place.
Every open backlog item across every project, with staleness flags. Items that haven't moved in 30 days show up with a warning before they become invisible.
The Claude Code hook layer runs 40+ scripts on every tool call. The dashboard shows recent hook fires, blocks, and silent failures so nothing disappears into the logs unnoticed.
Every Claude Code session writes a structured note to Convex. The dashboard surfaces the most recent ones by project so I can see what was worked on and what was left open.
I maintain a map of every hook, skill, rule, and memory file in my setup. When something is added or changed without the map being updated, the drift shows up here.
Convex notes are the long-term memory for the whole setup. Poorly tagged notes become unfindable. The dashboard flags notes that are missing required tags before they get buried.
Uncommitted changes, untracked files sitting for days, branches that haven't been pushed. The kinds of drift that accumulate quietly across five repos running in parallel.
The layout is dense by design. This isn't a presentation tool. It's a status panel. I open it, I scan it, I know where I am. The sections that matter most to me that day are the ones I look at first.
The instrument panel for a multi-project, multi-hook, AI-assisted workflow.
This dashboard is not finished and it never will be. Every time I add a new project, a new hook type, or a new kind of data I care about, another panel gets added. That's the point. It grows with the system it's watching.
The work here isn't the dashboard itself. It's knowing exactly what visibility you need, building it yourself, and keeping it current as everything around it changes.