What problem does it solve?
PostHog engineers often struggle to get a remote devbox working: the Coder control plane sits behind a private Tailscale tailnet, auth and SSH config require one-time setup, and keeping a local checkout mirrored to the remote stack is error-prone. This Skill walks an engineer (or an agent) through the entire lifecycle using the supported hogli devbox:* commands.
Core Features & Use Cases
- Diagnosis-first troubleshooting: Uses
hogli devbox:doctor to identify tailnet misconfiguration (wrong tailnet, missing ACL grant, MagicDNS off) before touching anything else.
- Full lifecycle management: Covers
devbox:setup, devbox:start, devbox:ssh, devbox:exec, devbox:stop, and secret management for gh and Claude Code tokens via Coder user secrets.
- Local-to-remote sync: Explains one-way mutagen mirroring with
devbox:sync so you edit locally while the full PostHog stack runs on the box, including conflict behavior on feature branches.
- Use Case: An engineer on a new laptop runs
devbox:doctor, discovers they are signed into the dev tailnet instead of posthog.com, switches tailnets, completes setup, starts a box, and mirrors their feature branch for remote testing.
Quick Start
Ask the assistant to check my devbox status with hogli devbox:doctor and help me start and connect to my PostHog devbox.