lore delete
Permanently remove a session and all its associated messages and links from the database. This operation is irreversible.
lore delete <SESSION> [OPTIONS]Examples
Section titled “Examples”# Delete a session by ID prefix (prompts for confirmation)lore delete abc123
# Delete without the confirmation promptlore delete abc123 --forceSample Output
Section titled “Sample Output”$ lore delete c9731a91
Session c9731a91-4f2b-4e8a-9c3d-1a2b3c4d5e6f Tool: claude-code Started: 2025-12-25 17:52:00 Directory: /Users/dev/myapp Branch: main
This will permanently delete 566 messages and 1 links.Delete session c9731a91? [y/N] yDeleted session c9731a91 (566 messages, 1 links)With --force, the confirmation prompt is skipped:
$ lore delete c9731a91 --force
Session c9731a91-4f2b-4e8a-9c3d-1a2b3c4d5e6f Tool: claude-code Started: 2025-12-25 17:52:00 Directory: /Users/dev/myapp Branch: main
This will permanently delete 566 messages and 1 links.Deleted session c9731a91 (566 messages, 1 links)Options
Section titled “Options”| Option | Description |
|---|---|
--force | Skip the confirmation prompt and delete immediately |
Session ID Prefix
Section titled “Session ID Prefix”You only need to provide enough characters to uniquely identify a session:
# Full UUIDlore delete c9731a91-4f2b-4e8a-9c3d-1a2b3c4d5e6f
# Short prefix (if unique)lore delete c9731a91
# Even shorterlore delete c973If the prefix matches multiple sessions, Lore lists the matches and asks for a more specific prefix.
What Gets Deleted
Section titled “What Gets Deleted”Deleting a session removes:
- The session record
- All of its captured messages
- All of its links to git commits
The session’s original transcript files (for example, the tool’s own .jsonl files) are not touched. If the source files still exist, a later lore import may re-import the session.
See Also
Section titled “See Also”- lore sessions - List sessions
- lore unlink - Remove a link without deleting the session
- lore db prune - Bulk-delete old sessions