← All speakers

Susheem Koul is a senior software engineer at Microsoft and a co-creator of AgentPlane, an open-source initiative building practical infrastructure for AI agents. With Tisha Chawla, he develops tools that make agent failures reproducible and impose enforceable spending limits on autonomous workflows.

Koul studied at Birla Institute of Technology and Science, Pilani, from 2015 to 2019. His earlier technical writing examined Git and version-control architecture; more recently, he has concentrated on the reliability, evaluation, and operating costs of systems that place probabilistic models in charge of consequential decisions.

At AI Engineer World’s Fair 2026, Koul and Chawla illustrated the problem with a trading agent that mistakes a requested dollar amount for a number of shares. The resulting order succeeds technically while producing the wrong outcome, leaving conventional infrastructure monitoring blind to the failure. Their conference presentation introduced a more useful operational distinction: engineers need replayable agent executions, not impossible guarantees that hosted models will always produce identical outputs.

  • Chronicle: production incidents as regression tests. Chronicle records inputs, outputs, and runtime metadata around model calls, retrieval, and tools. Developers can replay a failed execution, substitute recorded model responses, rerun a modified guardrail, and verify that the original mistake is blocked.
  • TokenOps: run-level token governance. TokenOps tracks spending across collaborating agents, tools, and model calls through a shared ledger and control plane. Its policies can intervene before a workflow makes another expensive request.

Read the topics behind these talks

2 conference talks

Key ideas

Scroll to read ↓

A successful API call can still execute the wrong trade. Recording agent boundaries turns an otherwise elusive failure into a repeatable test of the code that must stop it.

  • The production failure that disappears locally
    0:00 ↗
  • Temperature zero does not freeze the serving system
    2:26 ↗
  • Recover the run instead of regenerating it
    4:51 ↗
  • Record semantic boundaries
    6:14 ↗
  • Find where dollars became shares
    8:05 ↗
  • Replay the bad decision against the repaired tool
    9:56 ↗
  • Test enforcement and behavior separately
    12:08 ↗
  • Keep the execution envelope as a test case
    13:14 ↗

Key ideas

Scroll to read ↓

Tisha Chawla and Susheem Koul explain how TokenOps attributes spending to agent runs, applies shared budgets, and changes execution before a hard cap has to stop the work.

  • Attribute model consumption to agent runs and usage dimensions so policies can act on the workflow responsible for spending.
    4:17 ↗
  • TokenOps uses a boundary annotation for observations and action delivery, while a governor applies only developer-allowed changes.
    11:55 ↗
  • Preview mode evaluates policies without enforcing them, allowing thresholds and guardrails to be adjusted before they change live execution.
    16:24 ↗
  • A hard cap stops work; the cost guard uses consumed budget and consumption velocity to request shorter future outputs before predicted exhaustion.
    17:24 ↗
  • The companion article reports 78.9% lower mean cost per completed run and within-cap success rising from 18/27 to 26/27 versus no governance. The recording instead names throttling as the completion baseline, so the comparison remains unresolved.
    18:24 ↗
  • The proposed learning module would use ledger records to discover missed failure modes, generate policies, and refine existing parameters.
    19:55 ↗

References