#Automation

1 messages · Page 1 of 1 (latest)

empty forum
#

I need help automating my agents. I have various agents that pass information down the line. My main/chat agent is firing the subagents and passing the data from one to the next but sometimes it gets stalled, forgets, and doesn’t quite go to the next step. Sometimes it’s awesome other times I have to check it using the / commands… thankful of because it will pass the batan. So to speak, to the next agent but I have to hover over it to check it’s working - which is more than checking its work.

novel timberBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

tame jetty
#

What subagents are you talking about? What do they do?

shadow quest
# empty forum I need help automating my agents. I have various agents that pass information do...

yeah "hovering to check it's working" is not automation lol, that's just you being the orchestration layer
the stalling usually comes down to two things — no explicit handoff confirmation between agents, and no way to detect that a baton drop happened after the fact
what helps most is forcing a written checkpoint at every handoff, not just the agent saying "passing to next" but actually committing something to a file so there's a verifiable trail. then you can check the trail instead of watching the agent
the / commands saving you is actually a sign the state exists, it's just not being consulted automatically
what does the handoff between agents look like currently — is the main agent explicitly telling the sub what it's receiving or just spawning it (and hoping ...eek)

empty forum
#

I’m doing all that but it’s not working. I’m trying and maybe this new rewrite of the agents will work.

#

It seems to be doing good tho. Now that it understands the platform and is chugging along… I’m gonna see what it does in an hour lol.

shadow quest