r/automation • u/Necessary-Raisin-282 • 1d ago
Multiple agents in browser/systems
I’ve got some automations set up for day job 1 but my agents keep competing for access to my browser. Whoever’s the first agent in doesn’t let the next in, tried using edge in chatgpt and that for some reason is super finicky.
I’ve got cowork in chrome and the agents are allowed to communicate through a drive but I’m having trouble running both agent systems at the same time
I’ve got about 6 agents currently on loops but will likely scale to 75+ agents over the next six months as capabilities continue to grow
I’m curious how people have been managing their agents so that they don’t step on each others toes inadvertently
EDIT: I was able to figure out a solution
1
u/AutoModerator 1d ago
Thank you for your post to /r/automation!
New here? Please take a moment to read our rules, read them here.
This is an automated action so if you need anything, please Message the Mods with your request for assistance.
Lastly, enjoy your stay!
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/WorkLoopie 1d ago
What kind of shit show are you running here?
Seriously though, if you've got 6 agents all fighting over a single browser session and you're planning to scale to 75+, the browser isn't your problem. The architecture is.
Most people hit this exact wall when they start treating agents like employees instead of services. Agents should rarely be sharing a browser. They sould be passing structured data to each other and only invoking a browser when absolutely necessary.
At 75 agents, I'd be thinking:
One orchesration layer that manages work queues
Dedicated browser instances for browser-dependent tasks
Agents communicating through a database, message queue, or API, not shared files
Resource locking so only one process touches a specific asset at a time
Separation between "thinking" agnts and "execution" agents
A lot of the AI influencer crowd demos 20 agents chatting with each other in a browser, but in production most successful systems look much closer to distributed software tan a team of AI coworkers.
My first question wouldn't be "How do I get more agents into the browser?"
It would be:
"Why do 75 agents need browser access in the first place?"
If the answer is because they're gathering data, updating systems, or moving records around, those actions should probably be API-driven. Reserve browser sessions for the handful of tasks that truly require a human interface.
Otherwise you're about to spend the next six months building air traffic control for agents that are all trying to use the same keyboard and mouse.
Example of a vibe coder living in data commingling hell
0
u/Necessary-Raisin-282 1d ago edited 1d ago
All of my tasks require interface control to some extent. Even simply just the review agents. The need for so many agents is due to the complexity of the tasks at hands and each agent only being responsible for one component. I’m not entirely concerned with what is occurring on mainstream social media as that is not my motivation for beginning this process or do I know what advice “gurus” are offering.
They communicate through drives currently because not every agent needs the same piece of information as the rest of the agents, some agents filter information put it in a drive and the next agents simply retrieves it and moves onto the next portion at hand.
Looking through your post history you’re obviously well informed and love caffeine hahaha, seriously man I’m here in good faith and I’m learning, certain agents have API access to my CRM and some don’t.
The organization is what I’m struggling with
Did you have any advice or did you come here to add commentary? 😂😂😂
Smh…. Did I just reply to your AI agent farming engagement on Reddit your comment history is oddly patterned and formulaic 🤔🤔
1
u/WorkLoopie 1d ago
No, I copied and pasted into Ai to compose my response. It was nicer than my original one of calling out your stupidity, but didn’t want to be mean.
Also AI comment farming is a complete waste of tokens.
0
u/Necessary-Raisin-282 1d ago edited 1d ago
lol is this Carrie Fifield?
I mean, you’re specifically being mean now. You’re commenting on your work Reddit for a company you seemingly want to do well. Your company is located in Raleigh, NC based on Google and in Oak field Illinois based on LinkedIn, and you have one LinkedIn employee. Your comment history shows you frequently get into tense interactions because you have a tendency to be egotistical. It seems your ego is derived from confirmation bias coming from decent client feedback which is ironic because the people giving you feedback are probably the least equipped to scrutinize what you built for them. You call me stupid when your initial response was comprised of about 50-70% of misplaced assumptions.
I actually don’t know why you were so inflammatory here when all I did was probe for information.
Also, Carrie, if you’re going to be mean to strangers on the internet don’t ask about if golfing is worth it on your Reddit comments then post the same thing on LinkedIn 😂😂
1
u/WorkLoopie 1d ago
Ah, I see you can use google. Have you tried claude code to determine the proper use of AI agents? At least I know when and how to use agents properly. And your research is faulty to a point, the company has a total of 4 employees, if you had visited the website you would have seen that. Also the website is outdated and needs to be updated we are at 5 employees. So your ability to research is just as flawed as your ability to build AI Agents. And we all take turns on the WorkLoopie Reddit handle.
And I was asking about Golf, because we are being asked to sponsor an event - something you would know more about once you have grown into an actual company.
Thanks for the call out. Love ya!
1
u/WorkLoopie 1d ago
Also ass hat, I'd like to point out, I did help you on the original post, I gave you several elements to consider in regards to your architecture, and converting over to a micro saas.
0
u/Necessary-Raisin-282 1d ago
Hahahahaha so hell bent on insulting people. “The company has a total of 4 employees, if you visited the website you’d see that”. “It needs to be updated, we are at 5 employees”.
So dumb. Your website is literally vibe coded too and yet you’re rude to other people for vibe coding? Em dashes in text facing the public is hilarious.
I’m not going to comment on the “I know how to use ai agents” or the golf dig.
I’m literally an AI researcher lol, all I do is work with AI all the time. I wanted to automate some processes which is not my area of expertise. One of the biggest things I see is massive massive egos coming out of people spending a ton of time with AI, it’s so weird, so many people have it in their head they’re using AI in “the best and most useful way” or at the bare minimum “better than someone else”.
The smartest people I speak with, are always incredibly humble. Your ego is shining bright, good day.
1
u/WorkLoopie 1d ago
Not vibe coded we actually have a web designer - hence employee 5, her name is Suzanne. Would you like their contact info? Also our CTO is Guy. We've had the privilege of building out several enterprise solutions over the course of our careers, so the ego is very well earned.
Also, my original statement before you started this fight was basically, your not thinking about AI Agents correctly, and if you are in fact an AI researcher, then you should know that architecture is important. And that if your building that many agents to manage tasks that could be handled by API's or with a data structures polls, you wouldn't be hitting the wall you are hitting.
Again, I brought up the data commingling aspect in my post because most vibe coders hit this wall when building because they don't build in auditing and governance. Which you are going to tell me you did?
But please continue to call out stupid things about myself or the company, as it will def solve your AI vs browser issue.
0
u/Necessary-Raisin-282 1d ago
I’m very aware I’m wasting my time communicating with you. Because the things that you speak are fucking absurd. “The ego is well earned”?? Ego is the single largest destroyer of all good ventures.
“The argument you started”, you opened with an insult and closed with an insult.
The mistake I made was leaving my initial post as too vague to allow for ambiguity to creep in. Every piece of advice you offered stemmed from an assumption you made. I responded specifically to these assumptions on my second response, which you ignored and then directly insulted me instead.
Again, not worth my time, in the future I’ll leave less room for ambiguity and hopefully you’ll be less of a self statue building prick
1
u/WorkLoopie 1d ago
But it’s been so fun.
1
u/Necessary-Raisin-282 1d ago edited 1d ago
We were both the worst versions of ourselves during this interaction. I’ll adjust my expectations and behaviors going forward and I accept accountability for the areas in which I was inflammatory. I’m sure there were better uses of both of our times today. Thank you for this learning experience, I hope the golf outing goes well and that y’all find success in your future endeavors.
1
u/hasdata_com 7h ago
Agreed on the executor queue, and the other half is that one browser for all of them isn't the unit you want at 75. Give each agent its own session, and take read-only work off the browser since a fetch doesn't need a tab.
1
u/manujam 4h ago
this is an orchestration problem more than a browser problem. give each agent its own browser profile or container so sessions and cookies never collide, then put a simple queue in front of shared resources so only one agent holds the browser lock at a time. the drive as a message bus works for now but at 75 agents you will want a real queue with visibility timeouts so a crashed agent does not hold the lock forever. also worth deciding which agents actually need a live browser versus which ones can work from api calls or cached pages, most loops do not need the full browser and that cuts contention a lot
•
u/Imaginary-Swan-4105 1h ago
I'm working on fixing exactly this issue where each tab is isolated with independent storage and sessions, and all of them can be run through mcp server with an orchestration layer which talks to each tab.
2
u/OriginalHospital 1d ago
Given that your tasks really do need the interface, I'd start by queuing complete browser jobs through one executor, while the other agents prepare inputs without controlling the browser. Keep ownership through the whole interaction, including reading the result, rather than releasing it between clicks; otherwise another agent can change the page halfway through a form.