← ClaudeAtlas

chat-historyimportlisted

Surface prior chat-history sessions as a numbered table, let the user pick one, read it silently, and emit a short summary plus a resume offer — selective, user-driven cross-session import
event4u-app/agent-config · ★ 7 · AI & Automation · score 84
Install: claude install-skill event4u-app/agent-config
<!-- cloud_safe: noop --> # /chat-history import Read-only, **user-driven** cross-session import. Surfaces prior sessions logged in `agents/runtime/.agent-chat-history` as a numbered table, the user picks **one**, the agent reads that session **silently** and emits a 2–5 sentence summary, then offers to resume the last task from that session. The agent does **not** render entries verbatim, auto-import, or rewrite the user's context without an explicit instruction. This is the opt-in counterpart to the read-path filter (Phase 3 of `road-to-chat-history-session-isolation`): default reads stay session-scoped; `import` is the explicit surface for crossing the session boundary. For project-improving learnings derived from a prior session, see [`/chat-history learn`](learn.md). ## When NOT to use - Inspect the current session — that is the default of `/chat-history show` plus `scripts/chat_history.py read`. - Generate a learning proposal from a prior session — use [`/chat-history learn`](learn.md), which orchestrates `learning-to-rule-or-skill` on the picked session. - Bulk-import all sessions — out of scope for v1. One session per invocation; multi-pick is v2. - Search prior sessions by content — out of scope for v1; no fuzzy search, no full-text grep. The user picks by `last_ts` and `summary` from the listing. ## Steps ### 1. Check if enabled Read `chat_history.enabled` from `.agent-settings.yml`. If `false` or the section is missing, say so and stop: ``` >