Make your next integration reviewable.

Your first useful result: an inspected plan

Use an existing local GitHub checkout with open PRs, Git and Node.js 24 or newer. This is useful when PRs depend on one another or integration order is hard to track. For occasional independent PRs, you may not need it.

1. Install and discover

npm install --save-dev @smartergpt/lexrunner@2.4.0
npx lexrunner --version
npx lexrunner weave discover --json

Run from the repository root. Installation updates your package manifest, lockfile and dependencies. Discovery reads GitHub. Private repositories need an authorized GITHUB_TOKEN supplied securely to the process; signing into gh alone does not export it. Follow your repository's package-manager policy.

Use npx lexrunner --help for the main work and integration families. Use npx lexrunner --help-all for every command family and compatibility alias, or npx lexrunner <command> --help for complete options and nested operations. Help does not execute those operations or grant authority.

2. Freeze and inspect

npx lexrunner weave plan --from-github --output plan.json --json
npx lexrunner schema validate plan.json --json
npx lexrunner weave merge-order plan.json --json

Choose an unused output filename. Planning reads GitHub again and writes the plan locally. Open it and check the target, selected PRs, recorded heads, dependencies and gate commands. Drafts are included by default; filter the selection when needed. The printed JSON is a summary, so save the plan with --output.

3. Preview the gates

npx lexrunner gate run plan.json --dry-run --json

Stop here for your first trial. You have a validated plan and preview; gate commands have not run and no PR has merged. Preview paths may write local diagnostics. Generated lint, typecheck and test gates still need to match real checks in your repository.

You can next run reviewed gate commands. Since 2.2.0, single-repository GitHub plans bind source and target refs to exact commits; names such as PR-123 remain display labels. Local integration verifies those inputs and fails if they moved. Before explicit execution, review the plan and authority, settle installation changes, and use a clean checkout with plan files and outputs outside it or in existing ignored paths. The walkthrough explains preparation, local integration and receipts. Remote PR merging remains a separate authorized action; multi-repository plans remain legacy-unbound.

CLI first; MCP when your agent needs it

The commands above need no MCP connection and no separate Lex, AXF, LexSona or policy-host service installation. npm installs LexRunner's dependencies.

For agent-driven planning and integration, use the LexRunner MCP server shipped in the same package. Use AXF MCP when the task is discovering and running workspace capabilities. Connect each for a specific need; you do not need both to begin.

Keep merge mutations disabled for an initial MCP connection. That is not a sandbox: plan tools can write files and gate tools can execute commands. Your client must control those calls. See MCP setup and component compatibility.

LexRunner 2.4.0 deliberately pins Lex 4.0.3 as a dependency. A newer standalone Lex is not a reason to override that pin. Shared stores or cross-component runtime setup need their own compatibility evidence.

Start from the work you need