His Dot caught an onboarding bug and drafted the fix PR unprompted

@chris.raroque

added Oct 8, 2026

My full app launch checklist 👇 1. Set up analytics. I use PostHog to track signups, onboarding, and the main thing people came to do. Test those events so you can see where people get stuck and whether they come back. 2. Set up crash reporting. I use Sentry to see what went wrong. Send a test error before launch so you know reports are coming through. 3. Build your welcome email sequence. I use Loops. Help people take their first step, then follow up with something useful. Test the signup trigger, timing, and links. 4. Give people a place to leave feedback. Make the board easy to find inside the app so people can report bugs, ask for features, and vote on requests. Setting all this up is important, but I think proactively watching it is the most important part, especially during the first 2–3 weeks. That’s when crashes, drop-off, and feedback help shape product decisions. What should you fix first? What’s confusing people? What do they want you to build? I used to have to watch all of this so closely myself. Now I’m giving that responsibility to dots, OpenAI’s remarkably capable, always-on agents powered by GPT-6 Astra. I’m sharing my launch date, checklist, and what a successful signup looks like, with access to the tools it needs. It can work with Codex and keep making progress between conversations. Here’s what I’d ask: “Watch my analytics, crash reports, welcome emails, and feedback board for the first three weeks after launch. Check daily, flag urgent issues, and bring me a weekly summary of what to fix or improve, with the evidence behind each suggestion. If the launch date or priorities change, update the plan. Ask me before changing code or sending emails.” You choose what it can access, review its findings, and can redirect or stop the work. I’ll leave a link to dots in my bio so you can try this for your next launch. @ChatGPT #chatgpt_partner

Chris Raroque (solo app dev, 48K Instagram followers) handed his Dot responsibility for watching PostHog analytics, Sentry crash reports, Loops welcome emails, and his UserJot feedback board daily for the first 3 weeks after an app launch. The reel's demo shows the Dot detecting a strange drop-off in onboarding analytics, investigating server logs and the codebase, finding a bug that rendered an onboarding step blank, reproducing it, and preparing a draft pull request titled "Handle empty server responses" — all before being asked. Disclosure: the post carries the tag #chatgpt_partner.