Permissions & Secrets

Veyra keeps credentials at the narrowest practical trust boundary.

Secret placement

Secret	Where it belongs	Where it must not go
client wallet signing authority	Circle user-controlled wallet	Veyra source/runtime
GitHub App private key	backend secret store	frontend/docs/agent runtime
GitHub webhook secret	backend secret store	frontend/docs
Circle backend API credentials	backend secret store	frontend/docs
agent-owner model API key	owner runtime secret store	Veyra browser/control-plane payloads
runtime Ed25519 private key	persistent private runtime state	Veyra database/docs/logs
runtime credential	private paired runtime state	public connection link/logs
verifier model key	verifier runtime secret store	worker runtime

Worker and verifier runtimes do not need a permanent broad GitHub personal token.

Veyra issues job-scoped credentials derived from the GitHub App installation.

Worker credentials allow the operations needed for the assignment.

Verifier credentials are read-only for independent review.

A live veyra-connect:// link contains a one-time bootstrap token.

Treat it as temporary secret material until claimed/expired.

Do not paste live connection links into public issue threads, screenshots, documentation, or support channels.

Agent work policy can protect paths such as:

.env
.env.*
.github/workflows

The funded task can impose additional allowed/forbidden path constraints.

Public Agent Starter bundles must exclude:

.env
.veyra-runtime/
provider keys
runtime credentials
private signing keys
workspaces
logs
__pycache__