Run a plan

version: 2
identifier: changes_since
name: Changes since
description: The commits merged since a git ref.
input_schema:
  type: object
  required:
  - base
  properties:
    base:
      type: string
      description: The ref to start after, such as a release tag
steps:
- id: commits
  tool_name: github__tool__git_log
  input:
    base: '{{input.base}}'
    head: HEAD
finish:
  output:
    count: '{{commits.count}}'
    commits: '{{commits.commits}}'

version: 2
identifier: changes_since
name: Changes since
description: The commits merged since a git ref.
input_schema:
  type: object
  required:
  - base
  properties:
    base:
      type: string
      description: The ref to start after, such as a release tag
steps:
- id: commits
  tool_name: github__tool__git_log
  input:
    base: '{{input.base}}'
    head: HEAD
finish:
  output:
    count: '{{commits.count}}'
    commits: '{{commits.commits}}'

changes_since takes a git ref as its base input and returns the commits merged since it.

version: 2
identifier: changes_since
name: Changes since
description: The commits merged since a git ref.
input_schema:
  type: object
  required:
  - base
  properties:
    base:
      type: string
      description: The ref to start after, such as a release tag
steps:
- id: commits
  tool_name: github__tool__git_log
  input:
    base: '{{input.base}}'
    head: HEAD
finish:
  output:
    count: '{{commits.count}}'
    commits: '{{commits.commits}}'

See what it needs

Run changes_since without inputs:

graph plan run changes_since

graph checks the inputs before any step runs. It names what’s missing, prints the input schema, and exits with code 3:

plan 'changes_since' needs inputs:
  - "base" is a required property
input schema:
{
  "properties": {
    "base": {
      "description": "The ref to start after, such as a release tag",
      "type": "string"
    }
  },
  …
}

Pass the input

Set base with --input:

graph plan run changes_since \
  --input base=v0.15.0

The plan prints its result as JSON on stdout:

{
  "commits": [
    {
      "author": "Tyler Davis",
      "date": "2026-10-08T19:39:09-06:00",
      "pr": null,
      "sha": "648d34e22ede0d8c246576493b39487237272607",
      "short_sha": "648d34e",
      "subject": "feat!: plans state how they finish with a required finish key…"
    },
    …
  ],
  "count": 28
}

Pipe the result into jq

Progress goes to stderr, so stdout carries only the result and pipes cleanly:

graph plan run changes_since \
  --input base=v0.15.0 \
  | jq -r '.commits[] | "\(.short_sha) \(.subject)"'

648d34e feat!: plans state how they finish with a required finish key…
cd01c05 feat!: workbench agents work on plans through the same artifact tools…
1a8443c ci: a planner eval harness with goal sets, reference plans and a judge…
…

Handle failures

Tell why a run failed and choose how to respond.

Debug a plan

Step through a run in the workbench.

Draft a plan in the workbench

Turn a goal into a working, saved plan.

Getting started

Agents

Plans

Tools

Packs

Integrating

Reference

See what it needs

Pass the input

Pipe the result into jq

Handle failures

Debug a plan

Draft a plan in the workbench

​See what it needs

​Pass the input

​Pipe the result into jq

​Related guides

Handle failures

Debug a plan

Draft a plan in the workbench

See what it needs

Pass the input

Pipe the result into jq

Related guides