← ClaudeAtlas

chat-historyshowlisted

Show the status of the persistent chat-history log — file size, entry count, header fingerprint, age, and the last few entries
event4u-app/agent-config · ★ 7 · AI & Automation · score 84
Install: claude install-skill event4u-app/agent-config
<!-- cloud_safe: noop --> # /chat-history show Inspect `agents/runtime/.agent-chat-history` — the JSONL log appended by the structural chat-history hooks (`ChatHistoryAppendHook`, `ChatHistoryHaltAppendHook`) for crash recovery. Shows: - Whether the file exists and whether logging is currently enabled - File size vs `max_size_kb` - Header metadata: schema version, `started`, `frequency` - Entry count and age of the oldest/newest entry - A peek at the last 3–5 entries so the user can see what was captured Read-only — this command never writes to the file. ## When NOT to use - Wipe the file → delete `agents/runtime/.agent-chat-history` manually; it is git-ignored and will be recreated on the next hook fire. - Configure logging behavior → edit `.agent-settings.yml` directly (`chat_history.*`); see [`layered-settings`](../../docs/guidelines/agent-infra/layered-settings.md#section-aware-merge-rules). ## Steps ### 1. Check if enabled Read `chat_history.enabled` from `.agent-settings.yml`. If `false` or the section is missing, say so and stop: ``` > 📒 chat-history is disabled (chat_history.enabled = false). > Set it to true in .agent-settings.yml to start logging. ``` ### 2. Read status via helper Run `scripts/chat_history.py status`. The helper returns a JSON object with `exists`, `size_bytes`, `size_kb`, `entries`, `header`, and `path`. If `exists: false`, tell the user the file has not been created yet — it will be created on the next agent turn that writes an