Sponsored
vercat PokerGod Token Reset 3 Things Today DotDial
$5/week ↗
My Dot built a 3D model of my Club Penguin outfit from a screenshot, image 1 of 1
Building ideas

My Dot built a 3D model of my Club Penguin outfit from a screenshot

@sriramkiron

posted

I had my dot create a 3D model of my Club Penguin outfit! Gave it a screenshot of my penguin and told it to do research on every item being worn. Really impressed with the result!

First-hand report from @sriramkiron: his Dot researched every item on his Club Penguin penguin from a screenshot and created a 3D model of the outfit. Attached photo shows the result. Author handle: sriramkiron (X).

View on X

More Dots use cases in Building ideas

See all 40 →
Building ideas

Dot flags a five-figure revenue opportunity and preps a mobile app for launch

OpenAI's new always-on agent, dots, is here! Here's my new video showing you how it works and how it compares to Grok Bot and Muse. I've been testing it for a few days and it: → Flagged a five-figure revenue opportunity → Got my mobile app ready for launch → Made some great memes in Slack dots' biggest advantage is that it's natively integrated into ChatGPT, but that also comes with some trade-offs. 📌 Watch now: https://youtu.be/z5X1eMU6isI
Peter Yang

14.7K views on X

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

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

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