kandev/apps/cli/README_internal.md

Kandev CLI (internal docs)

Architecture

flowchart TD
    A["kandev"] --> B["CLI parses arguments"]
    B --> C{"Command?"}

    C -->|run / default| D["resolveRuntime()"]
    C -->|dev| F["Use local repo"]
    C -->|start| G["Use local build"]

    D --> D1{"KANDEV_BUNDLE_DIR set?"}
    D1 -->|yes| D2["Use env bundle (Homebrew)"]
    D1 -->|no| D3["require.resolve('@kdlbs/runtime-{platform}')"]
    D3 -->|hit| D4["Use installed npm bundle"]
    D3 -->|miss| D5{"--runtime-version given?"}
    D5 -->|yes| D6["Download from GitHub Releases (cache)"]
    D5 -->|no| D7["Throw: 'No runtime found'"]

    D2 --> E["Start backend + Next.js standalone"]
    D4 --> E
    D6 --> E

    F --> F1["make dev + next dev"]
    G --> G1["binary + next start"]

Overview

This package provides the kandev CLI launcher. The runtime bundle (Go backend, agentctl, Next.js standalone web) is installed by the package manager — there is no first-run download.

Two install channels share the same release artifacts:

• npm/npx: kandev@X.Y.Z declares optionalDependencies for @kdlbs/runtime-{platform}@X.Y.Z. npm 7+ filters by os/cpu and installs only the matching one.
• Homebrew: kdlbs/homebrew-kandev formula downloads the GitHub release tarball into the Cellar and sets KANDEV_BUNDLE_DIR.

Both channels resolve to the same runtime bundle layout (bin/kandev, bin/agentctl, web/server.js). The CLI launcher (runtime.ts) abstracts over them.

Artifact shapes

The GitHub release bundle and the npm runtime package are different shapes because they serve different consumers:

# GitHub release bundle (used by Homebrew + manual installs)
kandev/
├── bin/{kandev,agentctl}
├── web/server.js
└── cli/
    ├── bin/cli.js              # #!/usr/bin/env node + chmod +x
    └── dist/cli.bundle.js      # esbuild single-file bundle (deps inlined)

# npm runtime package (@kdlbs/runtime-{platform})
@kdlbs/runtime-{platform}/
├── bin/{kandev,agentctl}
└── web/server.js

The cli/ directory is only in the GitHub bundle (Homebrew needs the launcher). For npm installs, the main kandev package already provides the CLI; the runtime package only ships the binaries + web bundle.

Commands

Command	Description
kandev or kandev run	Run from installed runtime bundle (default)
kandev dev	Run local repo with hot-reload (requires repo checkout)
kandev start	Run local production build (requires make build first)

CLI Options

Option	Description
--version, -V	Print CLI version and exit
--port, --backend-port	Backend port
--web-internal-port	Override internal Next.js port
--verbose, -v	Show info logs
--debug	Show debug logs + agent message dumps
--runtime-version <tag>	Advanced/debug: download a specific GitHub runtime tag
--help, -h	Show help

Updates (package-manager owned)

The CLI no longer self-updates. Updates flow through the install channel:

brew upgrade kandev                  # Homebrew
npm install -g kandev@latest         # npm global
npx kandev@latest                    # always pulls latest

There is no KANDEV_NO_UPDATE_PROMPT or KANDEV_SKIP_UPDATE env var anymore — they're gone with the self-updater.

Bundling for Homebrew

The Homebrew bundle uses dist/cli.bundle.js, an esbuild single-file output that inlines tree-kill, tar, and other Node deps. Required because the Cellar has no node_modules. The npm package uses the unbundled dist/cli.js and resolves deps via npm.

pnpm -C apps/cli build      # produces dist/cli.js
pnpm -C apps/cli bundle     # produces dist/cli.bundle.js (~212KB)

Smoke test the bundle in a clean directory:

mkdir /tmp/smoke && cd /tmp/smoke
node /path/to/apps/cli/dist/cli.bundle.js --help

If Cannot find module 'tree-kill' appears, the bundle is broken.

Local Development

# Run CLI in dev mode (uses tsx)
pnpm -C apps/cli dev

# Run with arguments
pnpm -C apps/cli dev -- start
pnpm -C apps/cli dev -- --port 9000

Release

Releases run entirely in GitHub Actions. From the GHA UI:

1. Open the Release workflow.
2. Click Run workflow.
3. Choose bump (patch / minor / major) from the dropdown.
4. Optionally tick dry_run to validate without publishing.
5. Click Run workflow.

The workflow does everything: version bump, CHANGELOG, PR, merge, tag, build, npm publish, Homebrew tap update. See /.github/workflows/release.yml.

Single SemVer flow: apps/cli/package.json version, git tag, npm packages, and Homebrew formula are all bumped to the same X.Y.Z.

Versioning:

• One SemVer X.Y.Z for everything (npm, GitHub tag, Homebrew formula)
• Git tag format: vX.Y.Z
• Legacy vM.m tags normalized to M.m.0 during migration; new releases always use vX.Y.Z

Environment Overrides

Variable	Description
KANDEV_BUNDLE_DIR	Force runtime bundle location (set by Homebrew wrapper, tests)
KANDEV_PORT / KANDEV_BACKEND_PORT	Backend port
KANDEV_WEB_PORT	Internal Next.js port
KANDEV_HEALTH_TIMEOUT_MS	Override health check timeout (ms)
KANDEV_GITHUB_OWNER	Override GitHub repo owner (default: kdlbs) for --runtime-version
KANDEV_GITHUB_REPO	Override GitHub repo name (default: kandev) for --runtime-version
KANDEV_GITHUB_TOKEN	Optional GitHub token for rate limits

Supported Platforms

Platform	npm runtime package	GitHub asset name
macOS (Apple Silicon)	@kdlbs/runtime-darwin-arm64	kandev-macos-arm64.tar.gz
macOS (Intel)	@kdlbs/runtime-darwin-x64	kandev-macos-x64.tar.gz
Linux (x64)	@kdlbs/runtime-linux-x64	kandev-linux-x64.tar.gz
Linux (ARM64)	@kdlbs/runtime-linux-arm64	kandev-linux-arm64.tar.gz
Windows (x64)	@kdlbs/runtime-win32-x64	kandev-windows-x64.tar.gz
Windows (ARM64)	Falls back to windows-x64 (x64 emulation)

Note: platform.ts uses internal naming (macos, windows); npm os field uses npm conventions (darwin, win32). runtime.ts maps between the two.

npm requirements

The optional-dependency runtime resolution requires npm 7 or newer. npm 6 silently skips optional deps during npx, which would leave users with no runtime. package.json declares engines.npm: ">=7" to surface this at install time as a clear error.