Agent Result Schema Design with Claude Code: Cost Controls
A production playbook for agent result schema design in cross-industry operations using Claude Code: cost controls, run-scoped inputs, logs, typed results, and artifacts.
Audience: Backend engineers productizing agents
The problem
Backend engineers productizing agents need agent result schema design to run repeatedly against expected product events, downstream schemas, and examples. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Set explicit limits for agent result schema design: input size, run time, tool calls, artifacts, retries, and concurrent runs per organization.
Tradeoffs and failure modes
Limits reject pathological runs, but they keep one workflow from turning into an unbounded infrastructure bill. For agent result schema design, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Run limits
max_run_seconds=1800
max_input_bytes=104857600
max_artifact_bytes=104857600
max_tool_calls=120
retry_after_seconds=60
Run this on Argo