Batch
There is no batch() method in the SDK. When a host workflow or agent turn has a
clear list of independent, deterministic steps, compose them directly from the
session's deterministic helpers (readFile, grep, glob, ls, git) and
aggregate the results yourself. That keeps the "batch" fully under your control:
no model calls, explicit ordering, and no destructive operations unless you
invoke them.
The example below reads package metadata, the changelog, and the release script, then reports version mismatches without editing any files.
Do not mix destructive operations into these grouped reads. Any destructive host
workflow (writes, git commits, bash) should sit behind explicit application
confirmation or your automation gates, constrained with permissionPolicy /
permission_policy so no unexpected step runs silently.
When the steps are not independent — each one depends on the previous result
and you want an agent to drive them — use
session.pipeline(...) instead, which runs
the work in stages where each stage receives the prior stage's output.