Hydrating Files

Use crab hydrate when your working tree has Crab pointer files and you need the real content on disk.

crab hydrate --all
crab hydrate 'models/**'
crab hydrate --manifest .crab/manifests/ci.txt

Hydration reads each pointer, resolves its chunk metadata, downloads missing chunks from object storage or the local cache, writes the reconstructed file atomically, and verifies the result by hash.

Choose What to Hydrate

Use selective hydration in large repositories. CI jobs should normally hydrate only fixtures, models, or datasets needed by that job.

Typical Flows

# After clone
crab clone crab://team-bucket/ml-repo
cd ml-repo
crab hydrate 'models/**'

# After pulling changes
crab pull --remote origin

# Before switching context
crab dehydrate --all
git checkout experiment/new-architecture
crab hydrate 'models/**' 'data/eval/**'

Troubleshooting

• Already hydrated files are skipped.
• Failed files remain as pointers, so rerunning the same command is safe.
• Missing chunks usually mean the producing machine did not complete crab push or the remote store was modified outside Crab.
• For local recovery from a copy of the original file, use crab hydrate --recover-from <path>.

For full pattern precedence, manifest format, output modes, and options, see the crab hydrate reference.