Public beta terms
Use Veil with repositories
you are authorized to change.
Veil v0.3.0 is experimental developer software. Review its output, request context, and security boundaries before allowing it to handle sensitive work.
Consent and your responsibility
You must accept the versioned Terms and Privacy Policy before an organization is created. You must have the right to access the repository, provide relevant material to local tools or model providers, invite organization members, dispatch work, and publish to the chosen destination. Veil does not grant or bypass GitHub permissions.
Public-beta availability
The beta is free, best-effort, and has no service-level agreement. It is limited to 50 organizations. Per organization, the limits are 5 members, 3 paired devices, 1 running job, 20 dispatches per UTC day, and 1–30 days of event retention. Features, limits, compatibility, and availability may change or pause before a general release.
Local approval and publication
A hosted dispatch is only a request. It expires after ten minutes and requires approval in the paired foreground terminal before local work starts. Code written by a person, Connector, or harness is never publication approval. Patch and draft-PR publication remain local and require separate explicit confirmation; an unchecked draft PR requires an additional confirmation.
Supported public beta
The supported local path on macOS or Linux is a public GitHub URL or a clean, already-authenticated local GitHub checkout, including a private repository. Local import copies tracked regular files without Git metadata or repository credentials. Configured recipes use the current OS sandbox; repositories without a recipe are labeled unchecked. Windows, hosted private-repository import, hosted execution, production hostile-code containment, and a production GitHub App publication path are not supported claims.
Organization administration
Owners are responsible for invitations, roles, removals, devices, retention, and deletion. Invitations default to reviewer access and expire after seven days. Organization deletion immediately suspends access and schedules permanent hosted-data purge after seven days. Veil may reject actions that exceed quotas or would remove or demote the last owner.
Support
Email useveil.dev@gmail.com for best-effort beta support. No response time, uptime, recovery, compatibility, or data-restoration guarantee is offered.