How do I install the Deepagents Thread Inspector skill?

Run npx skillmds@latest add gabrielmoreira/deepagents-thread-inspector in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Deepagents Thread Inspector safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Deepagents Thread Inspector?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Deepagents Thread Inspector free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Deepagents Thread Inspector?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Deepagents Thread Inspector by gabrielmoreira

Name: Deepagents Thread Inspector
Rating: 4.5 (4 reviews)
Author: gabrielmoreira

Deepagents Thread Inspector

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.

gabrielmoreira Updated Sep 9, 2026 17 repo stars

File contents

Deep Agents Thread Inspector

If 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.

Inspect local state

Resolve 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:

python3 "$SKILL_DIR/scripts/inspect_sessions.py" THREAD_ID --mode latest-turn

A unique thread-ID prefix is accepted. Select another view when needed:

python3 "$SKILL_DIR/scripts/inspect_sessions.py" THREAD_ID --mode summary
python3 "$SKILL_DIR/scripts/inspect_sessions.py" THREAD_ID --mode transcript

Use --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.

If the user does not know the ID, list recent threads first:

python3 "$SKILL_DIR/scripts/inspect_sessions.py" --list 20

Pass --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.

Explain the result

Synthesize the JSON rather than pasting it verbatim.

State the user's request, the assistant's conclusion, and significant tool actions or failures.
Distinguish stored facts from your interpretation.
For the latest turn, describe only the final user message and subsequent activity unless earlier context is required to make it understandable.
Mention truncation when a relevant record has content_truncated or args_truncated set.
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.
Do not expose unrelated credentials, tokens, personal data, or hidden reasoning that may appear in local records.

Safety

Keep 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.

---name: deepagents-thread-inspectordescription: 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.license: MIT--- # Deep Agents Thread Inspector If 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. ## Inspect local state Resolve `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: ```bash python3 "$SKILL_DIR/scripts/inspect_sessions.py" THREAD_ID --mode latest-turn ``` A unique thread-ID prefix is accepted. Select another view when needed: ```bash python3 "$SKILL_DIR/scripts/inspect_sessions.py" THREAD_ID --mode summary python3 "$SKILL_DIR/scripts/inspect_sessions.py" THREAD_ID --mode transcript ``` Use `--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. If the user does not know the ID, list recent threads first: ```bash python3 "$SKILL_DIR/scripts/inspect_sessions.py" --list 20 ``` Pass `--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. ## Explain the result Synthesize the JSON rather than pasting it verbatim. - State the user's request, the assistant's conclusion, and significant tool actions or failures. - Distinguish stored facts from your interpretation. - For the latest turn, describe only the final user message and subsequent activity unless earlier context is required to make it understandable. - Mention truncation when a relevant record has `content_truncated` or `args_truncated` set. - 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. - Do not expose unrelated credentials, tokens, personal data, or hidden reasoning that may appear in local records. ## Safety Keep 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.

Frequently asked questions