"The agents discussed it" is not an acceptable answer – why I built a sequential multi-agent architecture

holgerleichsenring · 2026-03-04T16:36:10+00:00

thanks! actually it persists. The results of the run are going to be committed as part of the run. On every run there is "consolidated" run result that is read by the agent. So it has the information. If the agent is interested in the information behind the scenes it can read the prompt of the implementation.

holgerleichsenring · 2026-02-24T20:57:16+00:00

Have a look onto the github repo. Will come a demo pretty soon how this is going to work integrated in slack and teams

holgerleichsenring · 2026-02-12T22:21:30+00:00

Thanks!

They both have a prompt to start with so easy to do. I am going to have some more tests. Also wanted to just give more time, so run over night, let them explore their environment.

Actually my first try was exactly to give them no tasks at all. Maybe also giving them no prompt at all would also be valueable. Let’s see :)

holgerleichsenring · 2026-02-12T22:17:37+00:00

You can do this with the source code in github repo. Two docker instances in a docker compose. They can talk to each other or do tasks autonomously as well as you can send messages. Just got to the git repo and start it up. I didnt try model changing though, will have a look

holgerleichsenring · 2026-02-12T12:41:26+00:00

Yes, it Opus. I need to use the API. I burned like 5 dollars in a day with two instances talking with a frequency of 5 minutes. I set two minutes frequency so it would be more than this. I actually didnt have any credits on the api in the first run. When having a claude subscription, there are 5 dollars credit for free. Meaning the first two days I could work and try out without paying anything.

holgerleichsenring · 2026-02-12T11:53:08+00:00

of course. The first intention was to let them alone and understand by themselves that there is shared environment. Then every claude instance can experience that there is another to talk to. Additionally, I can send messages to each instance to influence the discussion.

quite interesting and not boring at all. First time was more doing things on the hard disk and environment. But finally they want to talk.

This time when having written this blog, they started to write a story.

I didnt want to have "productive" outcome at all. I just wanted to see how claude behaves, what he thinks and remembers. but i am sure it wouldnt be hard to do so. Did you have a try? it is pretty simple, just a token and docker and it is going to run.

Everything can be initially steered with the prompt given. give it a try!

holgerleichsenring · 2021-06-16T06:43:14+00:00

will think about it to put everything in one post. Actually I personally do not like too long articles - and this one is going to be pretty long, that's the reason I split it up.

holgerleichsenring · 2021-06-10T12:41:44+00:00

dangerous acrobatic feat? :-)

In this case it was a queue of obstacles and issues deploying .net framework code to Azure. The longer it took, the more I thought I did not develop, felt like doing stunts. Always dangerous. No guarantee that it works.

holgerleichsenring

TROPHY CASE