@lumpcode/cli 0.0.0 → 0.0.1

package/DOCS/advanced-config.md

@@ -104,7 +104,7 @@ Use `promptFn` when `promptTemplate` is not enough — it gives you fine-grained
 export default {
   baseBranch: 'main',
   contextListJson: { FILE: 'src/{NAME}.ts' },
-  command: 'claude',
+  command: 'copilot',
   steps: [
     {
       promptFn: ({ context, contextRunState }) => {
@@ -130,7 +130,7 @@ This enables branching workflows:
 export default {
   baseBranch: 'main',
   contextListJson: { FILE: 'src/{NAME}.ts' },
-  command: 'claude',
+  command: 'copilot',
   steps: [
     {
       promptTemplate: 'Does @{FILE} need a README section? Reply YES or NO only.',

package/DOCS/commands.md

@@ -6,8 +6,6 @@ This page documents every `lumpcode` subcommand and its options.
 
 **[Global conventions](#ref-global-conventions)** — [Working directory](#ref-working-directory) · [`--json`](#ref-json-output) · [Booleans](#ref-boolean-options) · [Validation](#ref-project-validation) · [`--help`](#ref-lumpcode-help)
 
-**[Auth](#ref-auth)** — [`lumpcode login`](#ref-cmd-login) · [`lumpcode logout`](#ref-cmd-logout)
-
 **[Project setup](#ref-section-project-setup)** — [`lumpcode project-setup`](#ref-cmd-project-setup) · [`lumpcode lump-create`](#ref-cmd-lump-create)
 
 **[Run](#ref-section-run)** — [`lumpcode run`](#ref-cmd-run) · [`lumpcode lump-plan`](#ref-cmd-lump-plan)
@@ -77,46 +75,6 @@ The program and each subcommand support **`--help`** (e.g. `lumpcode run --help`
 
 ---
 
-<a id="ref-auth"></a>
-
-## Auth
-
-<a id="ref-cmd-login"></a>
-
-### `lumpcode login`
-
-**Description:** Authenticate against the Lumpcode API and persist the session token locally. You need a Lumpcode account ([lumpcode.com](https://lumpcode.com)); same prerequisite as the [README](../README.md#before-you-run-anything).
-
-**Usage:** `lumpcode login [options]`
-
-
-| Option       | Type   | Required | Description                                                                                       |
-| ------------ | ------ | -------- | ------------------------------------------------------------------------------------------------- |
-| `--email`    | string | No       | Email; if omitted, you are prompted                                                               |
-| `--password` | string | No       | Password for non-interactive login; **not recommended** (visible in process list / shell history) |
-
-
-**Behavior:**
-
-- If a valid token already exists in `~/.lumpcode/auth.json`, prints that you are already logged in.
-- Otherwise authenticates with the Lumpcode service, then writes `~/.lumpcode/auth.json`.
-
-**See also:** [get-started.md](./get-started.md#step-1-log-in).
-
-<a id="ref-cmd-logout"></a>
-
-### `lumpcode logout`
-
-**Description:** Delete stored authentication.
-
-**Usage:** `lumpcode logout [options]`
-
-**Options:** None besides global [`--json`](#ref-json-output).
-
-**Behavior:** Removes `~/.lumpcode/auth.json`.
-
----
-
 <a id="ref-section-project-setup"></a>
 
 ## Project setup

package/DOCS/examples.md

@@ -8,7 +8,7 @@ Deep references: [concepts.md](./concepts.md), [lump-config.md](./lump-config.md
 
 ## 0. Smoke test — one context, minimal prompt
 
-*When to use:* right after `lumpcode lump-create` to confirm login, remotes, agent command, and marker commits before you invest in a real campaign.
+*When to use:* right after `lumpcode lump-create` to confirm remotes, agent command, and marker commits before you invest in a real campaign.
 
 Uses a single fixed path every repo already has (`README.md`). Adjust `FILE` if your project root has no `README.md`.
 
@@ -21,7 +21,7 @@ Uses a single fixed path every repo already has (`README.md`). Adjust `FILE` if
   },
   "prompt": {
     "promptTemplate": "Reply with exactly one line: smoke OK for @{FILE}. Do not edit any file.",
-    "command": "claude"
+    "command": "copilot"
   }
 }
 ```
@@ -38,7 +38,7 @@ A classic refactoring lump: discover every component folder, do a multi-step mig
 
 ```json
 {
-  "command": "claude",
+  "command": "copilot",
   "contextListJson": {
     "FOLDER": "src/components/{COMPONENT_NAME}/",
     "TYPES":  "src/components/{COMPONENT_NAME}/{COMPONENT_NAME}.types.ts",
@@ -65,7 +65,7 @@ Treat a JSON ticket file as the source of truth and let `dependsOnContexts` enfo
 
 ```json
 {
-  "command": "claude",
+  "command": "copilot",
   "getContextListFn": "./tickets.js",
   "numberOfContextsPerBranch": 1,
   "prompt": {
@@ -125,7 +125,7 @@ Use `contextMatchFn` so the matcher itself decides what to skip. Each call recei
 
 ```json
 {
-  "command": "claude",
+  "command": "copilot",
   "contextMatchFn": "./match.js",
   "maximumNumberOfConcurrentBranches": 5,
   "prompt": {
@@ -164,7 +164,7 @@ Each file that imports `lodash` becomes one context. Lumpcode handles the branch
 
 ```json
 {
-  "command": "claude",
+  "command": "copilot",
   "contextMatchFn": "./match.js",
   "numberOfContextsPerBranch": 10,
   "prompt": {
@@ -196,7 +196,7 @@ Run over `packages/*/` and produce or refresh each package README from real sour
 
 ```json
 {
-  "command": "claude",
+  "command": "copilot",
   "contextListJson": {
     "PKG_FOLDER":  "packages/{PKG}/",
     "PKG_JSON":    "packages/{PKG}/package.json",
@@ -218,7 +218,7 @@ Mix a static prompt with a function-form prompt item to short-circuit work when
 
 ```js
 export default {
-  command: 'claude',
+  command: 'copilot',
   contextListJson: { PKG_JSON: 'packages/{PKG}/package.json' },
   steps: [
     {

package/DOCS/get-started.md

@@ -8,10 +8,9 @@ Follow this guide in order to get started with your first `lumpcode run`. Links
 
 Install and prepare the following:
 
-1. **Lumpcode account** — Create one at [lumpcode.com](https://lumpcode.com); you’ll use it to log in.
-2. **Lumpcode CLI** on your `PATH` — Installers vary by OS (Homebrew `brew install lumpcode`, curl one-liners, Windows downloads, or `npm install -g @lumpcode/cli` on Node 22+). The npm install uses a native binary when available for your platform and otherwise runs with Node automatically. For installation details: [README.md § Install](../README.md#install).
-3. **Git** repository with **`origin`** reachable for fetch/push. The **`projectBaseBranch`** you'll declare in `.lumpcode/local.json` (typically `main`) must **already exist on `origin`** (e.g. `origin/main`): Lumpcode pulls it during pre-flight and reads it via `origin/<projectBaseBranch>` for status.
-4. **CLI coding agent** installed and runnable. Lumpcode invokes the **`command`** you set in lump config by resolving a command module in this order: `.lumpcode/commands/<name>.js` (project), then `~/.lumpcode/commands/<name>.js` (global override), then shipped presets at `~/.lumpcode/commands/presets/<name>.js`. Built-in preset names **`cursor`** and **`copilot`** work out of the box when `cursor-agent` or `copilot` is on `PATH`; other agents (e.g. **`claude`**, **`aider`**) need a custom module until more presets ship.
+1. **Lumpcode CLI** on your `PATH` — Installers vary by OS (Homebrew `brew install lumpcode`, curl one-liners, Windows downloads, or `npm install -g @lumpcode/cli` on Node 22+). The npm install uses a native binary when available for your platform and otherwise runs with Node automatically. For installation details: [README.md § Install](../README.md#install).
+2. **Git** repository with **`origin`** reachable for fetch/push. The **`projectBaseBranch`** you'll declare in `.lumpcode/local.json` (typically `main`) must **already exist on `origin`** (e.g. `origin/main`): Lumpcode pulls it during pre-flight and reads it via `origin/<projectBaseBranch>` for status.
+3. **CLI coding agent** installed and runnable. Lumpcode invokes the **`command`** you set in lump config by resolving a command module in this order: `.lumpcode/commands/<name>.js` (project), then `~/.lumpcode/commands/<name>.js` (global override), then shipped presets at `~/.lumpcode/commands/presets/<name>.js`. Built-in preset names **`cursor`** and **`copilot`** work out of the box when `cursor-agent` or `copilot` is on `PATH`; other agents (e.g. **`aider`**) need a custom module until more presets ship.
 
 ---
 
@@ -40,17 +39,7 @@ You only need **`.git/`** here. The next steps create **`.lumpcode/`** in this s
 
 ---
 
-## Step 1: Log in
-
-```bash
-lumpcode login
-```
-
-Use your Lumpcode email and password when prompted. The CLI saves the session to `~/.lumpcode/auth.json` and skips prompting if you are already logged in. For non-interactive use and flags, see [commands.md § `lumpcode login`](./commands.md#ref-cmd-login).
-
----
-
-## Step 2: Initialize the Lumpcode project
+## Step 1: Initialize the Lumpcode project
 
 From the repository root:
 
@@ -92,7 +81,7 @@ Extra fields (`maximumNumberOfConcurrentBranches`, …): [project-config.md](./p
 
 ---
 
-## Step 3: Create a lump
+## Step 2: Create a lump
 
 ```bash
 lumpcode lump-create myFirstLump
@@ -104,11 +93,11 @@ By default this writes **`.lumpcode/lumps/myFirstLump/config.json`** with a smal
 lumpcode lump-create myFirstLump --config js
 ```
 
-`lump-create` gives you one path template plus `@{FILE}` in the prompt; Step 4 is where you reshape that for your campaign.
+`lump-create` gives you one path template plus `@{FILE}` in the prompt; Step 3 is where you reshape that for your campaign.
 
 ---
 
-## Step 4: Define contexts
+## Step 3: Define contexts
 
 `contextListJson` maps variable names to path **templates** (e.g. `{NAME}`, `{COMPONENT_NAME}`). Lumpcode scans the repo and keeps only combinations where **every** template resolves to a real path; each map **key** is a **`{VAR}`** in `promptTemplate`, or **`@{VAR}`** with a leading `@` for agents that treat `@path` as file context. Substitution rules: [lump-config.md § Prompt template syntax](./lump-config.md#prompt-template-syntax).
 
@@ -124,7 +113,7 @@ Minimal stub (`lump-create` defaults look like this—adjust `FILE`/prompt):
   },
   "prompt": {
     "promptTemplate": "Improve the code at @{FILE}.",
-    "command": "claude"
+    "command": "copilot"
   }
 }
 ```
@@ -139,7 +128,7 @@ Repeat-per-component variant (multiple paths must exist per context—the prompt
   },
   "prompt": {
     "promptTemplate": "Migrate the component at @{COMPONENT} (folder @{FOLDER}) to Vue 3 <script setup>.",
-    "command": "claude"
+    "command": "copilot"
   }
 }
 ```
@@ -150,7 +139,7 @@ Transforms (e.g. `$upperFirst{…}`) and **`contextOptionsFn`** for `priority` /
 
 ---
 
-## Step 5: Run once
+## Step 4: Run once
 
 ```bash
 lumpcode run myFirstLump
@@ -172,7 +161,7 @@ Do **not** confuse **`lump-status`** (context rows from git) with **`daemon-stat
 
 ---
 
-## Step 6: Run continuously (optional)
+## Step 5: Run continuously (optional)
 
 From the same repository root:
 

package/DOCS/lump-config.md

@@ -39,7 +39,7 @@ Minimal shape:
   "contextListJson": { "FILE": "src/{NAME}.ts" },
   "prompt": {
     "promptTemplate": "Improve types in @{FILE}",
-    "command": "claude"
+    "command": "copilot"
   }
 }
 ```
@@ -71,7 +71,7 @@ Two forms appear repeatedly in the field tables below. Each is defined here once
 
 `command` fields (top-level and per-prompt-item) are **not** function references. They hold the **registered name** of a command module:
 
-- **String** (e.g. `"cursor"`, `"copilot"`, `"claude"`, `"aider"`, `"my-agent"`) — resolved against `commands/<name>.js` under the project (`.lumpcode/commands/`), then the global config folder (`~/.lumpcode/commands/`), then shipped presets (`~/.lumpcode/commands/presets/`). Project-local wins over global override; global wins over preset. **`cursor`** and **`copilot`** are built-in preset names (require `cursor-agent` / `copilot` on `PATH`).
+- **String** (e.g. `"cursor"`, `"copilot"`, `"aider"`, `"my-agent"`) — resolved against `commands/<name>.js` under the project (`.lumpcode/commands/`), then the global config folder (`~/.lumpcode/commands/`), then shipped presets (`~/.lumpcode/commands/presets/`). Project-local wins over global override; global wins over preset. **`cursor`** and **`copilot`** are built-in preset names (require `cursor-agent` / `copilot` on `PATH`).
 - **Inline function** (`config.js` only) — a `CommandFn` used directly without registry lookup.
 
 Pass agent flags inside the command module's exported `command` function (`executable` + `args`), not in the `command` string. See [advanced-config.md](./advanced-config.md#custom-agent-commands).
@@ -230,7 +230,7 @@ History is written **before** an optional `postCommandExecFn` on the same prompt
   "keepHistory": true,
   "prompt": {
     "promptTemplate": "Improve @{FILE}",
-    "command": "claude"
+    "command": "copilot"
   }
 }
 ```
@@ -263,7 +263,7 @@ import { defineConfig } from '@lumpcode/cli-types';
 
 export default defineConfig({
   contextListJson: { FILE: 'src/{NAME}.ts' },
-  prompt: { promptTemplate: 'Fix @{FILE}', command: 'claude' },
+  prompt: { promptTemplate: 'Fix @{FILE}', command: 'copilot' },
 });
 ```
 

package/DOCS/publishing.md

@@ -2,6 +2,17 @@
 
 Operator-only notes for publishing from the monorepo. End users install via `npm i -g @lumpcode/cli@beta` (see [README](../README.md)).
 
+## Bump versions
+
+Align all three publishable packages and workspace `@lumpcode/core` deps:
+
+```bash
+node scripts/set-npm-versions.mjs 0.0.1
+node scripts/set-npm-versions.mjs --patch
+```
+
+Runs `npm install` at the repo root by default (pass `--no-install` to skip).
+
 ## Packages and order
 
 Publish in dependency order:

package/DOCS/types.md

@@ -200,7 +200,7 @@ type CommandFn = ((
 
 Return `{ executable, args }` to run a subprocess. Return `null`, `undefined`, or nothing to skip execution; `postCommandExecFn` still runs with an empty `commandResult`. `keepHistory` entries are not written for skipped commands.
 
-Lumpcode runs the agent as `executable` + `args`. Agent-specific flags and the prompt text go into `args` the way your agent expects (e.g. `executable: 'claude', args: ['-p', prompt]` or `executable: 'aider', args: ['--message', prompt]`). This is exactly what a command module at `.lumpcode/commands/<name>.js` exports as its `command`.
+Lumpcode runs the agent as `executable` + `args`. Agent-specific flags and the prompt text go into `args` the way your agent expects (e.g. `executable: 'copilot', args: ['-p', prompt]` or `executable: 'aider', args: ['--message', prompt]`). This is exactly what a command module at `.lumpcode/commands/<name>.js` exports as its `command`.
 
 ### `PostCommandExecFn`
 

package/README.md

@@ -29,9 +29,8 @@ Operators can set `LUMPCODE_SKIP_BINARY=1` to skip the native download, `LUMPCOD
 
 You will need:
 
-- **A Lumpcode account** — sign up at [lumpcode.com](https://lumpcode.com); `lumpcode login` will prompt for credentials.
 - A project on your machine **with git push access to `origin`** for the repository you want to automate. The `baseBranch` you pick (e.g. `main`) must already exist on the remote — Lumpcode reads it via `origin/<baseBranch>`.
-- **A CLI coding agent on your `PATH`** — verify with e.g. `claude --version` or `aider --version`. Lumpcode invokes the agent through a **command module** registered by name (e.g. `claude`, `aider`) under `.lumpcode/commands/<name>.js` or `~/.lumpcode/commands/<name>.js`. See [DOCS/advanced-config.md](DOCS/advanced-config.md#custom-agent-commands).
+- **A CLI coding agent on your `PATH`** — verify with e.g. `copilot --version` or `cursor-agent --version`. Lumpcode invokes the agent through a **command module** registered by name (e.g. `copilot`, `cursor`) under `.lumpcode/commands/<name>.js` or `~/.lumpcode/commands/<name>.js`. See [DOCS/advanced-config.md](DOCS/advanced-config.md#custom-agent-commands).
 - **An understanding that `lumpcode run` calls your agent**, which usually means real LLM cost. Start with one context, review the resulting branch, then scale up.
 
 ## 60-second tour
@@ -39,7 +38,6 @@ You will need:
 From the root of a git repository:
 
 ```bash
-lumpcode login
 lumpcode project-setup
 lumpcode lump-create myFirstLump
 ```
@@ -117,7 +115,7 @@ src/components/
   },
   "prompt": {
     "promptTemplate": "Tighten the prop types in @{COMPONENT} (declared in @{TYPES}) and add any missing assertions to @{TEST}.",
-    "command": "claude"
+    "command": "copilot"
   }
 }
 ```
@@ -136,7 +134,7 @@ Each context becomes one work branch (`lump/myFirstLump/Button`, …) and one ma
 
 - `contextListJson` — Each value is a **path template** with `{PLACEHOLDER}` captures; each key (here `COMPONENT`, `TYPES`, `TEST`) becomes a variable usable in the prompt as `{COMPONENT}`, `{TYPES}`, `{TEST}`. See [DOCS/lump-config.md#contextlistjson](DOCS/lump-config.md#contextlistjson).
 - `promptTemplate` — `{VAR}` substitutes the literal value; e.g you can safely use `@{VAR}` to have the same value with a leading `@` for agents that treat `@path` as file context. See [DOCS/lump-config.md#prompt-template-syntax](DOCS/lump-config.md#prompt-template-syntax).
-- `command` — Registered [command name](DOCS/lump-config.md#command-names) only (`"claude"`, `"aider"`, …), not shell flags ([DOCS/advanced-config.md#custom-agent-commands](DOCS/advanced-config.md#custom-agent-commands)).
+- `command` — Registered [command name](DOCS/lump-config.md#command-names) only (`"copilot"`, `"cursor"`, …), not shell flags ([DOCS/advanced-config.md#custom-agent-commands](DOCS/advanced-config.md#custom-agent-commands)).
 - `$schema` — Optional but recommended: most editors will then autocomplete and validate every field above.
 
 ## TypeScript hints for `config.js` and command modules