From 77f38050838ebebaafd661bf13daa1d6fc1a75d6 Mon Sep 17 00:00:00 2001 From: nntrivi2001 Date: Thu, 6 Aug 2026 12:00:14 +0700 Subject: [PATCH] docs(lanes): document Add Lane auto-setup (F5) --- docs/LANES.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/LANES.md b/docs/LANES.md index 4594cf5..d102d4a 100644 --- a/docs/LANES.md +++ b/docs/LANES.md @@ -32,6 +32,8 @@ ccam lanes add --repo /path/to/repo --title "My Feature" --base main --slug my-f `--title`, `--base`, and `--slug` are optional. The CLI waits for background provisioning to finish and reports either the ready lane or its failure notes. +Adding a lane through the dashboard's "+ Add lane" flow also auto-runs, best-effort, in parallel: `ccam lanes profile init` (only if a Node.js project is detected — most repos won't be, and that's a normal outcome, not a failure), `ccam lanes agents install`, and `ccam lanes mcp sync`. None of the three blocks the lane from being created or from each other — a lane whose repo has no MCP servers configured, for instance, still gets created and is still usable, just without a synced `.mcp.json`. Run any of the three manually later (from the lane's own card, or the CLI) if the automatic attempt didn't apply. + ## Destructive lane actions Reset a managed worktree, remove one, or purge the lane's eligible session history with the CLI: