lore extract
Download a package’s .lore archive from the Registry and write its files to disk.
Usage
lore extract <namespace/name[:version]> [flags]Description
lore pull renders a package’s markdown content for an AI runtime — it never extracts spec.include files (real files bundled by Scaffold and similar packages) directly onto disk. Instead, lore pull writes an instruction file pointing at lore extract as the recommended way to fetch those real files.
lore extract downloads the raw archive via GET /v1/packages/:namespace/:name/:version/raw and writes every file it contains — manifest.yaml, content/*.md, and anything under spec.include — to a local directory. It authenticates exactly like lore push/lore pull (--token → LORE_AUTH_TOKEN → a saved lore login session), so it works for private packages without you or an AI having to obtain or pass a bearer token by hand.
This command exists specifically so AI agents following a lore pull instruction file don’t need to fetch an authenticated Registry endpoint directly (which would 401 for any private package) or read your credentials off disk themselves. They just run lore extract, the same way they’d run any other CLI command.
Flags
| Flag | Description |
|---|---|
--output, -o | Output directory (default: ./{name}-{version}/) |
--org | Org scope for org-owned private namespaces |
--token | Bearer token (default: LORE_AUTH_TOKEN or the saved lore login session) |
--registry | Registry URL |
Examples
# Extract to the default ./dotnet-service-1.0.0/ directory
lore extract solutio/dotnet-service:1.0.0
# Extract a private, org-scoped package to a specific directory
lore extract eicon/eicon-frontend-template:1.0.0 --org eicon --output ./scratch
# Version omitted resolves to the latest published version
lore extract solutio/dotnet-serviceOutput
✓ Extracted solutio/dotnet-service:1.0.0 → dotnet-service-1.0.0/ (14 files)See lore pull for how instruction files reference this command, and Bundling Real Files for the package-authoring side.