@growthub/cli

@growthub/cli is the local control plane for Growthub Local and Agent Workspace as Code (AWaC).

It turns repos, skills, starters, and templates into governed Workspaces that can be exported, forked, inspected, operated by agents, kept current, and optionally connected to hosted authority. The Workspace is the top-level product object; the CLI is the executor that moves it through the lifecycle.

Start here: create a governed Workspace

Power-user one-liner that exports the official starter directly:

npx -p @growthub/cli@latest growthub kit download growthub-custom-workspace-starter-v1 --out ./my-workspace

Or the guided installer:

npm create @growthub/growthub-local@latest

After export, open the no-code Workspace Builder:

cd my-workspace/apps/workspace
npm install
npm run dev

Install (CLI only)

npm install -g @growthub/cli

Reference contracts: Workspace Config Contract V1 · Governed Workspace Topology V1 · Workspace Builder Runtime V1

CLI role in the governed workspace architecture

Growthub Local keeps the Workspace as the owned artifact: a forkable app, growthub.config.json, .growthub-fork/ lifecycle state, builder state, agent-readable contracts, and optional hosted authority.

The CLI is the machine-readable path through that architecture:

• Export a starter, repo, skill, or template into a local Workspace.
• Register and inspect forks so customization carries identity, policy, and trace instead of becoming an untracked copy.
• Operate ongoing lifecycle checks for workspace status, QA, deploy readiness, upstream drift, surface detection, and portal preparation.
• Connect optional authority through Growthub auth, bridge-backed integrations, hosted agents, and capability activation when local value is already clear.
• Expose the same contracts to agents and humans through structured commands, JSON output, skill manifests, helper scripts, and the Workspace Builder.

Workspace-first setup (recommended)

The guided flow starts at the governed workspace export path before deeper harness/workflow choices:

npm create @growthub/growthub-local@latest -- --profile workspace --out ./my-workspace
npm create @growthub/growthub-local@latest -- --profile self-improving --out ./my-workspace

Discovery lanes

Main entry:

growthub discover

Core lanes:

1. Workspace Templates
2. Templates
3. Workflows
4. Local Intelligence
5. Agent Harness
6. Settings / account connection

Main commands

growthub
growthub discover

growthub kit
growthub template
growthub workflow
growthub pipeline assemble

growthub open-agents
growthub qwen-code

growthub auth login
growthub auth whoami
growthub auth logout

Discovery

growthub discover

Example:

Open the interactive hub and choose a lane by outcome (kit/template/workflow/harness/auth).

Kits

growthub kit list
growthub kit inspect <kit-id>
growthub kit download <kit-id>

Compatibility examples used by package validation:

growthub kit list
growthub kit inspect growthub-custom-workspace-starter-v1
growthub kit download growthub-custom-workspace-starter-v1
growthub kit path growthub-custom-workspace-starter-v1
growthub kit validate /absolute/path/to/kit

How local adapters use workspace exports

1. Export or resolve a workspace path from the CLI.
2. Point the agent working directory at the exported folder.
3. Start a new session so the workspace contract loads from AGENTS.md / SKILL.md.

Workflows + pipelines

growthub workflow
growthub pipeline assemble

Harnesses

growthub open-agents
growthub qwen-code

Account connection

growthub auth login
growthub auth whoami

Immediate value first, activation optional

You can get real local value without connecting a hosted account.

When ready, activate deeper hosted lanes:

Docs

• Growthub Local README
• First-Run Paths
• CLI Workflows Discovery
• Agent Harness Auth Primitive
• Contributing