All docs
Buy, acquire & install
Browse the Tool Store, acquire a free package or buy an approved paid plan from your USD Store balance, then install its exact signed build in LSD.
Getting a package from the marketplace is browse → acquire account access → install in Hub → activate in Desktop. Paid listings show only server-approved plans and exact USD prices. Installing code on the machine and enabling it for an open project are separate actions.
Browse#
Two front doors to the same catalog:
- Hub's Packages page, which owns machine package discovery and installation.
- The web store in your browser.
Each listing shows the package, its published version, available content packs, reviews, and dependencies. Content is optional, so a code package can legitimately show zero packs.
Acquire on the web#
Sign in on the web Store. Choose Get free for a free listing, or select an approved one-time or monthly plan and choose Buy with balance. The page shows the exact USD total and your available USD Store balance. The server resolves the published plan itself, then atomically debits the balance and grants access. Refreshing or repeating the same request converges on the same result rather than charging twice.
The supported lsd market CLI also provides catalog and account-acquisition commands. It has no
package-install or removal command; machine package bytes remain Hub's responsibility.
A one-time plan grants perpetual access. A monthly plan pays the first calendar month immediately and renews on the signup day. If the balance is short, it enters a three-day grace period; adding enough balance during grace lets the autonomous renewal complete. Canceling a monthly agreement stops the next debit without removing the period already paid for.
Your account page shows the balance, held amount, movements, and monthly agreements in USD. Automatic reload works only when an approved funding provider is configured. Production currently leaves that capability unavailable and fails closed; local development can add test USD without credentials or network access.
Open in LSD → select → install#
The Store hands LSD Hub the exact package coordinate to select:
# → lsd://store/lsd-widgets?action=select&version=1.0.0
Preview channels use their registered scheme (for example lsd-alpha://…), so the website must
be configured for the same desktop channel.
The selector opens Hub's Packages page at that exact version; it does not install, download, or change the machine default. Review the package there and choose Install explicitly. Hub then fetches authenticated metadata, including a digest-bound dependency-first list of every exact build and every required content pack needed for the install. It verifies all downloads and rechecks the graph before changing the machine inventory, so an entitled older version remains reproducible after a newer release supersedes it. Project activation remains a separate project-scoped choice after install.
Each required .lsdcontent authority is signed separately and bound to an exact package version and
package digest. The install-metadata set covers the full resolved dependency graph and includes its
own digest and total required bytes, so Hub can preflight disk space and commit code plus required
content atomically. Optional template, sample, and learning packs remain independently
downloadable and removable. A paid pack uses its parent package entitlement; it is not another
purchase.
Acquired and installed states#
Keep account access, machine inventory and project activation distinct:
- Acquired — your account holds free access or an active paid entitlement shown against the Store catalog.
- Installed — the code is present on this machine, ready to enable in a project.
- Active in this project — Desktop has activated the available build for the open project's exact package graph. Saving persists the chosen project state.
An acquired package therefore appears on another signed-in machine before you install it there. Enable an installed package in Desktop Settings → Project Packages and save the project. If its saved exact build is missing, the Package Manager hands that coordinate to Hub; opening the selection never substitutes or installs a build automatically.
Related#
Learn — The Package Manager · Publish a package
API — PackageManager · lsd_package.json
Examples — A complete package
Frequently asked questions
Why does acquisition use my browser?
The web Store binds a free acquisition or paid licence to your account. Open in LSD selects the exact package in Hub, where you separately choose Install. Desktop activates the already available build for a project.
What is the difference between acquired and installed?
Acquired means your account has access, either free or through an active paid licence. Installed means the code is on this machine and ready to activate. A package can be acquired but not yet installed on a given device.