Guides
Working with more than one account
Connect Claude Code to several Awesomate accounts, say which one a folder or a session uses, and check which one Claude is working on.
If you look after more than one Awesomate account (your own and your clients', say), connect each one the same way, from that account's hub page (Quickstart). Each becomes a profile in your key file, ~/.awesomate/credentials.json.
Which account a session uses
Claude picks the account in this order, and awesomate_whoami tells you which one it picked and why:
AWESOMATE_ACCOUNTset to an account's name for this session;- a
.awesomate.jsonfile in the folder you're working in (or a folder above it) naming the account; - the only account, when you've connected just one;
- your default account.
To tie a project folder to one account, put this in it as .awesomate.json:
{ "account": "brightwater" }Naming an account that isn't connected is an error, never a quiet fall back to another account. (A key set directly in AWESOMATE_PAT overrides all of these. It's meant for automated jobs, not for everyday use.)
Check before you change anything
Every answer from an Awesomate tool says which account it acted on. Start each session with:
Which Awesomate account are you connected to?
If it's the wrong one, fix it before asking for anything else.
Whose key it is, and what it may do
A Claude Code key is either the account owner's, and whatever Claude does with it is done as the owner, or a team member's own. A team member connects their own Claude Code once the owner turns it on for them on People; their key does only what they can do in the hub, never more, and never has a shell on the hosting account. awesomate_get_context says whose key it is at the start of a session.
A key carries the permissions your plan gives it. When a request needs one the key doesn't have (installing a template on a plan without it, for example), Claude says so straight away, in the same words the hub would use, instead of trying and being turned away.