Provider credentials

Coding assistants (Claude Code, Codex, Cursor, Muse) need a login to call their provider. AgentWorks holds these logins encrypted on the server and hands one to each launch that needs it.

Two ways to set them up

	Shared login	Your own login
Added by	An admin, for the team	You, yourself (unless your admin locked it)
Used by	Anyone it's available to	You
Good for	A team plan everyone shares	Personal quotas, identity, billing

Either kind reaches a launch the same way.

Encrypted storeAll logins, sealed. No agent process can read it.

→

One launchThe server resolves the single login this run needs.

→

HandoffLogin file linked + granted, or key placed in that launch's environment only.

Login files that rotate (OAuth-style) are shared live, so refreshed tokens keep working. API keys travel inside the launch's own environment — children never inherit the server's. Bridge tokens and per-launch files live in per-person folders, so one person's launch never leaves credentials where another can read them.

What each person sees

Server

Holds every login, sealed.
Hands one per launch.
Never exposes the store to any person.

Alice's launch

✓ The login her run was given
✓ Her own files
✗ Bob's launches and files
✗ Any login she wasn't given

Bob's launch

✓ The login his run was given
✓ His own files
✗ Alice's launches and files
✗ Any login he wasn't given

Isolation hides people from each other — not a login from the person using it. Alice's run holds the shared login while it works, because her assistant needs it to call the provider. Shared logins usually rotate, so a copied one decays; anything that must never be copyable should be a private login, not a shared one.

Rotate it at the provider and update the stored account: new launches pick up the new value, and in-flight runs keep only the old one until they end.