Clay CLI for Multiple Concurrent Clay Instances
Excerpt from my LinkedIn post:
When you run an agency you often have multiple customers at the same time, and you're often working multiple builds concurrently. So, one of the challenges we had to overcome was how to use the CLI safely in isolated client Clay instances.
A Claude Code task on Client A should only see and work on Client A's Clay instance, and a Claude Code task on Client B should only see and work on Client B's Clay instance.
It was a bit to figure out, so we built a skill and a guide in case anyone else finds it useful. It should work on any harness.
share.tryaware.ai/clay-workspace-isolation