Skip to content

agent_simulation: fix stale comments on how the dispatch and scenario tags reach the agent #1878

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
u9g merged 1 commit into from
Oct 20, 2026
Merged

agent_simulation: fix stale comments on how the dispatch and scenario tags reach the agent #1878

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions livekit/livekit_agent_simulation.pb.go
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

7 changes: 4 additions & 3 deletions protobufs/livekit_agent_simulation.proto
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -423,7 +423,7 @@ message Scenario {
string label = 1;
string instructions = 2;
string agent_expectations = 3;
// Set as participant attributes on the simulation participant's access token.
// Surfaced to the agent under test as SimulationContext scenario tags.
map<string, string> tags = 4;
// Arbitrary JSON-encoded object, surfaced to the agent under test as
// SimulationContext userdata (e.g. inputs and benchmark target state).
Expand Down Expand Up @@ -451,8 +451,9 @@ enum SimulationMode {
SIMULATION_MODE_AUDIO = 2;
}

// Carried (protojson-encoded) in the simulation room's metadata so the agent
// under test can read the scenario + run identity synchronously at connect.
// Carried (protojson-encoded) in the Job's lk.simulator.dispatch attribute, set
// on the agent dispatch, so the agent under test can read the scenario + run
// identity synchronously at job start.
message SimulationDispatch {
string simulation_run_id = 1;
string job_id = 2;
Expand Down
Loading