Skip to main content
Use this recipe when one workflow should:
  • inspect code-related context with local runtime tools
  • return strict structured output instead of free-form prose
  • pause high-risk decisions for human approval
  • checkpoint progress between model turns and tool calls

1. Define one narrow output contract

This keeps the first coding workflow inspectable in logs and easy to pass to downstream worker steps.

2. Define small runtime tools

Keep these tools deterministic and idempotent so the checkpointed step data stays useful if a worker resumes later.

3. Create the agent with a human-review seam

4. Use the gateway-backed adapter for strict JSON

5. Run and resume the workflow

6. What to verify

After one run with tools and one run that pauses for approval, confirm:
  • request detail views show the runtime tool loop clearly
  • paused runs enter waiting_for_human
  • step records checkpoint after tool execution
  • schema failures or plugin-healing activity stay visible in logs
Last modified on July 26, 2026