# Conversation Dump

> Dump and diagnose conversations from the local Bionic PostgreSQL database.

- Skill: `bionic-gpt/conversation-dump` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add bionic-gpt/conversation-dump`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bionic-gpt/conversation-dump/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: bionic-gpt (https://skillmd.com/u/bionic-gpt)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/bionic-gpt/conversation-dump

---


# Conversation Dump

Use this skill when you need to inspect a conversation stored in the locally
running Bionic database, especially to diagnose tool-call, provider, or output
problems.

Run the helper from the repository root:

```bash
bash .agents/skills/conversation-dump/scripts/dump_conversation.sh
bash .agents/skills/conversation-dump/scripts/dump_conversation.sh <conversation-id>
```

With no ID it selects the conversation with the most recent chat activity. The
dump is saved by default to the workspace-local, ignored path
`tmp/conversation-dumps/conversation-<id>.md`, where it can be opened directly
from VS Code. Set `DUMP_OUTPUT=/path/to/file.md` to override that path. The
script is read-only and uses `DATABASE_URL`, falling back to `APP_DATABASE_URL`.

Report database observations separately from inferred causes. Pay particular
attention to assistant tool calls that lack a matching tool response, failed
tool/provider messages, oversized responses, and generated output records.
Never include connection strings or credentials in the report.