Review the file-based memory store via the Agent Monitor Config Explorer API: the user and project CLAUDE.md plus per-project auto-memory files under ~/.claude/projects/<slug>/memory/*.md. Groups by project, shows the index (MEMORY.md) vs per-fact files, and flags stale or oversized facts. Reads /api/cc-config/memory and /api/cc-config/file?path=. Use when curating agent memory.
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Curate the user's file-based agent memory: the long-form CLAUDE.md files plus
the per-project auto-memory store — read through the Agent Monitor dashboard at
http://localhost:4820.
The user provides: $ARGUMENTS
This may be:
-Users-david-WebstormProjects-foo) — restrict the
review to that one project's auto-memory dir.| Endpoint | Returns |
|---|---|
GET /api/cc-config/memory | { items:[…] }. CLAUDE.md entries: { scope:"user"|"project", file, size, mtime, preview }. Auto-memory entries: { scope:"auto-memory", project, name, isIndex, file, size, mtime, frontmatter, preview } |
GET /api/cc-config/file?path=<abs> | full body of one file: { ok, file, size, mtime, truncated, text } — use to read a fact in full before recommending an edit |
List the user and project CLAUDE.md entries with scope, size (KB), and
last-modified (mtime). Note any that are truncated (over 256 KB) — these
are oversized and worth splitting into auto-memory facts.
Group scope: "auto-memory" items by project. For each project show the
index (isIndex: true, typically MEMORY.md) first, then the per-fact
files. For each fact show name, frontmatter.description if present, size,
and mtime.
Within each project, compare the index (MEMORY.md) against the per-fact files
present. Flag facts that exist on disk but are not referenced by the index, and
index entries that point at files which no longer appear in /memory.
Flag facts whose mtime is old relative to the rest of the store (stale —
candidates to confirm or retire) and facts whose size is large (oversized —
candidates to split into smaller, single-fact files). When the user wants to
act on one, fetch its full body with GET /api/cc-config/file?path=<file>
before recommending changes.
Auto-memory files are editable through the Config Explorer. To create/overwrite a fact:
curl -s -X PUT http://localhost:4820/api/cc-config/file \
-H 'Content-Type: application/json' \
-d '{"scope":"auto-memory","type":"auto-memory","project":"<slug>","name":"<fact>.md","content":"..."}'
To delete a fact:
curl -s -X DELETE http://localhost:4820/api/cc-config/file \
-H 'Content-Type: application/json' \
-d '{"scope":"auto-memory","type":"auto-memory","project":"<slug>","name":"<fact>.md"}'
A timestamped backup is written automatically before any edit or delete.
The user/project CLAUDE.md uses type:"memory" with a scope and no name.
Never edit or delete a memory file without explicit per-action confirmation
from the user — default to read-only review.
Scope | File | Size | Modified | Truncated).http://localhost:4820, say so and tell
the user to start it with npm start from the repo root.还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Inspect fired CCAM alerts and manage alert rules for token thresholds, event patterns, inactivity, and status duration. Use when acknowledging alerts, creating or editing a rule, checking cooldowns, or connecting alert rules to webhook targets.
中文简介正在准备中。当前显示原文说明。
Identify anomalous sessions using Agent Monitor data — cost outliers from the pricing engine, token anomalies (cache miss spikes, compaction baseline surges), unusual event type ratios (PreToolUse/PostToolUse gaps, APIError clusters), behavioral deviations from workflow intelligence (complexity score outliers, error propagation anomalies), and sessions with abnormal metadata (extreme turn_count, high thinking_blocks, zero turn_duration).
中文简介正在准备中。当前显示原文说明。
Produce a detailed report on APIError events from Agent Monitor data — counts over time, which sessions and models are affected, and the likely root cause (rate limits, overload/529, or context-window pressure) inferred from each event's summary and data payload. Use when API errors spike or when you need to explain why requests are failing.
中文简介正在准备中。当前显示原文说明。
Benchmark one session (or a small recent set) against the rolling average using Agent Monitor data — cost, total tokens, tool count, and workflow complexity score — and report where each metric lands as a percentile of the population. Tells you whether a session was normal, cheap, or an outlier. Use when judging whether a session was typical or out of band.
中文简介正在准备中。当前显示原文说明。
Define a spend budget for Claude Code and, optionally, create a cost alert rule that fires when usage crosses the limit, via POST /api/alerts/rules on the Agent Monitor dashboard. Reads current spend from /api/pricing/cost to size the budget sensibly and explains every rule field before writing. Use when setting a spend limit or wiring up a budget guardrail.
中文简介正在准备中。当前显示原文说明。
Analyze prompt-cache effectiveness for Claude Code usage from the Agent Monitor dashboard — cache hit rate (total_cache_read / (total_cache_read + total_input)), cache_write vs cache_read reuse, cache-read vs cache-write spend, and the sessions with the poorest reuse. Pulls token totals from /api/analytics, per-session detail from /api/sessions, and dollar splits from /api/pricing/cost. Use when diagnosing cache spend or deciding whether prompt caching is paying off.
中文简介正在准备中。当前显示原文说明。