title	Plugins
description	Every shipped plugin — what it mounts, what it contributes, and every setting it declares.
group	Reference
order	2

Plugin reference

Everything on this page is read out of the plugins themselves: each one is registered against a registry that only takes notes, and its declared config schema is read from the built package. Nothing here is a list somebody maintains.

Every shipped plugin

Plugin	What it is	Mounts	Contributes
`@amykit/plugin-agent-relay`	One agent made of several: swaps harness on a quota, escalates model on a failure.	`agent`
`@amykit/plugin-claude`	The claude CLI as the agent, with git on the side.		`agent:claude` `harness:claude`
`@amykit/plugin-codex`	The codex CLI as the agent, over its JSONL event stream.		`agent:codex` `harness:codex`
`@amykit/plugin-command`	Any command line tool, reached by a name the config allows.	`commands`
`@amykit/plugin-command-gate`	A gate that runs the target repository's own commands.	`gate`
`@amykit/plugin-file-notes`	Friction as a directory of notes: written by hand, by a hook, or by a tick that failed.	`notes`
`@amykit/plugin-file-queue`	A queue kept as one file per item, claimed by rename.	`queue`
`@amykit/plugin-file-store`	Work records kept as one file per item.	`store`
`@amykit/plugin-file-tasks`	Tasks as a directory of files: written by `amy btw`, by an editor, or by a hook.	`tasks`
`@amykit/plugin-github`	GitHub as the code host, through the gh CLI.	`code-host`
`@amykit/plugin-hermes-agent`	Hermes as the agent, over its one-shot mode and usage report.		`agent:hermes` `harness:hermes`
`@amykit/plugin-linear`	Linear as the tracker, over its GraphQL API.	`tracker`	`notify-channel:tracker`
`@amykit/plugin-notify-fanout`	Sends one announcement down every configured channel, and keeps going when one is down.	`notifier`
`@amykit/plugin-notify-hermes`	Announcements over Hermes, which already owns the messaging credentials.		`notify-channel:hermes`
`@amykit/plugin-notify-inbox`	Announcements as a file on disk plus a desktop notification.		`notify-channel:inbox`
`@amykit/plugin-plan-check`	The quality bar for a drafted plan: the repository's own check, run in its checkout.	`plan-check`
`@amykit/plugin-serial-engine`	Advances one work item by one move per tick.	the engine

Settings, plugin by plugin

Every field below is validated at boot. A key that is not one a plugin declared is a refusal naming the plugin and the key — see Plugins and the registry.

`@amykit/plugin-agent-relay`

One agent made of several: swaps harness on a quota, escalates model on a failure.


Source	`plugins/agent-relay`
Mounts	`agent`
Contributes	nothing
Needs in the environment	nothing
Depends on	`@amykit/agent-kit`, `@amykit/core`, `@amykit/workflow-ticket-to-qa`

plugins:
  "@amykit/plugin-agent-relay":
    budget: {}
    ladder: []
    ladderByStep: {}
    skillRoots: []
    skills: {}

Setting	Type	Required	Default	What it is
`budget`	`record`	no	`{}`	what the agents may spend, per window: perFiveHours and perWeek, each with tokens and/or costUsd, plus stopAt, the fraction of a ceiling at which new work stops being started
`ladder`	`string[]`	no	`[]`	the contributed agents to try, in order, such as [claude:sonnet, claude:opus, codex:gpt-5]. Empty means every contributed agent, in the order the plugins were mounted
`ladderByStep`	`record`	no	`{}`	a ladder for one step, overriding the one above, keyed by the workflow's action name: {"triage": ["claude:haiku"], "implement": ["claude:opus"]}. Reading a ticket and writing the change are not the same job, and one list for both means paying the expensive model to do the cheap step
`skillRoots`	`string[]`	no	`[]`	where installed skills are looked for. Empty means ~/.claude/skills, which is where the harness looks
`skills`	`record`	no	`{}`	which skills answer for a step, in the order they are tried, keyed by the workflow's action name: {"triage": ["/logion"]}. A skill named here must be installed, or the mount is refused

`@amykit/plugin-claude`

The claude CLI as the agent, with git on the side.


Source	`plugins/claude`
Mounts	nothing
Contributes	`agent:claude`, `harness:claude`
Needs in the environment	nothing
Depends on	`@amykit/agent-kit`, `@amykit/core`, `@amykit/model-specs`

plugins:
  "@amykit/plugin-claude":
    defaultBranch: main
    model: ""
    models: []
    reviewerHints: {}
    timeoutMs: 1800000

Setting	Type	Required	Default	What it is
`defaultBranch`	`string`	no	`main`	the branch new work is cut from, which is not always `main`
`model`	`string`	no	`""`	passed to the CLI as --model, which is the flag it accepts
`models`	`string[]`	no	`[]`	the model tiers to offer the relay, cheapest first. One agent is contributed per tier, named `claude:<model>`. Empty means a single agent using `model`
`reviewerHints`	`record`	no	`{}`	guidance appended when answering a particular reviewer, by host login
`timeoutMs`	`number`	no	`1800000`	how long one agent call may run before it is given up on

`@amykit/plugin-codex`

The codex CLI as the agent, over its JSONL event stream.


Source	`plugins/codex`
Mounts	nothing
Contributes	`agent:codex`, `harness:codex`
Needs in the environment	nothing
Depends on	`@amykit/agent-kit`, `@amykit/core`, `@amykit/model-specs`

plugins:
  "@amykit/plugin-codex":
    defaultBranch: main
    model: ""
    models: []
    reviewerHints: {}
    timeoutMs: 1800000

Setting	Type	Required	Default	What it is
`defaultBranch`	`string`	no	`main`	the branch new work is cut from, which is not always `main`
`model`	`string`	no	`""`	passed to the CLI as --model. Empty leaves the choice to codex
`models`	`string[]`	no	`[]`	the model tiers to offer the relay, cheapest first. One agent is contributed per tier, named `codex:<model>`. Empty means a single agent named `codex`
`reviewerHints`	`record`	no	`{}`	guidance appended when answering a particular reviewer, by host login
`timeoutMs`	`number`	no	`1800000`	how long one agent call may run before it is given up on

`@amykit/plugin-command`

Any command line tool, reached by a name the config allows.


Source	`plugins/command`
Mounts	`commands`
Contributes	nothing
Needs in the environment	nothing
Depends on	`@amykit/core`

plugins:
  "@amykit/plugin-command":
    allow: {}
    cwd: ""
    timeoutMs: 300000

Setting	Type	Required	Default	What it is
`allow`	`record`	yes		the commands a workflow may run, by name. The name is what a workflow asks for; the value is the command line it stands for, and this is the only place one is written
`cwd`	`string`	no	`""`	where a command runs when it does not say, defaulting to the state directory
`timeoutMs`	`number`	no	`300000`	how long one command may run before it is given up on

`@amykit/plugin-command-gate`

A gate that runs the target repository's own commands.


Source	`plugins/command-gate`
Mounts	`gate`
Contributes	nothing
Needs in the environment	nothing
Depends on	`@amykit/core`, `@amykit/workflow-ticket-to-qa`

plugins:
  "@amykit/plugin-command-gate":
    commands: {}
    defaultBranch: main
    timeoutMs: 1800000

Setting	Type	Required	Default	What it is
`commands`	`record`	yes		the check commands per repository, with a `default` fallback
`defaultBranch`	`string`	no	`main`	the branch new work is cut from, which is not always `main`
`timeoutMs`	`number`	no	`1800000`	how long one check may run before it is given up on

`@amykit/plugin-file-notes`

Friction as a directory of notes: written by hand, by a hook, or by a tick that failed.


Source	`plugins/file-notes`
Mounts	`notes`
Contributes	nothing
Needs in the environment	nothing
Depends on	`@amykit/core`, `@amykit/plugin-notify-fanout`

plugins:
  "@amykit/plugin-file-notes":
    directory: notes
    repo: ""
    writeFailureNotes: true

Setting	Type	Required	Default	What it is
`directory`	`string`	no	`notes`	where the notes are watched for, relative to the state directory
`repo`	`string`	no	`""`	the repository a note is about when it does not say, which is also the one this machine's own failures are filed against
`writeFailureNotes`	`boolean`	no	`true`	whether a tick this machine gave up on leaves a note behind, so the thing that broke becomes the thing that gets fixed

`@amykit/plugin-file-queue`

A queue kept as one file per item, claimed by rename.


Source	`plugins/file-queue`
Mounts	`queue`
Contributes	nothing
Needs in the environment	nothing
Depends on	`@amykit/core`

plugins:
  "@amykit/plugin-file-queue":
    directory: queue
    retentionDays: 7
    staleClaimMs: 1800000

Setting	Type	Required	Default	What it is
`directory`	`string`	no	`queue`	where the queue is kept, relative to the state directory. One per workflow, so two profiles under one `.amy` do not claim each other's work
`retentionDays`	`number`	no	`7`	how long a finished queue item is kept before it is pruned
`staleClaimMs`	`number`	no	`1800000`	how long a claimed item may sit before it counts as abandoned

`@amykit/plugin-file-store`

Work records kept as one file per item.


Source	`plugins/file-store`
Mounts	`store`
Contributes	nothing
Needs in the environment	nothing
Depends on	`@amykit/core`

plugins:
  "@amykit/plugin-file-store":
    directory: tickets

Setting	Type	Required	Default	What it is
`directory`	`string`	no	`tickets`	where the records are kept, relative to the state directory. One per workflow, so two profiles under one `.amy` do not read each other's work

`@amykit/plugin-file-tasks`

Tasks as a directory of files: written by amy btw, by an editor, or by a hook.


Source	`plugins/file-tasks`
Mounts	`tasks`
Contributes	nothing
Needs in the environment	nothing
Depends on	`@amykit/core`

plugins:
  "@amykit/plugin-file-tasks":
    directory: tasks
    repo: ""

Setting	Type	Required	Default	What it is
`directory`	`string`	no	`tasks`	where the tasks are kept, relative to the state directory
`repo`	`string`	no	`""`	what a task is about when it does not say

`@amykit/plugin-github`

GitHub as the code host, through the gh CLI.


Source	`plugins/github`
Mounts	`code-host`
Contributes	nothing
Needs in the environment	nothing
Depends on	`@amykit/core`

This plugin declares no settings, so the config must not give it any.

`@amykit/plugin-hermes-agent`

Hermes as the agent, over its one-shot mode and usage report.


Source	`plugins/hermes-agent`
Mounts	nothing
Contributes	`agent:hermes`, `harness:hermes`
Needs in the environment	nothing
Depends on	`@amykit/agent-kit`, `@amykit/core`, `@amykit/model-specs`

plugins:
  "@amykit/plugin-hermes-agent":
    defaultBranch: main
    model: ""
    models: []
    reviewerHints: {}
    timeoutMs: 1800000

Setting	Type	Required	Default	What it is
`defaultBranch`	`string`	no	`main`	the branch new work is cut from, which is not always `main`
`model`	`string`	no	`""`	passed to the CLI as --model. Empty leaves the choice to hermes
`models`	`string[]`	no	`[]`	the model tiers to offer the relay, cheapest first. One agent is contributed per tier, named `hermes:<model>`. Empty means a single agent named `hermes`
`reviewerHints`	`record`	no	`{}`	guidance appended when answering a particular reviewer, by host login
`timeoutMs`	`number`	no	`1800000`	how long one agent call may run before it is given up on

`@amykit/plugin-linear`

Linear as the tracker, over its GraphQL API.


Source	`plugins/linear`
Mounts	`tracker`
Contributes	`notify-channel:tracker`
Needs in the environment	`LINEAR_API_KEY`
Depends on	`@amykit/core`, `@amykit/plugin-notify-fanout`, `@amykit/workflow-ticket-to-qa`

plugins:
  "@amykit/plugin-linear":
    defaultRepo: ""
    endpoint: https://api.linear.app/graphql
    repoByTeam: {}
    workingStatusName: …

Setting	Type	Required	Default	What it is
`defaultRepo`	`string`	no	`""`	the repository used for a team that is not in repoByTeam
`endpoint`	`string`	no	`https://api.linear.app/graphql`	the GraphQL endpoint to talk to. Linear's own by default, and the one thing that has to move for a stand-in tracker to take its place in an end-to-end run
`repoByTeam`	`record`	no	`{}`	which repository a team's tickets land in, by team key
`workingStatusName`	`string`	yes		the exact status name a ticket must be in to be picked up

`@amykit/plugin-notify-fanout`

Sends one announcement down every configured channel, and keeps going when one is down.


Source	`plugins/notify-fanout`
Mounts	`notifier`
Contributes	nothing
Needs in the environment	nothing
Depends on	`@amykit/core`

This plugin declares no settings, so the config must not give it any.

`@amykit/plugin-notify-hermes`

Announcements over Hermes, which already owns the messaging credentials.


Source	`plugins/notify-hermes`
Mounts	nothing
Contributes	`notify-channel:hermes`
Needs in the environment	nothing
Depends on	`@amykit/core`, `@amykit/plugin-notify-fanout`

plugins:
  "@amykit/plugin-notify-hermes":
    target: …

Setting	Type	Required	Default	What it is
`target`	`string`	yes		a Hermes delivery target, such as `slack:my-channel` or a bare platform name for its home channel

`@amykit/plugin-notify-inbox`

Announcements as a file on disk plus a desktop notification.


Source	`plugins/notify-inbox`
Mounts	nothing
Contributes	`notify-channel:inbox`
Needs in the environment	nothing
Depends on	`@amykit/core`, `@amykit/plugin-notify-fanout`

plugins:
  "@amykit/plugin-notify-inbox":
    directory: needs-input

Setting	Type	Required	Default	What it is
`directory`	`string`	no	`needs-input`	where the questions are left, relative to the workspace

`@amykit/plugin-plan-check`

The quality bar for a drafted plan: the repository's own check, run in its checkout.


Source	`plugins/plan-check`
Mounts	`plan-check`
Contributes	nothing
Needs in the environment	nothing
Depends on	`@amykit/core`, `@amykit/workflow-note-to-plan`

plugins:
  "@amykit/plugin-plan-check":
    commands: 
      default:
        - sf check
    defaultBranch: main
    timeoutMs: 600000

Setting	Type	Required	Default	What it is
`commands`	`record`	no	`{"default":["sf check"]}`	the check commands per repository, with a `default` fallback. `sf check` is the whole quality bar in a repository that has one
`defaultBranch`	`string`	no	`main`	the branch a plan branch is cut from, which is not always `main`
`timeoutMs`	`number`	no	`600000`	how long one check may run before it is given up on

`@amykit/plugin-serial-engine`

Advances one work item by one move per tick.


Source	`plugins/serial-engine`
Mounts	the engine
Contributes	nothing
Needs in the environment	nothing
Depends on	`@amykit/core`, `@amykit/workflow-ticket-to-qa`

plugins:
  "@amykit/plugin-serial-engine":
    maxItemAttempts: 5
    retentionDays: 7
    retryDelayMs: 300000
    staleClaimMs: 1800000

Setting	Type	Required	Default	What it is
`maxItemAttempts`	`number`	no	`5`	how many times one item may fail before the operator is told and it is dropped
`retentionDays`	`number`	no	`7`	how long a finished queue item is kept before it is pruned
`retryDelayMs`	`number`	no	`300000`	how long a failed item is held before it is looked at again
`staleClaimMs`	`number`	no	`1800000`	how long a claimed item may sit before it counts as abandoned

Collections

Collection	Contributed to by	Read by
`agent`	`claude` — `@amykit/plugin-claude` `codex` — `@amykit/plugin-codex` `hermes` — `@amykit/plugin-hermes-agent`	`@amykit/agent-kit`
`harness`	`claude` — `@amykit/plugin-claude` `codex` — `@amykit/plugin-codex` `hermes` — `@amykit/plugin-hermes-agent`	`@amykit/agent-kit`
`notify-channel`	`hermes` — `@amykit/plugin-notify-hermes` `inbox` — `@amykit/plugin-notify-inbox` `tracker` — `@amykit/plugin-linear`	whichever plugin reads it
`workflow-runtime`	`errand` — `@amykit/workflow-errand` `note-to-plan` — `@amykit/workflow-note-to-plan` `ticket-to-qa` — `@amykit/workflow-ticket-to-qa`	`@amykit/agent-kit`

FilesExpand file tree

plugins.md

Latest commit

History

plugins.md

File metadata and controls

Plugin reference

Every shipped plugin

Settings, plugin by plugin

@amykit/plugin-agent-relay

@amykit/plugin-claude

@amykit/plugin-codex

@amykit/plugin-command

@amykit/plugin-command-gate

@amykit/plugin-file-notes

@amykit/plugin-file-queue

@amykit/plugin-file-store

@amykit/plugin-file-tasks

@amykit/plugin-github

@amykit/plugin-hermes-agent

@amykit/plugin-linear

@amykit/plugin-notify-fanout

@amykit/plugin-notify-hermes

@amykit/plugin-notify-inbox

@amykit/plugin-plan-check

@amykit/plugin-serial-engine