@techtyra2Has anyone solved Claude Artifact authentication inside an embedded website?
I'm experimenting with embedding a published Claude Artifact into an external website. The Artifact displays correctly, but its AI functionality doesn't seem to recognise an existing Claude login session. When I authenticate through the prompted login flow, the Artifact works in a separate browser tab, but the embedded version continues requesting authentication. I've tested this across multiple browsers with similar results.
Has anyone encountered and resolved this?
I'm particularly interested in whether this is a browser authentication limitation, an embedding configuration issue, or a known restriction with AI-powered Claude Artifacts. Would appreciate hearing from anyone who has successfully implemented this or found an officially supported workaround.
Answers2
Even if the embed starts working, asking a small business's website visitors to sign in to Claude before the tool does anything will lose most of them, because people rarely make a new account just to try something on a shop's site. For the small business clients TechTyra builds for, I'd plan on a version where the visitor never has to log in to anything.
That's a fair point, Ryan. I agree that requiring every customer to create a Claude account would introduce too much friction, especially for small business websites. My thinking was to offer two options: a simple AI experience for regular visitors, and an option for existing Claude subscribers to use their own AI allowance rather than having the application provider pay for every interaction. I've since been investigating other approaches, including subscription-based AI authentication and MCP integrations. Still exploring what is technically and commercially practical. Appreciate your perspective!
2 answers
Even if the embed starts working, asking a small business's website visitors to sign in to Claude before the tool does anything will lose most of them, because people rarely make a new account just to try something on a shop's site. For the small business clients TechTyra builds for, I'd plan on a version where the visitor never has to log in to anything.
That's a fair point, Ryan. I agree that requiring every customer to create a Claude account would introduce too much friction, especially for small business websites. My thinking was to offer two options: a simple AI experience for regular visitors, and an option for existing Claude subscribers to use their own AI allowance rather than having the application provider pay for every interaction. I've since been investigating other approaches, including subscription-based AI authentication and MCP integrations. Still exploring what is technically and commercially practical. Appreciate your perspective!