Well laziness could explain it (Occam's nap?) but it's also possible they added a bit of friction to get a cleaner signal of intent, so they can see who the most motivated prospective users are.

They are busy merging 30,000 PRs a day, who has time for UX?

I suspect such basic UX & integration misses is parallel to the general trend of customers somehow getting narrower services, a move away from supporting power users, and toward companies functioning more like fiefdoms where customers are subjects to be farmed.

Claude Code filled in the form for me.

Deploy gate in the app is surely more sophisticated than needed for a waitlist. And it's probably managed by a separate team and that separation makes sense.

Drives me nuts that it's such a manual process to link my ChatGPT/Codex machines individually to each other and my Dot can only seem to connect with the chats on one linked machine at a time (before even getting to control or how completely useless the cloud VPS for the Dot is).

I had a Pro 200 plan build my entire desktop environment from near scratch in C+Vulkan this last month and they can't even bother to have the bots let their Linux Electron app connect remotely to the same Electron app on Windows in the same way that already happens in reverse?

> I tried asking Claude fron the android app if it could sign me up for the waitlist and it said that it couldn't.

I assume this is because it would require account editing tools available to Claude. And it opens the possibility perhaps of user tricking the llm into doing something inappropriate with the account. Seems like if properly designed that should not be possible however ..

If only someone had invented a way to easily make great websites automatically? Ah well, I guess that’s just a pipe dream.

It's crazy how bad Dot has been with stuff like this. You'd think it would be able to (and need to be able to) edit a lot of environment settings, tunnels, plugins, etc., but I keep running into issues. For example, I wanted to make a Codex plugin to give it the ability to steer Codex agents running within my own infrastructure, tunneling in via Tailscale. Ended up just giving up and going with a different approach. Because, for example, every time I'd add a new tool to the plugin, I'd have to manually restart Dot (something that wasn't even obvious that it was possible until you fumble around menu dropdowns) and wait because it can't just refresh tools.

Everything I'm describing is more power user stuff than its most basic use cases ("Do this thing for me with your browser") but all the roadblocks I've run into involve one part of OpenAI's product not being able to talk to the other. I'd imagine Claude Duet is the same.

why would they implement a dedicated tool call in their harness to do this they have better things to be worrying about rather then that 1% of users that would want to put their name down for duet in a chat session