Thanks for sharing. I see the potential upside of using Spool, especially the adding info during loop aspect
I once had a case where I asked Claude Code, and it spawned around 70 fable agents, which consumed all my usage immediately
Can one pick a limit on subagents, or see usage across loops?
Been using it for the last couple of days via isolated Docker containers + Slack, loved it so far. For me, the best part is the isolated Docker containers + only handpicked secrets that I gave to loops, so that I can be more assured they won't freely roam through my dangerous credentials + MCP in my local workspace
Really glad you're enjoying it! Yeah, isolating loops from the local workspace, secrets, and MCPs was one of the things that needed to be done right from the beginning. It probably added a bit of complexity, but giving autonomous loops unrestricted access to everything just didn't feel right.
That’s actually an interesting idea. So far, I designed to use a single subscription since that was the case for me. But, just like you, teams might also want to have loops running on multiple subscriptions and collaborating. Let me think what the simplest could be to do this without making the onboarding too complicated. If you could spare time, that would be also great if you could file an issue on this to get spool’s own loops involved.
Thanks for sharing. I see the potential upside of using Spool, especially the adding info during loop aspect I once had a case where I asked Claude Code, and it spawned around 70 fable agents, which consumed all my usage immediately Can one pick a limit on subagents, or see usage across loops?
[dead]
Been using it for the last couple of days via isolated Docker containers + Slack, loved it so far. For me, the best part is the isolated Docker containers + only handpicked secrets that I gave to loops, so that I can be more assured they won't freely roam through my dangerous credentials + MCP in my local workspace
Really glad you're enjoying it! Yeah, isolating loops from the local workspace, secrets, and MCPs was one of the things that needed to be done right from the beginning. It probably added a bit of complexity, but giving autonomous loops unrestricted access to everything just didn't feel right.
I built Spool because I wanted persistent Claude Code loops I could talk to, without keeping track of separate terminal sessions.
It makes it easier to create and manage loops, and lets them communicate with you and each other.
I'd love to hear whether you'd find this useful.
Very interesting- will check it out
how does it work from a cost management perspective
Ie one subscription to each project - can we have spools of different claude subscriptions working together-
Trying to contain my dev costs and prevent claude orchestrated agent to subagent api overruns
That’s actually an interesting idea. So far, I designed to use a single subscription since that was the case for me. But, just like you, teams might also want to have loops running on multiple subscriptions and collaborating. Let me think what the simplest could be to do this without making the onboarding too complicated. If you could spare time, that would be also great if you could file an issue on this to get spool’s own loops involved.
On a side note, github is finally showing start count on mobile, took them just a few years!
Yeah I noticed too. What an insane omission to have for so long.