DocsExamplesCompareQuickstart
npm i -g agentplaneGitHub

A workflow CLI for coding agents

Less workflow to track.
More focus on the code.

AGENTS.md sets repository guardrails. The Agentplane CLI tracks task state, enforces approval boundaries, and gives your coding agent one bounded action at a time. Review observed changes and check results in Git.

Follow the quickstart

Agent-agnostic · Local-first · No account required · MIT licensed

Authority, in writing.
Changes you can inspect.
acme / web-app main
acr.json
{
"acr_version": "0.1.0",
"record_type": "agent_change_record",
"record_id": "acr_202609231539-BY7E3D",
"task": {
"task_id": "202609231539-BY7E3D",
"title": "Redesign the Agentplane homepage"
},
"changes": {
"summary": "Updated the homepage artifact explorer",
"diff_stats": { "files_changed": 2 }
},
"verification": {
"status": "passed"
},
"result": {
"status": "verified"
}
}
AuthorityRepository rules and task-specific scope
ObservedRepository changes observed independently
VerifiedRequired checks run and recorded
RecordedTask evidence retained in Git

04 / CHANGE RECORDAn ACR links the task, changes, verification, and result.

Record the outcome.
AuthorityRepository rules and task-specific scope
ObservedRepository changes observed independently
VerifiedRequired checks run and recorded
RecordedTask evidence retained in Git

One job at a time

The agent sees the next job. The CLI keeps the state.

A compact WorkOrder gives the agent the objective, scope, and context it needs. The CLI tracks the rest of the workflow, so the agent can focus on the code.

Repository rules

AGENTS.md gives the agent its guardrails and command contract.

Bounded handoff

The CLI returns the next objective, permitted scope, expected result, and stop rules.

Reviewable outcome

Observed changes and check results stay in the repository after the session ends.

Beyond the diff

A diff shows the change. The task record shows its boundaries.

See the approved scope, observed paths, and required check results together, without reconstructing the task from chat logs.

src/parser/lexer.ts+2 −1
42 function tokenize(input: string) {43 const tokens = [];44 let i = 0;45 - if (ch === "-") {46 + if (ch === "-") {47 + tokens.push(ch);48 return tokens;
Missing context

This diff alone shows no approved scope, approver, or check result.

The control loop

The CLI carries the process. The agent handles the problem.

After approval, Agentplane supplies one bounded WorkOrder at a time, observes the repository result, runs required checks, and records the outcome.

The agent receives the approved scope.Set the objective, writable paths, and required checks.AgentWorkOrder v2

The review trail

Inspect the task behind the diff.

This illustrative task shows the approved scope, changed paths, check results, and task files a reviewer can inspect after the agent session ends.

acme / web-appb1e9d4fagentplane: fix parser edge case
verified
  • README.md
  • observations.jsonl
  • acr.json
  • evidence/manifest.json
Authority
bounded WorkOrder
Scope
src/parser/**
Observed
3 paths changed
Verification
unit, lint, types passed
When you create an evidence bundle, verify its hashes and review the ACR with Git tooling.

Checking Agentplane itself

We test the guardrails, too.

A bounded Quint model explores a critical Task Kernel rule: a replayed effect must not gain a fresh right to dispatch. TLC checks the finite state space, and trace tests exercise the matching TypeScript paths.

Safety rule / effect ownershipTask Kernel
Record intent before dispatch. Replays cannot own the effect again.
  1. Model

    Quint describes the rule

  2. Explore

    TLC checks bounded states

  3. Match code

    Trace tests exercise TypeScript

A focused effect-ownership pilot, run during development and outside your agent's task.

Keep your tools

Use the coding agent you already trust.

Keep your model, editor, and CI. Agentplane adds a consistent task boundary and review trail around the agent's work.

CodexClaude CodeCursorHermesAny repository-capable agent
Explore runnable examples

Choose the route

Choose how each task moves to review.

Work in the current checkout for a focused change, or use an isolated worktree and PR. Both routes keep task state and check results in the repository.

01 / LOCAL LOOP

direct

Make a focused change in the current checkout. Review its task record and required checks before closing.

  • Fast iteration in your environment
  • Full control and visibility
  • The same verification record
02 / REVIEW ROUTE

branch_pr

Use an isolated worktree and a PR for changes that need a formal review and integration path.

  • Isolated changes in a branch
  • Review and discuss like normal
  • Evidence included with the PR
Explore the workflow

What to read next

Choose the next step for your repository.

Getting startedRun your first taskWorkflow modelSee how control worksReferenceInspect the ACRDeveloper trackExplore runnable examplesSupportCompare approaches

Start locally

Try Agentplane on one task in your repository.

Set the scope, hand the next bounded action to your agent, and inspect the result in Git.

Run quickstart Inspect an Agent Change Record