Lob CLI
🚧
Lob is a separate, external tensor-native version-control system that Tensormorph anchors to (see Merge Conflicts) - it is not part of the
tmorph CLI, and its own command reference is Lob's to document, not Tensormorph's. This page covers only how the two CLIs interact.Where tmorph operates on a checkpoint file directly, Lob's own CLI operates on weight history - commits, branches, and the structural conflicts that Merge Conflicts describes as needing resolution outside Tensormorph. If your work involves resolving a structural conflict or inspecting Lob history directly, that happens through Lob's CLI or a Lob-native tool, not through tmorph.
Where the two meet
A checkpoint opened in Tensormorph carries a commit pin back to the Lob commit it came from (see Hugging Face Models for the same addressing idea applied to Hub revisions). Scripting a pipeline that touches both tools typically looks like:
- Resolve or update history using Lob's own CLI.
- Materialize or check out the checkpoint at the commit you want.
- Hand that file to
tmorph index/tmorph validatefor the Tensormorph-side steps - see Batch Inspection and CI Validation.
Related resources
- Merge Conflicts - what Tensormorph does and doesn't do at the Lob boundary.
- Tensormorph CLI - the
tmorphcommands that pick up where a Lob checkout leaves off. - Versions and Branches - more on how Tensormorph addresses Lob-versioned checkpoints.