Lacp

LACP

Local policy, evidence, and recovery controls for coding agents.

LACP wraps Claude, Codex, Hermes, and other CLI agents with deterministic routing,
approval gates, execution records, memory controls, and rollback paths. It runs on your
machine and keeps remote execution opt-in.

Development status: main and the GitHub release are v0.10.1. Homebrew's last
bottled release may lag until the tap is updated; brew install --HEAD tracks main.
Git worktrees isolate files, not ports — see Runtime isolation.

Contents

- Quick Start
- Why teams adopt LACP
- Use-case recipes
- Documentation
- Architecture
- Features
- Prerequisites
- Install Options
- Who It's For
- Testing
- Security
- Contributing

What LACP controls

LACP is a local execution wrapper and control plane. The coding-agent host still owns its
model, tools, session, and interface. LACP owns the contract around a run: where it may
execute, which risk tier applies, when approval is required, what evidence must be kept,
and how a failed change is recovered.

ExecutionRisk tiers, budgets, context contracts, session fingerprints, and local or remote sandbox routing.
VerificationBrowser, API, and contract evidence manifests with PR preflight and release gates.
MemorySession memory, Obsidian workflows, ingestion, optional code intelligence, and provenance.
CoordinationWorktree isolation, tmux/dmux sessions, swarm manifests, handoffs, and recovery paths.

Quick start

Install

Bootstrap and verify

After bootstrap: .env is created, dependencies installed, directories scaffolded, Obsidian vault wired, and verification artifacts produced.

For the full setup and daily operator flow, start with the Runbook and Local Dev Loop.

First gated command

Why teams adopt LACP

- Route commands through explicit policy and…