Agent tracing captures request timing, token counts, worker placement, finish metadata, and replay hashes for eligible LLM requests. Requests with session identity also carry agent context, which lets analysis tools group LLM turns and tool activity into the same run.
Agent "thunderagent-program-scheduler" from ai-dynamo/dynamo, covering the problem, the scheduler, scheduler tick, tool-boundary pause/resume semantics and program lifetime.
How one stored agent source becomes the effective (resolved) source that is actually compiled and executed. Resolution expands FROM (inheritance) and IMPORT (textual inclusion) commitments, rewrites compact agent references into canonical URLs, and degrades gracefully when references cannot be loaded.
Compiling an agent (resolving inheritance, building model requirements, indexing KNOWLEDGE into provider-side vector stores) is expensive. The server therefore prepares agents in the background ahead of chat time and caches every derived artifact by content hash, so the first user message does not pay the indexing…
How agents move between servers and how a server's state is exported. Everything is book-centric: because a book is the single source of truth for an agent's behavior, plain .book files are the portable format.
Use to autonomously optimize a model's AMK megakernel, runs the correctness-gated propose->eval->keep/revert loop (and the unattended autoresearch driver) and reports the measured, drift-robust speedup over AMK's own baseline.
Senior Architect reviewer. Reviews plans and diffs for simplicity, duplication, encapsulation and abstraction. Read-only — never edits code. Use before opening a PR, or when a design decision needs a second opinion.