Operations
Security and privacy
Understand credential, source, network, and workload boundaries.
Hosted control plane
The hosted app stores repository configuration, workspace membership, runner token hashes, jobs, events, provider catalog metadata, status, and verified outcome evidence. GitHub OAuth is the hosted integration used for repository and Project coordination.
Local execution boundary
Source checkouts, provider keys, provider OAuth roots, Docker, kind, persistent workspaces, and agent workloads remain in the runner environment. The runner makes an outbound connection and does not expose an inbound local service.
Per-job isolation
Each job receives only what its role needs. Ordinary repository agents receive scoped GitHub access and an authenticated inference-proxy token. Provider roots stay in the trusted sidecar.
Issue Planner is stricter: a trusted init container refreshes the checkout, then the model receives a read-only mount with no GitHub credential or GitHub tool.
Frequently asked questions
Are provider keys stored in Supabase or Vercel?
No. Provider credentials remain in the local runner environment.
Is source code uploaded to the hosted app?
No hosted source checkout is created. Repository workspaces remain local to the runner.
Do custom images receive credentials?
Ordinary agent containers receive scoped GitHub access and a per-job inference-proxy token, so use only images you trust. They do not receive provider root credentials.
Can Issue Planner mutate GitHub during the interview?
No. It receives no GitHub credential or mutation tool while planning.