Agent filter

An agent decides pass or fail for each record, and the reason lands in the ledger.

Connector	`agent/filter`
Role	filter
Records	any type
Tier	built in
Credential	none
Cost	unset in the manifest; `gtme plan` prints what the step declares at run time
Source	internal/adapters

Use it

It ships inside the binary. In a pipeline file:

steps:
  - id: filter
    use: agent/filter

gtme plan pipeline.yaml checks the credential is set and that every field this step needs is provided by a step before it, without calling anyone.

Needs

Whatever fields the step's uses: line names. The runner checks them at plan time.

Provides

The fields the step's provides: line declares.

Config

Key	Type	What it does
`template`	string	What the participant is shown per record (ADR-057): a template over record.* (the uses:/of: fields) and config.*, in place of the field listing. The runner loads {file:} before validation.
`render`	object	What the participant is shown per record (ADR-049): the listed fields, or the step's template: (ADR-057)
`prompt`	never	tty (default): at a terminal, `gtme run` walks the records and asks; never: every record waits in the ledger for `gtme answer` (ADR-049). The mode, never text — the text is template: (ADR-057)

On this page, connector means what gtme calls an adapter. This one is a process adapter compiled into the binary. Two adapter tiers explains the difference.