Wednesday. A freelancer or studio with client projects.
Every client on their own terms.
Three clients, three sets of expectations, and one of them wants nothing posted to their Slack without a look first.
Without a fence between them
Mix up an account or a channel once, and it's a conversation you don't want to have. So the agents stay on your own side projects, and the client work waits for you.
Wire it up once.
One behaviour at a time, each in the real dashboard.
-
Each client on their own account.
A client's API key or cloud account runs that client's work, with its own limits and spend. Your own subscription stays yours.
How it works: each project maps to an account in Settings, and its agents only ever start there.
- Client onekeytheir API key, their limits and spend
- Client twocloudtheir cloud account
- Your own projectssubyour own subscription
-
Each client at their own rule.
Pull requests for one, draft PRs only for another, and plan and warn for the careful one: findings are held for you and nothing is posted.
How it works: Overhand reads a project's rule before it starts any agent there.
Client oneClient twoThe careful one -
Proof before anything reaches a client.
Every pull request shows the tests it ran and the shortcuts worth a look, with a preview to click. Updates go only to the channel you set on that project.
How it works: outward updates go only to the channel set on that project; a leak check on what agents post is coming.
Your morning, by client
Work per client, on the client's account.
Each client's pull requests, on the account they pay for, at the rule they agreed to. Nothing posted anywhere you didn't set up.
- 1account per client, with its own spend
- 0posts outside the channels you set
- Soona per-client work report for the invoice