[google/syzkaller] b2988c: aflow: show tool names in trajectory tooltips

[Alexander Potapenko]

Branch: refs/heads/gh-readonly-queue/master/pr-7215-ff940bdf86508c3bfe1232795722ed01d7249dac
Home: https://github.com/google/syzkaller
Commit: b2988c170875122bc250b755f3cfcd730933eb8c
https://github.com/google/syzkaller/commit/b2988c170875122bc250b755f3cfcd730933eb8c
Author: Alexander Potapenko <gli...@google.com>
Date: 2026-05-08 (Fri, 08 May 2026)

Changed paths:
M pkg/aflow/trajectory/html/trajectory.go
M pkg/aflow/trajectory/html/trajectory_block.html
A pkg/aflow/trajectory/html/trajectory_test.go

Log Message:
-----------
aflow: show tool names in trajectory tooltips

Include the names of the tools called by LLM agents in the tooltips of
the aflow trajectory charts (both Duration and Token Consumption charts).

The tool calls are inferred on the fly during HTML rendering in Go backend
post-processing.

We introduce a nesting-aware PopulateToolCalls helper in the html package.
It analyzes the flat sequence of spans, groups tool calls by their Nesting
level, and associates them with the subsequent LLM call at the same nesting
level. This prevents incorrect associations in complex trajectories with
nested sub-agents.

Both RenderReport (CLI) and RenderTrajectory (Dashboard) call this helper
internally. This automatically enables tooltips for both CLI runs and the
web dashboard with zero changes to dashboard/app code.

We also add a comprehensive Go unit test suite (trajectory_test.go) to
verify the inference logic under various scenarios (basic flow, multiple
tools, and nested sub-agents), ensuring the logic is type-safe, compiled,
and fully tested.



To unsubscribe from these emails, change your notification settings at https://github.com/google/syzkaller/settings/notifications

[Alexander Potapenko]

Branch: refs/heads/master