dvn

Support

Updated October 14, 2026

Get help

Contact Devin Thomas at Uppercut Labs about dvn access, skill loading, privacy or deletion requests.

What to include

Include the canonical skill identity, generic error code, source revision and client you used. Include a public packet ID when appropriate. Keep tokens, passwords, private packet contents and your full conversation out of support messages.

Public and private access

Public skills require no GitHub sign-in. Private skills require both identity and current repository access. Choosing owner scope in a tool argument cannot repair a private access denial; check the actual GitHub connection and repository access.

Missing context

Stop a stage whose required references cannot be loaded. Report the unresolved stage or reference key. Preserve the active packet for pinned follow-ups; request a refresh when you intend to check current pushed sources.

Contact dvn: devin@uppercut-labs.com