Security
Who can do what, which tokens exist, and where secrets live.
Identities
- People sign in to the studio with a password or passkeys. Sign-up is closed after setup except through invitation links.
- Agents act as the GitHub App with short-lived tokens limited to one repository and their station's permissions. They can't merge, approve, or change settings.
- The coordinator acts as the GitHub App with its own token to comment, label, and merge after approval.
- The worker authenticates to the coordinator with a worker token; results count only from the job's current lease holder.
Secrets
- Credentials are stored in the deployment's environment or encrypted at rest, never shown again after saving.
- Job tokens are written to a file only the worker's user can read, outside the worktree, and removed after the job.
- The coordinator's internal APIs need service tokens; only webhooks (signed) and the worker API are public.
Known risks
Open risks and their planned fixes are tracked as issues labeled risk.