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.
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.
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