ActPlane Agent工作流

Build from source

cargo install actplane is all most users need. To hack on ActPlane:

git clone --recurse-submodules https://github.com/eunomia-bpf/ActPlane
cd ActPlane/collector && cargo build --release   # uses the prebuilt eBPF object

Editing the kernel eBPF (bpf/*.bpf.c) requires the BPF toolchain (clang/llvm, libelf, zlib) and the libbpf/bpftool submodules. Rebuild and refresh the committed object with:

ACTPLANE_REBUILD_BPF=1 cargo build -p ebpf-ifc-engine   # regenerates bpf/prebuilt/process.bpf.o

Run the tests:

make test                          # bpf C unit tests + collector Rust unit tests
sudo bash script/e2e_examples.sh   # live E1–E12 enforcement

Quickstart

Install with one command. The eBPF program ships prebuilt (CO-RE, architecture independent), so there is no clang/llvm/libbpf to install — just a Rust toolchain:

cargo install actplane

Write a policy and run an agent (or any command) under the harness:

actplane init                                  # write a starter actplane.yaml
actplane check                                 # validate rules (no privileges)

sudo -E actplane run claude -p "review this repo"

When a rule matches, ActPlane kills the action and tells the agent why:

🚫 KILLED: process 'git' (pid 4213, ppid 4210) — /usr/bin/git
   effect: kill
   reason: no git under the agent; use the review workflow

The agent receives this reason through its hook integration, understands the constraint, and takes a different path to complete the task.

Requirements: Linux kernel 5.8+ with BTF (/sys/kernel/btf/vmlinux). run and watch load the eBPF engine, so they need root (or CAP_BPF + CAP_SYS_ADMIN); ActPlane drops the target command back to your user. With BPF-LSM enabled, rules can block before the action commits; otherwise they notify (report) or kill.

Agent integration

ActPlane feeds rule-match reasons back to agents via their hook systems.

Claude Code (.claude/settings.local.json):

{
  "hooks": {
    "PostToolUse": [{ "matcher": "*", "hooks": [{ "type": "command", "command": "/path/to/actplane feedback-hook" }] }],
    "PostToolUseFailure": [{ "matcher": "*", "hooks": [{ "type": "command", "command": "/path/to/actplane feedback-hook" }] }]
  }
}

Codex (.codex/hooks.json):

{
  "hooks": {
    "PostToolUse": [{ "matcher": ".*", "hooks": [{ "type": "command", "command": "/path/to/actplane feedback-hook" }] }]
  }
}

The adapter forwards new rule matches as hook context. The kernel remains the sole authority for observation and enforcement. See script/CLAUDE.snippet.md for the agent instruction snippet.