Work products and the bin
The scratch files a session writes usually dwarf its transcript. 3.3 GB against 360 MB on the machine these numbers come from.
Browsing them
Press w on a conversation. braids opens what that session wrote
under ~/.claude/jobs, heaviest first, with directories weighed
by everything under them.
| Key | What it does |
|---|---|
| ↵ | descend into a directory, or peek at a file |
| d | move this entry to the bin |
| f | filter this level |
| esc | up a level, then back to the map |
| y | copy the path, while reading a file |
Peeking shows the head of a text file, up to 128 KB. A binary is named and its size reported rather than spewed at your terminal. The harness's own record of a job is shown and refused, because deleting it would confuse the thing that wrote it.
From the command line
braids work --lane 46360382 braids work --lane 46360382 --path tmp braids work --lane 46360382 --json braids work --orphans # sets whose conversation is gone braids work --orphans --reclaim # move those to the bin
The bin
Nothing braids deletes is gone. It moves aside with a manifest and sits in
~/.braids/bin for 14 days. Press u from the map.
| Key | What it does |
|---|---|
| ↵ / r | restore it to where it came from |
| d | delete it for good |
| f | filter |
| esc | back |
Binned files keep the directory structure they came from. They used to be
named by basename alone, which silently lost one of two files called
data.json. That is a data-loss bug, so there is a test that
bins two files of the same name and reads both back.