Skip to content

Library Health

The first-session prompt proved the connection and summarized Rekordbox. Library Health compares that collection with the files and playlists around it.

Check files, playlists, and duplicates.

Safety: Read only

Time
Scope-dependent; filesystem traversal and exact duplicate hashing can take longer on large libraries.
You'll get
A point-in-time health report with counts, examples, and suggested manual follow-up.

Recommended

Read-only · No network · Nothing is changed

Check my library for common problems.
First show me the music folders you found and ask whether I want to check all of them or one folder. Then check for:
- missing files
- audio files that are not in Rekordbox
- tracks that are not in any playlist
- likely duplicates based on artist and title
Give me a short summary with counts and a few useful examples. Do not run the slower exact duplicate check, change or delete anything, or use online services. Ask before any follow-up action.
  • A short count summary across the four common checks.
  • A few useful examples, rather than an overwhelming dump of every result.
  • The confirmed folder scope so you know what was and was not checked.
  • Suggested next questions while every follow-up action remains your choice.

Optional · Slower: this reads and hashes every audio file in the confirmed scope, so it can take a while. Choose the folder scope before you copy it.

Look for byte-identical duplicate audio files in [folder or all music folders]. This can take a while. Show me the duplicate groups and which copy looks safest to keep, but do not move or delete anything.

Optional · Pauses for approval: this runs the quick checks first, shows you their summary, and waits before the slower exact duplicate pass.

Run a complete library health check for [folder or all music folders]. Start with the quick checks. Show me that summary, then ask before running the slower exact duplicate check. Do not change, move, or delete anything.

The quick path returns its summary and stops. An exact check starts only after you choose its scope and approve the slower pass. Likely artist-and-title matches are clues; exact hashes establish identical bytes. Neither result proves which copy should be deleted or authorizes deletion, and Library Health changes nothing.

Technical details, safety, and recovery

Complete reference

Workflow contract

Collection read-only

Scan broken links, orphan files, playlist gaps, and duplicate groups without changing the collection.

Best for
Users exploring a library safely or checking structure before and after larger changes.
Network
No networkAll scans use the local Rekordbox database and filesystem.
Scope
All content roots by default, with optional path/filter limits for individual scans.
Time
Scope-dependent; filesystem traversal and exact duplicate hashing can take longer on large libraries.
Resuming
Results are point-in-time snapshots rather than saved workflow state. Duplicate groups traverse page.next_offset while page.has_more; exact mode rehashes each request. Restart at offset zero, and re-run affected scans, after any Rekordbox scope or filesystem change.
Result
A point-in-time health report with counts, examples, and suggested manual follow-up.

What can change

Staged metadata
This workflow does not create staged metadata.
Direct user files
None.
Local state
None.
Files created
None.

Before you start

  • reklawdbox connected to the intended library.
  • Readable content roots for complete broken-link, orphan, and exact-duplicate scans.

Approval checkpoints

  • Quick checks need no approval after the user confirms all discovered content roots or selects one root.
  • Ask for explicit approval immediately before starting exact duplicate hashing.
  • Review every recommendation before taking the separate manual action in Rekordbox or on disk.

Recovery

  • Correct unreadable roots or narrow the scope, then re-run the scan.
  • Re-run all affected scans after relocating, importing, assigning, or removing tracks.

Rekordbox handoff

  1. Relocate files in Rekordbox When needed — Broken links have credible relocation suggestions.
  2. Import or remove orphan files When needed — Files exist in a content root but are not imported into Rekordbox.
  3. Assign tracks to playlists When needed — Tracks are intentionally kept but missing from playlists.
  4. Review and remove duplicates When needed — Metadata or exact-file duplicate groups are confirmed.