/export
Export issues to JSONL format
> /plugin marketplace add gastownhall/beads > /plugin install beads@beads-marketplace
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/export
Context preview
What this command does when you run it.
Export issues to JSONL format
Command definition
export.mddescription: Export issues to JSONL format argument-hint: "[-o output-file]"
Export all issues to JSON Lines format (one JSON object per line).
Usage
- **To stdout**: `bd export`
- **To file**: `bd export -o issues.jsonl`
- **Include all records**: `bd export --all -o full.jsonl`
Issues are sorted by ID for consistent diffs, making git diffs readable.
When to Use
Dolt is the primary storage backend, so manual export is rarely needed. Use `bd export` when you need:
- A JSONL snapshot of issue records
- Data migration to another system
- Sharing issues outside the Dolt workflow
`bd export` is not a full database backup. It does not capture Dolt branches, commit history, working-set state, or non-issue tables. Use `bd backup` for a restorable Dolt-native database backup.
Distributed graph issue tracker for AI agents, powered by Dolt. Platforms: macOS, Linux, Windows, FreeBSD Docs: Beads provides a persistent, structured memory for coding agents.
Repo: gastownhall/beads
Other commands on beads.
- /plan-to-beads
Convert a Claude Code plan file into beads epic + tasks for cross-session tracking.
Open command - /audit
Log and label agent interactions (append-only JSONL)
Open command - /blocked
Show blocked issues
Open command - /close
Close a completed issue
Open command - /comments
View or manage comments on an issue
Open command - /compact
Compact old closed issues using semantic summarization
Open command