🚀 A real-time monitoring dashboard for Claude Code & Codex, built with SQLite3, Node.js, Express, React, Vite, TailwindCSS, & WebSockets. It tracks sessions, agent activity, tool usage, and subagent orchestration, providing live analytics, a Kanban status board, status notifications, a cute buddy, & an interactive web UI/MacOS/Windows native app.
Indexed The index holds package records for this repository. The package count is historical registry records; it does not mean those packages are available now.
Repository
Canonical name
hoangsonww/Claude-Code-Agent-Monitor
GitHub repository ID
1173790477
Package records
35 (historical registry records, not current availability)
Discovery and queue
First recorded source
search:topic:claude-skills fork:false
Discovered
Queue state
ok
Recorded errors
0
Last settled processing
Next-check eligibility
Eligible from
The first recorded source is what the queue stored first, not the full discovery history. The error count increases when processing ends in the error state and resets after a successful settlement; it is not a count of all attempts. “Last settled processing” is when it finished, not when it started.
Eligibility is calculated as of . It is not a schedule: each collector run handles only a limited number of sources, and being eligible does not promise when a check happens.
Last saved scan
Repository metadata read
Scan status
complete
Scan saved
Extractor version
2
Continuation record
None
The scan record is separate from the queue state: the queue state shows processing progress, the scan record shows what was last saved. A continuation record only means unfinished state is stored; it has no remaining count.
Source-file evidence coverage
Raw counts of the pinned source files that stored package versions reference in this repository. They show what has been recorded, not how complete the repository is.
Scope and limits
Counts distinct pinned file links (repository, commit, path) across all stored versions, from any package, that name exactly this repository's canonical name. Files of packages owned by this repository are not counted unless some version links to them here. Alias names are not merged and no history is guessed from a current name.
“Known” means a regular-file identity is recorded. It does not mean a whole directory or package is covered. Links that are not valid pinned file URLs are not counted.
152 pinned source files referenced
152 known
0 absent at commit
0 file listing truncated
0 unsupported
0 not recorded
0 read failed
Deduplicated by repository, commit and path; the same path at two commits counts as two file identities. These are not component-group counts.
Failed source-commit reads 0
No source commit has a stored failed read for files that are still unrecorded.
Linked packages 35
Linked by verified repository identity. The count is historical registry records, not current availability.
Deep analytics and monitoring for Claude Code sessions — cost tracking, token usage breakdowns, usage trends, and productivity scoring powered by Agent Monitor.
Audit and govern your Claude Code configuration and file-based memory via the Agent Monitor Config Explorer API — skills, subagents, commands, MCP servers, hooks, settings, and the per-project memory store. Surfaces sprawl, duplication, ri…
Budget tracking, spend forecasting, and cost-threshold alerts for Claude Code usage via the Agent Monitor pricing engine. Watches spend against a target budget, projects month-end cost from the daily trend, surfaces the priciest sessions, …
Direct MCP integration with the Claude Code Agent Monitor dashboard — real-time session data access, quick stats, and dashboard health monitoring via Model Context Protocol.
Developer tools for Claude Code Agent Monitor — session debugging, hook diagnostics, data export, and system health checks for maintaining a healthy monitoring setup.
AI-powered insights for Claude Code — pattern detection, anomaly alerting, optimization recommendations, and session comparison using Agent Monitor analytics.
Administer CCAM's Claude Code and Codex configuration explorers, provider-aware history import, backup restore, hook installation, home directories, updates, and MCP server.
Reliability and error monitoring for Claude Code sessions — surfaces APIError events, hook delivery failures, tool-failure ratios (PreToolUse/PostToolUse gaps), and SLO tracking with error-budget reporting, all derived from the Claude Code…
Generate stakeholder-ready CCAM reports from local session, cost, reliability, and workflow data with explicit scope, evidence, and export-friendly Markdown.
Operate dashboard-launched Claude Code and Codex runs with safe launch, follow-up, stop, resume, model discovery, and persistent run-history workflows.
Search, inspect, replay, and manage Claude Code sessions tracked by the Agent Monitor dashboard — find sessions by project, model, status, or date; reconstruct event timelines; walk transcripts turn-by-turn; roll up activity per working di…
Analyze multi-agent orchestration and Workflow-tool fleet runs — DAGs, delegation, concurrency, error propagation, and effectiveness — via the Agent Monitor workflow intelligence API at http://localhost:4820. Maps parent→child subagent edg…
🚀 A real-time monitoring dashboard for Claude Code & Codex, built with SQLite3, Node.js, Express, React, Vite, TailwindCSS, & WebSockets. It tracks sessions, agent activity, tool usage, and subagent orchestration, providing live analytics,…
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data inconsistencies across hooks, API, DB, websocket, and UI.
MANDATORY for every coding agent (Claude Code, Codex, or any other) on every change-set — every applicable source file the agent creates or updates MUST start with the project's copyright/authorship header (file overview + exact author lin…
MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, mirrored READMEs, locale-aware formatting, language switchers) in parity across every supporte…
MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, mirrored READMEs, locale-aware formatting, language switchers) in parity across every supporte…
MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, mirrored READMEs, locale-aware formatting, language switchers) in parity across every supporte…
When last recorded, these names pointed to this repository. This is a recorded resolution, not a live GitHub check; packages and metadata are never merged because of it.
No aliases pointing to this repository are recorded.
Unsupported marketplace entries 0
Entries in this repository's marketplace that this registry does not support yet. They are preserved source data and are never fetched or executed.