~/talk

You Can't Fix a Prompt You Can't See Fail

links:none on file
slides:none on file

Shows a concrete fix: wrap the planning step in an OpenTelemetry plan span that stores the list of tools, then run a separate answer check and a plan check. Demo sends spans to Jaeger demo and runs the release-helper five times (scripted) to show one case where the answer passes but the plan reads yesterday’s summary. A benchmark, the agent telemetry benchmark, finds standard logs catch 6 of 14 fault types while adding planning spans catches all 14. Recording the plan takes only a few lines and reliably tells whether to change prompt or fix a tool.

AI-written summary · about

  1. 0:00Intro
  2. 0:23About the Speaker
  3. 1:10Why Agent Prompts Are Hard to Debug
  4. 2:11The Release Helper Example
  5. 3:19Making the Plan Visible with Tracing
  6. 5:18Recording and Checking the Plan
  7. 7:12Demo: Five Runs in Jaeger
  8. 11:14Deciding What to Fix
  9. 13:11Getting Started and Wrap-Up
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.