From 7f5908e77ae0e7fef4b7901341b8c2c4bbb74b28 Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Thu, 15 Jan 2026 20:53:57 +0100 Subject: pkg/aflow: make LLM model per-agent rather than per-flow Having LLM model per-agent is even more flexible than per-flow. We can have some more complex tasks during patch generation with the most elaborate model, but also some simpler ones with less elaborate models. --- pkg/aflow/trajectory/trajectory.go | 1 + 1 file changed, 1 insertion(+) (limited to 'pkg/aflow/trajectory') diff --git a/pkg/aflow/trajectory/trajectory.go b/pkg/aflow/trajectory/trajectory.go index 49e36933b..aa9558708 100644 --- a/pkg/aflow/trajectory/trajectory.go +++ b/pkg/aflow/trajectory/trajectory.go @@ -20,6 +20,7 @@ type Span struct { Nesting int Type SpanType Name string // flow/action/tool name + Model string // LLM model name for agent/LLM spans Started time.Time Finished time.Time Error string // relevant if Finished is set -- cgit mrf-deployment