OpenCode Handoff (P2P-only)

P2P-only variant: each user owns one private GitHub inbox repo. Senders push directly into it (requires collaborator access). No shared central repo, no fallback mode — simplest possible attack surface.

Need a shared central repo for team-scale (5+ people)? Use the combined opencode-handoff instead.

Recommended hardening checklist (do this once before first use)

1. Make your inbox repo private (skill creates it private by default). All share URLs end up in git history; a public repo leaks every transcript.
2. Set your git commit email to the GitHub no-reply form: <numeric-id>+<username>@users.noreply.github.com.
3. Enable GPG-signed commits and require signatures via require_signed_commits: true in trust.json.
4. Use fine-grained PAT scoped only to your inbox repo and any inboxes you've been invited to.
5. Consider a hardware GPG key (YubiKey 5, NitroKey, etc.) — defeats sender impersonation even if the local machine is fully compromised.

File format

• Filename: <ISO-8601 UTC timestamp>--from-<sender-github-username>.txt
• Content: a single line containing exactly one share URL, plus trailing newline.