I tried using Claude Code this week because I have a free account from my work.

However when I try to log in via CLI it takes me to a webpage with an “Authorize” button. Clicking the button does nothing. An error is logged to the console but nothing displays in the UI.

We reached out to support who have not helped.

Not a great first impression

Sadly their whole frontend seems to be built without QC and mostly blindly assuming a happy path.

For the claude.ai UI, I've never had a single deep research properly transition (and I've done probably 50 or so) to its finished state. I just know to refresh the page after ~10mins to make the report show up.

It's had enormous problems in Firefox. For me it would reliably hang the entire tab.

https://github.com/anthropics/claude-code/issues/14222

Claude likely built their front end.

Do you have API access (platform.claude.com) rather than Claude code (claude.ai)? I had similar issues trying to get Claude CLI working via the second method, not knowing there’s a difference

I think I have API access.

But it’s confusing.

The docs say run “Claude” and then pick your option.

I tried multiple options and neither worked

Yes, several times. I've been specializing in front-end dev for over a decade.

I shared a simple example because Shadcn has a simple design.

You do often hide the native appearance if you need something complex, but doing that via CSS is still much simpler than a bunch of JS and a third party dependency.

If you have a specific design in mind I can show you how to do it.

It needs JS to be interactive unlike the native radio button

Author here. I've implemented all of these with the native radio button and CSS:

> Pixel perfect styling, animations, focus behaviors, interactions with external state, componentized branding to fit in with companies' ecosystems, etc.

Do you have a more specific example of something you've struggled with recently?

Reading through the threads that sounds like a React bug not a browser bug

Author here.

Thanks for sharing the PR. Frankly that raises more questions for me. Why do they want to wrap a label in a label? What is the actual goal here?

Author here: I tried to find answers in their docs but they don't provide any context. I expected to find an explanation of why to use their solution there but did not.

How would you suggest I reach out?

Author here.

You can do pretty much any styling!

I did a basic example because that matches what Shadcn does (black/white circle) but you can customize it a lot more.

> This is why there's so much complexity in libraries like Radix - accessibility in the real world usually requires a lot of Javascript.

I agree in many scenarios, but for the two you mentioned it seems like the <dialog> and <details> elements provide accessible solutions out of the box?

They do, most issues that arise from making things accessible are self inflicted. Some people just want to redesign things for the sake of design while ignoring a core principle of design (accessibility) over aesthetics.

Sounds harsh but maybe somethings SHOULDN'T be designed a certain way because it breaks a11y when there are other roads to be taken that can still look pleasant, be accessible, and way easier to maintain (less brittle JS to worry about).

Author here. Can you provide a screenshot or more detail?

I'd be happy to implement an HTML + CSS only solution and share it with you.

Thanks