deepagents-thread-inspector

1---2name: deepagents-thread-inspector3description: Inspect and explain conversations in the local Deep Agents Code SQLite session store. Use as a fallback when LangSmith trace tooling is unavailable, for offline or untraced sessions, or when asked to identify or summarize a local dcode thread, inspect checkpoint metadata, list recent local threads, or parse $DEEPAGENTS_HOME/.state/sessions.db and a thread UUID or prefix.4license: MIT5compatibility: designed for deepagents-code6---7 8# Deep Agents Thread Inspector9 10If LangSmith tooling is available for a traced thread, prefer it. Otherwise, use `scripts/inspect_sessions.py` instead of manually decoding database blobs. It opens the database read-only and deserializes the root message channel with LangGraph's strict MsgPack loader — reading the materialized messages from the latest checkpoint, or replaying writes in checkpoint order when that fast path is unavailable — and emits JSON.11 12## Inspect local state13 14Resolve `SKILL_DIR` to the directory containing this `SKILL.md`; do not assume a user, project, or installation-specific location. Start with the smallest useful view:15 16```bash17python3 "$SKILL_DIR/scripts/inspect_sessions.py" THREAD_ID --mode latest-turn18```19 20A unique thread-ID prefix is accepted. Select another view when needed:21 22```bash23python3 "$SKILL_DIR/scripts/inspect_sessions.py" THREAD_ID --mode summary24python3 "$SKILL_DIR/scripts/inspect_sessions.py" THREAD_ID --mode transcript25```26 27Use `--include-metadata` only when run, repository, model, checkpoint, or LangGraph metadata matters. Use `--max-content N` to raise or lower the default 4,000-character limit per message, tool result, or tool-call argument.28 29If the user does not know the ID, list recent threads first:30 31```bash32python3 "$SKILL_DIR/scripts/inspect_sessions.py" --list 2033```34 35Pass `--db PATH` only for a non-default session store. The default is `$DEEPAGENTS_HOME/.state/sessions.db`, or `~/.deepagents/.state/sessions.db` when that variable is unset. `DEEPAGENTS_SESSIONS_DB` overrides both. The script applies the same rules dcode does, so a relative or `~user` value is rejected rather than resolved to a database dcode never writes.36 37## Explain the result38 39Synthesize the JSON rather than pasting it verbatim.40 41- State the user's request, the assistant's conclusion, and significant tool actions or failures.42- Distinguish stored facts from your interpretation.43- For the latest turn, describe only the final user message and subsequent activity unless earlier context is required to make it understandable.44- Mention truncation when a relevant record has `content_truncated` or `args_truncated` set.45- Surface reconstruction problems when the result includes a top-level `warnings` array (for example, a corrupt checkpoint, a skipped write, or malformed metadata) so conclusions are appropriately hedged.46- Do not expose unrelated credentials, tokens, personal data, or hidden reasoning that may appear in local records.47 48## Safety49 50Keep inspection read-only. Do not deserialize an untrusted database: checkpoint deserialization is intended for trusted local Deep Agents state. Do not mutate or delete session rows unless the user separately and explicitly requests it.51