[jelveh]

Why

When a user asked the AI to put their site on their own domain, the AI could only tell them to open the Publish menu. The chat's Publish card handled only .puter.site addresses, and an address like joes.com passed to OfferPublish became joes-com.puter.site.

The AI can't open Puter's domain window itself: puter.hosting.attach() opens a popup, and browsers only allow that straight from a user's click. A button on a chat card counts as that click, the same way the Publish card does.

What

A new OfferCustomDomain tool (src/tools/chat_ui/domain.js) puts the Publish card in the chat in a new domain mode. The card's button calls the popover's existing useOwnDomain, so the plan check, name reservation, Puter's window, domain records and status checks are all shared.

State	Card shows
Not published yet (paid)	Address field + Publish with your domain. Reserves the name, opens Puter's window, publishes behind it
Live, no domain	Site link + Use custom domain
Live, domain connected	Domain link + Change domain (or Connect again if the address changed), with a line while it waits for DNS / fails / stops working
Free plan	Use custom domain, which opens the upgrade dialog; the card switches once the plan changes
Signed out	No card; the AI tells them to sign in

Changes outside the new tool:

• ui.js: publishWithDomain / useOwnDomain take an optional via from the card (its typed name, fail, publish, onDomain). Without via, the popover behaves as before. connectCustomDomain takes onDomain. Domain and plan changes also redraw chat cards.
• publish.js:
  • Adds the domain view.
  • publishFromCard can publish onto a reserved name.
  • The chosen domain is saved on the card's tool result, and an older card reads "Domain added" after a reload.
  • A publish that lands after the domain was chosen doesn't overwrite that record.
• Prompt: own-domain requests go to OfferCustomDomain. Older chats whose prompt still sends users to the Publish menu get a note (DOMAIN_TOOL_NOTE). OfferPublish's description points to the new tool too.
• Connecting a domain from a live card isn't held up by a running turn, since it publishes nothing, matching the popover. It does wait during an address change.

Testing

• npm test and npm run build pass.
• test-custom-domain.mjs runs the real ui.js domain code with the card's via:
  • Puter's window opens in the click.
  • The card's name, rather than the popover's, is reserved.
  • The card runs the publish.
  • Errors go to the card, including after switching projects.
  • A build in progress blocks it; the free plan opens the upgrade.
• test-publish-card.mjs runs the real card and tool: every state above, the busy labels, saved records, the frozen "Domain added" card, reloads and wiring.
• Not tested in a live browser against Puter's real domain window, since that needs a paid account.

[reynaldichernando]

Preview of this branch at 631e9fe

• Website at https://builder-chat-custom-domain-ljmo.puter.site/
• Puter app at https://puter.com/app/builder-chat-custom-domain-ljmo

The preview is its own app, so it starts with no projects. Your builder.puter.com projects won't show up there.

[reynaldichernando]

[reynaldichernando]

[reynaldichernando]

for the manual "Use custom domain" button, we automatically picked the .puter.site subdomain for the user to avoid having them do double work (typing the name of puter site subdomain and typing their domain name)

i think this should just be a button that opens the dns flow, and we just automatically pick the puter.site subdomain for them

in any case, this is working as expected right now