intent, plan, findingsAgent-agnostic evidence layer for code review
Audit trails forAI-written codechanges.
When an agent changes code, reviewers need more than a diff. Agentplane keeps the task, approved plan, checks, traces, and Agent Change Record inside the repo.
Agent-agnostic. Local-first. No account required. MIT licensed.
Task intent, branch state, verification, and review packet stay in Git.
scope, checks, diffstatsteps, tools, checks$ npm i -g agentplane
$ agentplane init
$ agentplane demo
$ human reviews evidenceA diff is not enough to merge agent work.
A diff shows what changed. It does not show why the agent changed it, what scope was approved, what checks ran, or whether the result is ready for review.
Agentplane turns AI-written code changes into repo-local evidence: task intent, approved plan, verification, traces, commits, and Agent Change Records.
From uncertain diff to reviewable change.
Give reviewers a durable trail before asking them to trust an agent-authored pull request.
Before Agentplane
- The agent changed files, but the approved scope is buried in chat.
- Checks ran somewhere, but the result is not tied to the task.
- The reviewer sees a diff and has to infer intent.
After Agentplane
- The task README records intent, plan, owner, findings, and rollback.
- The ACR links changed files to verification evidence.
- The PR carries a review packet instead of a loose agent summary.
Try the review trail in a repo you control.
No account. No hosted dependency. Start locally, generate the evidence shape, then decide what to automate.
npm i -g agentplane
agentplane init
agentplane quickstart
agentplane demo
agentplane acr validate <task-id> --mode localAGENTS.md
.agentplane/WORKFLOW.md
.agentplane/tasks/<task-id>/README.md
.agentplane/tasks/<task-id>/acr.json
.agentplane/traces/<run-id>.jsonAGENTS.md
Repository policy gateway for coding agents.
.agentplane/WORKFLOW.md
Workflow and verification contract.
Task README
Task intent, lifecycle, plan, status, and handoff evidence.
acr.json
Machine-readable Agent Change Record for review and tooling.
Trace JSON
Inspectable run timeline and exportable trace data.
Recipes
Reusable workflow overlays for TDD, security review, and docs work.
Agent-agnostic by design.
Agentplane does not replace your model, coding agent, editor, or Git workflow. It gives any repository-capable agent the same harness boundary and evidence trail.
Agentplane is not another agent framework.
Agent frameworks define agent logic. Model providers run inference. Prompt tools shape instructions.
Agentplane coordinates the operational layer around coding-agent work: workflows, traces, context, recipes, verification, artifacts, and Git evidence.
Why harnesses matter
A model alone is not an agent. Real agents need workflows, tools, context, state, verification, and traces. Agentplane gives that surrounding harness a local, inspectable structure.
Read the harness engineering guideHow does Agentplane trace an agent run?
Traces turn workflow execution into a structured timeline that can be inspected or exported.
workflow.startrun begins from a declared workflowcontext.loadrepository rules and workflow statemodel.callmodel interaction metadatatool.callexternal action with input/output metadataverification.checktests, typecheck, lint, or custom validationtrace.exportJSON or OpenTelemetry-compatible artifactExamples and recipes
Start from runnable workflows: trace debugging, TDD recipes, local context, and Agent Change Records.
Who should open the repo?
- using agentic coding tools in real repositories
- reviewing AI-written pull requests and missing intent, plan, and check evidence
- maintaining an OSS project where agent changes need audit trails
- building platform workflows around reproducible AI-agent work
- tired of agent demos that disappear after the chat session
Make the next AI-written change reviewable.
Run the quickstart, inspect the generated evidence, then decide where Agentplane belongs in your agent workflow.