Skip to content

[wip] Add manager agent#3

Open
vsoch wants to merge 16 commits intomainfrom
add-manager-agent
Open

[wip] Add manager agent#3
vsoch wants to merge 16 commits intomainfrom
add-manager-agent

Conversation

@vsoch
Copy link
Member

@vsoch vsoch commented Feb 15, 2026

TODO:

  • design a set of tools that allow for easy query (save, retrieve, query) of a general result. The use case is that we want to allow agents to save along the way.
  • create logic in the state machine for recording the plan (already done) and the transitions and counts. We want to be able to go back and understand how a graph was traversed.
  • create an optimization agent (sub-agent) that is given a task to optimize a specific metric. They are given a most recent result, instructed to use tools to look up previous results that are similar, and then asked for an explicit decision to retry or stop. If retry is requested, an updated spec must be given (and we need to have the state machine return to the step that did the run to process everything again).

For the last point, we can eventually have tool calls be to different algorithms or models that the optimization agent can use to make the decision. We can imagine then that the agent is given the task to optimize, sees the tools available, and then does queries to prepare whatever inputs are needed for the algorithns, calls, and gets the decision. I thought through different designs for this today, from a very uncontrolled "here is the entire state machine graph, what can we do better?" to this more controlled design, and I think to start the controlled design makes more sense. The reason is that we want to have the agent do what it is best at - taking different sources of information and tools to make a deicison about what to do next (which is retry/stop and a new thing to try) but we don't want to give it so much unbounded control that it goes off the rails and can try almost anything (and not be able to focus on a specific task).

Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
…n plan

Signed-off-by: vsoch <vsoch@users.noreply.github.com>
I need to stop before I REALLY bork something.

Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
The tool responses are a bit different - there seem to be a label
thing that needs better parsing. This is up to the point it will
work with our mcp server and LivAI and we need to work on the
details with the manager agent

Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
@vsoch vsoch force-pushed the add-manager-agent branch from bed1030 to e6ebc33 Compare February 19, 2026 08:02
We are adding the concept of a step agent, meaning an independent unit
that can run under a state machine step. To support this, the abstraction
of an agent needs to be separate from the state machine. I am also adding
improvements so that the user can validate the plan before proceeding,
and we ensure that all prompts and tool calls are valid before
proceeding.

Signed-off-by: vsoch <vsoch@users.noreply.github.com>
This is not final! TODO:
- the transitions / rules need better validation before approval.
- we should move the result parser into hpc-mcp

Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Instead of trying to pass forward an async context and backend, let
us assume that we will generate the backends once via some manager,
and then import them as needed. Right now we just have one. I have
this working through the results parser and just need to debug that
now - getting closer, but need sleep.

Signed-off-by: vsoch <vsoch@users.noreply.github.com>
I want the validation class to be cleanly separate from
the manager agent. Done!

Signed-off-by: vsoch <vsoch@users.noreply.github.com>
The re-organization of code and classes borked the current transform
retry example. This fixes it.

Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant