@treeseed/cli

@treeseed/cli publishes the treeseed and trsd command surfaces. Use it to configure Treeseed, run local development, save/stage/release work, reconcile hosting, operate capacity providers, manage package images, and inspect workflow state.

The CLI is the human and automation entrypoint over package-owned capabilities. It delegates platform logic to @treeseed/sdk, web runtime orchestration to @treeseed/core, backend behavior to API surfaces, capacity runtime to @treeseed/agent, and TreeDX image workflows to package manifests.

What You Can Do With The CLI

• configure local, staging, and production environments
• start and inspect local development instances
• save, stage, close, resume, and release multi-repo work
• plan/apply/verify hosted infrastructure through reconciliation
• run operations-runner smoke checks
• build and operate capacity providers
• manage TreeDX package image workflows
• inspect package drift, workflow locks, and interrupted runs

Install

npm install @treeseed/cli

After installation:

treeseed --help
trsd --help

In this workspace, use npx trsd ... from the root.

Primary Commands

treeseed status --json
treeseed config
treeseed ready local --json
treeseed switch feature/my-change --plan --json
treeseed dev start --web-runtime local --json
treeseed save --verify local --json "describe the checkpoint"
treeseed stage --plan --json "describe the staging change"
treeseed release --patch --verify-deployed-resources --plan --json
treeseed recover --json

Hosted diagnostics:

treeseed ready staging --json
treeseed hosting plan --environment staging --service api --json
treeseed hosting verify --environment staging --service operationsRunner --live --json
treeseed operations smoke --environment staging --service operationsRunner --json

Capacity providers:

treeseed capacity build
treeseed capacity up
treeseed capacity status
treeseed capacity logs
treeseed capacity down

TreeDX package image:

treeseed package image --package treedx --branch staging --plan --json
treeseed package image --package treedx --branch staging --sync-config --json
treeseed package image --package treedx --branch staging --execute --json

Use treeseed help <command> for command-specific usage and examples.

Managed Package Set

The CLI coordinates the root market repo plus checked-out package repositories:

• @treeseed/sdk
• @treeseed/ui
• @treeseed/core
• @treeseed/admin
• @treeseed/api
• @treeseed/cli
• @treeseed/agent
• packages/treedx

Workflow commands save package repos in dependency order, update submodule pointers, verify package release gates, and avoid one-off provider mutation.

Save, Stage, And Release

treeseed save is the default checkpoint command. It saves dirty package repositories first, restores workspace links, performs lightweight release-candidate validation, and then saves the root market repo.

treeseed save --json "describe the checkpoint"
treeseed save --verify local --json "describe the checkpoint"
treeseed save --lane promotion --json "describe the checkpoint"

treeseed stage and treeseed release are promotion-grade commands. Use --plan before risky operations:

treeseed stage --plan --json "describe the staging change"
treeseed release --patch --verify-deployed-resources --plan --json

Interrupted workflow runs are journaled under .treeseed/workflow:

treeseed recover --json
treeseed resume <run-id> --json

How CLI Fits With Other Packages

• @treeseed/sdk owns workflow, reconciliation, config, package discovery, and platform primitives.
• @treeseed/core owns the local web runtime used by treeseed dev.
• @treeseed/admin and @treeseed/ui are consumed by the web app; CLI does not own those routes or components.
• @treeseed/api owns backend API and operations-runner implementation.
• @treeseed/agent owns capacity-provider runtime artifacts that CLI starts or reconciles.
• TreeDX owns its service/image; CLI exposes package-image workflow commands.

Package Development

From this package root:

npm install
npm run build
npm test
npm run release:verify

Release verification checks the packaged command surface, parser/help behavior, build output, and publishable artifact shape.

What CLI Does Not Own

• SDK reconciliation internals
• Core web runtime internals
• Admin routes or UI components
• backend API implementation
• capacity-provider runtime implementation
• TreeDX service internals
• root market content or ecommerce

See the root Package Ownership guide for cross-package boundaries.