Open source • Apache-2.0 • npm 2.4.0

Freeze, inspect and integrate GitHub PRs.

LexRunner turns changing PRs into a frozen dependency plan, runs reviewed gates and preserves results for review before authorized integration.

Start with the CLI and one package. The first-use guide takes you through discovery, planning and a gate preview before command execution or merging.

Try your first plan npm package GitHub Stack context Roadmap

First useful workflow

Discover PRs
Freeze a plan
Inspect dependency order
Preview gates

Then run checks, review and authorize integration

What LexRunner owns

Plans

Turn a work objective into an explicit plan with ordered steps, dependencies, expected artifacts, and review boundaries.

Gates

Run the right checks before a change advances: tests, lint, policy checks, authority checks, review hooks, and human escalation.

Receipts

Capture what happened at each step so another agent or human can understand the state without reconstructing the whole run.

Containment

Give agents a bounded place to work. The design goal is safer than raw worktrees: scoped roots, explicit mounted state, and clear promotion.

Coordination

Fan out independent work and merge it back through deterministic decisions, not conversational handoffs.

Recovery

When a tool, permission, test, or policy blocks work, return an actionable explanation instead of continuing blindly.

Advanced agent work

Assisted execution has separate setup and authority requirements. The tested headless application boundary is not a production supervisor; public headless launch and Stage 5 fault-injection remain unproven. Read the current execution limits before adopting this surface.

Agent swarm behavior should not mean every agent shares the same checkout, credentials, and context. The useful version is bounded parallelism.

Separate execution roots.

Each agent receives a contained working area with an explicit relationship to the project root and a known promotion path.

Per-agent authority envelopes.

A PM-shaped agent, analyst-shaped agent, developer-shaped agent, and operator-shaped agent should not all carry the same authority posture.

Credential reality stays external.

LexRunner should not become an IAM broker. It should discover when the environment cannot perform an effect and report the exact missing operator action.

Promotion is gated.

Artifacts move from contained work into canonical branches, queues, tickets, or reports only after gates and receipts make the decision reviewable.

What LexRunner should not become

Not memory	Lex owns durable memory, Frames, policy context, and recall.
Not a persona engine	LexSona owns behavioral constraints and posture.
Not an authority broker	Protected authority boundaries own effect decisions; enterprise IAM remains the source of truth for actual credentials.
Not a command catalog	AXF owns workspace capability declarations and adapter contracts.
Not a rigid SOP engine	Runner should leave room for agent reasoning while bounding effects through gates, receipts, and promotion rules.

Current access state

LexRunner is open source under Apache-2.0, with version 2.4.0 released publicly on npm. Older npm versions retain their published license terms. The containment and swarm model continues to evolve.

Licensing Start with Lex