Docs/Start
Get started : From install to the first PR
First PR on the machine you develop on. One campaign, by hand. Lumpcode never touches this checkout.
On this page
1. Prerequisites
- Node.js 22+
- A git repo with
originyou can push to, and a primary branch that already exists on that remote (usuallymain) - Git
user.nameanduser.emailset. Lumpcode writes commits. - A CLI coding agent on
PATH(Cursor, Copilot, Claude Code, Codex, or OpenCode) - Awareness that
lumpcode runinvokes that agent (LLM cost)
2. Install the CLI
Puts lumpcode on your PATH. This is what runs a lump.
npm install -g @lumpcode/cli2b. Optional: install the skill
Helps the agent in your editor write and update lumps. Call the skill /lumpcode in your agent's session to help it write and update lumps. Not used when a lump runs.
npx skills add lumpcode/skills3. Initialize a project and create a lump
From the repo root. project-setup writes .lumpcode/project.json (commit this) and .lumpcode/local.json (per machine, gitignored). Default primary branch is main. If this repo merges on something else, pass it: lumpcode project-setup --primaryBranch dev.
lumpcode project-setup
lumpcode lump-create myFirstLump4. Point the lump at real work
Edit .lumpcode/lumps/myFirstLump/config.json. This replaces the stub lump-create wrote. Change the path templates to files that exist in this repo. The snippet below is the same shape as the landing example; it only matches if you have src/components/{NAME}/. To confirm remotes and the agent first, use the README smoke test instead.
{
"contextListJson": {
"COMPONENT": "src/components/{NAME}/index.tsx",
"TEST": "src/components/{NAME}/index.test.tsx"
},
"prompt": {
"promptTemplate": "Port @{COMPONENT} to Vue 3 and update @{TEST}.",
"command": "cursor"
}
}
Commit .lumpcode/project.json and the lump folder. Push before you set up a worker: that clone only sees what is on the remote.
5. Preview, then run
Preview without calling the agent. If the context list is empty, the path templates do not match this repo. Fix them before you run.
lumpcode lump-plan myFirstLump --contexts
lumpcode run myFirstLumprun invokes the agent on one context, writes a LUMP: myFirstLump - … marker commit, and pushes a lump/myFirstLump/… branch. Open that as a PR.
This is how Lumpcode is meant to run
A one-off run is how you check it. A worker is how you live with it. Start it once on a clone you never edit; you keep authoring and merging on the laptop. .lumpcode/ must already be on the remote.
lump/ticketBacklog/LUMP-214pushedlump/docsSweep/cli-commandspushedlump/normalizeUtils/slugifyrunning